Mac Errors

Error Codes 1-30

ID=01 Bus Error

This means the computer tried to access memory that doesn't exist. You can get this error on almost any Macintosh. If one of these computers tried to access one or more bytes beyond the total number of bytes in RAM, you see a bus error. You should never see this error on a Macintosh Plus or SE, because address references that are out of bounds "roll over". This means if one of these computers tries to access one byte beyond the total bytes in RAM, it actually accesses the first byte in memory. If you see this error on a Macintosh Plus or SE, it's reporting the wrong error or having hardware problems.

ID=02 Address Error

The Motorola 68000 microprocessor can access memory in increments of one byte (8 bits), one word (16 bits), or one long word (32 bits). The microprocessor can access a byte of information at an odd or even memory address. But it must access a word or long word at an even memory address. So, when the microprocessor attempts to read or write a word or long word at an odd address, you see this error. Since that's a 50/50 proposition when running random code, this one shows up quite often.

ID=03 Illegal Instruction

The computer has a specific vocabulary of machine language instructions it can understand. If a computer tries to execute an instruction that isn't in its vocabulary, you see this error code. It's less likely than error 02, but still very common.

ID=04 Zero Divide Error

This error results if the microprocessor divides two numbers, and the divisor is zero. Sometimes a programmer puts these in as debugging aids, and then forgets to take them out.

ID=05 Range Check Error

Programmers can use an instruction in the Motorola 68000 to check if a number is within a certain range. This error indicates that the number tested isn't in the specified range.

ID=06 Overflow Error

Each number stored in a computer is given a certain amount of space. The larger the number, the more space is needed to represent the number. An overflow condition results if a generated number is too big for its allotted space. A Motorola 68000 instruction tests for an overflow condition, and displays this error if it detects an overflow.

ID=07 Privilege Violation

The Motorola 68000 runs in Supervisor or User mode. The Macintosh should always be in Supervisor mode, but sometimes is placed in User mode. Some of the instructions can only be executed in Supervisor mode. If the computer attempts one of these instructions while in User mode, a Privilege Violation error results.

ID=08 Trace Mode Error

A programmer can use a runtime debugger while in Trace mode. This allows tracing through a program one instruction at a time. You see this error if a debugger isn't installed and the 68000 is accidentally placed in Trace mode.

ID=09 and ID=10 Line 1010 & 1111 Trap

There are many routines in the Macintosh ROM that can be called by placing instructions in a program that aren't in the 68000's vocabulary. When the 68000 encounters such an instruction, it looks it up in the instruction table. This table gives the location of routines paired with each instruction. If it finds an entry in the table for the instruction, it branches to the routine. If there's no entry for the instruction, you see one of these errors.

ID=11 Miscellaneous Hardware Exception Error

ID=12 Unimplemented Core Routine

A programmer might set breakpoints in parts of a program to inspect for errors. This requires using a debugger. If a debugger isn't installed when a breakpoint occurs, you see this error code.

ID=13 Uninstalled Interrupt

The Macintosh uses an interrupt to identify when devices like keyboards and disk drives need service. Routines must be available in memory to tell the computer how to service the device. If those routines aren't available, you see this error.

ID=15 Segment Loader Error

Macintosh programs are broken up into segments, and each program will always have at least one segment. Multiple segments allow loading parts of the program into memory to provide more room for data in internal RAM. The segment loader is responsible for loading a needed segment into RAM. If the segment loader can't do this, you'll see this error.

ID=17 through ID=24 Missing Packages 0-7

The Macintosh uses packages to do specific tasks. Some of the packages are International Utilities, Binary-Decimal Conversion, Standard File Utilities, and Disk Initialization. These packages are located in the System file. If you get these errors, you probably have a damaged System file. Error codes 15, 16, 26, 27, 30, and 31 also come up when the System file is damaged. Try replacing the System file.

ID=25 Memory Full Error

You've probably run out of RAM. But you can get this error when an earlier error causes the Macintosh to falsely detect an out-of-memory condition.

ID=26 Bad Program Launch

The Macintosh couldn't execute the application opened.

ID=28 Stack Ran into Heap

This is similar to the Memory Full error. It's a good idea to save your work frequently, and keep current backups of your hard disk data. When a system crash does occur, you'll lose less data if you've taken these precautions.

 Negative Error Codes (0 to -99)

General System Errors (VBL Mgr, Queue)

0 noErr 0 for success "OR"

0 smNotTruncated No truncation necessary

-1 qErr queue element not found during deletion "OR"

-1 smTruncErr Truncation indicator alone is wider than the specified width

-2 vTypErr invalid queue element

-3 corErr core routine number out of range

-4 unimpErr unimplemented core routine

-5 SlpTypeErr invalid queue element

-8 seNoDB no debugger installed to handle debugger command Color Manager Errors

-9 iTabPurgErr from Color2Index/ITabMatch

-10 noColMatch from Color2Index/ITabMatch

-11 qAllocErr from MakeITable

-12 tblAllocErr from MakeITable

-13 overRun from MakeITable

-14 noRoomErr from MakeITable

-15 seOutOfRange from SetEntry

-16 seProtErr from SetEntry

-17 i2CRangeErr from SetEntry

-18 gdBadDev from SetEntry

-19 reRangeErr from SetEntry

-20 seInvRequest from SetEntry

-21 seNoMemErr from SetEntry

I/O System Errors

-17 controlErr Driver can't respond to Control call

-18 statusErr Driver can't respond to Status call

-19 readErr Driver can't respond to Read call

-20 writErr Driver can't respond to Write call

-21 badUnitErr Driver ref num doesn't match unit table

-22 unitEmptyErr Driver ref num specifies NIL handle in unit table

