Mercurial > hg > Members > kono > nitros9-code

changeset 992:1b5656126ac6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use <errorcode> where appropiate
author roug
date Sun, 23 Feb 2003 14:53:55 +0000
parents 0502363c6fa7
children 57b5e715a417
files docs/ReadMe docs/ccguide/chap1.chapter docs/nitros9guide/errorcodes.appendix docs/os9sysprog/os9sysprog.docbook
diffstat 4 files changed, 233 insertions(+), 126 deletions(-) [+]
line wrap: on
line diff
--- a/docs/ReadMe	Fri Feb 21 21:40:53 2003 +0000
+++ b/docs/ReadMe	Sun Feb 23 14:53:55 2003 +0000
@@ -10,6 +10,16 @@
 a text-based format, so it is possible to reverse-engineer and convert
 the format.
 
+Docbook is in a transition from an SGML-based format to XML. The two formats are
+not compatible. Primary differences are that the DTD is different. For SGML it is
+     <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+and for XML it is
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+  "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
+Furthermore, some elements are terminated with /, such as <void/>, <colspec/> etc.
+
+DOCBOOK SGML SOFTWARE:
+---------------------
 To create HTML, PDF or PostScript you must have these RPMs installed on
 your RedHat system:
 
@@ -20,9 +30,14 @@
 tetex-dvips
 tetex
 jadetex
+..see also http://sources.redhat.com/docbook-tools/
+
+DocBook Install mini-HOWTO: http://www.tldp.org/HOWTO/mini/DocBook-Install/
+
+Another approach is the xmlto application installed on newer RedHat systems.
 
 DOCBOOK REFERENCES:
-
+-------------------
   The Duck book
     http://www.docbook.org/
 
@@ -31,3 +46,6 @@
 
   The Crash Course to Docbook
     http://www.caldera.de/~eric/crash-course/HTML/index.html
+
+  Mark Galassi's tutorial/introduction to writing in DocBook.
+    http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html
--- a/docs/ccguide/chap1.chapter	Fri Feb 21 21:40:53 2003 +0000
+++ b/docs/ccguide/chap1.chapter	Sun Feb 23 14:53:55 2003 +0000
@@ -598,7 +598,7 @@
 <section>
 <title>Running the Compiler</title>
 <para>
-The are two commands which inlvoke distinct versions of the
+The are two commands which invoke distinct versions of the
 compiler. "cc1" is for OS-9 Level I which uses a two pass compiler,
 and, "cc2" is for Level II which causes a single pass version. Both
 versions of the compiler works identically, the main difference is
--- a/docs/nitros9guide/errorcodes.appendix	Fri Feb 21 21:40:53 2003 +0000
+++ b/docs/nitros9guide/errorcodes.appendix	Sun Feb 23 14:53:55 2003 +0000
@@ -22,165 +22,202 @@
 <row>
  <entry>$C8</entry>
  <entry>200</entry>
- <entry>PATH TABLE FULL - The file cannot be opened because
+ <entry><errorname>PATH TABLE FULL</errorname>
+ - The file cannot be opened because
  the system path table is currently full.</entry></row>
 <row>
  <entry>$C9</entry>
  <entry>201</entry>
- <entry>ILLEGAL PATH NUMBER - Number too large or for non-existant path.</entry></row>
+ <entry><errorname>ILLEGAL PATH NUMBER</errorname>
+ - Number too large or for non-existant path.</entry></row>
 <row>
  <entry>$CA</entry>
  <entry>202</entry>
- <entry>INTERRUPT POLLING TABLE FULL</entry></row>
+ <entry><errorname>INTERRUPT POLLING TABLE FULL</errorname></entry></row>
 <row>
  <entry>$CB</entry>
  <entry>203</entry>
- <entry>ILLEGAL MODE - attempt to perform I/O function of which the device or file is incapable.</entry></row>
+ <entry><errorname>ILLEGAL MODE</errorname>
+ - attempt to perform I/O function of which the device or file is incapable.</entry></row>
 <row>
  <entry>$CC</entry>
  <entry>204</entry>
- <entry>DEVICE TABLE FULL - Can't add another device</entry></row>
+ <entry><errorname>DEVICE TABLE FULL</errorname>
+ - Can't add another device</entry></row>
 <row>
  <entry>$CD</entry>
  <entry>205</entry>
