home *** CD-ROM | disk | FTP | other *** search
-
- Supplemental Doc File for CdCom
-
- The following is a list of the error numbers that can be generated by
- CdCom when encountering an error. CdCom will write this information to
- the cdcom.log file and also to critical.log in the form of
-
- Error # at Program Counter #
-
- The program counter is used internally by the compiler, if you cannot seem
- to get the program to work even with the below information then call me
- and I'll enter this number into the compiler and it will pin-point the
- problem.
-
- A Erdev and Erdev$ may be returned also, this if not 0 or blank will
- have the drive number and driver letter respectively of the drive
- that caused the error. This will usually have your cdrom drive letter
- if there are problems accessing the drive. Most errors besides 71 and
- 72 will have a 0 and a blank for these, and are not needed.
-
- The error #'s go as follows:
-
- Note: PE stands for programmers error. Call me and let me know the problem.
-
- Error 3 - Return without a Gosub. PE.
- Error 5 - Illegal Function Call. A multitude of things can cause this
- error. Make sure you have the program properly configured.
- If so, and it still bombs, then give me a call.
- Error 6 - Numeric Overflow. CdCom attempted a calculation that overflowed
- the variable it was storing the result in. PE.
- Error 7 - Out of Memory. Either from too large of an array or too large
- of a string. Try freeing up some memory and see if that fixes
- the problem. This could also happen when it tries to shell to
- dsz or the view programs.
- Error 9,10 - Array Errors, PE.
- Error 11 - Division by Zero. Either PE or protocol.def not configured
- correctly.
- Error 14 - Out of String Space. PE or not enough free memory.
- Error 15 - String too Long. PE.
- Error 24 - Device Timeout. A com port error. Insure com port is configured
- properly.
- Error 25 - Device Fault. Hardware device.
- Error 27 - Printer out of paper.
- Error 50 - Field Overflow. PE.
- Error 51 - Internal Error. Call me ASAP as this is a major problem.
- Error 53 - File Not Found. Insure you have CdCom configured properly, and
- that all work files are where you told the program they would be.
- Error 52, 54, 55 - Internal File Handling Errors. PE.
- Error 57 - Device I/O error. A serious hardware error occured.
- Error 61 - Disk Full. Ran out of disk space when writing to a file.
- Error 62 - Input Past End. Error occured when reading in a file that CdCom
- expected more data in. Insure all configuration files are
- correct. This should not be a PE, as these would have been
- found during testing.
- Error 63, 64 - File access errors. PE.
- Error 67 - Too many files. A dos error.
- Error 68 - Device Unavailable. Tried to access a device that is not there.
- Error 69 - Comm buffer overflow.
- Error 70 - Permission denied. Attempted to write to a protected floppy.
- Error 71 - Disk not ready. Either no disk or a timeout error.
- Error 72 - Disk media error, as reported by the controller. It may also
- occur if there is a problem reading the cdrom disk, which does not
- mean there is a defect on the disk just an error reading the data
- from the disk, which happens frequently I've found. Try cleaning
- the lens on the cdrom drive if this happens frequently.
- Error 73 - Feature not available. This should only happen if you are running
- a dos version less than 3.X, since all files are opened in share
- mode, which is a dos 3.X and above feature. Dos 2.X or less does
- not support these type of functions.
- Error 75 - Path/File access error. Incorrect drive or path in one of the
- configuration files most likely, although could be PE. It will
- also get this error if the file has the read-only attribute set,
- although this won't happen for all the files. If you are sure you
- have your setup correct then check the file attributes. Makexrf
- will also give this error when converting the description file(s)
- to the master list format if they are read-only. Some cdrom drivers
- do not change the attribute when copying files over.
- Error 76 - Path not found. Cannot find drive or path specified in one of the
- configuration files most likely, although could be PE.
- Error 201 - Out of stack space. PE.
- Error 242 - String/array memory corrupt. Could be PE or a glitch caused it.
-
- If you find you are getting Abort, Fail, etc. errors while in the door
- it may be due to a dirty lens on the cdrom drive. Computer cdrom drives
- are much more sensitive to this than the audio cd players, so you have to
- watch this. Also, if you notice the file access times slowing down when
- reading the cdrom drive this is another key indication, or the cdrom disk
- is dirty. I don't know the best method for cleaning the disk, but a dry
- cotton swab rubbed lightly across the lens to get rid of dust works just
- fine, or use a commercial cd cleaner. I usually just clean my disks with
- a clean soft cloth, without heavy rubbing.
-
- My home # is 805-987-2110, pacific time so be considerate about the time
- if you call. I do keep hacker hours on weekends, but have school during
- the week so may or may not be up at weird hours.
-
- Eric Schonning
-
-