- APPENDIX D -

# ERROR CODES

#### GEMDOS/BIOS Errors

Upon return from most GEMDOS and BIOS functions, register D0 contains a longword error code describing the failure or success of an operation. The BIOS uses error codes -1 to -31 while GEMDOS uses error codes -32 and lower. A return value of 0 always indicates success. The error codes and their meanings are as follows:

Name | BIOS # | Meaning
--- | --- | ---
E_OK | 0 | No error
ERROR | -1 | Generic error
EDRVNR | -2 | Drive not ready
EUNCMD | -3 | Unknown command
E_CRC | -4 | CRC error
EBADRQ | -5 | Bad request
E_SEEK | -6 | Seek error
EMEDIA | -7 | Unknown media
ESECNF | -8 | Sector not found
EPAPER | -9 | Out of paper
EWRITF | -10 | Write fault
EREADF | -11 | Read fault
EWRPRO | -12 | Device is write protected
E_CHNG | -14 | Media change detected
EUNDEV | -15 | Unknown device
EBADSF | -16 | Bad sectors on format
EOTHER | -17 | Insert other disk (request)

Name | GEMDOS # | Meaning
--- | --- | ---
EINVFN | -32 | Invalid function
EFILNF | -33 | File not found
EPTHNF | -34 | Path not found
ENHNDL | -35 | No more handles
EACCDN | -36 | Access denied
EIHNDL | -37 | Invalid handle
ENSMEM | -39 | Insufficient memory
EIMBA | -40 | Invalid memory block address
EDRIVE | -46 | Invalid drive specification
ENSAME | -48 | Cross device rename
ENMFIL | -49 | No more files
ELOCKED | -58 | Record is already locked
ENSLOCK | -59 | Invalid lock removal request
ERANGE or ENAMETOOLONG | -64 | Range error
EINTRN | -65 | Internal error
EPLFMT | -66 | Invalid program load format
EGSBF | -67 | Memory block growth failure
ELOOP | -80 | Too many symbolic links
EMOUNT | -200 | Mount point crossed (indicator)

Table of Contents | Index