-23 openErr Requested read/write permission doesn't match driver's open

permission, or Attempt to open RAM serial Driver failed

-24 closErr Close failed; Permission to close .MPP driver was denied

-25 dRemovErr tried to remove an open driver

-26 dInstErr DrvrInstall couldn't find driver in resources

-27 abortErr IO call aborted by KillIO; Publisher has written a new edition "OR"

-27 iIOAbortErr IO abort error (Printing Manager)

-28 notOpenErr Couldn't rd/wr/ctl/sts cause driver not opened

-29 unitTblFullErr Unit table has no more entries

-30 dceExtErr dce extension error

-32 File System Errors

-33 dirFulErr Directory full

-34 dskFulErr Disk full

-35 nsvErr No such volume; volume not found

-36 ioErr I/O error

-37 bdNamErr Bad file name; there may be no bad names in the final system!

-38 fnOpnErr File not open

-39 eofErr End of file; no additional data in the format

-40 posErr Tried to position to before start of file (r/w)

-41 mFulErr Memory full (open) or file won't fit (load)

-42 tmfoErr too many files open

-43 fnfErr File not found; Folder not found; Edition container not found; Target not found

-44 wPrErr Disk is write-protected; Volume is locked through hardware

-45 fLckdErr File is locked

-45 fLckedErr Publisher writing to an edition

-46 vLckdErr Volume is locked through software

-47 fBsyErr File is busy (delete); Section doing I/O

-48 dupFNErr Duplicate filename (rename); File found instead of folder

-49 opWrErr File already open with write permission

-50 paramErr Error in user parameter list

-51 rfNumErr Reference number invalid

-52 gfpErr Get file position error

-53 volOffLinErr Volume is off line

-54 permErr Software lock on file; Not a subscriber [permissions error on file open]

-55 volOnLinErr drive volume already on-line at MountVol

-56 nsDrvErr no such drive (tried to mount a bad drive num)

-57 noMacDskErr not a Macintosh disk (sig bytes are wrong)

-58 extFSErr External file system __ file system identifier is nonzero

-59 fsRnErr file system internal error: during rename the old entry was deleted but could not be restored.

-60 badMDBErr bad master directory block

-61 wrPermErr Write permissions error; Not a publisher Font Manager Errors

-64 fontDecError error during font declaration

-65 fontNotDeclared font not declared

-66 fontSubErr font substitution occurred

Disk, Serial Ports, Clock Specific Errors

-64 lastDskErr

-64 noDriveErr drive not installed

-65 offLinErr r/w requested for an off-line drive

-66 noNybErr couldn't find 5 nybbles in 200 tries

-67 noAdrMkErr couldn't find valid addr mark

-68 dataVerErr read verify compare failed

-69 badCksmErr addr mark checksum didn't check

-70 badBtSlpErr bad addr mark bit slip nibbles

-71 noDtaMkErr couldn't find a data mark header

-72 badDCksum bad data mark checksum

-73 badDBtSlp bad data mark bit slip nibbles

-74 wrUnderrun write underrun occurred

-75 cantStepErr step handshake failed

-76 tk0BadErr track 0 detect doesn't change

-77 initIWMErr unable to initialize IWM

-78 twoSideErr tried to read 2nd side on a 1-sided drive

-79 spdAdjErr unable to correctly adjust disk speed

-80 seekErr track number wrong on address mark

-81 sectNFErr sector number never found on a track

-82 fmt1Err can't find sector 0 after track format

-83 fmt2Err can't get enough sync

-84 verErr track failed to verify

-84 firstDskErr

-85 clkRdErr unable to read same clock value twice

-86 clkWrErr time written did not verify

-87 prWrErr parameter RAM written didn't read-verify

-88 prInitErr InitUtil found the parameter RAM uninitialized

-89 rcvrErr SCC receiver error (framing, parity, OR)

-90 breakRecd Break received (SCC)

AppleTalk Errors

-91 ddpSktErr Error opening socket "OR"

-91 eMultiErr Invalid address or table is full

-92 ddpLenErr Data length too big "OR"

-92 eLenErr Packet too large or first entry of the write-data structure

didn't contain the full 14-byte header

-93 noBridgeErr No router available [for non-local send]

-94 lapProtErr error in attaching/detaching protocol "OR"

-94 LAPProtErr Protocol handler is already attached, node's protocol

table is full, protocol not attached, or protocol handler pointer was not 0

-95 excessCollsns Hardware error [excessive collisions on write]

-97 portInUse driver Open error code (port is in use)

-98 portNotCf driver Open error code (parameter RAM not configured for

this connection)

-99 memROZErr hard error in ROZ

-99 memROZError hard error in ROZ

-99 memROZWarn soft error in ROZ

Negative Error Codes (-100 to -199)

Scrap Manager Errors

-100 noScrapErr No scrap exists error

-102 noTypeErr Format not available [no object of that type in scrap] Storage Allocator Errors

-108 memFullErr Ran out of memory [not enough room in heap zone]

-109 nilHandleErr GetHandleSize fails on baseText or substitutionText;

NIL master pointer [handle was NIL in HandleZone or other]

-110 memAdrErr Address was odd, or out of range

-111 memWZErr Attempted to operate on a free block; GetHandleSize fails

on baseText or substitutionText [WhichZone failed (applied to free block)]

-112 memPurErr Trying to purge a locked or non-purgeable block

-113 memAZErr Address in zone check failed

-114 memPCErr Pointer Check failed

-115 memBCErr Block Check failed

-116 memSCErr Size Check failed

-117 memLockedErr Trying to move a locked block (MoveHHi) HFS Errors

-120 dirNFErr Directory not found

-121 tmwdoErr No free WDCB available

