Rob Hagemans

These weird errors are a known issue in Python 2 on Windows with CP65001, see e.g. here: https://bugs.python.org/issue1602#msg148990 : > The ANSI C write() function as implemented by the Windows...

Also, per DOSBox, Tandy GW-BASIC has `"Ok"+chr$(32)` in all screen modes.

Upon further investigation: - GW-BASIC reports 0 in all graphical modes - It reports 0 on every blank cell, not just after the prompt So this may not be prompt...

Similarly, `?chr$(255)` `?screen(3,1)` gives - 255 on GW-BASIC, SCREEN 0; - 0 on GW-BASIC, other screens; - 32 on Tandy, all screens (based on DOSBox 0.74)

PCJr behaves like GW-BASIC (based on MAME)

More observations on reading text in graphics modes: - (GW-BASIC) if two different characters have the same shape, `SCREEN` reports the one with the lowest value. E.g. in DosBox using...

Discussion of character recognition (done by the BIOS it seems): https://www.vogons.org/viewtopic.php?t=9304 Related: https://www.vogons.org/viewtopic.php?t=37502&start=20

- If I GET and PUT text in graphics mode to another character cell, does it get read correctly? Yes, but we have to make sure the logical "end of...

Hi @Mrdavidyunker , `POKE`ing to change the contents of variables or strings is not currently supported (though read access with `PEEK` is supported). It may be added in a future...

Hi, thanks for the suggestion - more support for headless runs is on the list somewhere, but it's not been a high priority I'm afraid... If implemented it would probably...