- <entry>ILLEGAL MODULE HEADER - module not loaded because its
+ <entry><errorname>ILLEGAL MODULE HEADER</errorname>
+ - module not loaded because its
  sync code, header parity, or CRC is incorrect.</entry></row>
 <row>
  <entry>$CE</entry>
  <entry>206</entry>
- <entry>MODULE DIRECTORY FULL - Can't add another module</entry></row>
+ <entry><errorname>MODULE DIRECTORY FULL</errorname>
+ - Can't add another module</entry></row>
 <row>
  <entry>$CF</entry>
  <entry>207</entry>
- <entry>MEMORY FULL - Level One: not enough contiquous RAM free.
+ <entry><errorname>MEMORY FULL</errorname>
+ - Level One: not enough contiquous RAM free.
  Level Two: process address space full</entry></row>
 <row>
  <entry>$D0</entry>
  <entry>208</entry>
- <entry>ILLEGAL SERVICE REQUEST - System call had an illegal code number.</entry></row>
+ <entry><errorname>ILLEGAL SERVICE REQUEST</errorname>
+ - System call had an illegal code number.</entry></row>
 <row>
  <entry>$D1</entry>
  <entry>209</entry>
- <entry>MODULE BUSY - non-sharable module is in use by another process.</entry></row>
+ <entry><errorname>MODULE BUSY</errorname>
+ - non-sharable module is in use by another process.</entry></row>
 <row>
  <entry>$D2</entry>
  <entry>210</entry>
- <entry>BOUNDARY ERROR - Memory allocation or deallocation request not on a page boundary.</entry></row>
+ <entry><errorname>BOUNDARY ERROR</errorname>
+ - Memory allocation or deallocation request not on a page boundary.</entry></row>
 <row>
  <entry>$D3</entry>
  <entry>211</entry>
- <entry>END OF FILE - End of file encountered on read.</entry></row>
+ <entry><errorname>END OF FILE</errorname>
+ - End of file encountered on read.</entry></row>
 <row>
  <entry>$D4</entry>
  <entry>212</entry>
- <entry>RETURNING NON-ALLOCATED MEMORY - 
-attempted to deallocate memory not previously assigned.</entry></row>
+ <entry><errorname>RETURNING NON-ALLOCATED MEMORY</errorname>
+ - attempted to deallocate memory not previously assigned.</entry></row>
 <row>
  <entry>$D5</entry>
  <entry>213</entry>
- <entry>NON-EXISTING SEGMENT - device has damaged file structure.</entry></row>
+ <entry><errorname>NON-EXISTING SEGMENT</errorname>
+ - device has damaged file structure.</entry></row>
 <row>
  <entry>$D6</entry>
  <entry>214</entry>
- <entry>NO PERMISSION - file attributes do not permit access requested.</entry></row>
+ <entry><errorname>NO PERMISSION</errorname>
+ - file attributes do not permit access requested.</entry></row>
 <row>
  <entry>$D7</entry>
  <entry>215</entry>
- <entry>BAD PATH NAME - syntax error in pathlist (illegal character, etc.).</entry></row>
+ <entry><errorname>BAD PATH NAME</errorname>
+ - syntax error in pathlist (illegal character, etc.).</entry></row>
 <row>
  <entry>$D8</entry>
  <entry>216</entry>
- <entry>PATH NAME NOT FOUND - can't find pathlist specified.</entry></row>
+ <entry><errorname>PATH NAME NOT FOUND</errorname>
+ - can't find pathlist specified.</entry></row>
 <row>
  <entry>$D9</entry>
  <entry>217</entry>
- <entry>SEGMENT LIST FULL - file is too fragmented to be expanded further.</entry></row>
+ <entry><errorname>SEGMENT LIST FULL</errorname>
+ - file is too fragmented to be expanded further.</entry></row>
 <row>
  <entry>$DA</entry>
  <entry>218</entry>
- <entry>FILE ALREADY EXISTS - file name already appears in current directory.</entry></row>
+ <entry><errorname>FILE ALREADY EXISTS</errorname>
+ - file name already appears in current directory.</entry></row>
 <row>
  <entry>$DB</entry>
  <entry>219</entry>
- <entry>ILLEGAL BLOCK ADDRESS - device's file structure has been damaged.</entry></row>
+ <entry><errorname>ILLEGAL BLOCK ADDRESS</errorname>
+ - device's file structure has been damaged.</entry></row>
 <row>
  <entry>$DC</entry>
  <entry>220</entry>
