Steve Fosdick

``` 7561c7561 < 0001D880 - A9 19 20 93 98 A9 20 91 F0 A0 06 91 F0 88 A2 07 .. ... ......... --- > 0001D880 - 20 E0...

So now on to MOS 3.50 patched to become 3.52. First in the OS: ``` 750c750 < 00002ED0 - 60 D0 FB 00 F7 4D 4F 53 20 33 2E...

Thanks, David. The patch to 3.20 in the OS ROM at EEAB comes from BuildMOS and does say it fixes OSBYTE &6B so as you described. BuildMOS includes a Y2K...

It's interesting how coming from a different background one can have a different approach. From DOS or CP/M days closing a file if you were not going to be accessing...

Is this still a problem? I checked beebasm and it seems to be opening its output file for write/truncate in the usual way, whether a simple binary file or a...

I can reproduce this. A quick fix would be to move the call to _update_rom_menu_ from _change_model_ in gui-allegro.c to _main_restart_ in main.c. As _main_restart_ calls _model_init_ which in turn...

As a further piece of inconsistency, if you load a ROM into a spare bank and then quit, this is saved to the config file so the ROM is still...

For the time being I have done the simple thing of refreshing the ROM menu after reset. I have also changed the way models are saved to the config file...

I can reproduce this. What I think is happening here is that VDFS is intercepting the call to OSWORD 7F. Though that may seem a bit odd, the whole thing...

I have implemented a fix in https://github.com/stardot/b-em/commit/9462cf3e928367b2c586f67498af2548ca98ed7d It looks like it was intended that VDFS should only implement OSWORD 7F if it is the current filing system but the way...