/************************** I2ICE TUTORIAL SCREEN #35 **************************/
menu = 1
define literally P   = 'include scr.34 nolist'
define literally R   = 'include scr.35 nolist'
define literally RTN = 'include scr.35 nolist'
define literally N   = 'include scr.36 nolist'
define literally M   = 'include scr.2 nolist'
cls
/*******************************************************************************/
'                                                      ------------------------'
'Earlier, when we looked for the first program bug,   | SCR35: SPECIFYING BREAK|'
'we used a break specification to halt emulation at   | M = Go to main menu    |'
'line 75.  (The emulation command we used was "GO     | N = Next screen        |'
'FROM TOP TIL :CMAKER#75".)  The I2ICE system offers  | P = Previous screen    |'
'four kinds of commands to control emulation breaks:  | Q = Quit tutorial      |'
' 1. BREAK SPECIFICATIONS cause emulation to break at | R = Rewrite SCR35      |'
'    a specified object-code address.                 | SCR# = Screen desired  |'
' 2. SYSTEM SPECIFICATIONS cause emulation to break    ------------------------'
'    at a specified memory or I/O-access address or   '
'    data value.'
' 3. ARM SPECIFICATIONS set up a window within which execution can break.'  
'    Where emulation breaks within the window is controlled by a trigger spec-'
'    ification that is like a break or system specification.'
' 4. EVENT SPECIFICATIONS cause emulation to break when execution satisfies a'
'    more complex set of conditions than can be established with the other' 
'    three kinds of specifications.'
'All of these specifications are used with the following GO command:'
'    GO TIL specification-for-execution-break'
'These specifications can also be used in break, system, arm, and event reg-'
'isters.  Later in this module more information is given about these registers.'
'-------------------------------------------------------------------------------'