-122 badMovErr Move into offspring error

-123 wrgVolTypErr Not an HFS volume [wrong volume type error or

(obsolete) operation not supported for MFS]

-124 volGoneErr Server volume has been disconnected.

-125 updPixMemErr Insufficient memory to update a pixmap

-127 fsDSIntErr Internal file system error Menu Manager Errors

-126 dsMBarNFnd System error code for MBDF not found

-127 dsHMenuFindErr Couldn't find HMenu's parent in MenuKey

-128 userCanceledErr User canceled an operation  HFS FileID Errors

-130 fidNotFound no file thread exists

-131 fidNotAFile directory specified

-132 fidExists file ID already exists

Color QuickDraw and Color Manager Errors

-147 regionTooBigError Region too big or complex

-148 pixMapTooBigErr Pixel map record is deeper than 1 bit per pixel

[passed pixelmap is too large]

-149 notEnoughStack Not enough stack space for the necessary buffers "OR"

-149 mfStackErr Insufficient stack

-150 cMatchErr Color2Index failed to find an index

-151 cTempMemErr Failed to allocate memory for temporary structures

-152 cNoMemErr Failed to allocate memory for structure

-153 cRangeErr Range error on colorTable request

-154 cProtectErr ColorTable entry protection violation

-155 cDevErr Invalid type of graphics device

-156 cResErr Invalid resolution for MakeITable

-157 cDepthErr Invalid pixel depth

-158 cParmErr Invalid parameter

Resource Manager Errors (other than I/O)

-185 badExtResource Extended resource has a bad format.

-186 CantDecompress Resource bent ("the bends") can't decompress a

compressed resource

-188 resourceInMemory Resource already in memory

-189 writingPastEnd Writing past end of file

-190 inputOutOfBounds Offset or count out of bounds

-192 resNotFound Resource not found

-193 resFNotFound Resource file not found

-194 addResFailed AddResource failed

-195 addRefFailed AddReference failed

-196 rmvResFailed RmveResource failed

-197 rmvRefFailed RmveReference failed

-198 resAttrErr Attribute inconsistent with operation

-199 mapReadErr Map inconsistent with operation

Negative Error Codes (-200 to -261)

Sound Manager Errors

-200 noHardware Required sound hardware not available [no hardware

support for the specified synthesizer]

-201 notEnoughHardware Insufficient hardware available [no more channels

for the specified synthesizer]

-203 queueFull No room in the queue

-204 resProblem Problem loading the resource

-205 badChannel Channel is corrupt or unusable [invalid channel queue

length]

-206 badFormat Resource is corrupt or unusable [handle to 'snd '

resource was invalid]

-207 notEnoughBufferSpace Insufficient memory available

-208 badFileFormat File is corrupt or unusable, or not AIFF or AIFF-C

-209 channel Channel is busy

-210 buffersTooSmall Buffer is too small

-211 channelNotBusy Channel not currently used

-212 noMoreRealTime Not enough CPU time available

-213 badParam A parameter is incorrect

-220 siNoSoundInHardware No sound input hardware available

-221 siBadSoundInDevice Invalid sound input device

-222 siNoBufferSpecified No buffer specified

-223 siInvalidCompression Invalid compression type

-224 siHardDiskTooSlow Hard drive too slow to record

-225 siInvalidSampleRate Invalid sample rate

-226 siInvalidSampleSize Invalid sample size

-227 siDeviceBusyErr Sound input device is busy

-228 siBadDeviceName Invalid device name

-229 siBadRefNum Invalid reference number

-230 siInputDeviceErr Input device hardware failure

-231 siUnknownInfoType Unknown type of information

-232 siUnknownQuality Unknown quality

MIDI Manager Errors

-250 midiNoClientErr no client with that ID found

-251 midiNoPortErr no port with that ID found

-252 midiTooManyPortsErr too many ports already installed in the system

-253 midiTooManyConsErr too many connections made

-254 midiVConnectErr pending virtual connection created

-255 midiVConnectMade pending virtual connection resolved

-256 midiVConnectRmvd pending virtual connection removed

-257 midiNoConErr no connection exists between specified ports

-258 midiWriteErr couldn't write to all connected ports

-259 midiNameLenErr name supplied is longer than 31 characters

-260 midiDupIDErr duplicate client ID

-261 midiInvalidCmdErr command not supported for port type

Article Created: 19 February 1986

Article Reviewed/Updated: 20 November 1995

This article is one of many available through the Apple Fax center. For a complete list of available Fax documents, search the Tech Info Library for Apple Fax Document Index or call the Apple Fax line at 1-800-505-0171 and select document number 20000 (Apple Fax - Document Index - Product Support Literature). The Apple Fax center is available free of charge 24 hours a day, 7 days a week.

Article Change History:

20 Nov 1995 - Added new keyword and reviewed article for technical accuracy.

19 Oct 1994 - Added negative error codes.

12 Oct 1994 - Added keyword, description, and troubleshooting tips.

30 Nov 1993 - Reviewed and reorganized.

Support Information Services

Copyright 1986-94, Apple Computer, Inc.

01749: TIL

Negative Error Codes (-299 to -5553)

Notification Manager Error

-299 nmTypErr Invalid qType- must be ORD(nmType)

Start Manager Errors

-290 smSDMInitErr SDM could not be initialized.

-291 smSRTInitErr Slot Resource Table could not be initialized.

-292 smPRAMInitErr Slot Resource Table could not be initialized.

-293 smPriInitErr Cards could not be initialized.

-300 smEmptySlot No card in slot

-301 smCRCFail CRC check failed for declaration data

-302 smFormatErr FHeader Format is not Apple's

-303 smRevisionErr Wrong revison level

-304 smNoDir Directory offset is Nil

