CHRRDBA - DOS
13 Dec 98

8.0 Error Messages

8.1 Common CHRRDBA CD-ROM Errors

8.1.1 Caution!

It is important to remember that although CD-ROM disks are practically indestructible, they can be permanently damaged by careless handling. A very small scratch can render a disk unusable. Fingerprints and other dirt can cause fatal errors during program execution. Even microscopic dust particles can cause problems.

Anything you do to reduce disk handling is desirable. CD-ROM drives which use disk caddies have become common. A disk caddie for each CD-ROM you own may seem to be an unnecessary added expense, but it can be well worth the cost if it protects even one of your expensive CD-ROM disks. If you have to handle a CD-ROM disk, handle it only by the edges. NEVER touch the data surface of the disk (i.e., the bottom, shiny side without printing). Don't lay CD-ROM disks on anything. Use caddies or jewel cases to store them.

8.1.2 Error Messages

Error messages generated by CHRRDBA appear in the following format:

Where,

The errors come from Borland Pascal with Objects Version 8.0. More information about all errors can be found in the Programmer's Reference Manual.

8.1.3 DOS Errors
1 Invalid function number. {You should never get this}
2 File not found. {Often associated with CD-ROM drives connected via a network. Try the disk on a PC with a locally connected CD-ROM drive. You can compare directories produced with both setups. Usually the network directory will not show all the files.}
3 Path not found. {You should never get this}
4 Too many open files. {The program has too many open files. You probably don't have a FILES=xx entry in your CONFIG.SYS file or the number (xx) is too small. Add FILES=20 or increase the number to 20 and reboot your computer.}
5 File access denied. {You should never get this}
6 Invalid file handle. {You should never get this}
12 Invalid file access code. {You should never get this}
15 Invalid drive number. {You should never get this}
16 Cannot remove current directory. {You should never get this}
17 Cannot rename across drives. {You should never get this}
18 No more files. {You should never get this}

 

8.1.4 I/O Errors

100 Disk read error. {Sometimes this input/output error occurs because of faulty hardware or a dirty or damaged CD-ROM disk. What has happened is that a data field has been read incorrectly. This causes the program to attempt to read beyond the end of file.}
101 Disk write error. {Your output disk is full}
102 File not assigned. {You should never get this}
103 File not open. {You should never get this}
104 File not open for input. {You should never get this}
105 File not open for output. {You should never get this}
106 Invalid numeric format. {You should never get this}




8.1.5 Critical Errors

Critical errors will usually terminate the program. They are often caused by faulty hardware or dirty CD-ROM disks. For more information refer to a DOS programmer's reference manual.

150 Disk is write protected.
151 Unknown unit.
152 Drive not ready.
153 Unknown command.
154 CRC error in data.
155 Bad drive request structure length.
156 Disk seek error.
157 Unknown media type.
158 Sector not found.
159 Printer out of paper.
160 Device write fault.
161 Device read fault. {The most common hardware problem usually indicates a damaged or dirty CD-ROM disk. Usually this occurs during data extraction. If the error occurs at the same place repeatedly, the CD-ROM disk is probably damaged; otherwise, the CD-ROM drive may be faulty or the CD-ROM disk may be dusty or fingerprinted.}
162 Hardware failure.

 

8.1.6 Fatal Errors

Fatal errors immediately terminate the program.

200 Division by zero. {You should never get this}
201 Range check error. {This error is known to occur with certain mouse drivers. It MAY have been corrected. If it recurs, try rebooting without the mouse driver installed in CONFIG.SYS or AUTOEXEC.BAT.}
202 

203

Stack overflow error.
-or-
Heap overflow error.		 {Either of these errors indicates that there is not enough memory available to run CHRRDBA. Too many device drivers and TSR's (terminate and stay resident programs) loaded in CONFIG.SYS and AUTOEXEC.BAT can cause this error. Poor memory management or not enough RAM can also cause this.}
204 Invalid pointer operation. {You should never get this}
205 Floating point overflow. {You should never get this}
206 Floating point underflow. {You should never get this}
207 Invalid floating point operation. {You should never get this}


Table of Contents
E-mail: editor