You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to load files in FB.COM after modifying editor colors #110
I am encountering the oddest issue. What I'm trying to do is very simple, on the face of it: just modify the editor colors to white-on-black instead of the Atari default light-grey-on-blue. I was able to track that down in the source code to this section:
It compiles without issue and, when loaded up in either an emulator or on real hardware, the colors work as expected.
But I can't load files from any device. The initial HELP.TXT file is loaded on start, but attempting to load any other file - even the same HELP.TXT file - results in 130 I/O ERROR.
For a sanity check, I did a hard reset to HEAD a clean make. The resulting ATR and FB.COM binary is able to load files without issue. It's only when I modify that editor.bas file that I encounter this problem.
I'm not sure if I'm doing something wrong here, or if this is a bug, or a problem with my toolchain. Any guidance this community can offer me would be awesome.
Reproduction Steps
Check out the v4.7 tag to ensure working from the current stable source.
Edit src/editor.bas and insert setcolor 1,0,14:setcolor 2,0,0 into the InitScreen procedure.
Compile the code.
Boot the fastbasic.atr in either an emulator or on hardware.
Run FB.COM.
Press CTRL+L and attempt to load D:HELP.TXT.
Dev Environment
OS: Ubuntu 24.04 derivative (Pop!_OS)
Run Environment
Emulator: Atari800 v4.2.0 Hardware: Atari 800XL w/U1MB (SpartaDOS X 4.49)
I expected that would be the case. If you were able to easily reproduce the issue, you would probably encounter it every single time you made changes to the editor.
I'll start by confirming that I am, indeed, using the full ATR in all test instances. Here is a video demonstrating the issue:
Screencast.from.04-20-2025.01.37.59.PM.webm
I suspect this boils down to toolchain differences. All I've done is install build-essential, which installed:
gcc v11.4.0
make v4.3
Can you list your versions so I can try to match them and see if that resolves this?
The problem is visible in your video, while changing the editor.bas file, your editor replaced the $9C and $9D characters (that are invalid UTF-8 codes) with the "missing character" UTF-8.
I changed the code to use a more compatible syntax to avoid this problem.
Activity
[-]Unable to load files after modifying editor[/-][+]Unable to load files in FB.COM after modifying editor colors[/+]dmsc commentedon Apr 19, 2025
Hi!
This is strange - and I can't reproduce it :( , see my test over current GIT, I added just the lines you mentioned:
Remember to always try with the full ATR, as you need DOS loaded to be able to read/write files.
taylor-madeak commentedon Apr 20, 2025
I expected that would be the case. If you were able to easily reproduce the issue, you would probably encounter it every single time you made changes to the editor.
I'll start by confirming that I am, indeed, using the full ATR in all test instances. Here is a video demonstrating the issue:
Screencast.from.04-20-2025.01.37.59.PM.webm
I suspect this boils down to toolchain differences. All I've done is install
build-essential, which installed:Can you list your versions so I can try to match them and see if that resolves this?
Dushino commentedon Apr 21, 2025
I have not tested, but I think the problem is in dual @ in
poke @@LMARGN, $00Should not there be only one @?
dmsc commentedon Apr 21, 2025
Hi!
The problem is visible in your video, while changing the editor.bas file, your editor replaced the $9C and $9D characters (that are invalid UTF-8 codes) with the "missing character" UTF-8.
I changed the code to use a more compatible syntax to avoid this problem.
Have Fun!
dmsc commentedon Apr 21, 2025
Hi!
Two
@means that the reference is in zero-page, producing shorter code.Have Fun!
taylor-madeak commentedon Apr 21, 2025
I didn't even catch that. I applied your change and that solved my problem. Thank you for the help, @dmsc!
Use hex codes instead of control characters in the editor source.