-305 smLWTstBad Long Word test field $5A932BC7.

-306 smNosInfoArray No sInfoArray. Memory Mgr error.

-307 smResrvErr Fatal reserved error. Reserved field 0.

-308 smUnExBusErr Unexpected Bus Error

-309 smBLFieldBad ByteLanes field was bad.

-310 smFHBlockRdErr Error occured during _sGetFHeader.

-311 smFHBlkDispErr Error occured during _sDisposePtr (Dispose ofFHeader block).

-312 smDisposePErr _DisposePointer error

-313 smNoBoardsRsrc No Board sResource.

-314 smGetPRErr Error occured during _sGetPRAMRec (See SIMStatus).

-315 smNoBoardId No Board Id.

-316 smIntStatVErr The InitStatusV field was negative after primary or secondary init.

-317 smIntTblVErr An error occured while trying to initialize the Slot Resource Table.

-318 smNoJmpTbl SDM jump table could not be created.

-319 smBadBoardId BoardId was wrong, re-init the PRAM record.

-320 smBusErrTO BusError time out.

-330 smBadRefId Reference Id not found in list

-331 smBadsList Bad sResource [sList] structure:Id1

-332 smReservedErr Reserved field not zero

-333 smCodeRevErr Code revision is wrong

-334 smCPUErr Code revision is wrong

-335 smsPointerNil LPointer is nil {From sOffsetData. Check sInfo rec for more information.}

