ERROR MESSAGES AND CODES

    Error messages are divided into several categories.

    A. Compiler error messages are numbered 1 thru 131 and identify errors
       found during the compilation process.  When a compiler error is
       found the compilation process will stop, the error will be displayed
       at the top of the screen, and the affected text will be highlighted.

    B. Graphic errors are reported by GraphResult and occur during any
       graphic operation.

    C. Runtime errors are found during program execution and will usually
       cause the program to terminate. These errors are further divided
       into the categories of "Runtime" and "I/O" errors.

    D. I/O Errors are identified as codes 1 thru 199 and are equivalent
       to the error codes reported by DOS.  These errors occur when
       programs incorrectly access the input/output devices. I/O errors
       can be effectively trapped by first turning off error detection
       {$I-}, performing an I/O operation, and reading the status of the
       operation with IOResult.  IOResult will display a value of 0 is
       the operation was successful and a non-zero value otherwise.

    E. Fatal errors can be identifies as codes 200 thru 255 and are found
       to immediately terminate program execution with the display of
       "Runtime error XXX at XXXX:YYYY".