- <entry>ILLEGAL BLOCK SIZE - device's file structure has been damaged.</entry></row>
+ <entry><errorname>ILLEGAL BLOCK SIZE</errorname>
+ - device's file structure has been damaged.</entry></row>
 <row>
  <entry>$DD</entry>
  <entry>221</entry>
- <entry>MODULE NOT FOUND - request for link to module not found in directory.</entry></row>
+ <entry><errorname>MODULE NOT FOUND</errorname>
+ - request for link to module not found in directory.</entry></row>
  <row>
  <entry>$DE</entry>
  <entry>222</entry>
- <entry>SECTOR OUT OF RANGE - device file structure damaged or
+ <entry><errorname>SECTOR OUT OF RANGE</errorname>
+ - device file structure damaged or
 incorrectly formatted.</entry></row>
 <row>
  <entry>$DF</entry>
  <entry>223</entry>
- <entry>SUICIDE ATTEMPT - request to return memory where your stack is located.</entry></row>
+ <entry><errorname>SUICIDE ATTEMPT</errorname>
+ - request to return memory where your stack is located.</entry></row>
 <row>
  <entry>$E0</entry>
  <entry>224</entry>
- <entry>ILLEGAL PROCESS NUMBER - no such process exists.</entry></row>
+ <entry><errorname>ILLEGAL PROCESS NUMBER</errorname>
+ - no such process exists.</entry></row>
 <row>
  <entry>$E2</entry>
  <entry>226</entry>
- <entry>NO CHILDREN - can't wait because process has no children.</entry></row>
+ <entry><errorname>NO CHILDREN</errorname>
+ - can't wait because process has no children.</entry></row>
 <row>
  <entry>$E3</entry>
  <entry>227</entry>
- <entry>ILLEGAL SWI CODE - must be 1 to 3.</entry></row>
+ <entry><errorname>ILLEGAL SWI CODE</errorname>
+ - must be 1 to 3.</entry></row>
 <row>
  <entry>$E4</entry>
  <entry>228</entry>
- <entry>PROCESS ABORTED - process aborted by signal code 2.</entry></row>
+ <entry><errorname>PROCESS ABORTED</errorname>
+ - process aborted by signal code 2.</entry></row>
 <row>
  <entry>$E5</entry>
  <entry>229</entry>
- <entry>PROCESS TABLE FULL - can't fork now.</entry></row>
+ <entry><errorname>PROCESS TABLE FULL</errorname>
+ - can't fork now.</entry></row>
 <row>
  <entry>$E6</entry>
  <entry>230</entry>
- <entry>ILLEGAL PARAMETER AREA - high and low bounds passed in fork call are incorrect.</entry></row>
+ <entry><errorname>ILLEGAL PARAMETER AREA</errorname>
+ - high and low bounds passed in fork call are incorrect.</entry></row>
 <row>
  <entry>$E7</entry>
  <entry>231</entry>
- <entry>KNOWN MODULE - for internal use only.</entry></row>
+ <entry><errorname>KNOWN MODULE</errorname>
+ - for internal use only.</entry></row>
 <row>
  <entry>$E8</entry>
  <entry>232</entry>
- <entry>INCORRECT MODULE CRC - module has bad CRC value.</entry></row>
+ <entry><errorname>INCORRECT MODULE CRC</errorname>
+ - module has bad CRC value.</entry></row>
 <row>
  <entry>$E9</entry>
  <entry>233</entry>
- <entry>SIGNAL ERROR - receiving process has previous
+ <entry><errorname>SIGNAL ERROR</errorname>
+ - receiving process has previous
 unprocessed signal pending.</entry></row>
 <row>
  <entry>$EA</entry>
  <entry>234</entry>
- <entry>NON-EXISTENT MODULE - unable to locate module.</entry></row>
+ <entry><errorname>NON-EXISTENT MODULE</errorname>
+ - unable to locate module.</entry></row>
 <row>
  <entry>$EB</entry>
  <entry>235</entry>
- <entry>BAD NAME - illegal name syntax</entry></row>
+ <entry><errorname>BAD NAME</errorname>
+ - illegal name syntax</entry></row>
 <row>
  <entry>$EC</entry>
  <entry>236</entry>