-336 smNilsBlockErr Nil sBlock error {Don't allocate and try to use a nil sBlock}

-337 smSlotOOBErr Slot out of bounds error

-338 smSelOOBErr Selector out of bounds error; function not implemented

-339 smNewPErr _NewPtr error

-340 smBlkMoveErr _BlockMove error

-341 smCkStatusErr Status of slot = fail.

-342 smGetDrvrNamErr Error occured during _sGetDrvrName.

-343 smDisDrvrNamErr Error occured during _sDisDrvrName.

-344 smNoMoresRsrcs No more sResources *OR*

-344 smNoMoresResources Specified sResource data structure not found

-345 smsGetDrvrErr Error occurred during _sGetDriver.

-346 smBadsPtrErr Bad pointer was passed to sCaldSPointer function

-347 smByteLanesErr ByteLanes field in card's format block was determined to be zero

-348 smOffsetErr Offset was too big (temporary,should be fixed)

-349 smNoGoodOpens No opens were successfull in the loop.

-350 smSRTOvrFlErr SRT over flow.

-351 smRecNotFnd Record not found in the SRT. Device Manager Slot Support Errors

-360 slotNumErr invalid slot # error

-400 gcrOnMFMErr gcr format on high density media error

Edition Manager Errors

-450 editionMgrInitErr Manager not initialized or could notload package

-451 badSectionErr Not a valid section type

-452 notRegisteredSectionErr Not registered

-454 badSubPartErr Bad edition container spec or invalid edition container

-460 multiplePublisherWrn Already is a publisher

-461 containerNotFoundWrn Alias was not resolved

-463 notThePublisherWrn Not the publisher SCSI Manager Errors

-470 scsiBadPBErr invalid field(s) in the parameter block

-471 scsiOverrunErr attempted to transfer too many bytes

-472 scsiTransferErr write flag conflicts with data transfer phase

-473 scsiBusTOErr bus error during transfer

-474 scsiSelectTOErr scsiSelTO exceeded (selection failed)

-475 scsiTimeOutErr scsiReqTO exceeded

-476 scsiBusResetErr the bus was reset, so your request was aborted

-477 scsiBadStatus non-zero (not "Good") status returned

-478 scsiNoStatusErr device did not go through a status phase

-479 scsiLinkFailErr linked command never executed

-489 scsiUnimpVctErr unimplemented routine was called SysErrs used instead of inline $A9FF & $ABFF

-490 userBreak user debugger break

-491 strUserBreak user debugger break - display string on stack

-492 exUserBreak user debugger break - execute commands on stack

QuickDraw Error

-500 rgnTooBigErr Bitmap would convert into a region greater than 64 KB

Text Edit Error

-501 teScrapSizeErr scrap item too big for text edit record

O/S Error

-502 hwParamrErr bad selector for _HWPriv

Processes Errors

-600 procNotFound No eligible process with specified process serial number

-601 memFragErr Not enough room to launch application with special requirements

-602 appModeErr Memory mode is 32-bit, but application is not 32-bit clean

-603 protocolErr app made module calls in improper order

-604 hardwareConfigErr hardware configuration not correct for call

-605 appMemFullErr Partition size specified in 'SIZE' resource is not big enough for launch

-606 appIsDaemon Application is background-only

-607 bufferIsSmall Buffer is too small

-608 noOutstandingHLE No outstanding high-level event

-609 connectionInvalid Connection is invalid

-610 noUserInteractionAllowed Attempted PostHighLevelEvent from background and no session                                                yet established Memory Dispatch Errors

-620 notEnoughMemoryErr Insufficient physical memory

-621 notHeldErr Specified range of memory is not held

-622 cannotMakeContiguousErr Cannot make specified range contiguous

-623 notLockedErr Specified range of memory is not locked

-624 interruptsMaskedErr Called with interrupts masked

-625 cannotDeferErr Unable to defer additional user functions

DatabaseAccess (Pack 13) Errors

-800 rcDBNull The data item was NULL

-801 rcDBValue Data available or successfully retrieved

-802 rcDBError Error executing function

-803 rcDBBadType Next data item not of requested data type

-804 rcDBBreak Function timed out

-805 rcDBExec Query currently executing

-806 reDBBadSessID Session ID is invalid

-807 rcDBBadSessNum Invalid session number

-808 rcDBBadDDEV Couldn't find the specified database extension,or error occurred in opening database extension

-809 rcDBAsyncNotSupp The database extension does not support asynchronous calls

-810 rcDBBadAsyncPB Invalid parameter block specified

-811 rcDBNoHandler There is no handler for this data type installed for the current application

-812 rcDBWrongVersion Wrong version number

-813 rcDBPackNotInited The InitDBPack function has not yet been called

Help Manager Errors

-850 hmHelpDisabled Help balloons are not enabled

-851 hmResNotFound ????

-852 hmMemFullErr ????

-853 hmBalloonAborted Because of constant cursor movement,the help balloon wasn't displayed

-854 hmSameAsLastBalloon Menu and item are same as previous menu and item

-855 hmHelpManagerNotInited Help menu not set up

-856 hmBadSelector ????

-857 hmSkippedBalloon No ballon content to fill in

-858 hmWrongVersion Wrong version of Help Manager resource

-859 hmUnknownHelpType Help message record contained a bad type

-860 hmCouldNotLoadPackage ????

-861 hmOperationUnsupported Bad method parameter

-862 hmNoBalloonUp No balloon showing

-863 hmCloseViewActive User using CloseView won't let you remove balloon

AppleTalk - PPC Toolbox Errors

-900 notInitErr PPC Toolbox has not been initialized yet

-902 nameTypeErr Invalid or inappropriate locationKindSelector in location name

-903 noPortErr Invalid port name; Unable to open port or bad port reference number

-904 noGlobalsErr System unable to allocate memory, critical error

-905 localOnlyErr Network activity is currently disabled

-906 destPortErr Port does not exist at destination

-907 sessTableErr PPC Toolbox is unable to create a session

-908 noSessionErr Invalid session reference number

-909 badReqErr Bad parameter or invalid state for this operation

-910 portNameExistsErr Another port is already open with this name

-911 noUserNameErr User name unknown on destination machine

-912 userRejectErr Destination rejected the session request

-915 noResponseErr Unable to contact application

-916 portClosedErr The port was closed

-917 sessClosedErr The session has closed

-919 badPortNameErr PPC port record is invalid

-922 noDefaultUserErr User has not specified owner name in Sharing Setup control panel

-923 notLoggedInErr Default user reference number does not yet exist

-924 noUserRefErr Unable to create a new user reference number

-925 networkErr An error has occurred in the network

-926 noInformErr PPCStart failed because target application did not have an inform pending

-927 authFailErr User's password is wrong

-928 noUserRecErr Invalid user reference number

-930 badServiceMethodErr Service method is other than ppcServiceRealTime

-931 badLocNameErr Location name is invalid

-932 guestNotAllowedErr Destination port requires authentication

AppleTalk - NBP Errors

-1024 nbpBuffOvr Buffer overflow in LookupName

-1025 nbpNoConfirm Name not confirmed on ConfirmName

-1026 nbpConfDiff Name confirmed at different socket

-1027 nbpDuplicate Duplicate name exists already

-1028 nbpNotFound Name not found on remove

-1029 nbpNISErr Error trying to open the NIS

ASP Errors (XPP driver)

-1066 aspBadVersNum Server cannot support this ASP version

-1067 aspBufTooSmall Buffer too small

-1068 aspNoMoreSess No more sessions on server

-1069 aspNoServers No servers at that address

-1070 aspParamErr Parameter error

-1071 aspServerBusy Server cannot open another session

-1072 aspSessClosed Session closed

-1073 aspSizeErr Command block too big

-1074 aspTooMany Too many clients (server error)

-1075 aspNoAck No ack on attention request (server err)

AppleTalk - ATP Errors

-1096 reqFailed Request to contact router failed: retry count exceeded

-1097 tooManyReqs Too many concurrent requests

-1098 tooManySkts Too many concurrent responding-sockets

-1099 badATPSkt Bad ATP-responding socket

-1100 badBuffNum Bad response buffer number specififed

-1101 noRelErr No release received

-1102 cbNotFound Control Block not found; no pendingasynchronous calls

-1103 noSendResp AddResponse issued without SendResponse

-1104 noDataArea No data area for request to MPP

-1105 reqAborted ERdCancel function called for this ERead [SendRequest aborted by RelTCB]

Data Stream Protocol - DSP driver Errors

-1273 errOpenDenied Open request denied by recipient

-1274 errDSPQueueSize Send or receive queue is too small

-1275 errFwdReset Read terminated by forward reset

-1276 errAttention Attention message too long

-1277 errOpening Attempt to open connection failed

-1278 errState Bad connection state for this operation

-1279 errAborted Request aborted by dspRemove or dspClose function

-1280 errRefNum Bad connection reference number

HFS Errors

-1300 fidNotFound File ID not found [No file thread exists]

-1301 fidExists File id already exists

-1302 notAFileErr Specified file is a directory

-1303 diffVolErr Files on different volumes

-1304 catChangedErr Catalog has changed and CatPosition may be invalid

-1305 desktopDamagedErr The desktop database has become corrupted - the Finder will fix this, but if your application isnot running with the Finder, use DTReset or DTDelete

AppleEvent Errors

-1700 errAECoercionFail Data could not be coerced to therequested descriptor type

-1701 errAEDescNotFound Descriptor record was not found

-1702 errAECorruptData Data in an Apple event could not be read

-1703 errAEWrongDataType Wrong descriptor type

-1704 errAENotAEDesc Not a valid descriptor record

-1705 errAEBadListItem Operation involving a list item failed

-1706 errAENewerVersion Need a newer version of the Apple Event Manager

-1707 errAENotAppleEvent Event is not an Apple event

-1708 errAEEventNotHandled Event wasn't handled by an Apple event handler

-1709 errAEReplyNotValid AEResetTimer was passed an invalid reply

-1710 errAEUnknownSendMode Invalid sending mode was passed

-1711 errAEWaitCanceled User canceled out of wait loop for replyor reciept

-1712 errAETimeout Apple event timed out

-1713 errAENoUserInteraction No user interaction allowed

-1714 errAENotASpecialFunction Wrong keyword for a special function

-1715 errAEParamMissed Handler did not get all required paramters

-1716 errAEUnknownAddressType Unknown Apple event address type

-1717 errAEHandlerNotFound No handler found for an Apple event or a coersion

-1718 errAEReplyNotArrived Reply has not yet arrived

-1719 errAEIllegalIndex Not a valid list index

AppleTalk - ATP Errors

-3101 buf2SmallErr Packet too large for buffer; partial data returned

-3102 noMPPErr No MPP error

-3103 ckSumErr Check sum error

-3104 extractErr Extraction error

-3105 readQErr Read queue error

-3106 atpLenErr ATP length error

-3107 atpBadRsp ATP bad response error

-3108 recNotFnd Record not found

-3109 sktClosedErr Socket closed error

Print Manager w/LaserWriter Errors

-4096 ??? No free Connect Control Blocks available

-4097 ??? Bad connection reference number

-4098 ??? Request already active

-4099 ??? Write request too big

-4100 ??? Connection just closed

-4101 ??? Printer not found, or closed

File Manager Extensions Errors

-5000 accessDenied Incorrect access for this file/folder

-5006 DenyConflict Permission/Deny mode conflicts with the current mode in which this fork is already open

-5015 NoMoreLocks Byte range locking failure from Server

-5020 RangeNotLocked Attempt to unlock an already unlocked range

-5021 RangeOverlap Attempt to lock some of an already locked range

AFP Errors (XPP driver)

-5000 afpAccessDenied AFP Access denied

-5001 afpAuthContinue AFP Authorization continue

-5002 afpBadUAM AFP Bad UAM

-5003 afpBadVersNum AFP Bad version number

-5004 afpBitmapErr AFP Bit map error

-5005 afpCantMove AFP Can't move error

-5006 afpDenyConflict AFP Deny conflict

-5007 afpDirNotEmpty AFP Dir not empty

-5008 afpDiskFull AFP Disk full

-5009 afpEofError AFP End-of-File error

-5010 afpFileBusy AFP File busy

-5011 afpFlatVo AFP Flat volume

-5012 afpItemNotFound AFP Information not found

-5013 afpLockErr AFP Lock error

-5014 afpMiscErr AFP Misc error

-5015 afpNoMoreLocks AFP No more locks

-5016 afpNoServer AFP No server

-5017 afpObjectExists AFP Object already exists

-5018 afpObjectNotFound AFP Object not found

-5019 afpParmErr AFP Parm error

-5020 afpRangeNotLocked AFP Range not locked

-5021 afpRangeOverlap AFP Range overlap

-5022 afpSessClosed AFP Session closed

-5023 afpUserNotAuth AFP User not authorized

-5024 afpCallNotSupported AFP Call not supported

-5025 afpObjectTypeErr AFP Object type error

-5026 afpTooManyFilesOpen AFP Too many files open

-5027 afpServerGoingDown AFP Server going down

-5028 afpCantRename AFP Can't rename

-5029 afpDirNotFound AFP Directory not found

-5030 afpIconTypeError Size of new icon and one it replaces don't match

-5031 afpVolLocked Volume is Read-Only

-5032 afpObjectLocked Object is M/R/D/W inhibited

SysEnvirons Errors

-5500 envNotPresent SysEnvirons trap not present - returned by glue.

-5501 envBadVers Version non-positive

-5502 envVersTooBig Version bigger than call can handle

Gestalt Errors

-5550 gestaltUnknownErr Could not obtain the response

-5551 gestaltUndefSelectorErr Undefined selector

-5552 gestaltDupSelectorErr Selector already exists

-5553 gestaltLocationErr Function not in system heap

Article Change History:

29 Nov 1995 - Corrected minor typo.

07 Dec 1994 - Corrected spelling.

25 Sep 1992 - Reviewed for technical accuracy.

Support Information Services

Copyright 1992-95, Apple Computer, Inc.

Keywords: sys7,ktoptil

Sad Mac Error Codes

TITLE

Macintosh: "Sad Mac" Error Code Meaning◊

Article ID: 7748

Created: 7/2/91

Modified: 9/9/97

TOPIC

When I turn on my Macintosh, I get a black screen with a "sad Macintosh" face and the numbers

020016. There is no listing for this error code in any of my manuals. What does it mean?

DISCUSSION

The particular error code that appears with the "sad Macintosh" is not

as important as WHEN it occurs. If the Macintosh can start up from a

different system diskette, then the problem is probably with the system

software on the other disk. System problems are usually identified when

you get a "happy Macintosh" face and the "Welcome to Macintosh" screen

before the "sad Macintosh."

If the "sad Macintosh" face appears immediately at power up, that usually

suggests an issue with the logic board or memory. Try starting up from a

floppy disk before assuming it's a hardware problem.

Sad Mac Error Codes Description

On the Original ROMs (Macintosh 128k, 512k, 512ke, Plus):

When you press the interrupt button on the side of your Macintosh when

starting up, you should get a sad Mac icon with '0F000D' and some bits

cycling under the icon indicating it is performing a memory test.

This numeric code is in two parts:

• The first two characters are the class code. The class code tells

what part of the diagnostic program found the error.

• The second four are the sub code. The sub class code tells what the

error was. In the case of a bad RAM chip, the sub class identifies

the bad chip (this was very helpful to homegrown upgraders). 

Class Code  Sub Code 1 = ROM test failed Meaningless 2 = Memory test - bus subtest identifies bad chips 3 = Memory test - byte write identifies bad chips 4 = Memory test - Mod3 test identifies bad chips 5 = Memory test - address uniqueness identifies bad chips

Single Chip Identification Data Bit    Location   Sub Code Bits  0             F5           0001  1             F6           0002  2             F7           0004  3             F8           0008  4             F9           0010  5             F10          0020  6             F11          0040  7             F12          0080  8             G5           0100  9             G6           0200 10             G7           0400 11             G8           0800 12             G9           1000 13             G10          2000 14             G11          4000 15             G12          8000 Class Code      Sub Code F = Exception   0001 Bus error                 0002 Address error                 0003 Illegal instruction                 0004 Zero divide                 0005 Check instruction                 0006 Traps instruction                 0007 Privilege violation                 0008 Trace                 0009 Line 1010                 000A Line 1111                 000B Other exception                 000C Nothing                 000D NMI (normal indication)                 0064 Couldnt Read System File into Memory Macintosh SE & Macintosh II ROMs:  The Sad Mac error codes have been changed to incorporate additional power for testing and to support the 32-bit world. Generally, the same codes are used for 68000 exceptions as the Macintosh, however they are displayed differently. Traditional The traditional Macintosh error codes are displayed like this:  0F0003 Where F indicates an exception occurred, and 3 indicates an illegal instruction occurred. On the Macintosh SE and II, the display would appear:  0000000F 00000003 Note: 0000003 is a hex number. Power On The new power-on error codes have the following format: XXXXYYYY ZZZZZZZZ Where XXXX is internal test manager state information (ignore this), YYYY contains codes that indicate either an exception code, or the test number for a power on test failure. The ZZZZZZZZ code contains additional failure information to help track down the problem. YYYY Error Codes: $0001   The ROM checksum test failed. Ignore the Z field. $0002   The first small chunk of RAM to be tested failed. The Z field indicates which RAM Bit(s) failed. This small chunk of RAM is always in Bank B.    Example:   $AABBCCDD                    AA=8 bit mask for bits 31-24                    BB=8 bit mask for bits 23-16                    CC=8 bit mask for bits 15-8                    DD=8 bit mask for bits 7-0 $0003   The RAM test failed while testing bank B, after passing the chunk tested for code $0002. The Z field indicates which bits failed as in code $0002. $0004   The RAM test failed while testing bank A. The Z field indicates which  bits failed as in code $0002. $0005   The RAM External addressing test failed. The Z field indicates a failed address line. $0006   Unable to properly address the VIA1 chip. The Z field is not applicable. $0007   Unable to properly address the VIA2 chip (Macintosh II only). The Z field is not applicable. $0008   Unable to properly access the Front Desk Bus. The Z field is not applicable. $0009   Unable to properly access the MMU. The Z field is not applicable. $000A   Unable to properly access NuBus. The Z field is not applicable. $000B   Unable to properly access the SCSI Chip. The Z field is not applicable. $000C   Unable to properly access the IWM chip. The Z field is not applicable. $000D   Unable to properly access the SCC Chip. The Z field is not applicable. $000E   Failed Data Bus test. The Z field indicated the bad bit(s) as a 32-bit mask for bits 0-31. This may indicate either a bad SIMM or data bus failure. $000F   Reserved for Macintosh compatibility. $FFxx   A 680xx exception occurred during power on testing.         The xx indicates the exception:         $01  Bus Error         $02  Address Error         $03  Illegal Instruction Error         $04  Zero Divide         $05  Check Instruction         $06  cpTrapCC, Trap CC, Trap V         $07  Privilege violation         $08  Trace         $09  Line A         $0A  Line F         $0B  unassigned         $0C  CP protocol violation         $0D  Format exception         $0E  Spurious interrupt         $0F  Trap 015 exception         $10  Interrupt Level 1         $11  Interrupt Level 2         $12  Interrupt Level 3                  $13  Interrupt Level 4         $14  Interrupt Level 5         $15  Interrupt Level 6         $16  Interrupt Level 7         $17  FPCP bra or set on unordered condition         $18  FPCP inexact result         $19  FPCP divide by zero         $1A  FPCP underflow         $1B  FPCP operand error         $1C  FPCP overflow         $1D  FPCP signalling NAN         $1E  PMMU configuration         $1F  PMMU illegal operation         $20  PMMU access level violation Macintosh Portable ROMs: The bootup code in the Macintosh Portable contains a series of startup tests that are run to ensure that the fundamental operations of the machine are working properly. If any of those tests fail, a Sad Mac icon appears on the screen with a code below that describes what failure occurred. Here is a typical example of a Sad Mac display with an error code below it: SAD MAC CODE 05460203   =   (D7.L) 000OB6DB   =   (D6.L) The two codes are actually the contents of the two CPU data registers D6 and D7. The upper word (upper 4 hex digits, in this case 0546) of D7 contains miscellaneous flags that are used by the start-up test routines and are unimportant to just about everybody except a few test engineers within Apple. The lower word of D7 is the major error code. The major error code identifies the general area the test routines were in when a failure occurred. D6 is the minor error and usually contains additional information about the failure, something like a failed bit mask. SAD MAC CODE BROKEN DOWN Test Flags    Major Error  0546          0203 Minor Error   Minor Error 0000          B6DB The major error is further broken into the upper byte that contains the number of any 68000 exception that occurred ($00 meaning that no exception occurred), and the lower byte that usually contains the test that was being run at the time of failure. If an unexpected exception occurred during aparticular test, then the exception number is logically ORed into the major error code. This way both the exception that occurred as well as the test that was running can be decoded from the major error code: SAD MAC CODE FURTHER BROKEN DOWN 68000 Exception    Test Code 02                  03 In this example, the code says that an address error exception ($0200) occurred during the RAM test for Bank A ($03); $0200 ORed with $03 = $0203. Major Error Codes Below is a brief description of the various test codes that might appear in the major error code: **Warning**: Some of these codes may mean slightly different things in Macintosh models other than the Macintosh Portable. These descriptions describe specifically how they are used in the Macintosh Portable. $01   - ROM test failed. Minor error code is $FFFF, means nothing. $02   - RAM test failed. Minor error code indicates which RAM bits failed. $05   - RAM external addressing test failed. Minor error code indicates a failed address line. $06   - Unable to properly access the VIA 1 chip during VIA         initialization. Minor error code not applicable. $08   - Data bus test at location eight bytes off of top of memory failed.  Minor error code indicates the bad bits as a 16bit mask for bits 1500. This may indicate either a bad RAM chip or data bus failure. $0B  -  Unable to properly access the SCSI chip. Minor error code not applicable. $0C  -  Unable to properly access the IWM (or SWIM) chip. Minor error code not applicable. $0D  -  Not applicable to Macintosh Portable. Unable to properly access the SCC chip. Minor error code not applicable. $0E  -  Data bus test at location $0 failed. Minor error code indicates the bad bits as a 16bit mask for bits 1500. This may indicate either a bad RAM chip or data bus failure. $10  -  Video RAM test failed. Minor error code indicates which RAM bits failed. $11  -  Video RAM addressing test failed. Minor error code contains the following: upper word    =       failed address (16-bit) msb of lower word    =       data written     lsb of lower word    =       data read Data value written also indicates which address line is being actively tested. $12  -  Deleted $13  -  Deleted $14  -  Power Manager processor was unable to turn on all the power to the board. This may have been due to a communication problem with the Power Manager. If so, the minor error code contains a Power Manager error code, explained in the next section. $15  -  Power Manager failed its self-test. Minor error code contains the following: msw  = error status of transmission to power manager.  lsw  = Power Manager self-test results (0 means it passed, non-zero means it failed) $16  -  A failure occurred while trying to size and configure the RAM.  Minor error code not applicable. Minor error codesPower Manager Processor Failures If a communication problem occurs during communication with the Power Manager, the following error codes will appear somewhere in the minor error code (usually in the lower half of the code, but not always): $CD38   Power Manager was never ready to start handshake. $CD37   Timed out waiting for reply to initial handshake. $CD36   During a send, Power Manager did not start a handshake. $CD35   During a send, Power Manager did not finish a handshake. $CD34   During a receive, Power Manager did not start a handshake. $CD33   During a receive, Power Manager did not finish a handshake. Diagnostic Code Summary Below is a summarized version of the Sad Mac error codes: Test Codes       $01     ROM checksum test.       $02     RAM test.       $05     RAM addressing test.       $06     VIA 1 chip access.       $08     Data bus test at top of memory.       $0B     SCSI chip access.       $0C     IWM (or SWIM) chip access.       $0D     Not applicable to Macintosh Portable. SCC chip access.       $0E     Data bus test at location $0.       $10     Video RAM test.       $11     Video RAM addressing test.       $14     Power Manager board power on.         $15     Power Manager self-test.       $16     RAM sizing. Power Manager Communication Error Codes       $CD38   Initial handshake.       $CD37   No reply to initial handshake.       $CD36   During send, no start of a handshake.       $CD35   During a send, no finish of a handshake.       $CD34   During a receive, no start of a handshake.       $CD33   During a receive, no finish of a handshake. CPU Exception Codes (as used by the startup tests)       $0100   Bus error exception code       $0200   Address error exception code       $0300   Illegal error exception code       $0400   Zero divide error exception code       $0500   Check inst error exception code       $0600   cpTrapcc,Trapcc,TrapV exception code       $0700   Privilege violation exception code       $0800   Trace exception code       $0900   Line A exception code       $0A00   Line F exception code       $0B00   Unassigned exception code       $0C00   CP protocol violation       $0D00   Format exception       $0E00   Spurious interrupt exception code       $0F00   Trap inst exception code       $1000   Interrupt level 1       $1100   Interrupt level 2       $1200   Interrupt level 3       $1300   Interrupt level 4       $1400   Interrupt level 5       $1500   Interrupt level 6       $1600   Interrupt level 7 Troubleshooting System Errors Low Memory Conditions Many errors can be traced to low memory conditions. To make sure an application receives its full allotment of memory, quit other applications and close unnecessary windows. Next, try increasing the memory allocated to the application -- How to increase Application Memory... Step 1) Click once on the application to select it, then choose "Get Info" from the File menu. Step 2) Increase the "Preferred Size" to at least the Suggested Size. If it is already larger than the Suggested size, try increasing the Preferred Size in increments of 500. Apple-recommended procedures It's a good idea to save your work frequently, and keep current backup copies of your hard disk data. When a system crash occurs, you'll lose less data if you've taken these precautions. If you're getting system errors frequently, investigate these possibilities: • Try to open the document with a current version copy of the application. • Try opening other documents with the same copy of the application. • Check to see if the document size exceeds the application size limits. • Boot your system with extensions off (restart while holding the Shift key down). • Any changes (new Control Panels, extensions, etc.) you've made to the system might give you a clue to the cause of the crashes. • Make a note of the desk accessories you had open at the time of the crash and exactly what you did before the crash. • Also make a note of the error ID or text, and the version numbers of the application and system software you were using. • Try to recreate the problem on another Macintosh. • Cleanly install your system software and try the application again.