- APPENDIX D -
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:
ERROR CODES
GEMDOS/BIOS Errors
Name |
| Meaning |
---|---|---|
E_OK |
| No error |
ERROR |
| Generic error |
EDRVNR |
| Drive not ready |
EUNCMD |
| Unknown command |
E_CRC |
| CRC error |
EBADRQ |
| Bad request |
E_SEEK |
| Seek error |
EMEDIA |
| Unknown media |
ESECNF |
| Sector not found |
EPAPER |
| Out of paper |
EWRITF |
| Write fault |
EREADF |
| Read fault |
EWRPRO |
| Device is write protected |
E_CHNG |
| Media change detected |
EUNDEV |
| Unknown device |
EBADSF |
| Bad sectors on format |
EOTHER |
| Insert other disk (request) |
Name |
| Meaning |
---|---|---|
EINVFN |
| Invalid function |
EFILNF |
| File not found |
EPTHNF |
| Path not found |
ENHNDL |
| No more handles |
EACCDN |
| Access denied |
EIHNDL |
| Invalid handle |
ENSMEM |
| Insufficient memory |
EIMBA |
| Invalid memory block address |
EDRIVE |
| Invalid drive specification |
ENSAME |
| Cross device rename |
ENMFIL |
| No more files |
ELOCKED |
| Record is already locked |
ENSLOCK |
| Invalid lock removal request |
ERANGE or
ENAMETOOLONG |
| Range error |
EINTRN |
| Internal error |
EPLFMT |
| Invalid program load format |
EGSBF |
| Memory block growth failure |
ELOOP |
| Too many symbolic links |
EMOUNT |
| Mount point crossed (indicator) |