- <entry>BAD HEADER - module header parity incorrect</entry></row>
+ <entry><errorname>BAD HEADER</errorname>
+ - module header parity incorrect</entry></row>
 <row>
  <entry>$ED</entry>
  <entry>237</entry>
- <entry>RAM FULL - no free system RAM available at this time</entry></row>
+ <entry><errorname>RAM FULL</errorname>
+ - no free system RAM available at this time</entry></row>
 <row>
  <entry>$EE</entry>
  <entry>238</entry>
- <entry>UNKNOWN PROCESS ID - incorrect process ID number</entry></row>
+ <entry><errorname>UNKNOWN PROCESS ID</errorname>
+ - incorrect process ID number</entry></row>
 <row>
  <entry>$EF</entry>
  <entry>239</entry>
- <entry>NO TASK NUMBER AVAILABLE - all task numbers in use</entry></row>
+ <entry><errorname>NO TASK NUMBER AVAILABLE</errorname>
+ - all task numbers in use</entry></row>
 </tbody>
 </tgroup>
 </informaltable>
@@ -203,62 +240,76 @@
 <row>
  <entry>$F0</entry>
  <entry>240</entry>
- <entry>UNIT ERROR - device unit does not exist.</entry></row>
+ <entry><errorname>UNIT ERROR</errorname>
+ - device unit does not exist.</entry></row>
 <row>
  <entry>$F1</entry>
  <entry>241</entry>
- <entry>SECTOR ERROR - sector number is out of range.</entry></row>
+ <entry><errorname>SECTOR ERROR</errorname>
+ - sector number is out of range.</entry></row>
 <row>
  <entry>$F2</entry>
  <entry>242</entry>
- <entry>WRITE PROTECT - device is write protected.</entry></row>
+ <entry><errorname>WRITE PROTECT</errorname>
+ - device is write protected.</entry></row>
 <row>
  <entry>$F3</entry>
  <entry>243</entry>
- <entry>CRC ERROR - CRC error on read or write verify.</entry></row>
+ <entry><errorname>CRC ERROR</errorname>
+ - CRC error on read or write verify.</entry></row>
 <row>
  <entry>$F4</entry>
  <entry>244</entry>
- <entry>READ ERROR - Data transfer error during disk read
+ <entry><errorname>READ ERROR</errorname>
+ - Data transfer error during disk read
  operation, or SCF (terminal) input buffer overrun.</entry></row>
 <row>
  <entry>$F5</entry>
  <entry>245</entry>
- <entry>WRITE ERROR - hardware error during disk write operation.</entry></row>
+ <entry><errorname>WRITE ERROR</errorname>
+ - hardware error during disk write operation.</entry></row>
 <row>
  <entry>$F6</entry>
  <entry>246</entry>
- <entry>NOT READY - device has "not ready" status.</entry></row>
+ <entry><errorname>NOT READY</errorname>
+ - device has "not ready" status.</entry></row>
 <row>
  <entry>$F7</entry>
  <entry>247</entry>
- <entry>SEEK ERROR - physical seek to non-existant sector.</entry></row>
+ <entry><errorname>SEEK ERROR</errorname>
+ - physical seek to non-existant sector.</entry></row>
 <row>
  <entry>$F8</entry>
  <entry>248</entry>
- <entry>MEDIA FULL - insufficient free space on media.</entry></row>
+ <entry><errorname>MEDIA FULL</errorname>
+ - insufficient free space on media.</entry></row>
 <row>
  <entry>$F9</entry>
  <entry>249</entry>
