<sect1>Interrupts<p>
-The runtime for the Apple ][ uses routines marked as <tt/.CONDES/
-type <tt/interruptor/ for ProDOS 8 interrupt handlers. Such routines must be
-written as simple machine language subroutines and will be called automatically
-by the interrupt handler code when they are linked into a program. See the
-discussion of the <tt/.CONDES/ feature in the <htmlurl url="ca65.html"
-name="assembler manual">.
+The runtime for the Apple ][ uses routines marked as
+<tt/.INTERRUPTOR/ for ProDOS 8 interrupt handlers. Such routines must be
+written as simple machine language subroutines and will be called
+automatically by the interrupt handler code when they are linked into a
+program. See the discussion of the <tt/.CONDES/ feature in the <htmlurl
+url="ca65.html" name="assembler manual">.
<sect1>DIO<p>
<sect1>Interrupts<p>
-The runtime for the enhanced Apple //e uses routines marked as <tt/.CONDES/
-type <tt/interruptor/ for ProDOS 8 interrupt handlers. Such routines must be
-written as simple machine language subroutines and will be called automatically
-by the interrupt handler code when they are linked into a program. See the
-discussion of the <tt/.CONDES/ feature in the <htmlurl url="ca65.html"
-name="assembler manual">.
+The runtime for the enhanced Apple //e uses routines marked as
+<tt/.INTERRUPTOR/ for ProDOS 8 interrupt handlers. Such routines must be
+written as simple machine language subroutines and will be called
+automatically by the interrupt handler code when they are linked into a
+program. See the discussion of the <tt/.CONDES/ feature in the <htmlurl
+url="ca65.html" name="assembler manual">.
<sect1>DIO<p>
<sect1>Interrupts<p>
-The runtime for the Atari uses routines marked as <tt/.CONDES/ type 2 for
+The runtime for the Atari uses routines marked as <tt/.INTERRUPTOR/ for
interrupt handlers. Such routines must be written as simple machine language
subroutines and will be called automatically by the VBI handler code
when they are linked into a program. See the discussion of the <tt/.CONDES/
<sect1>Interrupts<p>
-The runtime for the C128 uses routines marked as <tt/.CONDES/ type 2 for
+The runtime for the C128 uses routines marked as <tt/.INTERRUPTOR/ for
interrupt handlers. Such routines must be written as simple machine language
subroutines and will be called automatically by the interrupt handler code
when they are linked into a program. See the discussion of the <tt/.CONDES/
</enum>
</article>
-
-
-
-
<tt/ST/ variable.
+<sect1>Interrupts<p>
+
+The runtime for the C16 uses routines marked as <tt/.INTERRUPTOR/ for
+interrupt handlers. Such routines must be written as simple machine language
+subroutines and will be called automatically by the interrupt handler code
+when they are linked into a program. See the discussion of the <tt/.CONDES/
+feature in the <htmlurl url="ca65.html" name="assembler manual">.
+
+
<sect>Bugs/Feedback<p>
<sect1>Interrupts<p>
-The runtime for the C64 uses routines marked as <tt/.CONDES/ type 2 for
+The runtime for the C64 uses routines marked as <tt/.INTERRUPTOR/ for
interrupt handlers. Such routines must be written as simple machine language
subroutines and will be called automatically by the interrupt handler code
when they are linked into a program. See the discussion of the <tt/.CONDES/
</enum>
</article>
-
-
-
<sect1>Interrupt handlers<p>
-The runtime for the Commodore 510 uses routines marked as <tt/.CONDES/ type 2
+The runtime for the Commodore 510 uses routines marked as <tt/.INTERRUPTOR/
for interrupt handlers. Such routines must be written as simple machine
language subroutines and will be called automatically by the interrupt handler
code when they are linked into a program. See the discussion of the
<sect1>Interrupt handlers<p>
-The runtime for the Commodore 610 uses routines marked as <tt/.CONDES/ type 2
+The runtime for the Commodore 610 uses routines marked as <tt/.INTERRUPTOR/
for interrupt handlers. Such routines must be written as simple machine
language subroutines and will be called automatically by the interrupt handler
code when they are linked into a program. See the discussion of the
</enum>
</article>
-
-
-
information.
-<sect>Building you first Hello World application<p>
+<sect>Building your first Hello World application<p>
Here is a small traditional Hello World program for the Atari Lynx.
As the Atari Lynx does not have ASCII characters available you need to use
the Tiny Graphics Interface library for producing letters on the screen.
-The cc65 compiler suite has a graphics library called "Tiny Graphics Interface". This interface has some relocatable code. In order to use this in your own program you need to load it at run time.
+The cc65 compiler suite has a graphics library called "Tiny Graphics
+Interface". This interface has some relocatable code. In order to use this
+in your own program you need to load it at run time.
-Unfortunately the Lynx does not have a disk drive from where to load it. Therefore you must already load it at compile time. The easiest way is to link it in statically.
+Unfortunately the Lynx does not have a disk drive from where to load it.
+Therefore you must already load it at compile time. The easiest way is to
+link it in statically.
-This relocatable driver is found in $(CC65_HOME)/tgi/lynx-160-102-16.tgi. Copy it from here.
+This relocatable driver is found in <tt>$(CC65_HOME)/tgi/lynx-160-102-16.tgi</tt>.
+Copy it from here.
The name comes from 160 by 102 pixels (The Lynx LCD size), 16 colors.
-In order to link in this statically we have to make it back to a source file so that we can compile it. The next command will turn the compiled driver object file into an assembler source and compile it with the ca65 assembler.
+In order to link in this statically we have to make it back to a source
+file so that we can compile it. The next command will turn the compiled
+driver object file into an assembler source and compile it with the ca65
+assembler.
<tscreen><verb>
co65 --code-label _lynxtgi lynx-160-102-16.tgi
</enum>
</article>
-
-
-
<sect1>Interrupts<p>
-The runtime for the PET uses routines marked as <tt/.CONDES/ type 2 for
+The runtime for the PET uses routines marked as <tt/.INTERRUPTOR/ for
interrupt handlers. Such routines must be written as simple machine language
subroutines and will be called automatically by the interrupt handler code
when they are linked into a program. See the discussion of the <tt/.CONDES/
</enum>
</article>
-
-
-
<sect1>Interrupts<p>
-The runtime for the Plus/4 uses routines marked as <tt/.CONDES/ type 2 for
+The runtime for the Plus/4 uses routines marked as <tt/.INTERRUPTOR/ for
interrupt handlers. Such routines must be written as simple machine language
subroutines and will be called automatically by the interrupt handler code
when they are linked into a program. See the discussion of the <tt/.CONDES/
</enum>
</article>
-
-
-
-
<sect1>Interrupts<p>
-The runtime for the VIC20 uses routines marked as <tt/.CONDES/ type 2 for
+The runtime for the VIC20 uses routines marked as <tt/.INTERRUPTOR/ for
interrupt handlers. Such routines must be written as simple machine language
subroutines and will be called automatically by the interrupt handler code
when they are linked into a program. See the discussion of the <tt/.CONDES/
</enum>
</article>
-
-
-