changeset 1500:b00cf13c9f61

Major changes for new NitrOS-9 manual
author boisy
date Mon, 05 Jan 2004 00:51:19 +0000
parents 6cd590fc076f
children fd0cc67b5e7d
files docs/nitros9guide/asm.refentry docs/nitros9guide/binex.refentry docs/nitros9guide/build.refentry docs/nitros9guide/cc.refentry docs/nitros9guide/chap1.chapter docs/nitros9guide/chap2.chapter docs/nitros9guide/chap3.chapter docs/nitros9guide/chap4.chapter docs/nitros9guide/chap5.chapter docs/nitros9guide/chap6.chapter docs/nitros9guide/chap7.chapter docs/nitros9guide/chd.refentry docs/nitros9guide/cobbler.refentry docs/nitros9guide/copy.refentry docs/nitros9guide/dcheck.refentry docs/nitros9guide/debug.refentry docs/nitros9guide/ded.refentry docs/nitros9guide/del.refentry docs/nitros9guide/deldir.refentry docs/nitros9guide/devs.refentry docs/nitros9guide/dirm.refentry docs/nitros9guide/disasm.refentry docs/nitros9guide/display.appendix docs/nitros9guide/dmem.refentry docs/nitros9guide/dsave.refentry docs/nitros9guide/dump.refentry docs/nitros9guide/echo.refentry docs/nitros9guide/exbin.refentry docs/nitros9guide/format.refentry docs/nitros9guide/free.refentry docs/nitros9guide/go51.refentry docs/nitros9guide/help.refentry docs/nitros9guide/ident.refentry docs/nitros9guide/iniz.refentry docs/nitros9guide/intro.preface docs/nitros9guide/irqs.refentry docs/nitros9guide/list.refentry docs/nitros9guide/login.refentry docs/nitros9guide/makefile docs/nitros9guide/mdir.refentry docs/nitros9guide/nitros9guide.book docs/nitros9guide/nitros9guide.docbook docs/nitros9guide/nitros9l1guide.docbook docs/nitros9guide/nitros9l2guide.docbook docs/nitros9guide/tuneport.refentry
diffstat 45 files changed, 466 insertions(+), 427 deletions(-) [+]
line wrap: on
line diff
--- a/docs/nitros9guide/asm.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/asm.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -15,7 +15,7 @@
 
 <refsect1><title>Description</title>
 <para>
-Standard OS-9 Assembler
+Standard NitrOS-9 Assembler
 </para>
 </refsect1>
 <refsect1><title>Examples</title>
--- a/docs/nitros9guide/binex.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/binex.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -20,17 +20,17 @@
 programmers, emulators, logic analyzers and similar devices that are
 interfaced RS-232 interfaces. It can also be useful for
 transmitting files over data links that can only handle character-type
-data; or to convert OS-9 assembler or compiler-generated
-programs to load on non-OS-9 systems.
+data; or to convert NitrOS-9 assembler or compiler-generated
+programs to load on non-NitrOS-9 systems.
 </para>
 <para>
-<command>Binex</command> converts &quot;path1&quot;, an OS-9 binary format file, to a new file
+<command>Binex</command> converts &quot;path1&quot;, a NitrOS-9 binary format file, to a new file
 named &quot;path2&quot; in S-Record format. If invoked on a non-binary load
 module file, a warning message is printed and the user is asked if
 <command>binex</command> should proceed anyway. A &quot;Y&quot; response means yes; any other
 answer will terminate the program. S-Records have a header record
 to store the program name for informational purposes and each data
-record has an absolute memory address which is not meaningful to OS-9
+record has an absolute memory address which is not meaningful to NitrOS-9
 since it uses position-independent-code. However, the S-Record
 format requires them so <command>binex</command> will prompt the user for a program
 name and starting load address. For example:
--- a/docs/nitros9guide/build.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/build.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -39,14 +39,14 @@
 
 OS9: build newfile
 
-? The powers of the OS-9
+? The powers of the NitrOS-9
 ? operating system are truly
 ? fantastic.
 ? [RETURN]
 
 OS9: list newfile
 
-The powers of the OS-9
+The powers of the NitrOS-9
 operating system are truly
 fantastic.
 </screen>
--- a/docs/nitros9guide/cc.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/cc.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -16,11 +16,11 @@
 <refsect1><title>Description</title>
 <para>
 The are two commands which invoke distinct versions of the
-compiler. <command>cc1</command> is for OS-9 Level I which uses a two pass compiler,
-and, <command>cc2</command> is for Level II which causes a single pass version. Both
+compiler. <command>cc1</command> is for NitrOS-9 Level 1 which uses a two pass compiler,
+and, <command>cc2</command> is for Level 2 which causes a single pass version. Both
 versions of the compiler works identically, the main difference is
 that <command>cc1</command> has been divided into two passes to fit the smaller memory
-size of OS-9 Level I systems. In the following text, "cc" refers to
+size of NitrOS-9 Level 1. In the following text, "cc" refers to
 either <command>cc1</command> or <command>cc2</command> as appropiate for your system.
 </para>
 </refsect1>
--- a/docs/nitros9guide/chap1.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap1.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -2,17 +2,23 @@
 <title>Getting Started...</title>
 
 <section id="sec1.0">
-<title>What You Need to Run OS-9</title>
+<title>What You Need to Run NitrOS-9</title>
 <para>
-This version of &os9level; runs on the &make;. To use it you'll need the following:
+To use NitrOS-9 Level 1, you'll need the following:
 </para>
 <itemizedlist mark="bullet">
-  <listitem><para>&minmem; &make; </para></listitem>
+  <listitem><para>TRS-80/Tandy Color Computer or Color Computer 2 with 64K of RAM</para></listitem>
   <listitem><para>Disk Drive With Controller Cartridge</para></listitem>
-  <listitem><para>&os9level; System Disk</para></listitem>
 </itemizedlist>
 <para>
-OS-9 is also ready to use the following optional equipment that you
+To use NitrOS-9 Level 2, you'll need the following:
+</para>
+<itemizedlist mark="bullet">
+  <listitem><para>Tandy Color Computer 3 with 128K of RAM (512K recommended)</para></listitem>
+  <listitem><para>Disk Drive With Controller Cartridge</para></listitem>
+</itemizedlist>
+<para>
+NitrOS-9 is also ready to use the following optional equipment that you
 may have now or may obtain in the future:
 </para>
 <itemizedlist mark="bullet">
@@ -21,26 +27,26 @@
   <listitem><para>Printers and Modems</para></listitem>
   <listitem><para>Additional Serial Ports</para></listitem>
   <listitem><para>Joysticks and Mice</para></listitem>
-  <listitem><para>Other OS-9 Compatible Languages and Software</para></listitem>
+  <listitem><para>Other NitrOS-9 Compatible Languages and Software</para></listitem>
 </itemizedlist>
 
 <section id="sec1.0.1">
 <title>Starting the System</title>
 <para>
-To start up OS-9 follow these steps:
+To start up NitrOS-9 from a floppy drive, follow these steps:
 
 <orderedlist numeration="arabic">
-<listitem><para>Turn the &make; and disk drive(s) on. You should see
+<listitem><para>Turn the Color Computer and disk drive(s) on. You should see
 the usual BASIC greeting message on the screen.</para></listitem>
 
-<listitem><para>Insert the OS-9 System Disk in drive zero and close the door.</para></listitem>
+<listitem><para>Insert the NitrOS-9 System Disk in drive zero and close the door.</para></listitem>
 
 <listitem><para>Type &quot;&DOSCMD;&quot;. After a few seconds of disk activity you should
-see a screen with the words &quot;OS9 BOOT&quot;.</para></listitem>
+see a screen with the words &quot;NITROS9 BOOT&quot;.</para></listitem>
 
-<listitem><para>OS-9 will then begin
+<listitem><para>NitrOS-9 will then begin
 its &quot;bootstrap&quot; loading process, which
-involves ten to twenty seconds of disk activity. When the system
+involves a number of seconds of disk activity. When the system
 startup has finished, a message followed by the shell prompt will be
 displayed.</para></listitem>
 </orderedlist>
@@ -48,22 +54,22 @@
 </section>
 
 <section id="sec1.0.2">
-<title>In Case You Have Problems Starting OS-9</title>
+<title>In Case You Have Problems Starting NitrOS-9</title>
 <itemizedlist>
 <listitem><para>If BASIC gives an error message after you
 type &quot;&DOSCMD;&quot;, remove the
 disk, turn the computer off and on, then try again. If this
-repeatedly fails your OS-9 diskette may be bad.</para></listitem>
+repeatedly fails your NitrOS-9 diskette may be bad.</para></listitem>
 
 <listitem><para>Did you remember to turn the disk drive power switch on?</para></listitem>
 
-<listitem><para>Does your &make; have &minmem; RAM? This is a must!</para></listitem>
+<listitem><para>Does your Color Computer meet the minimum RAM requirements? This is a must!</para></listitem>
 
-<listitem><para>If your &make; doesn't seem to understand the &DOSCMD; command,
+<listitem><para>If your Color Computer doesn't seem to understand the &DOSCMD; command,
 your controller has DOS 1.0.  You will need to upgrade to
 DOS 1.1.</para></listitem>
 
-<listitem><para>If the &quot;OS9 BOOT&quot; message is displayed but nothing else happens,
+<listitem><para>If the &quot;NITROS9 BOOT&quot; message is displayed but nothing else happens,
 you may have a corrupted system disk. Hopefully you did make a
 backup!</para></listitem>
 </itemizedlist>
@@ -74,13 +80,13 @@
 <para>
 For now, the only special keys on the keyboard of interest are
 the SHIFT key which works like a typewriter shift key; the ENTER key
-which you always use after typing a command or response to OS-9; and
+which you always use after typing a command or response to NitrOS-9; and
 the &lt;- left arrow key which you can use to erase typing mistakes.
 </para>
 <para>
-Your main disk drive is known to to OS-9 as &quot;/D0&quot; and is often
+Your main disk drive is known to to NitrOS-9 as &quot;/D0&quot; and is often
 called &quot;drive zero&quot;. If you have a second disk drive (drive one),
-OS-9 recognizes it as &quot;/D1&quot;. Why would anybody put a &quot;/&quot; in a name?
+NitrOS-9 recognizes it as &quot;/D1&quot;. Why would anybody put a &quot;/&quot; in a name?
 Because all input and output devices have names like files, and
 names that start with &quot;/&quot; are always device names.
 </para>
@@ -89,17 +95,17 @@
 <section id="sec1.0.4">
 <title>Initial Explorations</title>
 <para>
-When OS-9 first starts up, it will display a welcoming message,
-and then ask you to enter the date and time. This allows OS-9 to
+When NitrOS-9 first starts up, it will display a welcoming message,
+and then ask you to enter the date and time. This allows NitrOS-9 to
 keep track of the date and time of creation of new files and disks.
 Enter the current date and time in the format requested like this:
 <screen>
              yyyy/mm/dd hh:mm:ss
-     Time ?  2003 03 01 14 20
+     Time ?  2004 01 01 14 20
 </screen>
-In the example above, the date entered was March 1, 2003. OS-9
+In the example above, the date entered was January 1, 2004. NitrOS-9
 uses 24-hour time so the date entered was 1420 hours or 2:20 PM.
-Next, OS-9 will print the shell prompt to let you know it is ready
+Next, NitrOS-9 will print the shell prompt to let you know it is ready
 for you to type in a command.
 </para>
 <para>
@@ -110,21 +116,26 @@
 <screen>
 dir
 </screen>
-followed by a &quot;return&quot;. OS-9 should respond with a listing of file
+followed by a &quot;return&quot;. NitrOS-9 should respond with a listing of file
 names which should look something like this:
 <screen>
- OS9Boot     startup     CMDS      SYS      DEFS
+  Directory of .
+OS9Boot         CMDS            SYS             DEFS            sysgo
+startup         
 </screen>
-The file <filename>OS9Boot</filename> contains the OS-9 program in &CPU; machine
+The file <filename>OS9Boot</filename> contains the NitrOS-9 program in &CPU; machine
 language, which was loaded into memory during the bootstrap
 operation.
 </para>
 <para>
+The file <filename>sysgo</filename> is only located on the NitrOS-9 Level 2 System Disk.  It is the first program run on the system, and kick-starts the initial application (usually, the shell).
+</para>
+<para>
 The file <filename>startup</filename> is a &quot;command file&quot; which is automatically run
 when the system starts up, and has the commands that printed the
 welcoming message and asked for the time. Later, You may want to
 replace this startup file with your own customized version after you
-are more familiar with OS-9. Do you want to see the contents of
+are more familiar with NitrOS-9. Do you want to see the contents of
 this file? If so, just type
 <screen>
 list startup