- <entry>WRONG TYPE - attempt to read incompatible media (i.e.
+ <entry><errorname>WRONG TYPE</errorname>
+ - attempt to read incompatible media (i.e.
  attempt to read double-side disk on single-side drive)</entry></row>
 <row>
  <entry>$FA</entry>
  <entry>250</entry>
- <entry>DEVICE BUSY - non-sharable device is in use</entry></row>
+ <entry><errorname>DEVICE BUSY</errorname>
+ - non-sharable device is in use</entry></row>
 <row>
  <entry>$FB</entry>
  <entry>251</entry>
- <entry>DISK ID CHANGE - Media was changed with files open</entry></row>
+ <entry><errorname>DISK ID CHANGE</errorname>
+ - Media was changed with files open</entry></row>
 <row>
  <entry>$FC</entry>
  <entry>252</entry>
- <entry>RECORD IS LOCKED-OUT - Another process is accessing the 
+ <entry><errorname>RECORD IS LOCKED-OUT</errorname>
+ - Another process is accessing the 
 requested record.</entry></row>
 <row>
  <entry>$FD</entry>
  <entry>253</entry>
- <entry>NON-SHARABLE FILE BUSY - Another process is accessing the
+ <entry><errorname>NON-SHARABLE FILE BUSY</errorname>
+ - Another process is accessing the
 requested file.</entry></row>
 </tbody>
 </tgroup>
--- a/docs/os9sysprog/os9sysprog.docbook	Fri Feb 21 21:40:53 2003 +0000
+++ b/docs/os9sysprog/os9sysprog.docbook	Sun Feb 23 14:53:55 2003 +0000
@@ -8663,21 +8663,9 @@
   <entry></entry>
 </row>
 <row>
-  <entry>103F 28</entry>
-  <entry>F$SRqMem</entry>
-  <entry>System Memory Request </entry>
-  <entry></entry>
-</row>
-<row>
-  <entry>103F 29</entry>
-  <entry>F$SRtMemEM</entry>
-  <entry>System memory request</entry>
-  <entry></entry>
-</row>
-<row>
   <entry>103F 29</entry>
   <entry>F$SRtMem</entry>
-  <entry>System Memory Return </entry>
+  <entry>System memory return</entry>
   <entry></entry>
 </row>
 <row>
@@ -8706,7 +8694,7 @@
 </row>
 <row>
   <entry>103F 2E</entry>
-  <entry>F$VModulUL</entry>
+  <entry>F$VModul</entry>
   <entry>Validate module</entry>
   <entry></entry>
 </row>
@@ -9229,165 +9217,203 @@
 <row>
  <entry>$C8</entry>
  <entry>200</entry>
- <entry>PATH TABLE FULL - The file cannot be opened because
+ <entry><errorname>PATH TABLE FULL</errorname>
+ - The file cannot be opened because
  the system path table is currently full.</entry></row>
 <row>
  <entry>$C9</entry>
  <entry>201</entry>
- <entry>ILLEGAL PATH NUMBER - Number too large or for non-existant path.</entry></row>
+ <entry><errorname>ILLEGAL PATH NUMBER</errorname>
+ - Number too large or for non-existant path.</entry></row>
 <row>
  <entry>$CA</entry>
  <entry>202</entry>
- <entry>INTERRUPT POLLING TABLE FULL</entry></row>
+ <entry><errorname>INTERRUPT POLLING TABLE FULL</errorname></entry></row>
 <row>
  <entry>$CB</entry>
  <entry>203</entry>
- <entry>ILLEGAL MODE - attempt to perform I/O function of which the device or file is incapable.</entry></row>
+ <entry><errorname>ILLEGAL MODE</errorname>
+ - attempt to perform I/O function of which the device or file is incapable.</entry></row>
 <row>
  <entry>$CC</entry>
  <entry>204</entry>
- <entry>DEVICE TABLE FULL - Can't add another device</entry></row>
+ <entry><errorname>DEVICE TABLE FULL</errorname>
+ - Can't add another device</entry></row>
 <row>
  <entry>$CD</entry>
  <entry>205</entry>
- <entry>ILLEGAL MODULE HEADER - module not loaded because its
+ <entry><errorname>ILLEGAL MODULE HEADER</errorname>
+ - module not loaded because its
  sync code, header parity, or CRC is incorrect.</entry></row>
 <row>
  <entry>$CE</entry>
  <entry>206</entry>
- <entry>MODULE DIRECTORY FULL - Can't add another module</entry></row>
+ <entry><errorname>MODULE DIRECTORY FULL</errorname>
+ - Can't add another module</entry></row>
 <row>
  <entry>$CF</entry>
  <entry>207</entry>
- <entry>MEMORY FULL - Level One: not enough contiquous RAM free.
+ <entry><errorname>MEMORY FULL</errorname>
+ - Level One: not enough contiquous RAM free.
  Level Two: process address space full</entry></row>
 <row>
  <entry>$D0</entry>
  <entry>208</entry>
- <entry>ILLEGAL SERVICE REQUEST - System call had an illegal code number</entry></row>
+ <entry><errorname>ILLEGAL SERVICE REQUEST</errorname>
+ - System call had an illegal code number</entry></row>
 <row>
  <entry>$D1</entry>
  <entry>209</entry>
- <entry>MODULE BUSY - non-sharable module is in use by another process.</entry></row>
+ <entry><errorname>MODULE BUSY</errorname>
+ - non-sharable module is in use by another process.</entry></row>
 <row>
  <entry>$D2</entry>
  <entry>210</entry>
- <entry>BOUNDARY ERROR - Memory allocation or deallocation request not on a page boundary.</entry></row>
+ <entry><errorname>BOUNDARY ERROR</errorname>
+ - Memory allocation or deallocation request not on a page boundary.</entry></row>
 <row>
  <entry>$D3</entry>
  <entry>211</entry>
- <entry>END OF FILE - End of file encountered on read.</entry></row>
+ <entry><errorname>END OF FILE</errorname>
+ - End of file encountered on read.</entry></row>
 <row>
  <entry>$D4</entry>
  <entry>212</entry>
- <entry>RETURNING NON-ALLOCATED MEMORY - (NOT YOUR MEMORY)
+ <entry><errorname>RETURNING NON-ALLOCATED MEMORY</errorname>
+ - (NOT YOUR MEMORY)
  attempted to deallocate memory not previously assigned.</entry></row>
 <row>
  <entry>$D5</entry>
  <entry>213</entry>
- <entry>NON-EXISTING SEGMENT - device has damaged file structure.</entry></row>
+ <entry><errorname>NON-EXISTING SEGMENT</errorname>
+ - device has damaged file structure.</entry></row>
 <row>
  <entry>$D6</entry>
  <entry>214</entry>
- <entry>NO PERMISSION - file attributes do not permit access requested.</entry></row>
+ <entry><errorname>NO PERMISSION</errorname>
+ - file attributes do not permit access requested.</entry></row>
 <row>
  <entry>$D7</entry>
  <entry>215</entry>
- <entry>BAD PATH NAME - syntax error in pathlist (illegal character, etc.).</entry></row>
+ <entry><errorname>BAD PATH NAME</errorname>
+ - syntax error in pathlist (illegal character, etc.).</entry></row>
 <row>
  <entry>$D8</entry>
  <entry>216</entry>
- <entry>PATH NAME NOT FOUND - can't find pathlist specified.</entry></row>
+ <entry><errorname>PATH NAME NOT FOUND</errorname>
+ - can't find pathlist specified.</entry></row>
 <row>
  <entry>$D9</entry>
  <entry>217</entry>
- <entry>SEGMENT LIST FULL - file is too fragmented to be expanded further.</entry></row>
+ <entry><errorname>SEGMENT LIST FULL</errorname>
+ - file is too fragmented to be expanded further.</entry></row>
 <row>
  <entry>$DA</entry>
  <entry>218</entry>
- <entry>FILE ALREADY EXISTS - file name already appears in current directory.</entry></row>
+ <entry><errorname>FILE ALREADY EXISTS</errorname>
+ - file name already appears in current directory.</entry></row>
 <row>
  <entry>$DB</entry>
  <entry>219</entry>
- <entry>ILLEGAL BLOCK ADDRESS - device's file structure has been damaged.</entry></row>
+ <entry><errorname>ILLEGAL BLOCK ADDRESS</errorname>
+ - device's file structure has been damaged.</entry></row>
 <row>
  <entry>$DC</entry>
  <entry>220</entry>
- <entry>ILLEGAL BLOCK SIZE - device's file structure has been damaged.</entry></row>
+ <entry><errorname>ILLEGAL BLOCK SIZE</errorname>
+ - device's file structure has been damaged.</entry></row>
 <row>
  <entry>$DD</entry>
  <entry>221</entry>
- <entry>MODULE NOT FOUND - request for link to module not found in directory.</entry></row>
+ <entry><errorname>MODULE NOT FOUND</errorname>
+ - request for link to module not found in directory.</entry></row>
  <row>
  <entry>$DE</entry>
  <entry>222</entry>
- <entry>SECTOR OUT OF RANGE - device file structure damaged or
+ <entry><errorname>SECTOR OUT OF RANGE</errorname>
+ - device file structure damaged or
 incorrectly formatted.</entry></row>
 <row>
  <entry>$DF</entry>
  <entry>223</entry>
- <entry>SUICIDE ATTEMPT - request to return memory where your stack is located.</entry></row>
+ <entry><errorname>SUICIDE ATTEMPT</errorname>
+ - request to return memory where your stack is located.</entry></row>
 <row>
  <entry>$E0</entry>
  <entry>224</entry>
- <entry>ILLEGAL PROCESS NUMBER - no such process exists.</entry></row>
+ <entry><errorname>ILLEGAL PROCESS NUMBER</errorname>
+ - no such process exists.</entry></row>
 <row>
  <entry>$E2</entry>
  <entry>226</entry>
- <entry>NO CHILDREN - can't wait because process has no children.</entry></row>
+ <entry><errorname>NO CHILDREN</errorname>
+ - can't wait because process has no children.</entry></row>
 <row>
  <entry>$E3</entry>
  <entry>227</entry>
- <entry>ILLEGAL SWI CODE - must be 1 to 3.</entry></row>
+ <entry><errorname>ILLEGAL SWI CODE</errorname>
+ - must be 1 to 3.</entry></row>
 <row>
  <entry>$E4</entry>
  <entry>228</entry>
- <entry>PROCESS ABORTED - process aborted by signal code 2.</entry></row>
+ <entry><errorname>PROCESS ABORTED</errorname>
+ - process aborted by signal code 2.</entry></row>
 <row>
  <entry>$E5</entry>
  <entry>229</entry>
- <entry>PROCESS TABLE FULL - can't fork now.</entry></row>
+ <entry><errorname>PROCESS TABLE FULL</errorname>
+ - can't fork now.</entry></row>
 <row>
  <entry>$E6</entry>
  <entry>230</entry>
- <entry>ILLEGAL PARAMETER AREA - high and low bounds passed in fork call are incorrect.</entry></row>
+ <entry><errorname>ILLEGAL PARAMETER AREA</errorname>
+ - high and low bounds passed in fork call are incorrect.</entry></row>
 <row>
  <entry>$E7</entry>
  <entry>231</entry>
- <entry>KNOWN MODULE - for internal use only.</entry></row>
+ <entry><errorname>KNOWN MODULE</errorname>
+ - for internal use only.</entry></row>
 <row>
  <entry>$E8</entry>
  <entry>232</entry>
- <entry>INCORRECT MODULE CRC - module has bad CRC value.</entry></row>
+ <entry><errorname>INCORRECT MODULE CRC</errorname>
+ - module has bad CRC value.</entry></row>
 <row>
  <entry>$E9</entry>
  <entry>233</entry>
- <entry>SIGNAL ERROR - receiving process has previous
+ <entry><errorname>SIGNAL ERROR</errorname>
+ - receiving process has previous
  unprocessed signal pending.</entry></row>
 <row>
  <entry>$EA</entry>
  <entry>234</entry>
- <entry>NON-EXISTENT MODULE - unable to locate module.</entry></row>
+ <entry><errorname>NON-EXISTENT MODULE</errorname>
+ - unable to locate module.</entry></row>
 <row>
  <entry>$EB</entry>
  <entry>235</entry>
- <entry>BAD NAME - illegal name syntax.</entry></row>
+ <entry><errorname>BAD NAME</errorname>
+ - illegal name syntax.</entry></row>
 <row>
  <entry>$EC</entry>
  <entry>236</entry>
- <entry>BAD HEADER - module header parity incorrect</entry></row>
+ <entry><errorname>BAD HEADER</errorname>
+ - module header parity incorrect</entry></row>
 <row>
  <entry>$ED</entry>
  <entry>237</entry>
- <entry>RAM FULL - no free system RAM available at this time</entry></row>
+ <entry><errorname>RAM FULL</errorname>
+ - no free system RAM available at this time</entry></row>
 <row>
  <entry>$EE</entry>
  <entry>238</entry>
- <entry>UNKNOWN PROCESS ID - incorrect process ID number</entry></row>
+ <entry><errorname>UNKNOWN PROCESS ID</errorname>
+ - incorrect process ID number</entry></row>
 <row>
  <entry>$EF</entry>
  <entry>239</entry>
- <entry>NO TASK NUMBER AVAILABLE - all task numbers in use</entry></row>
+ <entry><errorname>NO TASK NUMBER AVAILABLE</errorname>
+ - all task numbers in use</entry></row>
 </tbody>
 </tgroup>
 </informaltable>
@@ -9416,63 +9442,75 @@
 <row>
  <entry>$F0</entry>
  <entry>240</entry>
- <entry>UNIT ERROR - device unit does not exist</entry></row>
+ <entry><errorname>UNIT ERROR</errorname>
+ - device unit does not exist</entry></row>
 <row>
  <entry>$F1</entry>
  <entry>241</entry>
- <entry>SECTOR ERROR - sector number is out of range.</entry></row>
+ <entry><errorname>SECTOR ERROR</errorname>
+ - sector number is out of range.</entry></row>
 <row>
  <entry>$F2</entry>
  <entry>242</entry>
- <entry>WRITE PROTECT - device is write protected.</entry></row>
+ <entry><errorname>WRITE PROTECT</errorname>
+ - device is write protected.</entry></row>
 <row>
  <entry>$F3</entry>
  <entry>243</entry>
- <entry>CRC ERROR - CRC error on read or write verify</entry></row>
+ <entry><errorname>CRC ERROR</errorname>
+ - CRC error on read or write verify</entry></row>
 <row>
  <entry>$F4</entry>
  <entry>244</entry>
- <entry>READ ERROR - Data transfer error during disk read
+ <entry><errorname>READ ERROR</errorname>
+ - Data transfer error during disk read
  operation, or SCF (terminal) input buffer overrun.</entry></row>
 <row>
  <entry>$F5</entry>
  <entry>245</entry>
- <entry>WRITE ERROR - hardware error during disk write operation.</entry></row>
+ <entry><errorname>WRITE ERROR</errorname>
+ - hardware error during disk write operation.</entry></row>
 <row>
  <entry>$F6</entry>
  <entry>246</entry>
- <entry>NOT READY - device has "not ready" status.</entry></row>
+ <entry><errorname>NOT READY</errorname>
+ - device has "not ready" status.</entry></row>
 <row>
  <entry>$F7</entry>
  <entry>247</entry>
- <entry>SEEK ERROR - physical seek to non-existant sector.</entry></row>
+ <entry><errorname>SEEK ERROR</errorname>
+ - physical seek to non-existant sector.</entry></row>
 <row>
  <entry>$F8</entry>
  <entry>248</entry>
- <entry>MEDIA FULL - insufficient free space on media.</entry></row>
+ <entry><errorname>MEDIA FULL</errorname>
+ - insufficient free space on media.</entry></row>
 <row>
  <entry>$F9</entry>
  <entry>249</entry>
- <entry>WRONG TYPE - attempt to read incompatible media (i.e.
+ <entry><errorname>WRONG TYPE</errorname>
+ - attempt to read incompatible media (i.e.
  attempt to read double-side disk on single-side drive)</entry></row>
 <row>
  <entry>$FA</entry>
  <entry>250</entry>
- <entry>DEVICE BUSY - non-sharable device is in use</entry></row>
+ <entry><errorname>DEVICE BUSY</errorname>
+ - non-sharable device is in use</entry></row>
 <row>
  <entry>$FB</entry>
  <entry>251</entry>
- <entry>DISK ID CHANGE - Media was changed with files open</entry></row>
+ <entry><errorname>DISK ID CHANGE</errorname>
+ - Media was changed with files open</entry></row>
 <row>
  <entry>$FC</entry>
  <entry>252</entry>
- <entry>RECORD IS LOCKED-OUT - Another process is accessing the
-requested record.</entry></row>
+ <entry><errorname>RECORD IS LOCKED-OUT</errorname>
+ - Another process is accessing the requested record.</entry></row>
 <row>
  <entry>$FD</entry>
  <entry>253</entry>
- <entry>NON-SHARABLE FILE BUSY - Another process is accessing the
-requested file.</entry></row>
+ <entry><errorname>NON-SHARABLE FILE BUSY</errorname>
+ - Another process is accessing the requested file.</entry></row>
 </tbody>
 </tgroup>
 </informaltable>
@@ -10836,7 +10874,7 @@
 <para>NOTE: THIS IS A PRIVILEGED SYSTEM MODE SERVICE REQUEST</para>
 </sect1>
 
-<sect1>
+<sect1 id="f.srtmem">
 <title>F$SRtMem - System Memory Return</title>
 
 <informaltable frame="none">