| Error Code | Explanation | Remedy |
|---|---|---|
| 000:002 | Keyboard quit (^E) typed | Ignore. Just indicates a Control-E was typed. |
| 000:003 | Keyboard interrupt (^C) typed | Ignore. Just indicates a Control-C was typed. |
| 000:214 | File not accessible | Typically read problems. Check hardware, reboot. |
| 000:215 | Bad pathlist specified | Check the path the error references. |
| 000:216 | File not found | Check the path the error references, particularly the filename. |
| 000:218 | Tried to create a file that already exists | Use -fr with copy or dsave to overwrite old file, or ignore if
current file is ok. |
| 000:221 | Module not found | Check the execution path or module directory for missing module. |
| 000:231 | Known module | Module is already in memory. Usually innocuous: just ignore. If desired, use unlink to unload it. Use multiple unlink commands, until a 000:221 error indicates the module is no longer in memory. |
| 000:232 | Bad module CRC | Use fixmod -u to repair, or install a new copy of the module. |
| 000:235 | Bad name | Check filename, especially adherence to OS9 naming rules. |
| 000:240 | Illegal unit (drive) number | Check drive name. |
| 000:244 | Read error | Check hardware, driver setup. |
| 000:245 | Write error | Check hardware, driver setup. |
| 000:246 | Device not ready | Check hardware, especially power. Reboot drive. |
| 000:247 | Seek error | Check hardware, driver setup. |
| 000:248 | Media full | Put the hard drive/floppy on a diet. |
| 000:249 | Bad type (incompatible media) | Use different device driver to access device. |
| 000:250 | Device busy | Check hardware, cycle power, reboot. |
This listing reprinted courtesy Microware Systems Corporation.