@@ -134,11 +145,11 @@
 <filename>OS9Boot</filename> file contain binary data such as machine language
 programs. These files are called &quot;binary files&quot;, and attempts to
 list them will result in a jumbled, meaningless display. On the
-other hand, OS-9 will complain mightily if you try to run a text
+other hand, NitrOS-9 will complain mightily if you try to run a text
 file as a program!
 </para>
 <para>
-As you may have surmised by now, the way you ask OS-9 to run a
+As you may have surmised by now, the way you ask NitrOS-9 to run a
 program or command (they're really the same thing) is to simply type
 its name. Some commands like <command>list</command> require one or more names of
 files or options. If so, they are typed on the same line using
@@ -149,13 +160,11 @@
 really more files on the disk than you suspect. The <command>dir</command> command
 showed you what is the disk's
 <emphasis>root directory</emphasis> - so named because the
-OS-9 filing system resembles a tree. Growing out of the root
+NitrOS-9 file system resembles a tree. Growing out of the root
 directory are three &quot;branches&quot; - files which are additional
 directories of file names instead of programs or data. They in turn
 can have even more &quot;branches&quot; - ad infinitum. If you draw a map on
 paper of how this works it does look like a tree.
-</para>
-<para>
 The directory files on your system disk are called <filename class="directory">CMDS</filename>,
 <filename class="directory">SYS</filename>, and <filename class="directory">DEFS</filename>.
 The file <filename class="directory">CMDS</filename> is a directory that consists of
@@ -168,7 +177,7 @@
 <filename class="directory">CMDS</filename>  instead
 of the root directory. After you type this you should see a long
 list of file names. These are the complete set of command programs
-that come with OS-9 and perform a myriad of functions. Chapter
+that come with NitrOS-9 and perform a myriad of functions. Chapter
 Seven explains each one in detail. The <command>dir</command> command also has a handy
 option to display the
 <filename class="directory">CMDS</filename> directory with less typing:
@@ -195,7 +204,7 @@
 <para>
 Before the actual backup procedure can be done (or any fresh
 diskette is used for any purpose), the blank disk which is to become
-the backup disk must be initialized by OS-9's <command>format</command> command.
+the backup disk must be initialized by NitrOS-9's <command>format</command> command.
 </para>
 <para>
 IF YOU HAVE ONLY ONE DISK DRIVE you have to be extra careful not to
@@ -299,7 +308,7 @@
 physically defective.
 </para>
 <para>
-After you have made your backup disk, try turning the &make;
+After you have made your backup disk, try turning the Color Computer
 off and restarting the system with the copy you just made.
 If it works OK, store it in a safe place in case it is needed later.
 You should always have a backup copy of your system disk and all
--- a/docs/nitros9guide/chap2.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap2.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -4,15 +4,15 @@
 <section id="sec2.0">
 <title>Running Commands and Basic Shell Operation</title>
 <para>
-The <command>shell</command> is a the part of OS-9 that accepts commands from your
+The <command>shell</command> is a the part of NitrOS-9 that accepts commands from your
 keyboard. It was designed to provide a convenient, flexible, and
 easy-to-use interface between you and the powerful functions of the
-operating system. The shell is automatically entered after OS-9 is
+operating system. The shell is automatically entered after NitrOS-9 is
 started up. You can tell when the shell is waiting for input
 because it displays the shell prompt. This prompt indicates that
 the shell is active and awaiting a command from your keyboard. It
 makes no difference whether you use upper-case letters, lower-case
-letters, or a combination of both because OS-9 matches letters of
+letters, or a combination of both because NitrOS-9 matches letters of
 either case.
 </para>
 <para>
@@ -83,7 +83,7 @@
 <section id="sec2.0.1">
 <title>Sending Output to the Printer</title>
 <para>
-Normally, most commands and programs display output on the &make; video display. The output of these programs can
+Normally, most commands and programs display output on the Color Computer video display. The output of these programs can
 alternatively be printed by specifying output redirection on the
 command line. This is done by including the following modifier to
 at the end of any command line:
@@ -93,8 +93,8 @@
 </screen>
 <para>
 The &quot;&gt;&quot; character tells the shell to redirect output (See <xref linkend="sec4.3.2"/>) to
-the printer using the &make;'s printer port, which has the device
-name &quot;/P&quot; (See <xref linkend="sec3.2"/>). For example, to redirect the output of the
+the printer using the Color Computer's printer port, which has the device
+name &quot;/p&quot; (See <xref linkend="sec3.2"/>). For example, to redirect the output of the
 <command>dir</command> command to the printer, enter:
 </para>
 <screen>
@@ -114,7 +114,7 @@
 end of every line, enter:
 </para>
 <screen>
-xmode /p lf;
+xmode /p lf
 </screen>
 </section>
 </section>
@@ -127,7 +127,7 @@
 line given to the shell. Parameters are separated from the command
 name and from each other by space characters (hence parameters and
 options cannot themselves include spaces). Each command program
-supplied with OS-9 has an individual description in the last section
+supplied with NitrOS-9 has an individual description in the last section
 of this manual which describe the correct usage of the parameters of
 each command.
 </para>
@@ -178,7 +178,7 @@
 </screen>
 <para>
 It is also possible to specify both a directory name parameter and
-the e  option, such as:
+the -e option, such as:
 </para>
 <screen>
 dir sys -e
@@ -192,7 +192,7 @@
 <title>Some Common Command Formats</title>
 <para>
 This section is a summary of some commands commonly used by new
-or casual OS-9 users, and some common formats. Each command is
+or casual NitrOS-9 users, and some common formats. Each command is
 followed by an example. Refer to the individual command
 descriptions later int his book for more detailed information and
 additional examples. Parameters or options shown in brackets are
@@ -246,7 +246,7 @@
 <section id="sec2.4">
 <title>Using the Keyboard and Video Display</title>
 <para>
-OS-9 has many features to expand the capability of the &make;
+NitrOS-9 has many features to expand the capability of the Color Computer
 keyboard and video display. The video display has screen pause,
 upper/lower case, and graphics functions. The keyboard can generate
 all ASCII characters and has a type-ahead feature that permits you
@@ -261,7 +261,7 @@
 <section>
 <title>Video Display Functions</title>
 <para>
-The &make; uses reverse video (green letters in a black box) to
+Most Color Computers use reverse video (green letters in a black box) to
 represent lower-case letters. Normally they are not used, so you
 have to turn them on if you want to use them with the command:
 </para>
@@ -269,6 +269,13 @@
 tmode -upc
 </screen>
 <para>
+However, the Color Computer 3 and certain models of the Color Computer 2 can also do true lowercase on the 32x16 video display.  To see if your Color Computer can do true lowercase, type the following command:
+<screen>
+xmode /term typ=1; display e
+</screen>
+If your Color Computer cannot do true lower case, your screen will show graphics garbage.
+</para>
+<para>
 The screen pause feature stops programs after 16 lines have been
 displayed. Output will continue if you hit any key. Normally this
 feature is on. It can be turned on or off with the <command>tmode</command> command as
--- a/docs/nitros9guide/chap3.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap3.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -1,9 +1,9 @@
 <chapter>
-<title>The OS-9 File System</title>
+<title>The NitrOS-9 File System</title>
 <section>
 <title>Introduction to the Unified Input/Output System</title>
 <para>
-OS-9 has a unified input/output system in which data transfers to
+NitrOS-9 has a unified input/output system in which data transfers to
 ALL I/O devices are performed in almost exactly the same manner,
 regardless of the particular hardware devices involved. It may seem
 that the different operational characteristics of the I/O devices
@@ -17,14 +17,14 @@
 more versatile input/output system.
 </para>
 <para>
-OS-9's unified I/O system is based upon logical entities called
+NitrOS-9's unified I/O system is based upon logical entities called
 &quot;I/O paths&quot;. Paths are analogous to &quot;software I/O channels&quot; which
 can be routed from a program to a mass-storage file, any other I/O
 device, or even another program. Another way to say the same thing
 is that paths are files, and all I/O devices behave as files.
 </para>
 <para>
-Data transferred through paths may be processed by OS-9 to
+Data transferred through paths may be processed by NitrOS-9 to
 conform to the hardware requirements of the specific I/O device
 involved. Data transfers can be either bidirectional (read/write)
 or unidirectional (read only or write only), depending on the device
@@ -34,7 +34,7 @@
 Data transferred through a path is considered to be a stream of
 8-bit binary bytes that have no specific type or value: what the
 data actually represents depends on how it is used by each program.
-This is important because it means that OS-9 does not require data
+This is important because it means that NitrOS-9 does not require data
 to have any special format or meaning.
 </para>
 <para>
@@ -63,11 +63,11 @@
 <section id="sec3.1">
 <title>Pathlists: How Paths Are Named</title>
 <para>
-Whenever a path is established (or &quot;opened&quot;), OS-9 must be given
+Whenever a path is established (or &quot;opened&quot;), NitrOS-9 must be given
 a description of the &quot;routing&quot; of the path. This description is
 given in the form of a character string called a &quot;pathlist&quot;. It
 specifies a particular mass-storage file, directory file, or any
-other I/O device. OS-9 &quot;pathlists&quot; are
+other I/O device. NitrOS-9 &quot;pathlists&quot; are
 similar to &quot;filenames&quot; used
 by other operating systems.
 </para>
@@ -91,8 +91,7 @@
 
 
 Names can have one to 29 characters, all of which are used for
-matching. They must becin with an upper- or lower-case letter
-followed by any combination of the following characters:
+matching. They may be composed of any combination of the following characters:
 </para>
 
 <simplelist>
@@ -100,7 +99,7 @@
 <member>lowercase letters: a - z</member>
 <member>decimal digits: 0 - 9</member>
 <member>underscore: _</member>
-<member>period: .</member>
+<member>period: . (cannot be the first character)</member>
 </simplelist>
 
 <para>
@@ -120,7 +119,7 @@
 </row>
 <row>
 <entry>RJJones</entry>
-<entry>search.bin</entry>
+<entry>22search.bin</entry>
 </row>
 </tbody>
 </tgroup>
@@ -134,10 +133,6 @@
 <colspec colwidth="2.0in"/>
 <tbody>
 <row>
-<entry>22November</entry>
-<entry>(does not start with a letter)</entry>
-</row>
-<row>
 <entry>max*min</entry>
 <entry>(* is not a legal character)</entry>
 </row>
@@ -165,7 +160,7 @@
 Each physical input/output device supported by the system must
 have a unique name. The actual names used are defined when the
 system is set up and cannot be changed while the system is running.
-The device names used for the &make; are:
+The device names used for the Color Computer are:
 </para>
 <informaltable frame="none">
 <tgroup cols="2">
@@ -212,10 +207,10 @@
 
 <para>
 I/O device names are actually the names of the &quot;device descriptor
-modules&quot; kept by OS-9 in an internal data structure called the
-&quot;module directory&quot; (See the OS-9 System Programmer's manual for more
+modules&quot; kept by NitrOS-9 in an internal data structure called the
+&quot;module directory&quot; (See the NitrOS-9 System Programmer's manual for more
 information about device driver and descriptor modules). This
-directory is automatically set up during OS-9's system start up
+directory is automatically set up during NitrOS-9's system start up
 sequence, and updated as modules are added or deleted while the
 system is running.
 </para>
@@ -244,7 +239,7 @@
 
 </para>
 <para>
-When OS-9 is asked to create a path, it uses the names in the
+When NitrOS-9 is asked to create a path, it uses the names in the
 pathlist sequentially from left to right to search various
 directories to obtain the necessary routing information. These
 directories are organized as a tree-structured hierarchy. The
@@ -255,7 +250,7 @@
 </para>
 <para>
 The diagram below is a simplified file system tree of a typical
-OS-9 system disk. Note that device and directory names are capitalized
+NitrOS-9 system disk. Note that device and directory names are capitalized
 and ordinary file names are not. This is a customary (but
 not mandatory) practice which allows you to easily identify directory
 files using the short form of the <command>dir</command> command.
@@ -380,8 +375,8 @@
 To make a new directory in this directory, the <command>makdir</command> command is
 used. The new directory will be called <filename class="directory">NEWDIR</filename>. Notice that
 throughout this manual directory names are always capitalized. This
-is <emphasis>not</emphasis> a requirement of OS-9 (see <xref linkend="sec3.1"/>) . Rather, it is a
-practice popular with many OS-9 users because it allows easy identification
+is <emphasis>not</emphasis> a requirement of NitrOS-9 (see <xref linkend="sec3.1"/>) . Rather, it is a
+practice popular with many NitrOS-9 users because it allows easy identification
 of directory files at all times (assuming all other file names use
 lower-case letters).
 </para>
@@ -445,7 +440,7 @@
 <para>
 The <command>del</command> command cannot be used to directly delete a directory
 file. If a directory file that still contained file names were to
-be deleted, OS-9 would have no way to access the files or to return
+be deleted, NitrOS-9 would have no way to access the files or to return
 their storage to the unallocated storage pool. Therefore, the
 following sequence must be performed to delete a directory file:
 </para>
@@ -468,7 +463,7 @@
 <section id="sec3.6">
 <title>Additional Information About Directories</title>
 <para>
-The OS-9 directory system is very useful because it allows each
+The NitrOS-9 directory system is very useful because it allows each
 user to privately organize files as desired (by project, function,
 etc.), without affecting other files or other user's files. Another
 advantage of the hierarchical directory system is that files with
@@ -540,7 +535,7 @@
 On the other hand, use of the current working directory allows
 all names in the file hierarchy tree to be implied instead of
 explicitly given. This not only makes pathlists shorter, but allows
-OS-9 to locate files faster because (typically) fewer directories
+NitrOS-9 to locate files faster because (typically) fewer directories
 need be searched. For example, if the current working directory is
 <filename class="directory">/D1/PETE/GAMES</filename> and a pathlist is given such as:
 </para>
@@ -577,11 +572,11 @@
 containing
 <emphasis>programs</emphasis> can be organized in different directories than
 files containing <emphasis>data</emphasis>.
-OS-9 automatically selects either working
+NitrOS-9 automatically selects either working
 directory, depending on the usage of the pathlist:
 </para>
 <para>
----&gt; OS-9 will search the execution directory when it attempts to
+---&gt; NitrOS-9 will search the execution directory when it attempts to
 load files into memory assumed to be executable programs. This
 means that programs to be run as commands or loaded into
 memory must be in the current execution directory.
@@ -591,7 +586,7 @@
 as text files, etc.)
 </para>
 <para>
-Immediately after startup, OS-9 will set the data directory to be
+Immediately after startup, NitrOS-9 will set the data directory to be
 (the root directory of) the system disk drive (usually &quot;D0&quot;), and
 the working directory to be a directory called <filename class="directory">cmds</filename> on the same
 drive (<filename class="directory">/D0/cmds</filename>). On timesharing systems, the <command>login</command> command
@@ -640,7 +635,7 @@
 <para>
 When using the <command>chd</command> or <command>chx</command> commands, pathlists work the same as they
 do for regular files, except for the last name in the pathlist must
-be a directory name. If the pathlist begins with a &quot;/&quot; , OS-9 will
+be a directory name. If the pathlist begins with a &quot;/&quot; , NitrOS-9 will
 begin searching in the device directory for the new working
 directory, otherwise searching will begin with the present directory.
  For example, the following sequence of commands set the
@@ -718,7 +713,7 @@
 how it many be used.
 </para>
 <para>
-OS-9 automatically stores with each file the user number
+NitrOS-9 automatically stores with each file the user number
 associated with the process that created it. This user is considered
 to be the &quot;owner&quot; of the file.
 </para>
@@ -746,7 +741,7 @@
 <para>
 EXECUTE PERMISSION FOR OWNER: If on, the owner can load the file into memory
 and execute it. Note that the file <emphasis>must</emphasis> contain one or
-more valid OS-9 format memory modules in order to actually load
+more valid NitrOS-9 format memory modules in order to actually load
 </para>
 <para>
 The following &quot;public permissions&quot; work the same way as
@@ -754,15 +749,15 @@
 DIFFERENT user numbers than the file's owner.
 </para>
 <para>
-WRITE PERMISSION FOR PUBLIC - If on, any other user may write to or
+WRITE PERMISSION FOR PUBLIC: If on, any other user may write to or
 delete the file.
 </para>
 <para>
-READ PERMISSION FOR PUBLIC - If on, any other user may read (and
+READ PERMISSION FOR PUBLIC: If on, any other user may read (and
 possibly copy) the file.
 </para>
 <para>
-EXECUTE PERMISSION FOR PUBLIC - If on, any other user may execute
+EXECUTE PERMISSION FOR PUBLIC: If on, any other user may execute
 the file.
 </para>
 <para>
@@ -842,7 +837,7 @@
 <title>Reading and Writing From Files</title>
 <para>
 A single file type and format is used for all mass storage files.
-Files store an ordered sequence of 8-bit bytes. OS-9 is not usually
+Files store an ordered sequence of 8-bit bytes. NitrOS-9 is not usually
 sensitive to the contents of files for most functions. A given file
 may store a machine language program, characters of text, or almost
 anything else. Data is written to and read from files exactly as
@@ -854,7 +849,7 @@
 When a file is created or opened a &quot;file pointer&quot; is established
 for it. Bytes within the file are addressed like memory, and the
 file pointer holds the &quot;address&quot; of the next byte in the file to be
-written to or read from. The OS-9 &quot;read&quot; and &quot;write&quot; service
+written to or read from. The NitrOS-9 &quot;read&quot; and &quot;write&quot; service
 functions always update the pointer as data transfers are performed.
 Therefore, successive read or write operations will perform sequential data transfers.
 </para>
@@ -871,11 +866,11 @@
 </para>
 
 <section id="sec3.9.1">
-<title>File Usage in OS-9</title>
+<title>File Usage in NitrOS-9</title>
 <para>
 Even though there is physically only one type of file, the logical
-usage of files in OS-9 covers a broad spectrum. Because all
-OS-9 files have the same physical type, commands such as <command>copy</command>,
+usage of files in NitrOS-9 covers a broad spectrum. Because all
+NitrOS-9 files have the same physical type, commands such as <command>copy</command>,
 <command>del</command>, etc., can be used with any file regardless of its logical
 usage. Similarly, a particular file can be treated as having a
 different logical usage at different times by different programs. The
@@ -939,7 +934,7 @@
 numbers, etc.
 </para>
 <para>
-It is important to understand that OS-9 itself does not directly
+It is important to understand that NitrOS-9 itself does not directly
 process or deal with records other than providing the basic file
 functions required by all high-level languages to create and use
 random-access files.
@@ -955,21 +950,21 @@
 contain <emphasis>one or more</emphasis> program modules.
 </para>
 <para>
-OS-9 program modules resident in memory have a standard module
+NitrOS-9 program modules resident in memory have a standard module
 format that, besides the object code, includes a &quot;module header&quot; and
 a CRC check value. Program module(s) stored in files contain exact
 binary copies of the programs as they will exist in memory, and not
-one byte more. OS-9 does not require a &quot;load record&quot;
-system commonly used by other operating systems because OS-9
+one byte more. NitrOS-9 does not require a &quot;load record&quot;
+system commonly used by other operating systems because NitrOS-9
 programs are position-independent code and therefore do not have to
 be loaded into specific memory addresses.
 </para>
 <para>
-In order for OS-9 to load the program module(s) from a file, the
+In order for NitrOS-9 to load the program module(s) from a file, the
 file itself must have execute permission and each module
 must have a valid module header and CRC check value. If a program
 module has been altered in any way, either as a file or in memory,
-its CRC check value will be incorrect And OS-9 will refuse to load
+its CRC check value will be incorrect And NitrOS-9 will refuse to load
 the module. The <command>verify</command> command can be used to check the correctness
 of the check values, and update them to corrected values if
 necessary.
@@ -990,7 +985,7 @@
 <section id="sec3.9.5">
 <title>Directory Files</title>
 <para>
-Directory files play a key role in the OS-9 file system.  They can only be created by the <command>makdir</command> command, and
+Directory files play a key role in the NitrOS-9 file system.  They can only be created by the <command>makdir</command> command, and
 can be identified by the &quot;d&quot; attribute being set (see <xref linkend="sec3.8.1"/>). The
 file is organized into 32-byte records. Each record can be a
 directory entry. The first 29 bytes of the record is a string of
@@ -1016,7 +1011,7 @@
 <section id="sec3.9.6">
 <title>Miscellaneous File Usage</title>
 <para>
-OS-9's basic file functions are so versatile it is possible to
+NitrOS-9's basic file functions are so versatile it is possible to
 devise an almost unlimited number of special-purpose file formats
 for particular applications, which do not fit into any of the three
 previously discussed categories.
@@ -1025,7 +1020,7 @@
 Examples of this category are COBOL Indexed Sequential (ISAM)
 files and some special word processor file formats which allow
 random access of text lines. As discussed in Sec.
-3.9.1, most OS-9 utility commands work with any file format including
+3.9.1, most NitrOS-9 utility commands work with any file format including
 these special types. In general, the <command>dump</command> command is the preferred
 method for examining the contents of unusually formatted files.
 </para>
@@ -1035,14 +1030,14 @@
 <section id="sec3.10">
 <title>Physical File Organization</title>
 <para>
-OS-9's file system implements a universal logical organization
+NitrOS-9's file system implements a universal logical organization
 for all I/O devices that effectively eliminates most hardware-related
 considerations for most applications. This section gives
-basic information about the physical file structure used by OS-9.
-For more information, see the OS-9 System Programmer's Manual.
+basic information about the physical file structure used by NitrOS-9.
+For more information, see the NitrOS-9 System Programmer's Manual.
 </para>
 <para>
-Each OS-9 file is comprised of one or more sectors  which are
+Each NitrOS-9 file is comprised of one or more sectors  which are
 the physical storage units of the disk systems. Each sector holds
 exactly 256 data bytes, and disk is numbered sequentially starting
 with sector zero, track zero. This number is called a &quot;logical
@@ -1053,7 +1048,7 @@
 <para>
 Sectors are the smallest allocatable physical unit on a disk
 system, however, to increase efficiency on some larger-capacity disk.
-systems, OS-9 uses uniform-sized groups of sectors, called
+systems, NitrOS-9 uses uniform-sized groups of sectors, called
 <emphasis>clusters</emphasis>,
 as the smallest allocatable unit. Cluster sizes are always an
 integral power of two (2, 4, 8, etc.). One sector of each disk is
@@ -1064,11 +1059,11 @@
 free for allocation to files.
 </para>
 <para>
-The &make; Computer disk system uses the following format:
+The Color Computer disk system uses the following format:
 </para>
 <itemizedlist mark="square">
 <listitem><para>
-double density recording on one side
+double density recording on two sides
 </para></listitem>
 <listitem><para>
 40 tracks per disk
--- a/docs/nitros9guide/chap4.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap4.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -2,7 +2,7 @@
 <title>Advanced Features of the Shell</title>
 <para>
 The basic shell functions were introduced in a prior chapter in order
-to provide an understanding of how basic OS-9 commands work. In
+to provide an understanding of how basic NitrOS-9 commands work. In
 this section the more advanced capabilities of the shell are
 discussed. In addition to basic command line processing, the shell
 has functions that facilitate:
@@ -152,7 +152,7 @@
 <para>
 The second kind of modifier is used to redirect the program's
 &quot;standard I/O paths&quot; to alternate files or devices. Well-written
-OS-9 programs use these paths for routine I/O. Because the programs
+NitrOS-9 programs use these paths for routine I/O. Because the programs
 do not use specific file or device names, it is fairly simple to
 &quot;redirect&quot; the I/O to any file or device without altering the
 program itself. Programs which normally receive input from a
@@ -435,7 +435,7 @@
 Here is a very practical example of the use of pipelines. Recall
 that the <command>dsave</command> command generates a procedure file to copy all the
 files in a directory. The example below shows how the output of
-<command>dsave</command> can be pipelined to a shell which will execute the OS-9
+<command>dsave</command> can be pipelined to a shell which will execute the NitrOS-9
 commands as they are generated by <command>dsave</command>. Assume that we want to
 copy all files from a directory called <filename class="directory">WORKING</filename> to a directory called
 <filename class="directory">ARCHIVE</filename>:
@@ -542,7 +542,7 @@
 <para>
 The shell is a reentrant program that can be simultaneously
 executed by more than one process at a time. As is the case with
-most other OS-9 programs, it uses standard I/O paths for routine
+most other NitrOS-9 programs, it uses standard I/O paths for routine
 input and output. specifically, it requests command
 lines from the standard input path and writes its prompts and other
 data to the standard error path.
@@ -597,7 +597,7 @@
 OS9: procfile&amp;
 </screen>
 <para>
-OS-9 does not have any constraints on the number of jobs that can be
+NitrOS-9 does not have any constraints on the number of jobs that can be
 simultaneously executed as long as there is memory available. Also, the procedure files can themselves cause sequential or
 concurrent execution of additional procedure files. Here's a more
 complex example of initiating two processing streams with
@@ -621,7 +621,7 @@
 <section id="sec4.7">
 <title>Error Reporting</title>
 <para>
-Many programs (including the shell) use OS-9's standard error
+Many programs (including the shell) use NitrOS-9's standard error
 reporting function, which displays an error number on the error
 output path. The standard error codes are listed in the <xref linkend="errorcodes"/> of
 this manual. If desired, the <command>printerr</command> command can be executed,
@@ -673,7 +673,7 @@
 <title>Setting Up Timesharing System Procedure Files</title>
 
 <para>
-OS-9 systems used for timesharing usually have a procedure file
+NitrOS-9 systems used for timesharing usually have a procedure file
 that brings the system up by means of one simple command or by using
 the system <filename>startup</filename> file. A procedure file which initiates the
 timesharing monitor for each terminal is executed to start up the
--- a/docs/nitros9guide/chap5.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap5.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -1,9 +1,9 @@
 <chapter>
 <title>Multiprogramming and Memory Management</title>
 <para>
-One of OS-9's most extraordinary abilities is multiprogramming,
+One of NitrOS-9's most extraordinary abilities is multiprogramming,
 which is sometimes called timesharing or multitasking. Simply
-states, OS-9 lets you computer run more than one program at the same
+states, NitrOS-9 lets you computer run more than one program at the same
 time. This can be a tremendous advantage in many situations. For
 example, you can be editing one program while another is being
 printed. Or you can use your Color Computer to control household
@@ -11,23 +11,23 @@
 entertainment.
 </para>
 <para>
-OS-9 uses this capability all the time for internal functions.
+NitrOS-9 uses this capability all the time for internal functions.
 The simple way for you to do so is by putting a &quot;&amp;&quot; character at the
 end of a command line which causes the shell to run your command as
 a &quot;background task&quot;.
 </para>
 <para>
 The information presented in this chapter is intended to give you
-an insight into how OS-9 performs this amazing feat. You certainly
+an insight into how NitrOS-9 performs this amazing feat. You certainly
 don't have to know every detail of how multiprogramming works in
-order to use OS-9, but a basic working knowledge can help you
+order to use NitrOS-9, but a basic working knowledge can help you
 discover many new ways to use your Color Computer.
 </para>
 <para>
 In order to allow several programs to run simultaneously and
-without interference, OS-9 must perform many coordination and
+without interference, NitrOS-9 must perform many coordination and
 resource allocation functions. The major system resources managed
-by OS-9 are:
+by NitrOS-9 are:
 </para>
 <simplelist>
 <member>CPU Time</member>
@@ -37,7 +37,7 @@
 <para>
 In order for the computer to have reasonable performance, these
 resources must be managed in the most efficient manner possible.
-Therefore, OS-9 uses many techniques and strategies to optimize
+Therefore, NitrOS-9 uses many techniques and strategies to optimize
 system throughput and capacity.
 </para>
 
@@ -53,11 +53,11 @@
 basis. Every time the program has to wait for a line of characters
 to be typed or displayed, it (typically) cannot do any useful
 processing and would waste CPU time. An efficient multiprogramming
-operating system such as OS-9 automatically assigns CPU time to only
+operating system such as NitrOS-9 automatically assigns CPU time to only
 those programs that can effectively use the, time.
 </para>
 <para>
-OS-9 uses a technique called <emphasis>timeslicing</emphasis> which allows processes
+NitrOS-9 uses a technique called <emphasis>timeslicing</emphasis> which allows processes
 to share CPU time with all other active processes. Timeslicing is
 implemented using both hardware and software functions. The
 system's CPU is interrupted by a real time clock many (60 in the
@@ -69,7 +69,7 @@
 continuously, unless the computer becomes overloaded with processing. If this
 happens, a noticeable delay in response to terminal
 input may occur, or &quot;batch&quot; programs may take much longer to run
-than they ordinarily do. At any occurrence of a tick, OS-9 can suspend
+than they ordinarily do. At any occurrence of a tick, NitrOS-9 can suspend
 execution of one program and begin execution of another. The
 starting and stopping of programs is done in a manner that does not
 affect the program's execution. How frequently a process is given
@@ -139,7 +139,7 @@
 <para>
 The sequence of operations required to create a new process and
 initially allocate its resources (especially memory) are
-automatically performed by OS-9's &quot;fork&quot; function. If for any
+automatically performed by NitrOS-9's &quot;fork&quot; function. If for any
 reason any part of the sequence cannot be performed the fork is
 aborted and the prospective parent is passed an appropriate error
 code. The most frequent reason for failure is unavailablity of
@@ -159,17 +159,17 @@
 fact, this hierarchy is a tree structure that resembles a family
 tree. The &quot;family&quot; concept makes it easy to describe relationships
 between processes, and so it is used extensively in descriptions of
-OS-9's multiprogramming operations.
+NitrOS-9's multiprogramming operations.
 </para>
 <para>
-When the parent issues a fork request to OS-9, it must specify
+When the parent issues a fork request to NitrOS-9, it must specify
 the following required information:
 </para>
 <itemizedlist mark="square">
 <listitem><para>
 A PRIMARY MODULE, which is the name of the program to be
 executed by the new process. The program can already be present
-in memory, or OS-9 may load it from a mass storage file having
+in memory, or NitrOS-9 may load it from a mass storage file having
 the same name.
 </para></listitem>
 <listitem><para>
@@ -206,7 +206,7 @@
 </para></listitem>
 </itemizedlist>
 <para>
-As part of the fork operation, OS-9 automatically assigns:
+As part of the fork operation, NitrOS-9 automatically assigns:
 </para>
 <itemizedlist mark="square">
 <listitem><para>
@@ -258,7 +258,7 @@
 <section id="sec5.4">
 <title>Basic Memory Management Functions</title>
 <para>
-An important OS-9 function is memory management. OS-9 automatically allocates
+An important NitrOS-9 function is memory management. NitrOS-9 automatically allocates
 all system memory to itself and to processes, and
 also keeps track of the logical <emphasis>contents</emphasis>
 of memory (meaning which
@@ -292,7 +292,7 @@
 <title>Loading Program Modules Into Memory</title>
 
 <para>
-When performing a fork operation, OS-9's first step is to attempt
+When performing a fork operation, NitrOS-9's first step is to attempt
 to locate the requested program module by searching the &quot;module
 directory&quot;, which has the address of every module present in memory.
 The &CPU; instruction set supports a type of program called
@@ -302,13 +302,13 @@
 program has am independent memory area for its variables.
 </para>
 <para>
-Almost all OS-9 family software is reentrant and can make most
+Almost all NitrOS-9 family software is reentrant and can make most
 efficient use of memory. For example, Basic09 requires 22K bytes of
 memory to load into. If a request to run Basic09 is made, but
 another user (process) had previously caused it to be loaded into
 memory, both processes will share the same copy, instead of causing
 another copy to be loaded (which would use an additional 22K of
-memory). OS-9 automatically keeps track of how many processes are
+memory). NitrOS-9 automatically keeps track of how many processes are
 using each program module and deletes the module (freeing its memory
 for other uses) when all processes using the module have terminated.
 </para>
@@ -319,25 +319,25 @@
 </para>
 <para>
 Every program module has a &quot;module header&quot; that describes the
-program and its memory requirements. OS-9 uses this to determine
+program and its memory requirements. NitrOS-9 uses this to determine
 how much memory for variable storage should be allocated to the
 process (it can be given more memory by specifying an optional
 parameter on the shell command line). The module header also
 includes other important descriptive information about the program,
-and is an essential part of OS-9 operation at the machine language
+and is an essential part of NitrOS-9 operation at the machine language
 level. A detailed description of memory modules and module headers
-can be found in the &quot;OS-9 System Programmer's Manual&quot;.
+can be found in the &quot;NitrOS-9 System Programmer's Manual&quot;.
 </para>
 <para>
 Programs can also be explicitly loaded into memory using the
 <command>load</command> command. As with fork, the program will actually be loaded
 only if it is not already in memory. If the module is not in
-memory, OS-9 will copy a candidate memory module from the file into
+memory, NitrOS-9 will copy a candidate memory module from the file into
 memory, verify the CRC, and then, if the module is not already in
 the module directory, add the module to the directory. This process
 is repeated until all the modules in the file are loaded, the 64K
 memory limit is exceeded, or until a module with an invalid format
-is encountered. OS-9 always links to the first module read from the
+is encountered. NitrOS-9 always links to the first module read from the
 file.
 </para>
 <para>
@@ -395,7 +395,7 @@
 <para>
 Another important aspect of program loading is the ability to
 have two or more programs resident in memory at the same time. This
-is possible because all OS-9 program modules are &quot;position-independent
+is possible because all NitrOS-9 program modules are &quot;position-independent
 code&quot;, or &quot;PIC&quot;. PIC programs do not have to be loaded into
 specific, predetermined memory addresses to work correctly, and can
 therefore be loaded at different memory addresses at different
@@ -439,7 +439,7 @@
 </para>
 <para>
 The <command>mfree</command> command shows the location and size of each unused
-memory area and the <command>mdir e</command> command shows the address, size, and
+memory area and the <command>mdir -e</command> command shows the address, size, and
 link (use) count of each module in the address space. These
 commands can be used to detect fragmentation. Memory can usually be
 de-fragmemted by unlinking scattered modules and reloading them.
--- a/docs/nitros9guide/chap6.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap6.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -1,7 +1,7 @@
 <chapter id="sec6">
 <title>Use of the System Disk</title>
 <para>
-Disk-based OS-9 systems use a system disk to load many parts of
+Disk-based NitrOS-9 systems use a system disk to load many parts of
 the operating system during the system startup and to provide files
 frequently used during normal system operations. Therefore, the
 system disk is generally kept in disk drive zero (&quot;/D0&quot;) when the
@@ -25,9 +25,9 @@
 
 <para>
 The file called <filename>OS9Boot</filename> loaded into RAM memory by the
-&quot;bootstrap&quot; routine located in the OS-9 firmware. It includes file
+&quot;bootstrap&quot; routine located in the NitrOS-9 firmware. It includes file
 managers, device drivers and descriptors, and any other modules
-which are permanently resident in memory. A typical Microware OS-9
+which are permanently resident in memory. The NitrOS-9
 distribution disk's <filename>OS9Boot</filename> file contains the following modules:
 </para>
 <informaltable frame="none">
@@ -36,12 +36,12 @@
 <colspec colwidth="3.5in"/>
 <tbody>
   <row>
-    <entry>OS9P2</entry>
-    <entry>OS-9 Kernel, Part 2</entry>
+    <entry>KernelP2</entry>
+    <entry>NitrOS-9 Kernel, Part 2</entry>
   </row>
   <row>
     <entry>IOMan</entry>
-    <entry>OS-9 Input/Output Manager</entry>
+    <entry>NitrOS-9 Input/Output Manager</entry>
   </row>
   <row>
     <entry>Init</entry>
@@ -104,7 +104,11 @@
     <entry>Real-Time Clock Module</entry>
   </row>
   <row>
-    <entry>CC3Go</entry>
+    <entry>Clock2</entry>
+    <entry>Second Part of Real-Time Clock Module</entry>
+  </row>
+  <row>
+    <entry>SysGo</entry>
     <entry>System Startup Process</entry>
   </row>
 </tbody>
@@ -125,7 +129,7 @@
 <title>The SYS Directory</title>
 
 <para>
-The directory <filename>/d0/SYS</filename> contains two important files:
+The directory <filename>/d0/SYS</filename> contains several important files:
 </para>
 <informaltable frame="none">
 <tgroup cols="2">
@@ -140,13 +144,17 @@
 <entry>errmsg</entry>
 <entry>the error message file</entry>
   </row>
+  <row>
+<entry>helpmsg</entry>
+<entry>the help database file</entry>
+  </row>
 </tbody>
 </tgroup>
 </informaltable>
 <para>
 These files (and the <filename class="directory">SYS</filename> directory itself) are not absolutely
-required to boot OS-9, they are needed if <command>login</command>, <command>tsmon</command>, or
-<command>printerr</command> will be used. Users may add other system-wide files of
+required to boot NitrOS-9, they are needed if <command>login</command>, <command>tsmon</command>, or
+<command>help</command> will be used. Users may add other system-wide files of
 similar nature if desired.
 </para>
 </section>
@@ -155,7 +163,7 @@
 <title>The Startup File</title>
 
 <para>
-The file <filename>/d0/startup</filename> is a shell procedure file which
+The file <filename>startup</filename> in the root directory is a shell procedure file which
 is automatically processed immediately after system startup. The
 user may include in <filename>startup</filename> any legal shell command line. Often
 this will include <command>setime</command> to start the system clock. If this file
@@ -168,10 +176,10 @@
 <title>The CMDS Directory</title>
 
 <para>
-The directory <filename class="directory">/d0/CMDS</filename> is the system-wide command object code
+The directory <filename class="directory">CMDS</filename> is the system-wide command object code
 directory, which is normally shared by all users as their working
 execution directory. If <command>shell</command> is not part of the
-<filename>OS9Boot</filename> file, it must be present in this directory. The system
+<filename>OS9Boot</filename> file (and it shouldn't be in a Level 2 system), it must be present in this directory. The system
 startup process &quot;sysgo&quot; makes <filename class="directory">CMDS</filename> the initial execution directory.
 </para>
 </section>
@@ -180,10 +188,10 @@
 <title>The DEFS Directory</title>
 
 <para>
-The directory <filename class="directory">/d0/DEFS</filename> is a directory that contains assembly
+The directory <filename class="directory">DEFS</filename> is a directory that contains assembly
 language source code files which contain common system-wide symbolic
 definitions, and are normally included in assembly language programs
-by means of the OS-9 Assembler &quot;use&quot; directive. The presence and
+by means of the NitrOS-9 Assembler &quot;use&quot; directive. The presence and
 use of this directory is optional, but highly recommended for any
 system used for assembly language programs. The files commonly
 contained in this directory are:
@@ -267,9 +275,14 @@
 <filename class="directory">SYS</filename> directories and the files they contain must be
 copied.
 </para></listitem>
+
+<listitem><para>
+For Level 2, the <filename>sysgo</filename> file in the root directory must be
+copied.
+</para></listitem>
 </orderedlist>
 
-Steps 2 through 4 may be performed manually, or automatically by any
+Steps 2 through 5 may be performed manually, or automatically by any
 of the following methods:
 <orderedlist  numeration="arabic">
 <listitem><para>
--- a/docs/nitros9guide/chap7.chapter	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chap7.chapter	Mon Jan 05 00:51:19 2004 +0000
@@ -2,17 +2,17 @@
 <title>System Command Descriptions</title>
 <para>
 This section contains descriptions for each of the command
-programs that are supplied with OS-9. These programs are usually
-called using the shell, but can be called from most other OS-9
+programs that are supplied with NitrOS-9. These programs are usually
+called using the shell, but can be called from most other NitrOS-9
 family programs such as BASIC09, Interactive Debugger, Macro Text
 Editor, etc. Unless otherwise noted, these programs are designed to
 run as individual processes.
 </para>
 <warning>
 <para>
-Although many OS-9 commands may work on Level One or Level
-Two systems, there are differences. Take care not to mix command
-files from Level One systems on Level Two, or the reverse.
+Although many NitrOS-9 commands may work on Level 1 or Level
+2 systems, there are differences. Take care not to mix command
+files from Level 1 systems on Level 2, or the reverse.
 </para>
 </warning>
 <section>
@@ -88,7 +88,6 @@
 &chdref;
 &cmpref;
 &cobblerref;
-&configref;
 &copyref;
 &cputyperef;
 &dateref;
--- a/docs/nitros9guide/chd.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/chd.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -21,11 +21,11 @@
 
 <refsect1><title>Description</title>
 <para>
-These are shell &quot;built in&quot; commands used to change OS-9's working
-data directory or working execution directory. Many commands in OS-9
+These are shell &quot;built in&quot; commands used to change NitrOS-9's working
+data directory or working execution directory. Many commands in NitrOS-9
 work with user data such as text files, programs, etc. These
 commands assume that a file is located in the working data
-directory. Other OS-9 commands will assume that a file is in the
+directory. Other NitrOS-9 commands will assume that a file is in the
 working execution directory.
 </para>
 <para>
--- a/docs/nitros9guide/cobbler.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/cobbler.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -16,12 +16,12 @@
 <refsect1><title>Description</title>
 <para>
 <command>Cobbler</command> is used to create the <filename>OS9Boot</filename> file required on any disk
-from which OS-9 is to be bootstrapped. The boot file will consist
+from which NitrOS-9 is to be bootstrapped. The boot file will consist
 of the <emphasis>same modules which were loaded into memory during the most
 recent boostrap.</emphasis>
 To add modules to the bootstrap file use the
-<command>OS9Gen</command> command. <command>Cobbler</command> also writes the OS-9 kernel on the first
-fifteen sectors of track 34, and excludes these sectors from the
+<command>OS9Gen</command> command. <command>Cobbler</command> also writes the NitrOS-9 kernel on the eighteen
+sectors of track 34, and excludes these sectors from the
 disk allocation map. If any files are present on these sectors
 <command>cobbler</command> will display an error message.
 </para>
@@ -30,7 +30,7 @@
 device. For this reason <command>cobbler</command> is normally used on a
 freshly formatted disk. If <command>cobbler</command> is used on a disk and there is
 not a contiguous block of storage large enough to hold the boot
-file, the old boot file may have been destroyed and OS-9 will not be
+file, the old boot file may have been destroyed and NitrOS-9 will not be
 able to boot from that disk until it is reformatted.
 </para>
 <para>
--- a/docs/nitros9guide/copy.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/copy.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -14,7 +14,7 @@
   <replaceable>path</replaceable>
 </arg>
 <arg choice="opt">
-  <option>-s</option>
+  <option>-a -p -r -s -w=&lt;dir&gt; -x</option>
 </arg>
 </cmdsynopsis>
 </refsynopsisdiv>
@@ -36,6 +36,15 @@
 is to be sent to a terminal or printer.
 </para>
 <para>
+The &quot;-a&quot; option will force <command>copy</command> to abort its operation if it receives an error during the copy of a file.  If this option is not specified, copy will continue to attempt to copy any other files specified on its command line.
+</para>
+<para>
+The &quot;-p&quot; option prevents copy from echoing the filenames that it is copying (used in conjunction with -w).
+</para>
+<para>
+The &quot;-r&quot; option allows copy to rewrite the destination file if it matches the name of a source file that is being copied.  If this option is not used, then the user will be prompted to overwrite a file of the same name.
+</para>
+<para>
 The &quot;-s&quot; option causes <command>copy</command> to perform a single drive copy
 operation. The second pathlist must be a full pathlist if &quot;-s
 appears. <command>Copy</command> will read a portion of the source disk into memory,
@@ -44,6 +53,12 @@
 this process continues until the entire file is copied.
 </para>
 <para>
+The &quot;-w=&lt;dir&gt;&quot; option allows you to specify a destination directory where all the files will be copied to.  Use this option when specifing multiple filenames on the command line.
+</para>
+<para>
+The &quot;-x=&lt;dir&gt;&quot; will cause the files to be copied to an execution-relative directory.
+</para>
+<para>
 Using the shell's alternate memory size modifier to give a large
 memory space will increase speed and reduce the number of media
 exchanges required for single drive copies.
@@ -55,6 +70,8 @@
 
 copy /d1/joe/news /D0/peter/messages
 
+copy /d1/joe/news /d1/joe/weather -w=/D0/peter (where /D0/peter is a directory)
+
 copy /term /p                   (copies console to printer)
 
 copy /d0/cat /d0/animals/cat -s #32k
--- a/docs/nitros9guide/dcheck.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/dcheck.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -167,7 +167,7 @@
 For more information see: <xref linkend="sec3.10"/>,
 <xref linkend="sec3.5"/>,
 <command>format</command>,
-6.1 of OS-9 Systems Programmer's Manual
+6.1 of NitrOS-9 Systems Programmer's Manual
 </para>
 </refsect1>
 <refsect1><title>Examples</title>
--- a/docs/nitros9guide/debug.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/debug.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -108,7 +108,7 @@
 </row>
 <row>
 <entry>$ command</entry>
-<entry>Call OS-9 shell with optional command</entry>
+<entry>Call NitrOS-9 shell with optional command</entry>
 </row>
 <row>
 <entry>Q</entry>
--- a/docs/nitros9guide/ded.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/ded.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -19,11 +19,9 @@
 sectors. It performs most of the functions of Patch, from 
 Computerware, but is faster, more compact, and
 screen-oriented rather than line-oriented. Individual files 
-or the disk itself (hard, floppy, ram) can be examined and 
+or the disk itself (hard, floppy, RAM) can be examined and 
 changed, sectors  can  be  written   to an output file, and 
 executable  modules can be located, linked to and verified. 
-With   simple changes, it will run on any CoCo Level I OS-9 
-and possibly others (CoCo Level II OS-9).
 </para><para>
 To use, type:
 <screen>
--- a/docs/nitros9guide/del.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/del.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -16,9 +16,6 @@
 <arg choice="plain">
   &repeatst;<replaceable>path</replaceable>&repeaten;
 </arg>
-<arg choice="opt">
-  <option>-x</option>
-</arg>
 </cmdsynopsis>
 </refsynopsisdiv>
 
--- a/docs/nitros9guide/deldir.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/deldir.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -28,7 +28,7 @@
 List directory, delete directory, or quit ? (l/d/q)
 </screen>
 <para>
-An &quot;l&quot; response will cause a <command>dir e</command> command to be run so you can
+An &quot;l&quot; response will cause a <command>dir -e</command> command to be run so you can
 have an opportunity to see the files in the directory before they
 are deleted.
 </para>
--- a/docs/nitros9guide/devs.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/devs.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -13,9 +13,9 @@
 <refsect1><title>Description</title>
 <para>
 Devs displays a list of the system's device table.  The device table contains an
-entry for each active device known to OS-9.  devs does not display information
+entry for each active device known to NitrOS-9.  devs does not display information
 for uninitialized devices. The devs display header lists the system name,
-the OS-9 version number, and the maximum number of devices allowed in the device table.
+the NitrOS-9 version number, and the maximum number of devices allowed in the device table.
 </para>
 <para>
 Each line in the devs display contains five fields:
--- a/docs/nitros9guide/dirm.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/dirm.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -1,7 +1,7 @@
 <refentry id="dirm">
 <refnamediv>
 <refname>DIRM</refname>
-<refpurpose>Display Module Directory for OS-9 Level Two</refpurpose>
+<refpurpose>Display Module Directory for NitrOS-9 Level 2</refpurpose>
 </refnamediv>
 
 <refsynopsisdiv>
@@ -32,7 +32,7 @@
 of each module is displayed. All numbers shown are in hexadecimal.
 </para>
 <para>
-WARNING: Many of the modules listed by <command>dirm</command> are OS-9 system modules
+WARNING: Many of the modules listed by <command>dirm</command> are NitrOS-9 system modules
 and <emphasis>not</emphasis> executable as programs: always check the module type code
 before running a module if you are not familiar with it!
 </para>
--- a/docs/nitros9guide/disasm.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/disasm.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -1,7 +1,7 @@
 <refentry id="disasm">
 <refnamediv>
 <refname>DISASM</refname>
-<refpurpose>OS9 Module Disassembler</refpurpose>
+<refpurpose>NitrOS-9 Module Disassembler</refpurpose>
 </refnamediv>
 
 <refsynopsisdiv>
@@ -17,7 +17,7 @@
 
 <refsect1><title>Description</title>
 <para>
-Disasm was written to hack apart OS9 system modules,command modules,
+Disasm was written to hack apart NitrOS-9 system modules,command modules,
 file managers and device drivers/descriptors either from memory or disk.
 Unlike most other disassemblers, <command>disasm</command> is a two pass disassembler, creating
 output using only referenced labels. This output can be redirected to a file
@@ -68,14 +68,4 @@
 immediately follow the '-' and there must be no spaces separating the options.
 </para>
 </refsect1>
-<refsect1><title>OS9 Level I Users</title>
-<para>
-by changing relative address $17 from $64 to $30 will cause the output
-source to reference /d0/defs instead of /dd/defs
-</para><para>
-also,if you are not using a driver which supports level II display codes,
-you *MUST* change relative address $15 from 01 to 00 to avoid problems
-in the event of an error message being printed out.
-</para>
-</refsect1>
 </refentry>
--- a/docs/nitros9guide/display.appendix	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/display.appendix	Mon Jan 05 00:51:19 2004 +0000
@@ -4,19 +4,19 @@
 <section>
 <title>The Video Display Generator</title>
 <para>
-&os9level; allows the VDG display to be used in
+NitrOS-9 allows the VDG display to be used in
 alphanumeric, semigraphic, and graphics modes. There are many
 built-in functions to control the display, which are activated by
 used of various ASCII control character. Thus, these functions are
 available for use by software written in any language using standard
-output statements (such as &quot;PRINT&quot; in BASIC). The &make;'s Basic09
+output statements (such as &quot;PRINT&quot; in BASIC). The Color Computer's Basic09
 language has a Graphics Interface Module that can automatically
 generate these codes using Basic09 RUN statements.
 </para>
 <para>
 The display system has two display modes: Alphanumeric
 (&quot;Alpha&quot;) mode and Graphics mode. The Alphanumeric mode also
-includes &quot;semigraphic&quot; box-graphics. The &make;'s display
+includes &quot;semigraphic&quot; box-graphics. The Color Computer's display
 system uses a separate - memory area for each display mode so
 operations on the Alpha display do not affect the Graphics display,
 and visa-versa. Either display can be selected under software
@@ -85,7 +85,7 @@
 displayed if its high order bit (sign bit) is cleared. Lower case
 letters are displayed in reverse video. If the high order bit of
 the character is set it is assumed to be a &quot;Semigraphic 6&quot; graphics
-box. See the &make; manual for an explanation of semigraphics
+box. See the Color Computer manual for an explanation of semigraphics
 functions.
 </para>
 
@@ -441,7 +441,7 @@
 <section>
 <title>Get Status Commands</title>
 <para>
-The &make; I/O driver includes OS-9 Get Status
+The Color Computer I/O driver includes OS-9 Get Status
 commands that return the display status and joystick values,
 respectively. These are accessable via the Basic09 Graphics
 Interface Module, or by the assembly language  system calls listed
--- a/docs/nitros9guide/dmem.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/dmem.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -12,7 +12,7 @@
 
 <refsect1><title>Description</title>
 <para>
-Displays memory under OS-9 Level Two.
+Displays memory under NitrOS-9 Level 2.
 </para>
 </refsect1>
 <refsect1><title>Examples</title>
--- a/docs/nitros9guide/dsave.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/dsave.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -8,10 +8,7 @@
 <cmdsynopsis>
 <command>dsave</command>
 <arg choice="opt">
-  <option>-opts</option>
-</arg>
-<arg choice="opt">
-  <replaceable>devname</replaceable>
+  <option>opts</option>
 </arg>
 <arg choice="opt">
   <replaceable>path</replaceable>
@@ -22,18 +19,14 @@
 <refsect1><title>Description</title>
 <para>
 Dsave is used to backup or copy all files in one or more
-directories. It is unlike most other commands in that it does NOT
-directly affect the system, rather, it generates a procedure file
-which is executed later to actually do the work.
+directories. It does not execute the commands; instead, it echos commands
+to standard output.  This output can be redirected to a file and executed later as a procedure file.
 </para>
 <para>
 When <command>dsave</command> is executed, it writes copy commands to
 <emphasis>standard output</emphasis>
 to copy files from the current <emphasis>data</emphasis> directory
-on <replaceable>devname</replaceable> (the default is /D0) to the directory
-specified by <replaceable>path</replaceable>. If <replaceable>path</replaceable>
-does not appear, the copy is performed to the current data directory
-<emphasis>at the time the <command>dsave</command> procedure file is executed.</emphasis>
+to the directory specified by <replaceable>path</replaceable>.
 If <command>dsave</command>
 encounters a directory file, it will automatically include <command>makdir</command>
 and <command>chd</command> commands in the output before generating copy commands for
@@ -73,7 +66,7 @@
 <entry>indent for directory levels</entry>
 </row>
 <row>
-<entry>-L</entry>
+<entry>-l</entry>
 <entry>do not process directories below the current level</entry>
 </row>
 <row>
@@ -81,6 +74,10 @@
 <entry>do not include <command>makdir</command> commands in procedure file</entry>
 </row>
 <row>
+<entry>-r</entry>
+<entry>forces the copy command to rewrite the file at its destination if it already exists</entry>
+</row>
+<row>
 <entry>-s<replaceable>integer</replaceable></entry>
 <entry>set copy size parameter to <replaceable>integer</replaceable> K</entry>
 </row>
@@ -98,13 +95,12 @@
 Example which copies all files on &quot;d2&quot; to &quot;d1&quot;:
 </para>
 <screen>
-chd /d2                          (select &quot;from&quot; directory)
-dsave /d2 &gt;/d0/makecopy       (make procedure file &quot;makecopy&quot;)
-chd /d1                          (select &quot;to&quot; directory)
+chd /d0                          (select &quot;from&quot; directory)
+dsave /d1 &gt;/d0/makecopy       (make procedure file &quot;makecopy&quot;)
 /d0/makcopy                      (run procedure file)
 
 chd /d0/MYFILES/STUFF
-dsave -is32 /d0 /d1/BACKUP/STUFF &gt;saver
+dsave -is32 /d1/BACKUP/STUFF &gt;saver
 /d0/MYFILES/STUFF/saver
 </screen>
 </refsect1>
--- a/docs/nitros9guide/dump.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/dump.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -8,6 +8,9 @@
 <cmdsynopsis>
 <command>dump</command>
 <arg choice="opt">
+  <replaceable>-h -m -x</replaceable>
+</arg>
+<arg choice="opt">
   <replaceable>path</replaceable>
 </arg>
 </cmdsynopsis>
@@ -33,28 +36,49 @@
 dump correspond to the relative load addresses of memory-module
 files.
 </para>
+<informaltable frame="none">
+<tgroup cols="2">
+<colspec colwidth="1in"/>
+<colspec colwidth="4in"/>
+<tbody>
+<row>
+<entry>-h</entry>
+<entry>prevent dump from printing its header every 256 bytes</entry>
+</row>
+<row>
+<entry>-m</entry>
+<entry>names on the command line are modules in memory</entry>
+</row>
+<row>
+<entry>-x</entry>
+<entry>names on the command line are files relative to the execution directory</entry>
+</row>
+</tbody>
+</tgroup>
+</informaltable>
 </refsect1>
+
 <refsect1><title>Examples</title>
 <screen>
-DUMP              (display keyboard input in hex)
-DUMP myfile &gt;/P   (dump myfile to printer)
-DUMP shortfile
+dump              (display keyboard input in hex)
+dump myfile &gt;/p   (dump myfile to printer)
+dump -m kernel    (dump the kernel module in memory)
 </screen>
 </refsect1>
 
 <refsect1><title>Sample Output</title>
 <screen>
-   Addr  0 1  2 3  4 5  6 7  8 9  A B  C D  E F   0 2 4 6 8 A C E
-   ---- ---- ---- ---- ---- ---- ---- ---- ----  ----------------
-   0000 87CD 0038 002A P181 2800 2E00 3103 FFE0  .M.8.*q.(...1..'
-   0010 0418 0000 0100 0101 0001 1808 180D 1B04  ................
-   0020 0117 0311 0807 1500 002A 5445 S2CD 5343  .........*TERMSC
-   0030 C641 4349 C10E 529E                      FACIA.R.
+   Address   0 1  2 3  4 5  6 7  8 9  A B  C D  E F   0 2 4 6 8 A C E
+   -------- ---- ---- ---- ---- ---- ---- ---- ----  ----------------
+   00000000 87CD 0038 002A P181 2800 2E00 3103 FFE0  .M.8.*q.(...1..'
+   00000010 0418 0000 0100 0101 0001 1808 180D 1B04  ................
+   00000020 0117 0311 0807 1500 002A 5445 S2CD 5343  .........*TERMSC
+   00000030 C641 4349 C10E 529E                      FACIA.R.
 
-    ^                     ^                              ^
+        ^                     ^                              ^
 
-starting       data bytes in hexadecimal           data bytes in
-address                format                      ASCII format
+    starting       data bytes in hexadecimal           data bytes in
+    address                format                      ASCII format
 </screen>
 </refsect1>
 </refentry>
--- a/docs/nitros9guide/echo.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/echo.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -24,7 +24,7 @@
 </refsect1>
 <refsect1><title>Examples</title>
 <screen>
-echo &gt;/T2 Hello John how's it going &amp;    (echo to T2)
+echo &gt;/t2 Hello John how's it going &amp;    (echo to t2)
 
 echo &gt;/term ** warning ** disk about to be scratched 1
 
--- a/docs/nitros9guide/exbin.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/exbin.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -20,8 +20,8 @@
 programmers, emulators, logic analyzers and similar devices that are
 interfaced RS-232 interfaces. It can also be useful for
 transmitting files over data links that can only handle character-type
-data; or to convert OS-9 assembler or compiler-generated
-programs to load on non-OS-9 systems.
+data; or to convert NitrOS-9 assembler or compiler-generated
+programs to load on non-NitrOS-9 systems.
 </para>
 <para>
 &quot;Path1&quot; is assumed to be an
@@ -30,7 +30,7 @@
 must describe continguous data in ascending order.
 </para>
 <para>
-<command>Exbin</command> does not generate or check for the proper OS-9 module
+<command>Exbin</command> does not generate or check for the proper NitrOS-9 module
 headers or CRC check value required to actually load the binary
 file. The IDENT or VERIFY commands can be used to check the
 validity of the modules if they are to be loaded or run.
--- a/docs/nitros9guide/format.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/format.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -17,7 +17,7 @@
 <para>
 This command is used to physically initialize, verify, and establish
 an initial file structure on a disk. All disks must be formatted
-before they can be used on an OS-9 system.
+before they can be used on an NitrOS-9 system.
 </para>
 <para>
 NOTE: If the diskette is to be used as a system disk, <command>OS9gen</command> or
--- a/docs/nitros9guide/free.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/free.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -42,7 +42,7 @@
 1,020 free sectors, largest block 935 sectors
 
 OS9: free /D1
-OS-9 Documentation Disk created on: 81/04/13
+NitrOS-9 Documentation Disk created on: 81/04/13
 Capacity: 1,232 sectors (1-sector clusters)
 568 Free sectors, largest block 440 sectors
 </screen>
--- a/docs/nitros9guide/go51.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/go51.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -14,7 +14,7 @@
 <para>
 An alternative video screen device driver, which provides a 51
 column by 24 line display with upper and lower case character sets,
-can be incorporated into OS-9 with the command:
+can be incorporated into NitrOS-9 with the command:
 <screen>
 GO51
 </screen>
--- a/docs/nitros9guide/help.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/help.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -1,7 +1,7 @@
 <refentry id="help">
 <refnamediv>
 <refname>HELP</refname>
-<refpurpose>Displays the usage and syntax of OS-9 commands.</refpurpose>
+<refpurpose>Displays the usage and syntax of NitrOS-9 commands.</refpurpose>
 </refnamediv>
 
 <refsynopsisdiv>
@@ -19,87 +19,26 @@
 as many command names in one <command>help</command> line as you wish.  The proper form and
 syntax appears for each valid command you include.
 </para>
-</refsect1>
-
-<refsect1><title>Notes</title>
 <para>
-To use <command>help</command>, first copy <filename>Cmds.hp</filename> from the <filename class="directory">SYS</filename> directory of the CONFIG/BOOT
-Diskette to the <filename class="directory">SYS</filename> directory of your system diskette.
-Next, copy <command>help</command>
-from the <filename class="directory">CMDS</filename> directory of
-the CONFIG/BOOT Diskette to the <filename class="directory">CMDS</filename> directory
-of your system diskette as follows:
-</para>
-<para>
-Procedure for one disk drive:
-</para>
-<para>
-1. With OS-9 booted and the system diskette in your drive, type:
-</para>
-<screen>
-	LOAD COPY [ENTER]
-</screen>
-<para>
-2. Replace the system diskete with the CONFIG/BOOT Diskette and type:
-</para>
-<screen>
-	COPY /D0/SYS/CMDS.HP /D0/SYS/CMDS.HP -S #30K [ENTER]
-</screen>
-<para>
-3. Exchange the two diskettes as requested by the screen prompts until the
-process is complete.
-</para>
-<para>
-4. Again, place the CONFIG/BOOT DIskette int he drive, and type:
-</para>
-<screen>
-	COPY /D0/CMDS/help /D0/CMDS/help -S #30K [ENTER]
-</screen>
-<para>
-5. Swap diskettes as requested until the process is complete.
+If you do not include a command name, help will show you the list of
+available topics for you to choose from.
 </para>
-<para>
-Procedure for two disk drives
-</para>
-<para>
-1. With OS-9 booted, place the CONFIG/BOOT Diskette in Drive 1.  Be sure
-the system diskette is in Drive 0.
-</para>
-<para>
-2. Type:
-</para>
-<screen>
-	COPY /D1/SYS/CMDS.HP /D0/SYS/CMDS.HP [ENTER]
-</screen>
-<para>
-3. When the first copy is complete, type:
-</para>
+</refsect1>
+<refsect1>
+<title>
+Examples:
+</title>
 <screen>
-	COPY /D1/CMDS/help /D0/CMDS/help [ENTER]
-</screen>
-<para>
-Cmds.hp is a data file, not a text file, and you cannot successfully display
-it on your screen or edit it with a standard text editor.  It contains help
-for standard OS-9 commands.
-</para>
-<para>
-<command>Help</command> displays the form and syntax of the specified command.  If you use a
-non-standard command name, a screen display tells you that help is not
-available for that command.
-</para>
-<para>
-Examples:
-</para>
-<screen>
-	HELP BACKUP [ENTER]
-	BACKUP [e][s][-v][dev][dev]
-	Copies all data from one device to another
+	help ex [ENTER]
+	Syntax: Ex &lt;modname&gt;
+	Usage : Chain to the given module
 
-	HELP ME [ENTER]
-	ME Help not available
+	help me [ENTER]
+	me: no help available
 
-	HELP [ENTER]
-	HELP [command name][...]
+	help [ENTER]
+	Help available on:
+        ASM     ATTR   [...]
 </screen>
 </refsect1>
 </refentry>
--- a/docs/nitros9guide/ident.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/ident.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -1,7 +1,7 @@
 <refentry id="ident">
 <refnamediv>
 <refname>IDENT</refname>
-<refpurpose>Print OS-9 module identification</refpurpose>
+<refpurpose>Print NitrOS-9 module identification</refpurpose>
 </refnamediv>
 
 <refsynopsisdiv>
@@ -21,7 +21,7 @@
 
 <refsect1><title>Description</title>
 <para>
-This command is used to display header information from OS-9 memory
+This command is used to display header information from NitrOS-9 memory
 modules. <command>Ident</command> displays the module size, CRC bytes (with verification), and for
 program and device driver modules, the execution
 offset and the permanent storage requirement bytes. <command>ident</command> will
@@ -80,28 +80,23 @@
 </screen>
 <screen>
 OS9: ident /d0/os9boot -s
-    1 $C0 $A366DC . OS9p2
+    1 $C0 $A366DC . KernelP2
    83 $C0 $7FC336 . Init
     1 $11 $39BA94 . SysGo
     1 $C1 $402573 . IOMan
-    3 $D1 $EE937A . REF
+    3 $D1 $EE937A . RBF
+   82 $F1 $526268 . DD
    82 $F1 $526268 . D0
    82 $F1 $D65245 . D1
    82 $F1 $E32FFE . D2
     1 $D1 $F944D7 . SCF
-    2 $E1 $F9FE37 . ACIA
-   83 $F1 $765270 . TERM
-   83 $F1 $B4396C . T1
-   83 $F1 $63B73B . T2
-   83 $F1 $0F9B78 . T3
-   83 $F1 $F83EB9 . T4
-   83 $F1 $D6DD9A . T5
-    3 $E1 $3EE015 . PIA
-   83 $F1 $12A43B . P
+    2 $E1 $F9FE37 . VDGInt
+   83 $F1 $765270 . Term
     2 $D1 $BBC1EE . PipeMan
     2 $E1 $5B2B56 . Piper
    80 $F1 $CC06AF . Pipe
     2 $C1 $248B2C . Clock
+    2 $C1 $248B2C . Clock2
     ^  ^     ^    ^ ^
     |  |     |    | |
     |  |     |    | Module name
--- a/docs/nitros9guide/iniz.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/iniz.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -16,7 +16,7 @@
 <refsect1>
 <title>Description</title>
 <para>
-Links the specified device to OS-9, places the device addres in a new device
+Links the specified device to NitrOS-9, places the device addres in a new device
 table entry, allocates the memory needed by the device driver, and calls
 the device driver initialization routine.  If the device is already
 installed, <command>iniz</command> does not reinitialize it.
@@ -48,10 +48,10 @@
 <refsect1>
 <title>Example:</title>
 <literallayout>
-	INIZ P T2 [ENTER]
+	iniz p t2 [ENTER]
 </literallayout>
 <para>
-initializes the P (printer) and T2 (terminal 2) devices.
+initializes the p (printer) and t2 (terminal 2) devices.
 </para>
 </refsect1>
 </refentry>
--- a/docs/nitros9guide/intro.preface	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/intro.preface	Mon Jan 05 00:51:19 2004 +0000
@@ -1,18 +1,9 @@
 <preface>
-<title>Welcome to &os9level;!</title>
+<title>Welcome to NitrOS-9!</title>
 <titleabbrev>Introduction</titleabbrev>
 <para>
-At the heart of your &make; is an amazing device: the
-&CPU; central processing unit (CPU).  When introduced in 1980, This
-microprocessor offered sophisticated features that were only
-found only on much larger and costly computers. Even today, it is
-architecture is considered feature-rich.  The OS-9 operating system
-was designed around the 6809 microprocessor to provide an extremely
-efficient and powerful operating system.
-</para>
-<para>
-The foundation of a computer's software system is its
-<emphasis>Operating System</emphasis> or "OS". It is the master control
+The foundation of a modern computer system is its
+<emphasis>Operating System</emphasis> or "OS".  The OS is the master control
 program that interfaces all other software to the system's hardware. Some
 of the things it must do are performing input and output operations,
 coordinating memory use, and many other "housekeeping" functions. All
@@ -25,7 +16,7 @@
 </para>
 
 <para>
-OS-9's overall structure was based on the famous UNIX<footnote id="unixdesc">
+NitrOS-9 is an operating system for the TRS-80/Tandy Color Computer family which provides harmony to the chaos of multiple devices, memory management and application service requests.  Its overall structure was based on the famous UNIX<footnote id="unixdesc">
 <para>
 UNIX is an operating system designed by Bell Telephone
 Laboratories, which is becoming widely recognized as a standard for
@@ -33,21 +24,17 @@
 elegant structure.
 </para>
 </footnote>
-operating system, which has been widely acclaimed as the operating
-system of the future because of its versatility, logical structure,
-and friendly user commands. The OS-9 family of advanced software is
-not only more powerful than most other microcomputer scftware - it
-is also much easier to learn and use.
+operating system.
 </para>
 <para>
-Some of the advanced OS-9 features you'll learn about in this
+NitrOS-9 is 100% compatible with OS-9 Level One and OS-9 Level Two for the Color Computer.  These products were manufactured by Tandy Corporation and sold through Radio Shack stores in the 1980s, and were purchased by many Color Computer users.  Today, the Color Computer is no longer manufactured and those versions of OS-9 are no longer for sale.  NitrOS-9 has evolved to be even better than these operating systems, and stands as the logical choice for those Color Computer owners who wish to use their CoCos today and tomorrow.
+</para>
+<para>
+Some of the advanced NitrOS-9 features you'll learn about in this
 book are:
 </para>
 <orderedlist numeration="arabic">
 
-<listitem><para>Friendly UNIX-like
-user interface and environment</para></listitem>
-
 <listitem><para>Multiuser/Multitasking Real-Time Operating System</para></listitem>
 
 <listitem><para>Extensive support for structured, modular programming</para></listitem>
@@ -63,19 +50,19 @@
 </orderedlist>
 <para>
 If you don't know what some of these thing mean yet - don't
-worry. As you explore OS-9 you'll soon learn how they enhance the
-capability of your &make; and make it so much easier to use
+worry. As you explore NitrOS-9 you'll soon learn how they enhance the
+capability of your Color Computer; and make it so much easier to use
 in almost any application.
 </para>
 <para>
-OS-9 has many commands and functions - definitely more than
-you can learn in an evening! The best way to become an OS-9 expert
-is to study this manual carefully, section-by-section, taking tire
+NitrOS-9 has many commands and functions - definitely more than
+you can learn in an evening! The best way to become an NitrOS-9 expert
+is to study this manual carefully, section-by-section, taking time
 to try out each command or function. Because many functions affect
 others, you'll find this manual extensively cross-referenced so you
 can skip ahead to help you understand a new topic. Taking the time
 to study this book will certainly increase your knowledge and
-enjoyment of OS-9.
+enjoyment of NitrOS-9.
 </para>
 <para>
 But if you can't wait, at least read the rest of this chapter,
--- a/docs/nitros9guide/irqs.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/irqs.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -16,7 +16,7 @@
 list of the service routines for each interrupt handler known by the system.
 </para>
 <para>
-The irqs display header lists the system name, the OS-9 version number, the maximum
+The irqs display header lists the system name, the NitrOS-9 version number, the maximum
 number of devices allowed in the device table, and the maximum number of entries in
 the IRQ table.
 </para>
--- a/docs/nitros9guide/list.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/list.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -33,11 +33,11 @@
 </refsect1>
 <refsect1><title>Examples</title>
 <literallayout>
-list /d0/startup &gt;/P &amp;        (output is redirected to printer)
+list /d0/startup &gt;/p &amp;        (output is redirected to printer)
 
-list /D1/user5/document /d0/myfile /d0/Bob/text
+list /d1/user5/document /d0/myfile /d0/Bob/text
 
-list /TERM &gt;/p                    (copy keyboard to printer - use
+list /term &gt;/p                    (copy keyboard to printer - use
                                   &quot;escape&quot; key to terminate input)
 </literallayout>
 <screen>
--- a/docs/nitros9guide/login.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/login.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -116,13 +116,14 @@
 <screen>
 OS9: login
 
-OS-9 Level 1 Timesharing System Version 1.2 82/12/04 13:02:22
+NitrOS-9/6309 Timesharing System
+Level 2 V03.02.01
+    2003/12/04 13:02:22
 
 User name?: superuser
 Password: secret
 
-Process #07 logged 81/12/04 13:03:00
-
+Process #07 logged on    2003/12/04 13:03:00
 Welcome!
 </screen>
 </refsect1>
--- a/docs/nitros9guide/makefile	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/makefile	Mon Jan 05 00:51:19 2004 +0000
@@ -1,40 +1,26 @@
-BOOKL1		= os9l1guide
-BOOKL2		= os9l2guide
+BOOK		= nitros9guide
 STYLESHEET	= ../stylesheets/docbook-utils.dsl
 
-all:	$(BOOKL1).pdf $(BOOKL2).pdf
-
-$(BOOKL1).pdf: $(BOOKL1).docbook $(SRCS)
-	 docbook2pdf -d $(STYLESHEET)#print $(BOOKL1).docbook
+all:	$(BOOK).pdf #$(BOOK).html $(BOOK).ps
 
-$(BOOKL2).pdf: $(BOOKL2).docbook $(SRCS)
-	 docbook2pdf -d $(STYLESHEET)#print $(BOOKL2).docbook
+$(BOOK).pdf: $(BOOK).docbook $(SRCS)
+	 docbook2pdf -d $(STYLESHEET)#print $(BOOK).docbook
 
-$(BOOKL1).ps: $(BOOKL1).docbook $(SRCS)
-	 docbook2ps -d $(STYLESHEET)#print $(BOOKL1).docbook
-
-$(BOOKL2).ps: $(BOOKL2).docbook $(SRCS)
-	 docbook2ps -d $(STYLESHEET)#print $(BOOKL2).docbook
+$(BOOK).ps: $(BOOK).docbook $(SRCS)
+	 docbook2ps -d $(STYLESHEET)#print $(BOOK).docbook
 
-$(BOOKL1).html: $(BOOKL1).docbook $(SRCS)
-	$(RM) *.html
-#	jade -t sgml -V html-index -d /usr/share/sgml/docbook/dsssl-stylesheets-1.64/html/docbook.dsl $(BOOKL1).docbook
-#	collateindex.pl -p -o index.docbook HTML.index
-	docbook2html -d $(STYLESHEET)#html $(BOOKL1).docbook
-
-$(BOOKL2).html: $(BOOKL2).docbook $(SRCS)
+$(BOOK).html: $(BOOK).docbook $(SRCS)
 	$(RM) *.html
-#	jade -t sgml -V html-index -d /usr/share/sgml/docbook/dsssl-stylesheets-1.64/html/docbook.dsl $(BOOKL2).docbook
+#	jade -t sgml -V html-index -d /usr/share/sgml/docbook/dsssl-stylesheets-1.64/html/docbook.dsl $(BOOK).docbook
 #	collateindex.pl -p -o index.docbook HTML.index
-	docbook2html -d $(STYLESHEET)#html $(BOOKL2).docbook
+	docbook2html -d $(STYLESHEET)#html $(BOOK).docbook
 
-print: $(BOOKL1).ps $(BOOKL2).ps
-	psnup -2 $(BOOKL1).ps | lpr
-	psnup -2 $(BOOKL2).ps | lpr
+print: $(BOOK).ps
+	psnup -2 $(BOOK).ps | lpr
 
 clean:
-	$(RM) *.html $(BOOKL1).pdf $(BOOKL1).ps $(BOOKL2).pdf \
-	      $(BOOKL2).ps *.log *.out *.aux
+	$(RM) *.html $(BOOK).pdf $(BOOK).pdf \
+	      $(BOOK).ps *.log *.out *.aux
 
 SRCS          = $(CHAPS) $(APXS) $(REFS)
 CHAPS         = intro.preface \
--- a/docs/nitros9guide/mdir.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/mdir.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -50,7 +50,7 @@
 </screen>
 <caution>
 <para>
-Many of the modules listed by <command>mdir</command> are OS-9 system modules
+Many of the modules listed by <command>mdir</command> are NitrOS-9 system modules
 and <emphasis>not</emphasis> executable as programs: always check the module type code
 before running a module if you are not familiar with it!
 </para>
--- a/docs/nitros9guide/nitros9guide.book	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/nitros9guide.book	Mon Jan 05 00:51:19 2004 +0000
@@ -1,9 +1,9 @@
 <bookinfo>
- <title>&os9level; Operating System User's Guide</title>
- <subtitle>&os9version;</subtitle>
+ <title>NitrOS-9 Operating System User's Guide</title>
+ <subtitle>&nitros9version;</subtitle>
 
 <copyright>
-  <year>2003</year>
+  <year>2004</year>
   <holder>&vendor;</holder>
 </copyright>
 
@@ -13,13 +13,8 @@
 
 <revhistory>
   <revision>
-    <revnumber>Org.</revnumber>
-    <date>1983</date>
-    <revremark>Original OS-9 Level One Guide</revremark>
-  </revision>
-  <revision>
     <revnumber>A</revnumber>
-    <date>March 2003</date>
+    <date>December 2003</date>
     <revremark>Updated with the changes made by Boisy Pitre</revremark>
   </revision>
 </revhistory>
@@ -37,5 +32,4 @@
 &errorcodesapp;
 &displayapp;
 &keysapp;
-&acia51app;
 
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/nitros9guide/nitros9guide.docbook	Mon Jan 05 00:51:19 2004 +0000
@@ -0,0 +1,93 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+  <!ENTITY repeatst   "{">
+  <!ENTITY repeaten   "}">
+  <!ENTITY CPU           "6809">
+  <!ENTITY nitros9version    "Version 03.02.01">
+  <!ENTITY vendor        "The NitrOS-9 Project">
+  <!ENTITY DOSCMD        "DOS">
+  <!ENTITY ctrlkey       "<keycap>CLEAR</keycap>">
+  <!ENTITY nitros9guide      SYSTEM "nitros9guide.book">
+  <!ENTITY preface       SYSTEM "intro.preface">
+  <!ENTITY chap1         SYSTEM "chap1.chapter">
+  <!ENTITY chap2         SYSTEM "chap2.chapter">
+  <!ENTITY chap3         SYSTEM "chap3.chapter">
+  <!ENTITY chap4         SYSTEM "chap4.chapter">
+  <!ENTITY chap5         SYSTEM "chap5.chapter">
+  <!ENTITY chap6         SYSTEM "chap6.chapter">
+  <!ENTITY chap7         SYSTEM "chap7.chapter">
+  <!ENTITY errorcodesapp SYSTEM "errorcodes.appendix">
+  <!ENTITY displayapp    SYSTEM "display.appendix">
+  <!ENTITY keysapp       SYSTEM "keys.appendix">
+
+  <!ENTITY asmref        "">
+  <!ENTITY attrref       SYSTEM "attr.refentry">
+  <!ENTITY backupref     SYSTEM "backup.refentry">
+  <!ENTITY basic09ref    SYSTEM "basic09.refentry">
+  <!ENTITY binexref      SYSTEM "binex.refentry">
+  <!ENTITY buildref      SYSTEM "build.refentry">
+  <!ENTITY ccref         SYSTEM "cc.refentry">
+  <!ENTITY chdref        SYSTEM "chd.refentry">
+  <!ENTITY cmpref        SYSTEM "cmp.refentry">
+  <!ENTITY cobblerref    SYSTEM "cobbler.refentry">
+  <!ENTITY copyref       SYSTEM "copy.refentry">
+  <!ENTITY cputyperef    SYSTEM "cputype.refentry">
+  <!ENTITY dateref       SYSTEM "date.refentry">
+  <!ENTITY dcheckref     SYSTEM "dcheck.refentry">
+  <!ENTITY debugref      SYSTEM "debug.refentry">
+  <!ENTITY dedref        SYSTEM "ded.refentry">
+  <!ENTITY delref        SYSTEM "del.refentry">
+  <!ENTITY deldirref     SYSTEM "deldir.refentry">
+  <!ENTITY devsref       SYSTEM "devs.refentry">
+  <!ENTITY dirref        SYSTEM "dir.refentry">
+  <!ENTITY disasmref     SYSTEM "disasm.refentry">
+  <!ENTITY displayref    SYSTEM "display.refentry">
+  <!ENTITY dmoderef      SYSTEM "dmode.refentry">
+  <!ENTITY dsaveref      SYSTEM "dsave.refentry">
+  <!ENTITY dumpref       SYSTEM "dump.refentry">
+  <!ENTITY echoref       SYSTEM "echo.refentry">
+  <!ENTITY exref         SYSTEM "ex.refentry">
+  <!ENTITY exbinref      SYSTEM "exbin.refentry">
+  <!ENTITY exmoderef     SYSTEM "exmode.refentry">
+  <!ENTITY formatref     SYSTEM "format.refentry">
+  <!ENTITY freeref       SYSTEM "free.refentry">
+  <!ENTITY go51ref       SYSTEM "go51.refentry">
+  <!ENTITY helpref       SYSTEM "help.refentry">
+  <!ENTITY identref      SYSTEM "ident.refentry">
+  <!ENTITY inizref       SYSTEM "iniz.refentry">
+  <!ENTITY irqsref       SYSTEM "irqs.refentry">
+  <!ENTITY killref       SYSTEM "kill.refentry">
+  <!ENTITY linkref       SYSTEM "link.refentry">
+  <!ENTITY listref       SYSTEM "list.refentry">
+  <!ENTITY loadref       SYSTEM "load.refentry">
+  <!ENTITY loginref      SYSTEM "login.refentry">
+  <!ENTITY makdirref     SYSTEM "makdir.refentry">
+  <!ENTITY mdirref       SYSTEM "mdir.refentry">
+  <!ENTITY mergeref      SYSTEM "merge.refentry">
+  <!ENTITY mfreeref      SYSTEM "mfree.refentry">
+  <!ENTITY os9genref     SYSTEM "os9gen.refentry">
+  <!ENTITY printerrref   SYSTEM "printerr.refentry">
+  <!ENTITY procref      "">
+  <!ENTITY procsref      SYSTEM "procs.refentry">
+  <!ENTITY pwdref        SYSTEM "pwd.refentry">
+  <!ENTITY renameref     SYSTEM "rename.refentry">
+  <!ENTITY runbref       SYSTEM "runb.refentry">
+  <!ENTITY saveref       SYSTEM "save.refentry">
+  <!ENTITY setimeref     SYSTEM "setime.refentry">
+  <!ENTITY setprref      SYSTEM "setpr.refentry">
+  <!ENTITY shellref      SYSTEM "shell.refentry">
+  <!ENTITY sleepref      SYSTEM "sleep.refentry">
+  <!ENTITY smapref      "">
+  <!ENTITY teeref        SYSTEM "tee.refentry">
+  <!ENTITY tmoderef      SYSTEM "tmode.refentry">
+  <!ENTITY tsmonref      SYSTEM "tsmon.refentry">
+  <!ENTITY tuneportref   SYSTEM "tuneport.refentry">
+  <!ENTITY unlinkref     SYSTEM "unlink.refentry">
+  <!ENTITY verifyref     SYSTEM "verify.refentry">
+  <!ENTITY wcreateref    "">
+  <!ENTITY xmoderef      SYSTEM "xmode.refentry">
+ ]>
+<book id="nitros9guide" lang="en">
+&nitros9guide;
+</book>
--- a/docs/nitros9guide/nitros9l1guide.docbook	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/nitros9l1guide.docbook	Mon Jan 05 00:51:19 2004 +0000
@@ -4,14 +4,14 @@
   <!ENTITY repeatst   "{">
   <!ENTITY repeaten   "}">
   <!ENTITY CPU           "6809">
-  <!ENTITY os9level      "OS-9 Level One">
-  <!ENTITY os9version    "Version 02.01.01 BETA1">
+  <!ENTITY nitros9level      "NitrOS-9 Level 1">
+  <!ENTITY nitros9version    "Version 03.02.01">
   <!ENTITY vendor        "The CoCo Community">
   <!ENTITY make          "TRS-80/Tandy Color Computer">
   <!ENTITY minmem        "64K">
   <!ENTITY DOSCMD        "DOS">
   <!ENTITY ctrlkey       "<keycap>CLEAR</keycap>">
-  <!ENTITY os9guide      SYSTEM "os9guide.book">
+  <!ENTITY nitros9guide      SYSTEM "nitros9guide.book">
   <!ENTITY preface       SYSTEM "intro.preface">
   <!ENTITY chap1         SYSTEM "chap1.chapter">
   <!ENTITY chap2         SYSTEM "chap2.chapter">
@@ -35,7 +35,6 @@
   <!ENTITY chdref        SYSTEM "chd.refentry">
   <!ENTITY cmpref        SYSTEM "cmp.refentry">
   <!ENTITY cobblerref    SYSTEM "cobbler.refentry">
-  <!ENTITY configref     SYSTEM "config.refentry">
   <!ENTITY copyref       SYSTEM "copy.refentry">
   <!ENTITY cputyperef    SYSTEM "cputype.refentry">
   <!ENTITY dateref       SYSTEM "date.refentry">
@@ -93,6 +92,6 @@
   <!ENTITY wcreateref    "">
   <!ENTITY xmoderef      SYSTEM "xmode.refentry">
  ]>
-<book id="os9guide" lang="en">
-&os9guide;
+<book id="nitros9guide" lang="en">
+&nitros9guide;
 </book>
--- a/docs/nitros9guide/nitros9l2guide.docbook	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/nitros9l2guide.docbook	Mon Jan 05 00:51:19 2004 +0000
@@ -4,14 +4,14 @@
   <!ENTITY repeatst   "{">
   <!ENTITY repeaten   "}">
   <!ENTITY CPU           "6809">
-  <!ENTITY os9level      "OS-9 Level Two">
-  <!ENTITY os9version    "Version 03.00.02 BETA3">
+  <!ENTITY nitros9level      "NitrOS-9 Level 2">
+  <!ENTITY nitros9version    "Version 03.02.01">
   <!ENTITY vendor        "The CoCo Community">
   <!ENTITY make          "Tandy Color Computer 3">
   <!ENTITY minmem        "128K">
   <!ENTITY DOSCMD        "DOS">
   <!ENTITY ctrlkey       "<keycap>CTRL</keycap>">
-  <!ENTITY os9guide      SYSTEM "os9guide.book">
+  <!ENTITY nitros9guide      SYSTEM "nitros9guide.book">
   <!ENTITY preface       SYSTEM "intro.preface">
   <!ENTITY chap1         SYSTEM "chap1.chapter">
   <!ENTITY chap2         SYSTEM "chap2.chapter">
@@ -99,6 +99,6 @@
   <!ENTITY wcreateref    SYSTEM "wcreate.refentry">
   <!ENTITY xmoderef      SYSTEM "xmode.refentry">
  ]>
-<book id="os9guide" lang="en">
-&os9guide;
+<book id="nitros9guide" lang="en">
+&nitros9guide;
 </book>
--- a/docs/nitros9guide/tuneport.refentry	Thu Dec 25 14:19:21 2003 +0000
+++ b/docs/nitros9guide/tuneport.refentry	Mon Jan 05 00:51:19 2004 +0000
@@ -1,7 +1,7 @@
 <refentry id="tuneport">
 <refnamediv>
 <refname>TUNEPORT</refname>
-<refpurpose>Tune the printer port on the &make;</refpurpose>
+<refpurpose>Tune the printer port on the Color Computer</refpurpose>
 </refnamediv>
 
 <refsynopsisdiv>
@@ -17,7 +17,7 @@
 
 <para>
 This command lets you test and set delay loop values for the current baud
-rate and select the best value for your printer (/P) or terminal (/T1).
+rate and select the best value for your printer (/p) or terminal (/t1).
 </para>
 <para>
 Examples
@@ -35,17 +35,17 @@
 entering a value at the prompt.  A closing message displays your new value.
 </para>
 <para>
-Use the same process to set a new delay loop value for /T1 terminal
+Use the same process to set a new delay loop value for /t1 terminal
 </para>
 <screen>
-	TUNEPORT /P -s=225 [ENTER]
+	tuneport /p -s=225 [ENTER]
 </screen>
 <para>
 Sets the delay loop value for your printer at 225.  Use such a command on
 future system boots to set the optimum delay value determined with the
 TUNEPORT test function.  Then, using OS9GEN or COBBLER, generate a new
 boot file for your system diskette.  You can also use TUNEPORT in your
-system startup file to set the value using the -S option.
+system startup file to set the value using the -s option.
 </para>
 </refsect1>
 </refentry>