Replies: 9 comments 5 replies
-
Related to changes in #122 |
Beta Was this translation helpful? Give feedback.
-
Did you rebuild the apple2driver after pulling the latest from upstream? It sounds like it's still using the old code. You can verify this by |
Beta Was this translation helpful? Give feedback.
-
I thought I had but I did get 0027 back so I must have missed that. I went through the update steps in #65 & am now seeing 0028. But I'm not seeing new files show up in I also noticed that after you symlinked the |
Beta Was this translation helpful? Give feedback.
-
The .bas files are symlinked into the the driveimage directory... Not sure why you are seeing them in apple2driver... https://github.com/tjboldt/Apple2-IO-RPi/tree/main/RaspberryPi/driveimage Also, while not automatically polling yet, you can manually trigger a drive regen from the Apple II...
|
Beta Was this translation helpful? Give feedback.
-
Because it no longer uses the current working directory to generate, the code that set the initial working directory to |
Beta Was this translation helpful? Give feedback.
-
I've noticed something else that I think crept in recently. It seems the issue where it's impossible to do anything after exiting from Resetting the Apple2 gets things back to working again. |
Beta Was this translation helpful? Give feedback.
-
This is definitely a bug. I doesn't happen every time but it is reproducible. It is different than bug #57 which would completely hang the RPi code. At least now a reboot of the Apple II fixes it due to commit #58. Would you care to open a new bug? If not, I can open one later. |
Beta Was this translation helpful? Give feedback.
-
I can open one later or tomorrow but I'd be happy to. I'm hoping I can spend some time tomorrow troubleshooting it myself too.
|
Beta Was this translation helpful? Give feedback.
-
Opened bug issue: #130 |
Beta Was this translation helpful? Give feedback.
-
The live update seems to require changing out of the directory for the live image & then changing back into it for the refresh/update to happen. Is this correct? If so, could logic be added to watch the directory for file changes & regenerate without the need to change out of & into the directory to refresh?
I'm thinking something along the lines of inotify but more native in the Go code.
(Moving from ProDOS-Utilities discussion)
Beta Was this translation helpful? Give feedback.
All reactions