File operations (OPEN/PRINT#) in current directory fails

[SerOlmy16]

This might be the drive emulation in the emulator, or it could be a ROM issue. Consider the following program:

10 OPEN 1,8,1,"TEST"
20 PRINT#1,"FOO"
30 CLOSE 1

Expected result with no SD card file mounted: The file "TEST" should be created in the current directory, containing the text "FOO".

Actual result: The emulator prints a newline and a question mark to the console, and then locks up. A file "TEST" is indeed created in the current directory, containing only the first character of the string ("F" in this case). The file remains exclusively locked until the emulator is closed.

This is 100% reproducible under 64-bit Windows. I have not tried running the emulator on other platforms.

[irmen]

99% likely caused by the current minimalistic host filesystem support in the emulator.
I'm confident your program works fine on sdcard

[mooinglemur]

I found that this was because emulated hostfs CIOUT did not clear the carry bit in the status flag on return. Without that, I get ?I ERROR in 20 from BASIC, which is bafflingly confused.

However the real KERNAL routines always do a clc regardless of success, so we need the emulated one to do so unconditonally.

I've added this fix to my hostfs enhancement PR. #466

[mooinglemur]

Similar weird behavior also manifested itself on INPUT# from hostfs, and the issue was basically the same for that as it was for PRINT#, just for reading instead of writing. Fix in PR#479