Date   : Tue, 01 Dec 2009 22:56:07 +0000 (GMT)
From   : info@... (Sprow)
Subject: Tube - I/O processor memory questions

In article <4B159074.2060002@...>,
   Kevin Bracey <kevin@...> wrote:
> Which has left me pondering how best to handle Break. What's the 
> most elegant way to deduce that my language 
> has been re-entered after a Break [...] is there some definite 
> cue that this is a Break-derived entry?

Entry is with C=0 for reset triggered start (hard/soft/power on).
         with C=1 for start due to *FX142
when your service handler matches the command it should start the language
using OSByte 142, not just calling the language entry point!

Not sure if that carry distinction makes it across the Tube though.

Of course, setting a flag in your lavish 1 byte service ROM workspace on
matching the command and immediately clearing it on language start would
serve the same purpose,
Sprow.