Mercurial > hg > Members > kono > nitros9-code
changeset 1011:cc153d1671f7
Updated for new manuals
| author | boisy |
|---|---|
| date | Tue, 04 Mar 2003 15:11:34 +0000 |
| parents | 1027549ee381 |
| children | 7aa7d982aa8e |
| files | docs/nitros9guide/acia51.appendix 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/config.refentry docs/nitros9guide/cputype.refentry docs/nitros9guide/devs.refentry docs/nitros9guide/display.appendix docs/nitros9guide/intro.preface docs/nitros9guide/makefile docs/nitros9guide/tuneport.refentry |
| diffstat | 15 files changed, 228 insertions(+), 206 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/nitros9guide/acia51.appendix Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/acia51.appendix Tue Mar 04 15:11:34 2003 +0000 @@ -3,7 +3,7 @@ <para> For those who wish to use the serial port, the input or output path of a program may be redirected to the serial port of -your &make; computer. +your &make;. </para> <para> This is done by including the following module in the OS-9 kernel: @@ -43,7 +43,7 @@ <section> <title>Serial Terminal Implementation</title> <para> -For those who wish to connect two &make; computers, running +For those who wish to connect two &make;s, running OS-9, together using the serial port, redirection of the input or output paths is possible using the following modifier at the end of a command line:
--- a/docs/nitros9guide/chap1.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap1.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -4,21 +4,21 @@ <section> <title>What You Need to Run OS-9</title> <para> -OS-9 has been tailored to run on your standard, unmodified &make; -Computer. To use it you'll need the following things: +&os9level &os9version has been tailored to run on the &make;. To use it you'll need the following things: </para> <itemizedlist mark="bullet"> - <listitem><para>A 64K Memory &make; Computer</para></listitem> - <listitem><para>A &make; Computer Disk Drive With Contoller Cartridge</para></listitem> - <listitem><para>An OS-9 &make; Computer System Disk</para></listitem> + <listitem><para>A &minmem &make; </para></listitem> + <listitem><para>A Disk Drive With Contoller Cartridge</para></listitem> + <listitem><para>An OS-9 &make; System Disk</para></listitem> </itemizedlist> <para> OS-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"> - <listitem><para>Additional Expansion Disk Drive(s)</para></listitem> - <listitem><para>A Parallel Printer</para></listitem> + <listitem><para>Additional Floppy Disk Drives</para></listitem> + <listitem><para>SCSI or IDE Hard Drives</para></listitem> + <listitem><para>Printers and Serial Ports</para></listitem> <listitem><para>Game Joysticks</para></listitem> <listitem><para>Other OS-9 Compatible Languages and Software</para></listitem> </itemizedlist> @@ -29,18 +29,18 @@ To start up OS-9 follow these steps: <orderedlist numeration="arabic"> -<listitem><para>Turn the &make; Computer and disk drive(s) on. You should see -the usual Basic greeting message on the screen.</para></listitem> +<listitem><para>Turn the &make; 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>Type "BOOT". After a few seconds of disk activity you should -see a screen with the words "OS9BOOT".</para></listitem> +<listitem><para>Type "&DOSCMD". After a few seconds of disk activity you should +see a screen with the words "OS9 BOOT".</para></listitem> <listitem><para>OS-9 will then begin its "bootstrap" loading process, which involves ten to twenty seconds of disk activity. When the system -startup has finished, a message followed by an "OS9:" prompt will be +startup has finished, a message followed by the shell prompt will be displayed.</para></listitem> </orderedlist> </para> @@ -49,19 +49,19 @@ <section> <title>In Case You Have Problems Starting OS-9</title> <itemizedlist> -<listitem><para>If Basic gives an error message after you -type "BOOT", remove the +<listitem><para>If BASIC gives an error message after you +type "&DOSCMD", 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> <listitem><para>Did you remember to turn the disk drive power switch on?</para></listitem> -<listitem><para>Does your &make; Computer have 64K RAM? This is a must!</para></listitem> +<listitem><para>Does your &make; have &minmem RAM? This is a must!</para></listitem> -<listitem><para>If your &make; Computer doesn't seem to understand the BOOT -command, contact your dealer.</para></listitem> +<listitem><para>If your &make; 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 "OS9BOOT message is displayed but nothing else happens, +<listitem><para>If the "OS9 BOOT message is displayed but nothing else happens, you may have a corrupted system disk. Hopefully you did make a backup!</para></listitem> </itemizedlist> @@ -92,12 +92,12 @@ 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> - YY/MM/DD HH:MM:SS - TIME ? 83 7 14 1420 + yyyy/mm/dd hh:mm:ss + Time? 2003 03 01 14 20 </screen> -In the example above, the date entered was July 14, 1983. OS-9 +In the example above, the date entered was March 1, 2003. OS-9 uses 24-hour time so the date entered was 1420 hours or 2:20 PM. -Next, OS-9 will print an "OS9:" prompt to let you know it is ready +Next, OS-9 will print the shell prompt to let you know it is ready for you to type in a command. </para> <para> @@ -113,7 +113,7 @@ <screen> OS9Boot startup CMDS SYS DEFS </screen> -The file "OS9Boot" contains the OS-9 program in 6809 machine +The file "OS9Boot" contains the OS-9 program in &CPU machine language, which was loaded into memory during the bootstrap operation. </para> @@ -160,7 +160,7 @@ all the system commands such as DIR, LIST, FORMAT, etc. To see the files contained in this directory, enter: <screen> -DIR CMDS +dir cmds </screen> which tells DIR to show files on the directory file CMDS instead of the root directory. After you type this you should see a long @@ -169,12 +169,11 @@ Seven explains each one in detail. The DIR command also has a handy option to display the CMDS directory with less typing: <screen> -DIR X +dir -x </screen> Whenever you want a list of available commands you can use this so you don't have to look it up in the book. The DIR command has -options which can give you more detailed information about each file -(see sections 3.4 and 3.8.1). +options which can give you more detailed information about each file. </para> </section> </section> @@ -199,16 +198,16 @@ accidentally FORMAT your system disk. Type: <screen> -FORMAT /D0 +format /d0 </screen> and when you see the message <screen> -DRAGON DISK FORMATTER 1 . 2 +COLOR COMPUTER FORMATTER FORMAT DRIVE /D0 Y (YES) OR N (NO) -READY? +Ready? </screen> immediately remove your system disk and insert a blank disk @@ -252,7 +251,7 @@ IF YOU HAVE ONE DRIVE type </para> <screen> -BACKUP /D0 #32k +backup /d0 #32k </screen> <para> The BACKUP program will prompt you to alternately insert the source @@ -263,7 +262,7 @@ IF YOU HAVE TWO DRIVES type </para> <screen> -BACKUP #32K +backup #32K </screen> <para> @@ -276,7 +275,7 @@ Now enter Y for yes. It will then ask: </para> <screen> -X IS BEING SCRATCHED +X is being scratched OK ?: </screen> <para> @@ -297,7 +296,7 @@ </para> <para> After you have made your backup disk, try turning the &make; -Computer off and restarting the system with the copy you just made. +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 other important disks.
--- a/docs/nitros9guide/chap2.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap2.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -9,7 +9,7 @@ easy-to-use interface between you and the powerful functions of the operating system. The shell is automatically entered after OS-9 is started up. You can tell when the shell is waiting for input -because it displays the "OS9:" prompt. This prompt indicates that +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 @@ -24,8 +24,8 @@ <listitem><para>The name of a machine language program on disk</para></listitem> <listitem><para>The name of a machine language program already in memory</para></listitem> <listitem><para>The name of an executable program compiled by a high-level -language such as Basic09, Pascal, Cobol, etc. (See 4.8)</para></listitem> -<listitem><para>The name of a procedure file (See 4.6)</para></listitem> +language such as Basic09, Pascal, Cobol, etc.</para></listitem> +<listitem><para>The name of a procedure file</para></listitem> </itemizedlist> <para> If you're a beginner, you will almost always use the first case, @@ -39,13 +39,13 @@ <orderedlist numeration="arabic"> -<listitem><para>- If the program named is already in memory, it is run.</para></listitem> +<listitem><para> If the program named is already in memory, it is run.</para></listitem> -<listitem><para>- The "execution directory", usually "CMDS", is searched. +<listitem><para> The "execution directory", usually "CMDS", is searched. If a file having the name given is found, it is loaded and -run (See 5.4.1).</para></listitem> +run.</para></listitem> -<listitem><para>- The user's "data directory" is searched. If a file having +<listitem><para> The user's "data directory" is searched. If a file having the name given is found, it is processed as a "procedure file" which means that the file is assumed to contain one or more command lines which are processed by the shell in @@ -56,7 +56,7 @@ Mention is made above of the "data directory" and the "execution directory". At all times each user is associated with two file directories. A more detailed explanation of directories is presented -in section 3.3. The execution directory (usually CMDS) includes +later. The execution directory (usually CMDS) includes files which are executable programs. </para> <para> @@ -68,7 +68,7 @@ For example, in the command line: </para> <screen> -LIST FILE1 +list file1 </screen> <para> the program name is LIST, and the parameter passed to it is FILE1. @@ -76,30 +76,29 @@ <para> A command line may also include one or more "modifiers" which are specifications used by the shell to alter the program's standard -input/output files or memory assignments (See 4.2). +input/output files or memory assignments. </para> <section> <title>Sending Output to the Printer</title> <para> -Normally, most commands and programs display output on the Color -Computer video display. The output of these programs can +Normally, most commands and programs display output on the &make 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: </para> <screen> ->/P +>/p </screen> <para> The ">" character tells the shell to redirect output (See 4.3.2) to -the printer using the &make; Computer's parallel port, which has the device +the printer using the &make;'s printer port, which has the device name "/P" (See 3.2). For example, to redirect the output of the "dir" command to the printer, enter: </para> <screen> -DIR >/P +dir >/p </screen> <para> The "xmode" command can be used to set the printer port's @@ -107,7 +106,7 @@ the printer's current settings, type: </para> <screen> -xmode /P +xmode /p </screen> <para> To change any of these type XMODE followed by the new value. @@ -115,7 +114,7 @@ end of every line, enter: </para> <screen> -xmode /P lf; +xmode /p lf; </screen> </section> </section> @@ -141,7 +140,7 @@ procedure file), you enter the command line: </para> <screen> -LIST STARTUP +list startup </screen> <para> Some commands have two parameters. For example, the COPY command is @@ -150,24 +149,24 @@ to be the copy, for example: </para> <screen> -COPY STARTUP NEWSTARTUP +copy startup newstartup </screen> <para> Other commands have parameters which select options. For example: </para> <screen> -DIR +dir </screen> <para> shows the names of the files in the user's data directory. Normally -it simply lists the file names only, but if the "E" +it simply lists the file names only, but if the "-e" (for <emphasis>e</emphasis>ntire) option is given, it will also give complete statistics for each file such as the date and time created, size, security codes, etc. To do so enter: </para> <screen> -DIR E +dir -e </screen> <para> The DIR command also can accept a file name as a parameter which @@ -175,17 +174,17 @@ For example, to list file names in the directory sys , type: </para> <screen> -DIR SYS +dir sys </screen> <para> It is also possible to specify both a directory name parameter and the e option, such as: </para> <screen> -DIR SYS E +dir sys -e </screen> <para> -giving file names and complete statistics (See example in 3.8.1). +giving file names and complete statistics. </para> </section> @@ -195,7 +194,7 @@ This section is a summary of some commands commonly used by new or casual OS-9 users, and some common formats. Each command is followed by an example. Refer to the individual command -descriptions in Section 8 for more detailed information and +descriptions later int his book for more detailed information and additional examples. Parameters or options shown in brackets are optional. Whenever a command references a directory file name, the file <emphasis>must</emphasis> be a directory file. @@ -215,7 +214,7 @@ </screen> Deletes (destroys) the file specified. <screen> -DIR [filename] [e] [x] dir myfiles e +DIR [filename] [-e] [-x] dir myfiles -e </screen> List names of files contained in a directory. If the "x" option is used the files in the current <emphasis>execution</emphasis> @@ -261,12 +260,12 @@ <section> <title>Video Display Functions</title> <para> -The &make; Computer uses reverse video (green letters in a black box) to +The &make; uses 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> <screen> -TMODE -UPC +tmode -upc </screen> <para> The screen pause feature stops programs after 16 lines have been @@ -275,8 +274,8 @@ follows: </para> <screen> -TMODE -PAUSE turns pause mode off -TMODE PAUSE turns pause mode on +tmode -pause turns pause mode off +tmode pause turns pause mode on </screen> <para> The display system also has a complete set of commands to emulate @@ -290,13 +289,13 @@ <para> Two keys are used in combination with other keys to change their meaning. The SHIFT KEY selects between upper case and lower case -letters or punctuation, and the CLEAR key can be used to generate -control characters . +letters or punctuation, and the &ctrlkey key can be used to generate +control characters. </para> <para> The keyboard has a shift lock function similar to a typewriter's, which is normally "locked". The keyboard's shift lock may be -reversed by depressing the control key (CLEAR) and 0 keys +reversed by depressing the control key and 0 keys simultaneously. The shift lock only affects the letter (A-Z) keys. When the keyboard is locked, these keys generate upper case letters, and lower case only if the SHIFT key is depressed. When the @@ -311,9 +310,9 @@ <para> There are a number of useful control functions that can be generated from the keyboard. Many of these functions use "control -keys" which are generated by simultaneously depressing the CLEAR key +keys" which are generated by simultaneously depressing the &ctrlkey key plus some other key. For example, to generate the character for -CONTROL D press the CLEAR and D keys at the same time. +CONTROL D press the &ctrlkey and D keys at the same time. </para> <variablelist> <varlistentry>
--- a/docs/nitros9guide/chap3.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap3.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -165,7 +165,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; Computer are: +The device names used for the &make; are: </para> <informaltable frame="none"> <tgroup cols="2"> @@ -407,7 +407,7 @@ the COPY command to duplicate "file1": </para> <screen> -OS9: COPY /D1/file1 /D1/NEWDIR/file1.copy +OS9: copy /d1/file1 /d1/newdir/file1.copy </screen> <para> Observe that the second pathlist now has three names: the name of @@ -450,14 +450,14 @@ following sequence must be performed to delete a directory file: </para> <para> -1 - All file names in the directory must be deleted. +1. All file names in the directory must be deleted. </para> <para> -2 - The "attr" command is used to turn off the files directory +2. The "attr" command is used to turn off the files directory attrribute (-d option), making it an ordinary file (see 3.8). </para> <para> -3 - The file may now be deleted using the "del" command. +3. The file may now be deleted using the "del" command. </para> <para> A simpler alternative is to use the DELDIR command to automatically @@ -485,7 +485,7 @@ <itemizedlist> <listitem><para> Directories have the same ownership and security attributes -and rules as regular files. See Section 3.6. +and rules as regular files. </para></listitem> <listitem><para> The name of a given file appears in exactly one directory. @@ -584,7 +584,7 @@ ---> OS-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 (See 5.4.1). +memory must be in the current execution directory. </para> <para> ---> The data directory is used for all other file references (such @@ -630,7 +630,7 @@ directories, respectively. These command names must be followed by a pathlist that describes the new directory file. You must have permission to access the directory according to normal file security -rules (See 3.8). Here are some examples: +rules. Here are some examples: </para> <screen> OS9: chd /D1/MY.DATAFILES @@ -642,8 +642,8 @@ do for regular files, except for the last name in the pathlist must be a directory name. If the pathlist begins with a "/" , OS-9 will begin searching in the device directory for the new working -directory, otherwise searching will begin with the present directory -(See 3.6). For example, the following sequence of commands set the +directory, otherwise searching will begin with the present directory. + For example, the following sequence of commands set the working directory to the same file: </para> <screen> @@ -690,7 +690,7 @@ <entry>lists names in the working data directory's parent directory.</entry> </row> <row> -<entry>OS9: DEL ../temp</entry> +<entry>OS9: del ../temp</entry> <entry>deletes the file "temp" from the working data directory's parent directory.</entry> </row> @@ -699,8 +699,8 @@ </informaltable> <para> The substitute names refer to either the execution or data -directories, depending on the context in which they are used (See -3.7.1). For example, if ".." is used in a pathlist of a file which +directories, depending on the context in which they are used. +For example, if ".." is used in a pathlist of a file which will be loaded and/or executed, it will represent the parent directory of the execution directory. Likewise, if "." is used in a pathlist describing a program's input file, it will represent the @@ -734,20 +734,19 @@ attributes are: </para> <para> -WHITE PERMISSION FOR OWNER: If on, the owner may write to the file +WRITE PERMISSION FOR OWNER: If on, the owner may write to the file or delete it. This permission can be used to protect important files from accidental deletion or modification. </para> <para> READ PERMISSION FOR OWNER: If on, the owner is allowed to read from the file. This can be used to prevent "binary" files from -being used as "text" files (See 3.9) +being used as "text" files </para> <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 (See -3.9.4 and 5.4.1). +more valid OS-9 format memory modules in order to actually load </para> <para> The following "public permissions" work the same way as @@ -784,12 +783,12 @@ <screen> Directory of . 10:20:44 -Owner Last Modified Attributes Sector Bytecount Name ------ ------------- ---------- ------ --------- ---- - 1 81/05/29 1402 --e--e-r 47 42 file1 - 0 81/10/12 0215 ---wr-wr 48 43 file2 - 3 81/04/29 2335 -s----wr 51 22 file3 - 1 82/01/06 1619 d--wr-wr 6D 800 NEWDIR +Owner Last Modified Attributes Sector Bytecount Name +----- ----------------- ---------- ------ --------- ---- + 1 2002/05/29 14:02 --e--e-r 47 42 file1 + 0 2002/10/12 02:15 ---wr-wr 48 43 file2 + 3 2002/04/29 23:35 -s----wr 51 22 file3 + 1 2003/01/06 16:19 d--wr-wr 6D 800 NEWDIR </screen> <para> @@ -829,9 +828,9 @@ <para> The "directory" attribute behaves somewhat differently than the read, write, and execute permissions. This is because it would be -quite dangerous to be able to change directory files to normal files -(See 3.5), and creation of a directory requires special initialization -(See 3.4). Therefore, the "attr" command +quite dangerous to be able to change directory files to normal files, +and creation of a directory requires special initialization. +Therefore, the "attr" command <emphasis>cannot</emphasis> be used to turn the directory (d) attribute on (only "makdir" can), and can be used to turn it off <emphasis>only</emphasis> if the directory is empty. @@ -960,14 +959,14 @@ format that, besides the object code, includes a "module header" 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 (See 5.4.1). OS-9 does not require a "load record" +one byte more. OS-9 does not require a "load record" system commonly used by other operating systems because OS-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 -file itself must have execute permission (See 3.8) and each module +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 @@ -1030,7 +1029,7 @@ <para> Examples of this category are COBOL Indexed Sequential (ISAM) files and some special word processor file formats which allow -random access of text lines (See 3.9.2). As discussed in Sec. +random access of text lines. As discussed in Sec. 3.9.1, most OS-9 utility commands work with any file format including these special types. In general, the "dump" command is the preferred method for examining the contents of unusually formatted files.
--- a/docs/nitros9guide/chap4.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap4.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -1,7 +1,7 @@ <chapter> <title>Advanced Features of the Shell</title> <para> -The basic shell functions were introduced in Section 2 in order +The basic shell functions were introduced in a prior chapter in order to provide an understanding of how basic OS-9 commands work. In this section the more advanced capabilities of the shell are discussed. In addition to basic command line processing, the shell @@ -112,8 +112,7 @@ The verb must be the first name in the command line. After it has been scanned, the shell first checks if it is a "built-in" command. If it is, it is immediately executed. Otherwise, the shell -assumes it is a program name and attempts to locate and execute it -as described in Sections 5.3 and 5.4.1. +assumes it is a program name and attempts to locate and execute it. </para> </section> @@ -136,7 +135,7 @@ allocated the minimum amount of working RAM memory specified in the program's module header. A module header is part of all executable programs and holds the program's name, size, memory requirements, -etc. (See 5.4). Sometimes it is desirable to increase this default +etc. Sometimes it is desirable to increase this default memory size. Memory can be assigned in 256-byte pages using the modifier "#n" where n is the decimal number of pages, or in 1024 byte increments using the modifier "#nK". The two examples below @@ -178,7 +177,7 @@ </para> <para> When new processes are created, they inherit their parent process' -standard I/O paths (See 5.3). Therefore, when the shell +standard I/O paths. Therefore, when the shell creates new processes, they usually inherit its standard I/O paths. When you log-on the shell's standard input is the terminal keyboard; the standard output and error output is the terminal's display. @@ -216,7 +215,7 @@ instead of the terminal: </para> <screen> -OS9: LIST correspondence >/p +OS9: list correspondence >/p </screen> <para> Files referenced by I/O redirection modifiers are automatically @@ -232,7 +231,7 @@ from the DIR command will be displayed as shown below: </para> <screen> -OS9: LIST /D1/savelisting +OS9: list /d1/savelisting Directory of . 10:15:00 myfile savelisting file1 @@ -266,7 +265,7 @@ from the next one with a ";" character. For example: </para> <screen> -OS9: COPY myfile /D1/newfile ; DIR >/p +OS9: copy myfile /d1/newfile ; dir >/p </screen> <para> This command line will first execute the COPY command and then the @@ -288,9 +287,9 @@ </screen> <para> All programs executed sequentially are in fact separate, child -processes of the shell (See 5.3). After initiating execution of a +processes of the shell. After initiating execution of a program to be executed sequentially, the shell enters the "wait" -state (See 5.2) until execution of the called program terminates. +state until execution of the called program terminates. </para> </section> @@ -299,7 +298,7 @@ <para> The second kind of separator is the "&" which implies concurrent execution, meaning that the program is run (as a separate, child -process, see 5.3), but the shell does not wait for it to complete +process), but the shell does not wait for it to complete before processing the next command. </para> <para> @@ -311,7 +310,7 @@ Here is an example: </para> <screen> -OS9: DIR >/P& +OS9: dir >/p& &007 OS9: @@ -326,7 +325,7 @@ another example: </para> <screen> -OS9: DIR >/P& LIST file1& COPY file1 file2 ; DEL temp +OS9: dir >/p& list file1& copy file1 file2 ; del temp </screen> <para> @@ -440,7 +439,7 @@ ARCHIVE: </para> <screen> -OS9: chd /d0/WORKING; dsave ! (chd /d0/ARCHIVE) +OS9: chd /d0/WORKING; dsave /d0/ARCHIVE ! shell -p </screen> </section> @@ -467,12 +466,12 @@ <row> <entry>chd <replaceable>pathlist</replaceable></entry> <entry>change the working data directory to the directory -specified by the pathlist (see 3.6).</entry> +specified by the pathlist.</entry> </row> <row> <entry>chx <replaceable>pathlist</replaceable></entry> <entry>change the working execution directory to the -directory specified by the pathlist (see 3.6).</entry> +directory specified by the pathlist.</entry> </row> <row> <entry>ex name</entry> @@ -495,7 +494,7 @@ </row> <row> <entry>setpr <replaceable>proc ID</replaceable> <replaceable>priority</replaceable></entry> -<entry>changes process' priority (see 5.1).</entry> +<entry>changes process' priority.</entry> </row> <row> <entry>x</entry> @@ -503,7 +502,7 @@ </row> <row> <entry>-x</entry> -<entry>causes shell not to abort on error (See 4.7)</entry> +<entry>causes shell not to abort on error</entry> </row> <row> <entry>p</entry> @@ -542,7 +541,7 @@ 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 -input and output (see 4.2.3). specifically, it requests command +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. </para> @@ -551,7 +550,7 @@ means of the "shell" command. If the standard input path is redirected to a mass storage file, the new "incarnation" of the shell can accept and execute command lines from the file instead of -a terminal keyboard. The text file (see 3.9.2) to be processed is +a terminal keyboard. The text file to be processed is called a "procedure file". It contains one or more command lines that are identical to command lines that are manually entered from the keyboard. This technique is sometimes called "batch" or @@ -561,7 +560,7 @@ If the <replaceable>program name</replaceable> specified on a shell command line can not be found in memory or in the execution directory, shell will search the data directory for a file with the desired name. If one is found, -shell will automatically execute it as a procedure file (see 2.0). +shell will automatically execute it as a procedure file. </para> <para> Execution of procedure files have a number of valuable @@ -597,8 +596,7 @@ </screen> <para> OS-9 does not have any constraints on the number of jobs that can be -simultaneously executed as long as there is memory available (see -5.4). Also, the procedure files can themselves cause sequential or +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 redirection of each shell's output to files: @@ -627,18 +625,18 @@ this manual. If desired, the "printerr" command can be executed, which replaces the smaller, built-in error display routine with a larger (and slower) routine that looks up descriptive error messages -from a text file called "/d0/sys/errmsg". +from a text file called "/dd/sys/errmsg". Once the "printerr" command has been run it cannot be turned off. Also, its effect is system-wide. </para> <para> -Programs called by the shell can return an error code in the MPU +Programs called by the shell can return an error code in the CPU's "B" register (otherwise B should be cleared) upon termination. This type of error, as well as errors detected by the shell itself, will cause an error message to be displayed and processing of the command line or procedure file to be terminated unless the "-x" built-in -command has been previously executed (See 4.5). +command has been previously executed. </para> </section> @@ -646,7 +644,7 @@ <title>Running Compiled Intermediate Code Programs</title> <para> Before the shell executes a program, it checks the program -module's language type. If its type is not 6809 machine language, +module's language type. If its type is not &CPU machine language, shell will call the appropriate run-time system for that module. Versions of the shell supplied for various systems are capable of calling different run-time systems. Most versions of shell call @@ -655,11 +653,11 @@ runtime system (RunC). </para> <para> -For example, if you wanted to run a BASIC09 I-code module called +For example, if you wanted to run a Basic09 I-code module called "adventure", you could type the command given below: </para> <screen> -OS9: BASIC09 adventure +OS9: basic09 adventure </screen> <para> Or you could accomplish the same thing by typing the following: @@ -703,7 +701,7 @@ </programlisting> <para> NOTE: This LOGIN procedure will not work until a password file -called "/D0/SYS/PASSWORD" has been created. For more information, +called "/DD/SYS/PASSWORD" has been created. For more information, please see the LOGIN command description. </para> <para>
--- a/docs/nitros9guide/chap5.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap5.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -170,14 +170,14 @@ 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 -the same name (see 5.4.1). +the same name. </para></listitem> <listitem><para> PARAMETERS, which is data specified by the parent to be passed to and used by the new process. This data is copied to part of the child process' memory area. Parameters are frequently used to pass file names, initialization values, etc. -The shell, passes command line parameters this way (see 4.1). +The shell, passes command line parameters this way. </para></listitem> </itemizedlist> <para> @@ -191,18 +191,18 @@ (this is not the same as the "process ID", which identifies a specific process) . This number is usually obtained from the system password file when a user logs on. The system manager -always is user number zero (see 3.8). +always is user number zero. </para></listitem> <listitem><para> STANDARD INPUT AND OUTPUT PATHS: the three paths (input, output, and error/status) used for routine input and output. Note that most paths (files) may be shared simultaneously by -two or more processes (see 4.2.2). The two current working +two or more processes. The two current working directories are also inherited. </para></listitem> <listitem><para> PROCESS PRIORITY which determines what proportion of CPU -time the process receives with respect to others (see 5.1). +time the process receives with respect to others. </para></listitem> </itemizedlist> <para> @@ -212,7 +212,7 @@ <listitem><para> A PROCESS ID: a number from 1 to 255, which is used to identify specific processes. Each process has a unique process -ID number (see 4.3.2). +ID number. </para></listitem> <listitem><para> MEMORY: enough memory required for the new process to run. @@ -221,7 +221,7 @@ space. A "data area", used for the program's parameters, variables, and stack is allocated for the process' exclusive use. A second memory area may also be required to load the -program (primary module) if it is not resident in memory (see 5.4).. +program (primary module) if it is not resident in memory. </para></listitem> </itemizedlist> <para> @@ -295,7 +295,7 @@ When performing a fork operation, OS-9's first step is to attempt to locate the requested program module by searching the "module directory", which has the address of every module present in memory. -The 6809 instruction set supports a type of program called +The &CPU instruction set supports a type of program called "reentrant code" which means the exact same "copy" of a program can be shared by two or more different processes simultaneously without affecting each other, provided that each "incarnation" of the @@ -315,7 +315,7 @@ <para> If the requested program module is not already in memory, the name is used as a pathlist (file name) and an attempt is made to -load the program from mass storage (see 3.9.4). +load the program from mass storage. </para> <para> Every program module has a "module header" that describes the @@ -400,13 +400,13 @@ specific, predetermined memory addresses to work correctly, and can therefore be loaded at different memory addresses at different times. PIC programs require special types of machine language instructions -which few computers have. The ability of the 6809 +which few computers have. The ability of the &CPU microprocessor to use this type of program is one of its most powerful features. </para> <para> The "load" command can therefore be used two or more times (or a -single file may contain several memory modules, see 3.9.4), and each +single file may contain several memory modules), and each program module will be automatically loaded at different, non-overlapping addresses (most other operating systems write over the previous program's memory whenever a new program is loaded). This
--- a/docs/nitros9guide/chap6.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap6.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -19,7 +19,7 @@ </para> <section> -<title>The OS9BOOT File</title> +<title>The OS9Boot File</title> <para> The file called "OS9Boot" loaded into RAM memory by the @@ -34,10 +34,18 @@ <colspec colwidth="3.5in"/> <tbody> <row> - <entry>IOMAN</entry> + <entry>OS9P2</entry> + <entry>OS-9 Kernel, Part 2</entry> + </row> + <row> + <entry>IOMan</entry> <entry>OS-9 Input/Output Manager</entry> </row> <row> + <entry>Init</entry> + <entry>Initialization Data Module</entry> + </row> + <row> <entry>RBF</entry> <entry>Random Block (disk) File Manager</entry> </row> @@ -46,47 +54,55 @@ <entry>Sequential Character (terminal) File Manager</entry> </row> <row> - <entry>Pipeman</entry> - <entry>Pipeline File Manager</entry> + <entry>PipeMan</entry> + <entry>Pipe File Manager</entry> </row> <row> <entry>Piper</entry> - <entry>Pipeline Driver</entry> + <entry>Pipe Driver</entry> </row> <row> <entry>Pipe</entry> - <entry>Pipeline Device Descriptor</entry> + <entry>Pipe Device Descriptor</entry> + </row> + <row> + <entry>CC3IO</entry> + <entry>CoCo 3 Keyboard/Video Device Driver</entry> + </row> + <row> + <entry>WindInt</entry> + <entry>CoCo 3 Graphics Co-Module</entry> </row> <row> - <entry>KBDVID</entry> - <entry>Keyboard/video/Graphics Device Driver</entry> + <entry>VDGInt</entry> + <entry>CoCo 2 Compatible Graphics Co-Module</entry> + </row> + <row> + <entry>Term</entry> + <entry>Terminal Device Descriptor</entry> </row> <row> - <entry>PRINTER</entry> + <entry>CC3Disk</entry> + <entry>CoCo 3 Disk Driver</entry> + </row> + <row> + <entry>DD, D0, D1</entry> + <entry>Disk Device Descriptors</entry> + </row> + <row> + <entry>Printer</entry> <entry>Printer Device Driver</entry> </row> <row> - <entry>DDISK</entry> - <entry>Disk Driver</entry> - </row> - <row> - <entry>D0, D1</entry> - <entry>Disk Device Descriptor</entry> - </row> - <row> - <entry>TERM</entry> - <entry>Terminal Device Descriptor</entry> - </row> - <row> - <entry>P</entry> + <entry>p</entry> <entry>Printer Device Descriptor</entry> </row> <row> - <entry>CLOCK</entry> + <entry>Clock</entry> <entry>Real-Time Clock Module</entry> </row> <row> - <entry>SYSGO</entry> + <entry>CC3Go</entry> <entry>System Startup Process</entry> </row> </tbody> @@ -120,7 +136,7 @@ </row> <row> <entry>errmsg</entry> -<entry>the error message file (see 4.7)</entry> +<entry>the error message file</entry> </row> </tbody> </tgroup> @@ -137,7 +153,7 @@ <title>The Startup File</title> <para> -The file "/d0/startup" is a shell procedure file (see 4.6) which +The file "/d0/startup" is a shell procedure file which is automatically processed immediately after system startup. The user may include in "startup" any legal shell command line. Often this will include "setime" to start the system clock. If this file @@ -152,7 +168,7 @@ <para> The directory "/d0/CMDS" is the system-wide command object code directory, which is normally shared by all users as their working -execution directory (see 3.7). If "shell" is not part of the +execution directory. If "shell" is not part of the "OS9Boot" file, it must be present in this directory. The system startup process "sysgo" makes CMDS the initial execution directory. </para>
--- a/docs/nitros9guide/chap7.chapter Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/chap7.chapter Tue Mar 04 15:11:34 2003 +0000 @@ -81,10 +81,8 @@ &attrref; &backupref; -&basic09ref; &binexref; &buildref; -&ccref; &chdref; &cmpref; &cobblerref; @@ -109,7 +107,6 @@ &exmoderef; &formatref; &freeref; -&go51ref; &helpref; &identref; &inizref; @@ -124,7 +121,6 @@ &mergeref; &mfreeref; &os9genref; -&printerrref; &procsref; &pwdref; &renameref;
--- a/docs/nitros9guide/config.refentry Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/config.refentry Tue Mar 04 15:11:34 2003 +0000 @@ -151,7 +151,7 @@ </para> <para> When the driver selection is complete, a screen prompt requests that you -select among the &make; Computer terminal I/O subroutines. Select these +select among the &make; terminal I/O subroutines. Select these subroutines in the same manner that you selected the device drivers. You have the following modules from which to make your selections: </para>
--- a/docs/nitros9guide/cputype.refentry Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/cputype.refentry Tue Mar 04 15:11:34 2003 +0000 @@ -1,7 +1,7 @@ <refentry id="cputype"> <refnamediv> <refname>CPUTYPE</refname> -<refpurpose>Identify 6809 or 6309</refpurpose> +<refpurpose>Identify the CPU</refpurpose> </refnamediv> <refsynopsisdiv> @@ -12,7 +12,7 @@ <refsect1><title>Description</title> <para> -Identify 6809 or 6309 +Identifies the CPU as 6809 or 6309. </para> </refsect1> <refsect1><title>Examples</title>
--- a/docs/nitros9guide/devs.refentry Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/devs.refentry Tue Mar 04 15:11:34 2003 +0000 @@ -7,13 +7,12 @@ <refsynopsisdiv> <cmdsynopsis> <command>DEVS</command> -<arg choice="opt">-?</arg> </cmdsynopsis> </refsynopsisdiv> <refsect1><title>Description</title> <para> -Show device table entries +Show device table entries. </para> </refsect1> </refentry>
--- a/docs/nitros9guide/display.appendix Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/display.appendix Tue Mar 04 15:11:34 2003 +0000 @@ -1,23 +1,22 @@ <appendix> -<title>Display System Functions</title> +<title>VDG Display System Functions</title> <section> -<title>The Video Display</title> +<title>The Video Display Generator</title> <para> -&vendor; OS-9 allows the video display to be used in +&os9level 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 "PRINT" in BASIC). The &make; -Computer's Basic09 +output statements (such as "PRINT" in BASIC). The &make;'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 ("Alpha") mode and Graphics mode. The Alphanumeric mode also -includes "semigraphic" box-graphics. The &make; Computer's display +includes "semigraphic" box-graphics. The &make;'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 @@ -86,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 "Semigraphic 6" graphics -box. See the &make; Computer manual for an explanation of semigraphics +box. See the &make; manual for an explanation of semigraphics functions. </para> @@ -442,7 +441,7 @@ <section> <title>Get Status Commands</title> <para> -The &make; Computer I/O driver includes OS-9 Get Status +The &make; 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/intro.preface Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/intro.preface Tue Mar 04 15:11:34 2003 +0000 @@ -2,11 +2,11 @@ <title>Welcome to OS-9!</title> <titleabbrev>Introduction</titleabbrev> <para> -The heart of your &make; Computer is an amazing device: the -6809 microprocessor chip. This advanced microcomputer can run the +The heart of your &make; is an amazing device: the +&CPU microprocessor chip. This advanced microcomputer can run the kind of sophisticated software normally found only on much larger and costly computers. Because the OS-9 operating system was designed -by the same people who designed the 6809 microcomputer, together +by the same people who designed the 6809 microprocessor, together they provide an extremely efficient and powerful combination. </para> <para> @@ -26,7 +26,7 @@ <para> OS-9's overall structure was based on the famous UNIX<footnote id="unixdesc"> <para> -Unix is an operating system designed by Bell Telephone +UNIX is an operating system designed by Bell Telephone Laboratories, which is becoming widely recognized as a standard for mini and micro operating systems because of its versatility and elegant structure. @@ -44,7 +44,7 @@ </para> <orderedlist numeration="arabic"> -<listitem><para>Friendly Unix<footnoteref linkend="unixdesc"/>-type +<listitem><para>Friendly UNIX-like user interface and environment</para></listitem> <listitem><para>Multiuser/Multitasking Real-Time Operating System</para></listitem> @@ -63,7 +63,7 @@ <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; Computer and make it so much easier to use +capability of your &make; and make it so much easier to use in almost any application. </para> <para>
--- a/docs/nitros9guide/makefile Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/makefile Tue Mar 04 15:11:34 2003 +0000 @@ -1,26 +1,43 @@ -BOOK = os9guide +BOOKL1 = os9l1guide +BOOKL2 = os9l2guide STYLESHEET = docbook-utils.dsl -all: $(BOOK).pdf +all: $(BOOKL1).pdf $(BOOKL2).pdf + +$(BOOKL1).pdf: $(BOOKL1).docbook $(SRCS) + docbook2pdf -d docbook-utils-a4.dsl#print $(BOOKL1).docbook + +$(BOOKL2).pdf: $(BOOKL2).docbook $(SRCS) + docbook2pdf -d docbook-utils-a4.dsl#print $(BOOKL2).docbook -$(BOOK).pdf: $(BOOK).docbook $(SRCS) - docbook2pdf -d docbook-utils-a4.dsl#print $(BOOK).docbook +$(BOOKL1).ps: $(BOOKL1).docbook $(SRCS) + docbook2ps -d docbook-utils-a4.dsl#print $(BOOKL1).docbook +# docbook2ps -d $(STYLESHEET) $(BOOKL1).docbook -$(BOOK).ps: $(BOOK).docbook $(SRCS) - docbook2ps -d docbook-utils-a4.dsl#print $(BOOK).docbook -# docbook2ps -d $(STYLESHEET) $(BOOK).docbook +$(BOOKL2).ps: $(BOOKL2).docbook $(SRCS) + docbook2ps -d docbook-utils-a4.dsl#print $(BOOKL2).docbook +# docbook2ps -d $(STYLESHEET) $(BOOKL2).docbook -$(BOOK).html: $(BOOK).docbook $(SRCS) +$(BOOKL1).html: $(BOOKL1).docbook $(SRCS) $(RM) *.htm *.html -# jade -t sgml -V html-index -d /usr/share/sgml/docbook/dsssl-stylesheets-1.64/html/docbook.dsl $(BOOK).docbook +# 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 docbook-utils-a4.dsl#html $(BOOK).docbook + docbook2html -d docbook-utils-a4.dsl#html $(BOOKL1).docbook -print: $(BOOK).ps - psnup -2 $(BOOK).ps | lpr +$(BOOKL2).html: $(BOOKL2).docbook $(SRCS) + $(RM) *.htm *.html +# jade -t sgml -V html-index -d /usr/share/sgml/docbook/dsssl-stylesheets-1.64/html/docbook.dsl $(BOOKL2).docbook +# collateindex.pl -p -o index.docbook HTML.index + docbook2html -d docbook-utils-a4.dsl#html $(BOOKL2).docbook + +print: $(BOOKL1).ps $(BOOKL2).ps + psnup -2 $(BOOKL1).ps | lpr + psnup -2 $(BOOKL2).ps | lpr clean: - $(RM) *.htm *.html $(BOOK).pdf $(BOOK).ps + $(RM) *.htm *.html $(BOOKL1).pdf $(BOOKL1).ps $(BOOKL2).pdf \ + $(BOOKL2).ps + SRCS = $(CHAPS) $(APXS) $(REFS) CHAPS = intro.preface \ chap1.chapter chap2.chapter chap3.chapter chap4.chapter \
--- a/docs/nitros9guide/tuneport.refentry Tue Mar 04 15:06:11 2003 +0000 +++ b/docs/nitros9guide/tuneport.refentry Tue Mar 04 15:11:34 2003 +0000 @@ -1,7 +1,7 @@ <refentry id="tuneport"> <refnamediv> <refname>TUNEPORT</refname> -<refpurpose>Tune the printer port on the &make; Computer</refpurpose> +<refpurpose>Tune the printer port on the &make;</refpurpose> </refnamediv> <refsynopsisdiv>