Picomite/PicoMiteVGA V5.07.05 release candidates

Author Message


Joined: 07/08/2011
Location: Australia
Posts: 5841
Posted: 10:43pm 29 Sep 2022      

  thwill said  
  TassyJim said   notice that you change OPTION BREAK and do not restore it in your break-handler. I don't think that matters but...

I wonder if that's it? The timeline would fit, the appearance of this problem and adding the break-handling code are both events of the last week. I will check first thing in the morning.

<EOT>, CHR$(4) is sent by xmodem but only at the end of all text so it shouldn't be doing anything at the time.

Phil has confirmed the problem so I might change the firmware to VGA and do some investigating if time permits today. Spring time so lots to do.

My guess is, there is something that gets cleaned up with a ^C that doesn't get cleaned up with a simple END. I am not sure if there is any way to simulate a ^C from within a program. 'ERROR' seems the closest but not very nice for the end user to see.

Edited 2022-09-30 09:05 by TassyJim