[an error occurred while processing this directive]
[an error occurred while processing this directive] [an error occurred while processing this directive] _

Mac Error Codes and Tips

Positive Error Codes

Type XX errors are general in nature and don't point to a specific software or hardware component level error. Common Type XX errors are:

Error 01: Bus Error

The computer attempted to access memory that simply doesn't exist.

Error 02: Address Error

Memory can be accessed in certain sizes and at certain locations. If the wrong size is accessed at an improper location, this error results.

Error 03: Illegal Instruction

Computers have a "vocabulary" of instructions that they understand. If a computer tries to execute a command that isn't in its vocabulary, this error results.

Error 11: Miscellaneous Hardware Exception

Usually associated with the 68k emulator on Power Macintoshes. If the emulator is corrupted when loaded to RAM, this error results. Note that this error can be caused by both software and hardware.

Error 25: Memory Full Error

Buy some more RAM!

Error 26: Bad Program Launch

The opened application couldn't launch or execute a command as expected.

Negative Error Codes

Negative error codes include:

Error -35

Volume not found.

Error -36

Input/Output Error

Error -38

File not open.

Error -108

Memory Full Error; heap zone full.

Error -189

An attempt was made to write past the end of a file.

Error -1305

The desktop database has become corrupted. This is by no means an exhaustive list. The above represents some of the common errors I've come across in troubleshooting the Mac OS over the years.

Tips

Mac OS troubleshooting and maintenance:

1. Use a disk utility.

Disk First Aid, which is included with the Mac OS, alleviates common disk problems, but for heavy duty analysis pick up a copy of Norton Utilities or TechTool Pro. Norton tests for disk related errors while TechTool Pro tests hardware components as well. A recently released utility, Disk Warrior, has been receiving rave reviews. It rebuilds and optimizes the disk directory.

2. Delete the Finder Preferences File.

The finder preferences file often becomes corrupt after a series of crashes. Delete the finder preferences file in the Preferences folder in the System folder to force the Finder to create a new file.

3. Clear the Chooser cache.

If you are experiencing AppleTalk related crashes, try clearing the Chooser cache by holding down the Command and Option keys while launching the Chooser.

4. Zap the PRAM.

If you are encountering miscellaneous errors, try zapping the PRAM. Hold down the Command-Option-P-R keys while restarting your machine. For good measure, repeat the procedure at least twice. Remember that several settings such as the AppleTalk connection and the disk cache will need to be reset from their default values.

5. Increase the memory allocation.

Applications often produce errors when they have an inadequate memory allocation. If an application frequently crashes, try increasing its memory allocation above the suggested preferred size.

6. Rebuild the desktop.

Periodically rebuild your desktop database. To do so, hold down the Command and Option keys when the Finder starts up. For best results, start up with extensions off to rebuild.

7. Use a virus checker.

Autostart worms and the numerous macro viruses can be particularly insidious and can cause various random errors.
[an error occurred while processing this directive]