giovedì 11 novembre 2010

Apple Error Codes - Codici degli errori Apple

L'altro giorno mi trovavo a far girare Photoshop 5.0 su Mac OS 9 in virtuale, e ad un certo punto mi ha sparato un indimenticabile, per chi l'ha vissuto, finestra bomba con allegato "error type" (nell'immagine, col nome del blog sostituito a quello dell'applicazione).
Nella maggior parte dei casi bisognava riavviare, a suo tempo era uno stress che oggi diventa anche simpatico ricordare... se solo ricordassi cosa significavano quegli errori.

Ecco perciò la lista, l'ho ricavata dalla cache di un sito che non esiste più, e che si appoggiava a, che pure non esiste più.

La rendo disponibile, potrebbe servire a qualcuno. Sicuramente ci saranno altre liste online, ma è talmente vasta che non perdo tempo a verificare se coincidono, faccio prima a pubblicarla direttamente. A Voi.

PARTE 1: Error Codes 1-30
PARTE 1.1: Power Macintosh: Meaning of Error Type 11 (7/96) Power Macintosh: Type 11 & No FPU Errors Technote (7/96)
PARTE 2: Negative Error Codes 0 to -99
PARTE 3: Negative Error Codes -100 to -199
PARTE 4: Negative Error Codes -200 to -261
PARTE 5: Negative Error Codes -290 to -5533
PARTE 6: Apple Remote Access(ARA) Error Codes (-5800 to -7199)
PARTE 7: Error codes for AOCE (Apple Open Collaborative Environment) -15000 to -15199
PARTE 8: Mac TCP Error Codes (-23000 to -23099)
PARTE 9: Open Transport/PPP, Error Codes (7100 to 7199)
PARTE 10: Sad Mac Error Codes



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
Click here to view article: Power Macintosh: Meaning of Error Type 11 (7/96)
Click here to view article: Power Macintosh: Type 11 & No FPU Errors Technote (7/96)

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.



Power Macintosh: Meaning of Error Type 11 (7/96)
Article Created: 8 August 1994
Article Reviewed/Updated: 02 July 1996

I get an error Type 11 on my Power Macintosh computer when a program crashes. I never got this error on my 68k based Macintosh computers. Is this a new error for the Power Macintosh?

A Type 11 error is listed as a hardware exception error. However, As with all Macintosh Type xx errors, they usually do not identify a particular software or hardware component error. Type xx errors are more general in nature. You may see more Type 11 errors on a Power Macintosh computer because of problems with the software-based 68k emulator. The emulator allows the RISC processor to run older Macintosh software. If the emulator gets corrupted while loading into RAM, then some of the failures caused by this are reported as Type 11 or Hardware Exception errors. The emulator can get corrupted by either incompatible software or faulty ardware.

Troubleshooting Type 11 Errors
When troubleshooting Type 11 errors, always eliminate software problems first, then check the hardware.To troubleshoot the problem, follow these steps:

Step 1
Upgrade your hard disk drivers and system software to the latest versions available.

Step 2
Contact the software vendor for compatibility information if the problem only occurs in one application, and you can reproduce it consistently.

Step 3
Turn off all extensions and control panels if the error occurs in an application that is fully compatible with a Power Macintosh computer. Check the application again. If the problem goes away, then troubleshoot your extensions, control panels or fonts. Large numbers of fonts can cause similar errors, troubleshoot by moving them from the Fonts folder to another folder. If you still have problems, follow Step 4.

Step 4
Perform a clean installation of the system software, then test the system performance for a few days. If the problems continue, particularly in the Finder, there may be an issue with your Apple or non-Apple hardware.

Step 5
Disconnect any external or internal SCSI devices that have been may added (or exchanged for the original Apple hardware) and continue testing. Since SCSI device drivers load into memory when the Macintosh is turned on, they can generate conflicts similar to extension conflicts. If you are using a non-Apple formatting utility, contact the vendor of the utility for compatibility information. Removing internal SCSI devices is best performed by an Apple-authorized service provider.

Step 6
Remove any extra third-party RAM and test. This is best performed by an Apple-authorized service provider. Also verify that you are not using composite RAM.

Step 7
Remove Level 2 Cache RAM, if present, and test. If you continue to get Type 11 errors using a clean version of the system software without any third-party hardware attached (including internal or external SCSI devices, additional RAM, or Level 2 cache RAM), you need to have your computer serviced by an Apple-authorized service rovider.

For additional information about the cause of Type 11 errors, see Tech Info article, "Power Macintosh: Type 11 & No FPU Errors Technote."

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.

Copyright 1994-96, Apple Computer, Inc.

Keywords: kppc,ktoptil,kfax
This information is from the Apple Technical
Information Library.
ArticleID: TECHINFO-0016004
19960724 15:55:27.00

Power Macintosh: Type 11 & No FPU Errors Technote (7/96)
Article Created: 10 November 1995
Article Reviewed/Updated: 02 July 1996

This Technote explains some of the causes of "Type 11" and "No FPU Installed" errors, along with debugging hints to help you find and fix them. It also focuses on what you as a programmer can do to prevent such errors.

Both Type 11 and No FPU Installed errors occur on Power Macintosh computers, depending on various factors. Both error messages are the result of programming errors. The No FPU Installed error usually means that your program is executing data rather than instructions. The Type 11 error is any error (such as a bus error) in native code.
NOTE: In this Technote, I will occasionally mention third-party products by name. If a third-party product is mentioned by name, it's meant to be a possible solution for you to investigate, not a recommendation. DTS doesn't evaluate third-party tools, nor maintain complete lists of possible third-party solutions. You should consult catalogs of development tools such as:
  • Macintosh Development Tools & Languages
  • the Redgate Macintosh Registry
  • the ubiquitous Internet
  • the APDA catalog and
  • reviews in technical magazines to find a product that fits your needs.
There are many Web sites on the Internet for example, Apple's Third-Party Development Products Database at lists many Macintosh development tools. Perhaps you may find an appropriate tool to meet your development needs in this way.

About "No FPU Installed" Errors
On a Power Macintosh computer, the error message No FPU Installed usually means your code has jumped to a non-code area and is executing garbage. Somewhere in that data (which is being interpreted as instructions) is an instruction whose op code begins with the hex value F. No FPU Installed is equivalent to a Type 10 Error i.e., your program has attempted to execute an unknown instruction op code starting with the hex value F.
On a Power Macintosh, No FPU Installed means that some program has jumped to an area of data and has tried to execute any data word starting with the hex value F. The PowerPC chip has floating point support built in, but that floating-point support is different from the Motorola 680x0 family floating- point support. The Motorola 680x0 family uses an external floating-point unit. (There are also external memory management units (MMUs) and other specialized coprocessors.) Motorola 680x0 CPUs use instructions starting with hex value F as instructions for these coprocessors.

680x0 Microprocessor Instructions
All Motorola 680x0 microprocessors have instructions consisting of at least one word (the operation word); some instructions can have up to eleven words (see the Motorola MC68020 32-bit Microprocessor User's Manual, Third edition, page 3-1.) The operation word determines what kind of instruction is to be executed.
For example, the instruction
translates to the hexadecimal value
This instruction starts with the hex value 1. The instruction
translates to
F227 6980
This instruction starts with the hex value F.

F-line Instructions
The Motorola 680x0 architecture was originally designed to support a floating- point coprocessor chip. This chip, the Floating Point Unit (FPU), communicates with the CPU via a special set of instructions called F-line instructions. These instructions always start with an operation word beginning with the hex value F.
A program can be compiled to take advantage of the hardware assistance the FPU provides, and thus yield faster floating-point calculations than would be available with SANE (the Standard Apple Numerics Package). Such programs would have instructions in the program which start with the hex value F. A program only using SANE would never have an instruction starting with the hex value F.
NOTE: Some Macintosh models, such as the Macintosh SE/30, the Macintosh IIci, and the Macintosh IIfx, shipped with an FPU coprocessor installed. Other 680x0-based Macintosh computers, such as the Macintosh IIsi and the Macintosh Color Classic, had an optional FPU coprocessor. For these machines, it was possible to purchase an optional card with an FPU coprocessor.

68040 & 68040LC Microprocessors
With the introduction of the 68040 and 68040LC chips, things got a bit more complicated. The 68040 microprocessor has most of the 68882 FPU included on the chip. Not everything in the 68881/68882 FPU is in the 68040 chip, however just the routines that Motorola determined were most frequently used. The rest of the FPU routines are automatically emulated by software. Because the FPU is "built-in," as it were, the 68040 chip handles instructions that start with an operation word beginning with the hex value F by itself. There is no way to add a coprocessor to a 68040 chip; the instructions are never brought out of the chip itself.
The 68040LC is a cost-reduced version of the 68040 chip. Savings came about by removing the FPU portion of the chip. Not only does a 68040LC chip have no FPU, there is no way to add one.

The Power Macintosh
Power Macintosh computers emulate a Motorola 68040LC, i.e., a machine without FPU support. When you get a bomb with the message No FPU installed, it means some instruction has been executed with an operation word starting with the hex value F, and that your program is running on a machine without a FPU. This machine could be one of the following:
  • a Macintosh with a 68020 or 68030 microprocessor and no FPU coprocessor
  • a Macintosh with a 68040LC microprocessor (which can never have a FPU)
  • a Macintosh with a PowerPC chip running 68K code in emulation (since the 68K emulator emulates a 68040LC microprocessor).
Power Macintosh computers contain very fast floating-point support as part of the CPU. This floating-point support is different from the floating-point support provided by the Motorola 680x0 microprocessors. Inside Macintosh:PowerPC Numerics, describes Power Macintosh floating-point support.

Defining a Type 11 Error
A Type 11 error means an illegal interrupt vector on a 680x0 machine. On a Power Macintosh, a Type 11 error is any exception in native code not handled by one of the installed exception handlers. On a Power Macintosh, a Type 11 error can be almost any error that occurred in native code. Type 11 errors may include:
  • an address error
  • a bus error
  • an illegal instruction error that occurred in native code.
The exception handlers installed for native code don't correctly handle the particular condition which was raised, and the error is returned back to the System Error manager via the Mixed Mode manager. The System Error manager maps all such exceptions to the system error Type 11 Error.
If you install Macsbug 6.5.2 or later, some Type 11 errors may be reported as a PowerPC unmapped memory exception. This is equivalent to a bus error, i.e., an error indicating your program is accessing memory that doesn't exist.
The Modern Memory Manager was designed to be less forgiving than the classic (68K) Memory Manager. Disposing of something twice, disposing of memory that was never allocated, and other memory handling problems will often generate a Type 11 error, while on a 68K machine the problem may go unnoticed.

Programming Mistakes Causing Type 11 Errors
The following sections give you examples of programming mistakes that may cause Type 11 errors.

Example #1: Writing Past the End of an Array
Writing past the end of an array can be a subtle and difficult-to-find bug. Example #1 shows you why.
;Begin C Code
void IAmGoingToCrash(void)
Str27 badArray;
BlockMoveData("\pThis string is too long for this array",
badArray, 39);
;End C Code

NOTE: I've made the bug very obvious; it may not be quite so obvious, however, in your code. In this example, I've put a string of 39 characters into an array defined to hold 27 characters. This overwrites the stack, which contains such useful things as your return address. On a 68K Mac, this causes a bus error. On a PowerPC Mac in 68K emulation, this causes a bus error. On a Power Macintosh in native code, this causes a Type 11 error.

Example #2: Using a Poorly Initialized Pointer or Handle
If your program tries to use an uninitialized or badly initialized pointer, it can generate a Type 11 error.
Here is what happens in Example #2:
;Begin C Code
Ptr badPointer = (Ptr)-2;
*badPointer = 0;
;End C Code

NOTE: I've made the bug very obvious; it may not be quite so obvious, however, in your code. In this example, I've created a pointer to non-existent memory (-2 isn't a valid address) and then tried to access the memory to which the pointer refers. On a 68K Mac, this causes a bus error. On a PowerPC Mac in 68K emulation, this also causes a bus error. On a Power Macintosh in native code, this causes a Type 11 error.

Other Situations Causing Type 11 Errors
The following sections document some of the known bugs in various products that may cause Type 11 errors.

Color Picker vs Third-Party SCSI Drivers
One reproducible problem stems from a known bug in several third-party SCSI hard disk drivers. The bug causes the Color Picker to crash when trying to resolve a boot volume alias it makes at startup time. This problem exists in any system when Color Picker 2.0 or 2.0.1 is installed and the boot volume is not a removable drive. The fundamental cause of the problem is that the SCSI driver incorrectly marks the boot drive as a removable drive during the boot process and changes it to be properly marked as a fixed device after startup. To find its code, the Color Picker resolves the boot volume alias it made during startup. Since the alias passed to the Alias Manager is for a removable drive, the Alias Manager can't resolve the alias (since the device is now marked as fixed.) The Color Picker design did not anticipate the boot volume not being found. This results in a Type 11 error. The fix is to upgrade your SCSI driver to a later version.

Calling a Routine That May Move Memory at Interrupt Time
The Apple Media Kit, release 1.2, had a problem that could cause random errors. During a VBL task, AMK was calling SetCCursor. SetCCursor can possibly move memory. Moving memory during interrupt time is a very bad idea. The Memory Manager may be in an unstable state, such as compacting memory, when an interrupt routine gets called. This can cause a Type 11 error in native code. A replacement cursor.c file has been provided in the Apple Media Tool/Programming Environment Runtime folder, and we do have a replacement Runtime Maker:Codes:Program file for Apple Media Tool. If you are currently developing titles, replacing these files and rebuilding your projects will remove the bug.

Not Enough Heap Space
There are some situations where having small amounts of memory available in the system heap may lead to a Type 11 error. As an example, if the shared library manager can't load a shared library, you may get a Type 11 error. This can happen when QuickTime tries to load a decompressor for certain kinds of images.

Writing Past the End of an Array
In OpenTransport 1.0.5 or earlier, there was a bug in the TCP/IP control panel code that could corrupt memory if there were more than 256 zones and a MacIP server was found in a zone past the 256th zone. Under these conditions, the control panel code wrote past the end of one of its buffers. This bug would manifest itself if the user opened the select zone dialog and the TCP/IP control panel was left open long enough for the NBP lookup calls for zones past the 256th zone to complete. This is corrected in OpenTransport 1.0.6 and later, but is given here as an example of a Type 11 error.

Insufficient Stack Space
Heavy use of local variables or recursion may cause your program to run out of stack space. When this happens, you may have crashes that are difficult to track down. Increasing your program's stack is one solution. Whenever you are using a large number of local variables or recursive routines, you should increase your program's stack (using the procedure listed in Inside Macintosh: Memory on page 1-40).
As an extreme example, a faceless background application (documented in Technical Note PS 2) has only a 2K stack by default. A 68K application has 24K of stack on most modern machines (8K if no Color QuickDraw is installed, 32K if A/UX is installed.) You can use the low memory accessor function LMGetDfltStack to find your current stack size. Native QuickDraw has several changes in algorithms that have increased the size of some structures. PowerPC alignment issues may cause the size of data structures to increase. Check your compiler documentation for further details.
To help detect collisions between the stack and the heap, a stack sniffer VBL task is installed that compares the current ends of the stack and heap and generates a system error 28 in case of a collision. Unfortunately, the Thread Manager is forced to disable the stack sniffer whenever it is installed. (This is because threads can have a stack in places where the stack sniffer doesn't expect them; if the stack sniffer is enabled, it would generate a system error 28.) This means you don't have the same level of protection as you did under older system software versions without the Thread Manager installed.

Too Much Recursion in QuickDraw
Native QuickDraw before version 2.4.1 used a recursive routine to handle regions. This recursive code could cause your stack to run into the heap when handling certain region shapes. Version 2.4.1 of QuickDraw changed to a non-recursive routine which eliminates this error. (You can detect the version of QuickDraw using the Gestalt selector qd which returns a version.) In general, recursion on PowerMacs is dangerous unless you have substantial stack space available; PowerPC stack frames are very large, and putting many of them on the stack may quickly exhaust available stack.

Interrupts Not Handled by Device Drivers
Some Type 11 errors may legitimately be illegal interrupt vector errors, rather than simply unhandled exceptions in native code. If a device driver for a NuBus or PCI card does not install an interrupt service routine, but the card raises an interrupt, you will receive a Type 11 error. This will happen whether you are running in 68K code or PowerPC code. The only solution for such a problem is to update the driver to correctly handle the interrupt issued by the card.

Other Programming Errors
Common programming errors may cause Type 11 or No FPU Installed errors. These include the same kinds of errors that usually result in address errors on 680x0-based Macintosh computers. For example:
  • Indexing through an array incorrectly so that your program goes outside the memory allocated for that array (as demonstrated above).
  • Disposing of memory twice
  • Disposing of memory that was never allocated
  • Calling DisposeHandle on a resource handle (use DisposeResource instead, to ensure that the Resource Manager doesn't lose handles behind its back.)
Some Techniques To Help Avoid Type 11 Errors
The following techniques may help resolve situations that might lead to Type 11 errors:
  • Test your code carefully.
  • Install the Debugging Modern Memory Manager, available on the Tool chest Developer CD. This version of the Modern Memory Manager has additional checks installed which allow you to track down and eliminate many memory management bugs.
  • Use extensions such as EvenBetterBusError (found on the Tool chest Developer CD) in conjunction with Macsbug 6.5.2 or later, to detect use of uninitialized pointers or handles.
  • Use third-party testing tools such as QC by Onyx or MemoryMine by Adianta.IMPORTANT: It goes without saying that good testing before you release a product will prevent expensive customer support calls later on.
User-Level Recommendations
Here are some user-level suggestions recommended by Apple for unexplained Type 11 or No FPU installed errors:
  1. Upgrade your hard disk driver(s) to the latest version available. There are some known problems between SCSI Manager 4.3 and some SCSI disk drivers. Starting with System 7.5, the SCSI Manager 4.3 is installed on all Macintosh Quadras and Power Macintosh computers. There are some known programming problems in some older third-party disk drivers.
  2. Upgrade to the latest System Software appropriate for your system. Several significant bug fixes in system updates should reduce the number of Type 11 and No FPU Installed errors you encounter.
  3. Do a clean install of your System Software. Use the Extensions Manager control panel to determine if any additional control panels or extensions are conflicting with your system software.
  4. Some Type 11 errors may result from corrupted PRAM. Unfortunately, most of extended PRAM is undocumented. (See Inside Macintosh:Operating System Utilites, chapter 7, Parameter RAM Utilities, for what details are documented.) You can restore your default PRAM values by holding down Command-Option-P-R at system startup time, or by using a shareware utility such as TechTool.
  5. Make sure you are not using composite RAM in a Power Macintosh. Memory specifications are in the developer hardware notes for each computer.
  6. Some users claim that installing the shareware extension SoftwareFPU cuts down on No FPU Installed problems. This extension emulates the Motorola FPU (at a considerably slower speed), thus preventing bombs from software which incorrectly makes FPU calls. This may alleviate no FPU Installed errors, but it doesn't address the fundamental problem, namely that some software is executing unexpected data or making illegal calls to a non-existent FPU.
  7. Upgrade any software you find that causes repeatable errors.
There are no easy solutions for handling Type 11 Error or No FPU Installed errors. Only careful debugging and testing can reduce the number and frequency of these errors. Most problems stem from common programming errors.

Further Reference

  • Inside Macintosh, PowerPC System Software, Addison-Wesley
  • Inside Macintosh:PowerPC Numerics, Addison-Wesley
  • Macsbug Reference and Debugging Guide, Addison-Wesley
  • Macsbug Release Notes, part of the distribution of Macsbug
  • Motorola MC68020 32-bit Microprocessor User's Manual, Third edition (available from Motorola)
  • PowerPC Microprocessor Family: The Programming Environment (available from IBM or Motorola)
  • Inside Macintosh:Memory, Addison-Wesley
This article provides information about a non-Apple product. Apple Computer, Inc. is not responsible for its content. Please contact the vendor for additional information. The Tech Info Library article titled "Locating Vendor Information" can help you search for a particular vendor's address and phone number.

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.

Copyright 1995-96, Apple Computer, Inc.

Keywords: kppc,supt,ksts,hts,ktoptil,kfax
This information is from the Apple Technical
Information Library.
ArticleID: TECHINFO-0018912
19960724 15:55:27.00



Negative Error Codes 0 to -99

0 noErr 0 is generally considered success, or no error.
General System Errors (VBL Mgr, Queue)

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

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 occurre
-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

Macintosh System Error Codes Explained (11/95)

Article Created: 19 February 1986
Article Reviewed/Updated: 20 November 1995

Support Information Services
Copyright 1986-94, Apple Computer, Inc.
01749: TIL



Negative Error Codes -290 to -5533

Notification Manager Error

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

Start Manager Errors

Result code
-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 is not running with the Finder, use DTReset or DTDelete

AOCE General Errors (-1500 to -1521)
-1500  kOCEToolboxNotOpen toolbox not open; perhaps it's closing
-1501 kOCEInvalidCommand request code passed to trap call invalid
-1502 kOCEInvalidRef reference to object obsolete/invalid
-1503 kOCEBufferTooSmall buffer supplied too small for task
-1504 kOCEVersionErr some manner of software version mismatch
-1505 kOCESyncAsyncErr op tried synchronously; may only be done async, or vice versa
-1506 kOCEInternalErr OCE toolbox has an internal error
-1507 kOCENotAnOwner operation can only be done by object's owner
-1508 kOCENotImplemented feature not implemented
-1509 kOCENotAuthenticated user must be authenticated
-1510 kOCEAlreadyExists object being added already exists
-1511 kOCEDoesntExist object being referenced doesn't exist or cannot be found
-1512 kOCEConnectionErr unable to open or maintain network transport
-1513 kOCEConnectionClosed connect has closed
-1514 kOCEInvalidRecipient invalid recipient/address for command
-1515 kOCEInvalidIndex invalid index (out of range)
-1516 kOCERefIsClosing object references being closed, cannot complete command
-1517 kOCEHasPendingMsgs  
-1518 kOCEInvalidConfiguration  
-1519 kOCERequiredServicesNotAvailable  
-1520 kOCEServerInactive  
-1521 kOCEMoreDiskSpaceNeeded inadequate disk space to safely complete operation
-1522  kOCEParamErr paramErr invalid parameter passed to toolbox

AOCE Authentication Errors (-1540 to -1571)
-1540 kOCEReadAccessDenied  
-1541 kOCEWriteAccessDenied  
-1542 kOCEAccessRightsInsufficient stream needs to be authenticated, or not authorized, or someone other than agent trying to TPFC, or problem in server-to-server authentication
-1543 kOCEUnsupportedCredentialsVersion don't know how to read version of credentials
-1544 kOCECredentialsProblem couldn't successfully decrypt credentials
-1545 kOCECredentialsImmature current time < first valid time
-1546 kOCECredentialsExpired current time > expiry time
-1547 kOCEProxyImmature current time < proxy start time
-1548 kOCEProxyExpired current time > proxy expiry time
-1549 kOCEDisallowedRecipient recipient not specified in proxy
-1550 kOCENoKeyFound found no key for entity in question
-1551 kOCEPrincipalKeyNotFound couldn't decode proxy because principal has no key
-1552 kOCERecipientKeyNotFound recipient has no key
-1553 kOCEAgentKeyNotFound in TPFC, agent has no key
-1554 kOCEKeyAlreadyRegistered entity already has a key
-1555 kOCEMalformedKey key is of an unknown encryption method, or key doesn't match password
-1556 kOCEUndesirableKey password too short, key too simple, or trying to change cluster key to the same value
-1557 kOCEWrongIdentityOrKey in CheckIdentity, name doesn't exist or key is wrong
-1558 kOCEInitiatorKeyProblem either we couldn't find the initiator's key or we found it but couldn't successfully decrypt instructions or proxy
-1559 kOCEBadEncryptionMethod specified encryption method is not supported
-1560 kOCELocalIdentityDoesNotExist LocalIdentity has to be setup
-1561 kOCELocalAuthenticationFail LocalIdentity Login has to be done for this operation
-1562 kOCELocalIdentitySetupExists LocalIdentity setup exists, use change instead of setup
-1563 kOCEDirectoryIdentitySetupExists DirectoryIdentity setup exists, use change instead of setup
-1564 kOCEDirectoryIdentitySetupDoesNotExist DirectoryIdentity setup does not exist
-1565 kOCENotLocalIdentity use LocalIdentity calls instead!
-1566 kOCENoMoreIDs identity table is full
-1567 kOCEUnknownID identity passed is not valid
-1568 kOCEOperationDenied LocalID operation denied
-1569 kOCEAmbiguousMatches ambiguous matches found in resolving CIDs (more than 1 CID)
-1570 kOCENoASDSPWorkSpace No ASDSP workspace passed for Open Secure Stream
-1571 kOCEAuthenticationTrouble generic authentication problem

AOCE Catalog Errors (-1610 to -1646) 
-1610 kOCENotLocal server does not serve requested dNode
-1611 kOCETooBusy server cannot complete call at this time
-1612 kOCEDatabaseFull disk full
-1613 kOCETargetDirectoryInaccessible catalog server not responding
-1614 kOCEBogusArgs args not formatted correctly on wire
-1615 kOCENoSuchDNode requested dNode does not exist
-1616 kOCEDNodeUnavailable could not find any servers that serve requested dNode
-1617 kOCEBadRecordID invalid RecordID (usually name and/or type don't match cid)
-1618 kOCENoSuchRecord specified record does not exist
-1619 kOCENoSuchAttributeValue attribute value that was passed does not exist
-1620 kOCENoSuchPseudonym specified pseudonym does not exist
-1621 kOCEAttributeValueTooBig self-explanatory
-1622 kOCETypeExists type already exists in record
-1623 kOCEMoreData only a warning - buffer not big enough
-1624 kOCERefNumBad RefNum is not valid
-1625 kOCEStreamCreationErr problem creating stream
-1626 kOCEOperationNotSupported the specified catalog does not support operation
-1627 kOCEPABNotOpen specified Personal Catalog is not open to make the operation
-1628 kOCEDSAMInstallErr specified CSAM could not be installed
-1629 kOCEDirListFullErr catalog list is full, try removing an entry
-1630 kOCEDirectoryNotFoundErr catalog was not found in the list
-1631 kOCEAbortNotSupportedForThisCall this call cannot be aborted
-1632 kOCEAborted this call was aborted
-1633 kOCEOCESetupRequired LocalIdentity Setup is required
-1634 kOCEDSAMRecordNotFound CSAM Record not found
-1635 kOCEDSAMNotInstantiated CSAM is not instantiated
-1636 kOCEDSAMRecordExists CSAM record already exists
-1637 kOCELengthError supplied buffer was too small
-1638 kOCEBadStartingRecord Lookup starting record is not within range
-1639 kOCEBadStartingAttribute Lookup starting attribute is not within range
-1640 kOCEMoreAttrValue attribute value could not fit into buffer (even though it was the only value)
-1641 kOCENoDupAllowed  
-1642 kOCENoSuchAttributeType  
-1643 kOCEMiscError some other error
-1644 kOCENoSuchIcon no matching icon from GetDirectoryIcon
-1645 kOCERLIsDontMatch RLIs do not match in lookup
-1646 kOCEDirectoryCorrupt Serious disk fill corruption problem

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

AOCE Standard Mail Errors (-1900 to -1928) 
-1900  kSMPNotEnoughMemoryForAllRecips
-1901 kSMPCopyInProgress
-1902 kSMPMailerNotInitialized
-1903 kSMPShouldNotAddContent
-1904 kSMPMailboxNotFound
-1905 kSMPNoNextLetter
-1906 kSMPHasOpenAttachments
-1907 kSMPFinderNotRunning
-1908 kSMPCommandDisabled
-1909 kSMPNoMailerInWindow
-1910 kSMPNoSuchAddress
-1911 kSMPMailerAlreadyInWindow
-1912 kSMPMailerUneditable
-1913 kSMPNoMatchingBegin
-1914 kSMPCannotSendReceivedLetter
-1915 kSMPIllegalForDraftLetter
-1916 kSMPMailerCannotExpandOrContract
-1917 kSMPMailerAlreadyExpandedOrContracted
-1918 kSMPIllegalComponent
-1919 kSMPMailerAlreadyNotTarget
-1920 kSMPComponentIsAlreadyTarget
-1921 kSMPRecordDoesNotContainAddress
-1922 kSMPAddressAlreadyInList
-1923 kSMPIllegalSendFormats
-1924 kSMPInvalidAddressString
-1925 kSMPSubjectTooBig
-1926 kSMPParamCountErr enclosure count <>1
-1927 kSMPTooManyPages Exceeding the image page limit
-1928 kSMPTooManyEnclosures

AOCE Standard Directory Errors (-1950 to -1953) 
-1950  kSDPNoSearchText
-1951 kSDPTooManyLoginAttempts
-1952 kSDPNoSelection
-1953 kSDPPersonalDirectoryRepairFailed

AOCE Digital Signature Errors (-1970 to -1983)
-1970 kSIGOperationIncompatibleErr context in use for different type of operation
-1971 kSIGCertificateQueryDenied can't query certificates with this context
-1972 kSIGVerifyFailedErr verification failed
-1973 kSIGInvalidCredentialErr verified OK but credential out of date, either pending or expired
-1974 kSIGIndexErr the index given is outside range of allowable values
-1975 kSIGSignerErr problem with signer or signature
-1976 kSIGPasswordErr password incorrect
-1977 kSIGInternalsErr internal error occurred like a bad digest,context or signature
-1978 kSIGToolboxNotPresentErr for client services (ie servers) to report back - not returned bythe TB
-1979 kSIGContextPrepareErr context either prepared with VerifyPrepare, SignPrepare or DigestPrepare already or has been corrupted  
-1980 kSIGNoDigestErr no digest in signature
-1981 kSIGConversionErr unabld to convert attribute to Mac format
-1982 kSIGSignerNotValidErr signer has either expired or is pending and can not sign
-1983 kSIGNoSignature standard file signature not found

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

Open Transport Errors
-3150 kOTBadAddressErr The specified protocol address was in an incorrect format or contained illegal information.
-3151 kOTBadOptionErr The specified protocol options were in an incorrect format or contained illegal information.
-3152 kOTAccessErr The user does not have permission to negotiate the specified address or options.
-3153 kOTBadReferenceErr The specified EndpointRef or TEndpoint * does not refer to a valid endpoint.
-3154 kOTNoAddressErr The endpoint could not allocate an address, or an address was required and not supplied by the client.
-3155 kOTOutStateErr The function was issued in the wrong sequence.
-3156 kOTBadSequenceErr An invalid sequence number was specified, or a NULL call pointer was specified when rejecting a connection request.
-3158 kOTLookErr An asynchronous event has occurred on this endpoint.
-3159 kOTBadDataErr The amount of client data specified was not within the bounds allowed by the endpoint.
-3160 kOTBufferOverflowErr The number of bytes allocated to hold a result is greater than zero, but not sufficient to store the result.
-3161 kOTFlowErr The endpoint is in asynchronous mode, but the flow control mechanism prevents the endpoint from accepting any data at this time.
-3162 kOTNoDataErr This endpoint is in non-blocking mode, but no data is currently available. It is also returned by LookupName when no names are found.
-3163 kOTNoDisconnectErr No disconnect indication is available.
-3164 kOTNoUDErrErr No unit data error indication currently exists on this endpoint.
-3165 kOTBadFlagErr An invalid flag was specified.
-3166 kOTNoReleaseErr No orderly release indication currently exists on this endpoint.
-3167 kOTNotSupportedErr This action is not supported by this endpoint.
-3168 kOTStateChangeErr The endpoint is undergoing a transient state change. This error is returned when a function call is made while an endpoint is in the process of changing states. The client should wait for an event indicating the endpoint has finished changing state and call the function again.

Note: The equivalent state-change error code, TSTATECHNG, is not described in the 1992 X/Open XTI specification.

This error is also returned if you attempt to use an "incompatible" function while another operation is still ongoing (for example: calling SndUData while an OptionManagement call is still outstanding).
-3169 kOTStructureTypeErr An unsupported structure type was passed in the structType field. This error is also returned when the structType field is inconsistent with the endpoint type.
-3170 kOTBadNameErr The endpoint name is invalid.
-3171 kOTBadQLenErr The argument qlen when the endpoint was bound with Bind was zero.
-3172 kOTAddressBusyErr The requested address is in use, or this endpoint does not support multiple connections with the same local and remote addresses. This result code indicates that a connection already exists. As a return value for a Bind call, it may also indicate that no dynamic addresses are available for protocols or configuration methods that allow dynamic addressing.
-3173 kOTIndOutErr There are outstanding connection indications on the endpoint. All other connection indications must be handled either by rejecting them with SndDisconnect, or by accepting them with Accept.
-3174 kOTProviderMismatchErr The endpoint that is to accept the connection is not the same kind of endpoint as this one.
-3175 kOTResQLenErr When this endpoint was bound (see Bind), the qlen parameter was greater than zero. But to accept a connection on an alternate end-point, such as this one, the endpoint must be bound with a qlen parameter equal to zero.
-3176 kOTResAddressErr The address to which this endpoint is bound differs from that of the endpoint that received the connection request; thus, this endpoint cannot accept this connection request.
-3177 kOTQFullErr The maximum number of outstanding indications has been reached for the endpoint.
-3178 kOTProtocolErr An unspecified protocol error occurred.
-3179 kOTBadSyncErr A call to Sync was made at non-SystemTask time.
-3180 kOTCanceledErr An outstanding call was canceled.
0000 kOTNoError The function completed execution without 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

Support Information Services
Copyright 1992-95, Apple Computer, Inc.
Keywords: sys7,ktoptil



Apple Remote Access(ARA) Error Codes (-5800 to -7199)



Result code

-5825 ERR_VLD8_ALLCBSERVERSBUSY All of the Callback Clients are in use
-5835 ERR_DAMAGED The ARA file has been modified
-5842 ERR_EXTAUTH_MODULE_NOTFOUND Client does not have a needed securtiy module
-5843 ERR_EXTAUTH_MODULE_BADVERSION Incorrect version of a securtiy module
-5844 ERR_EXTAUTH_MODULE_BADRESULT Client has returned some error in the result field
-5845 ERR_EXTAUTH_MODULE_REJECT_USER Module is rejecting this user

-5901 ERR_LTM_LISTENER_ID_IN_USE Specified Listener identifier is in use
-5902 ERR_LTM_NO_LISTENER Listener of specified type is not available
-5903 ERR_LTM_RESOURCE_NOT_REGISTERED Listener of specified type is not available
-5904 ERR_LTM_PORT_NOT_CLAIMED claim request failed because to port is busy
-5905 ERR_LTM_COMMAND_NOT_ALLOWED LTM command not allowed on specified port
-5906 ERR_LTM_BAD_VERSION connect failed due to incompatible LTM versions
-5907 ERR_LTM_ARBITRATION_TIMEOUT Time outduring the listener arbitration.
-5908 ERR_LTM_KODE_NOT_FOUND kode resource not found in specified file fail.
-5910 ERR_LTM_RESOURCE_CLAIMED call failed because resource is already claimed
-5911 ERR_LTM_PORT_RESOURCES_CLAIMED Port's resources are already claimed
-5912 ERR_LTM_RESOURCE_NOT_CLAIMED call failed because the resource was unclaimed
-5913 ERR_LTM_PORT_RESOURCES_NOT_CLAIMED  The LTM port's resources are NOT claimed.
-5914 ERR_LTM_PORT_UNCLAIMED LTM listen port unclaimed
-5915 ERR_LTM_CONNECTION_REFUSED LTM listener refused connect request
-5916 ERR_LTM_CLAIM_ABORTED LTM claim call aborted due to LTM_ARB_CLAIM_CANCEL call
-5917 ERR_LTM_END_OF_PORT_LIST End of open port list reached in current port status session
-5918 ERR_LTM_NOT_CONNECTED Not connected.
-5919 ERR_LTM_CONNECTION_ABORTED Connection request aborted
-5920 ERR_LTM_BAD_LENGTH Length of write request exceeds maximum.
-5921 ERR_LTM_BAD_PARAMETER Bad parameter.
-5922 ERR_LTM_COMMAND_IN_PROGRESS Command already in progress.
-5923 ERR_LTM_CONNECTED Connection established.
-5924 ERR_LTM_CONNECT_CANCELED Connection request canceled.
-5925 ERR_LTM_CONNECT_TIMEDOUT Connection time out.
-5926 ERR_LTM_NO_DEFAULTS Could not get default info...
-5927 ERR_LTM_GOOD_BYE The driver is going away in a rude fashion
-5928 ERR_LTM_BAD_CHECKSUM Bad checksum in framer
-5929 ERR_LTM_BAD_PROTOCOL Bad protocol type in PPP frame
-5930 ERR_LTM_BAD_FRAME Bad PPP frame

-6051 ERR_MNP_NEGOTIATION_FAILURE Connection parameter negotiation failure
-6052 ERR_MNP_CONNECT_TIME_OUT Connect request (acceptor mode) timed out
-6053 ERR_MNP_NOT_CONNECTED Not connected
-6054 ERR_MNP_ABORTED Request aborted by disconnect request
-6055 ERR_MNP_ATTENTION_DISABLED Link attention service is not enabled
-6056 ERR_MNP_CONNECT_RETRY_LIMIT Connect (initiator mode) request retry limit reached.
-6057 ERR_MNP_COMMAND_IN_PROGRESS Command already in progress.
-6058 ERR_MNP_ALREADY_CONNECTED Connection already established.
-6059 ERR_MNP_INCOMPATIBLE_PROT_LVL Connection failed due to incompatible protocol levels
-6060 ERR_MNP_HANDSHAKE_FAILURE Connection handshake failed.

-6000 cclErr_AbortMatchRead internal error used to abort match read
-6006 cclErr_CCLErrorBase CCL error base
-6007 cclErr_CloseError There is at least one script open
-6008 cclErr_ScriptCancelled Script Canceled
-6009 cclErr_TooManyLines Script contains too many lines
-6010 cclErr_ScriptTooBig Script contains too many characters
-6011 cclErr_NotInitialized CCL has not been initialized
-6012 cclErr_CancelInProgress Cancel in progress.
-6013 cclErr_PlayInProgress Play command already in progress.
-6014 cclErr_ExitOK Exit with no error.
-6015 cclErr_BadLabel Label out of range.
-6016 cclErr_BadCommand Bad command.
-6017 cclErr_EndOfScriptErr End of script reached, expecting Exit.
-6018 cclErr_MatchStrIndxErr Match string index is out of bounds.
-6019 cclErr_ModemErr Modem error, modem not responding.
-6020 cclErr_NoDialTone No dial tone.
-6021 cclErr_NoCarrierErr No carrier.
-6022 cclErr_LineBusyErr Line busy.
-6023 cclErr_NoAnswerErr No answer.
-6024 cclErr_NoOriginateLabel No @ORIGINATE label
-6025 cclErr_NoAnswerLabel No @ANSWER label
-6026 cclErr_NoHangUpLabel No @HANGUP label

ARA 3.0 Scripting
-7102 Remote Access did not load properly at system startup
-7103 Remote Access could not set up a port
-7104 Remote Access is out of memory
-7105 The requested action is not supported
-7106 One or more resources are missing from Remote Access installed files
-7107 The Remote Access Connections file is not compatible with the installed version of Remote Access
-7108 An action requiring a connection was requested when there was no connection
-7109 The connection attempt or established connection was terminated by the user
-7112 An unexpected error with no useful information has occurred
-7113 One or more of the installed Remote Access files is damaged
-7114 The requested action could not be performed because Remote Access was busy
-7115 The Remote Access logical port is in an unknown state
-7116 The Remote Access logical port is in an invalid state
-7117 The Remote Access logical port has detected an invalid serial protocol
-7118 Login is disabled for the given user
-7120 The server administrator requires the user to enter a password
-7122 Remote Access could not initialize Open Transport
-7123 The requested action could not be performed because Remote Access is not fully initialized yet
-7124 TCP/IP is inactive and can not be loaded
-7125 TCP/IP is not yet configured
-7126 PPP is not selected as the TCP/IP interface in the current TCP/IP configuration
-7128 The requested PPP protocol was rejected by the PPP peer
-7129 User authentication failed
-7130 PPP negotiation failed
-7131 Connection was lost unexpectedly
-7132 The remote side disconnected unexpectedly
-7133 The remote side is not responding
-7151 The Remote Access log file is not open
-7152 The Remote Access log file is already open
-7153 The Remote Access log entry could not be retrieved
-7155 Remote Access cannot locate the active System Folder
-7156 Remote Access cannot locate its Preferences folder
-7157 There is a preexisting file using a Remote Access type or creator
-7158 There is a preexisting folder using a Remote Access folder name and location
-7159 The Remote Access Connections file is not open
-7161 An unknown control protocol type was received
-7162 Remote Access received a packet with an invalid length
-7163 Remote Access received a negotiable option with an invalid value
-7164 Remote Access received a negotiable option with invalid flags
-7165 Remote Access ran out of memory while negotiating with the peer
-7169 Remote Access encountered an error with no useful information
-7170 Remote Access is in an invalid state
-7180 The user canceled the password entry dialog
-7181 The user did not respond to the password entry dialog in time
-7182 An unknown serial port was referenced
-7183 The Remote Access logical port is not configured
-7184 No AppleTalk servicesÕ endpoints are available
-7185 The modem script ASK or manual dialing dialog was canceled by the user

Apple Remote Access: Error Codes
Article ID:16456



Error codes for AOCE (Apple Open Collaborative Environment) -15000 to -15199

aka PowerTalk and PowerShare
AOCE Allocated ranges
AOCE General Errors             -1500 to -1539
AOCE Authentication Errors      -1540 to -1609
AOCE Directory Errors           -1610 to -1680

AOCE Standard Mail Errors       -1900 to -1949
AOCE Standard Directory Errors  -1950 to -1969
AOCE Digital Signature Errors   -1970 to -1999

AOCE Directory Templates Errors -15000 to -15039
AOCE Mail Errors                -15040 to -15089
AOCE Messaging Errors           -15090 to -15169
Reserved for future             -15170 to -15199

AOCE Directory Templates Errors (-15000 to -15020) 
-15000 kDETInvalidTargetAspectName could not locate aspect by name
-15001 kDETInvalidTargetItemNumber item number target invalid (out of range 1..)
-15002 kDETInvalidTargetFromNonAspect target selection relative to non-aspect object which requires an aspect
-15003 kDETInvalidTargetDSSpec target DSSpec could not be resolved
-15004 kDETUnknownTargetSelector unknown selector type for target specification
-15005 kDETInvalidTarget target specification was invalid (for reasons other than those above)
-15006 kDETTargetNotAnAspect specified target object was not an aspect
-15007 kDETInvalidCommandItemNumber command item number invalid (out of range 1..)
-15008 kDETUnableToGetCommandItemSpec unable to retrieve item specification (internal error, possibly out of memory)
-15009 kDETRequestedTypeUnavailable command item could not be represented in the form requested
-15010 kDETInvalidDSSpec could not resolve DSSpec (other than in target; see error above for targets)
-15011 kDETUnableToAccessProperty property could not be found and/or created
-15012 kDETInfoPageNotOpen info-page not open; request requires an open info-page
-15013 kDETNoSuchView no view found with specified property number
-15014 kDETCouldNotAddMenuItem could not add item to dynamic menu
-15015 kDETCouldNotRemoveMenuItem could not remove item from dynamic menu
-15016 kDETCouldNotFindMenuItem could not find menu item
-15017 kDETCouldNotFindCustomView could not find custom view in info-page
-15018 kDETInvalidReqFunction invalid call-back request function
-15019 kDETInvalidCallBack invalid call-back (for reasons other than those above)
-15020 kDETPropertyBusy edit is open on the property being set

AOCE Mail Errors (-15040 to -15068) 
-15040 kMailInvalidOrder this object has already been written to and cannot be written again, handle non-zero offsets for now
-15041 kMailInvalidSeqNum invalid letter sequence refers to an nonexistent letter
-15042 kMailAttrNotInHdr attribute does not exist in letter header
-15043 kMailHdrAttrMissing required attribute not written into letter header
-15044 kMailBadEnclLengthErr incorrect number of bytes has been written after memForm of PutEnclosure
-15045 kMailInvalidRequest cannot putAttr for report, putRcptReport for letter
-15046 kMailInvalidPostItVersion cannot create new postit with this version
-15047 kMailNotASlotInQ queueID does not refer to a slot's incoming queue
-15048 kMailLtrNotOpen letter is not open, probably not cached in inQ
-15049 kMailMissingMailCat trying to create message in inq, with no postIt
-15050 kMailCannotWriteMailCat cannot update a mail catentry
-15051 kMailTooManyTagsPerLetter cannot add more than kMaxTagsPerLetter tags
-15052 kMailGwyDead MSAM died
-15053 kMailIgnoredErr ePPC message was ignored
-15054 kMailLengthErr ePPC message did not complete
-15055 kMailTooManyErr too many requests outstanding
-15056 kMailNoMSAMErr no MSAMs found in mailbox! or for command
-15057 kMailCancelled  
-15058 kMailSlotSuspended  
-15059 kMailMSAMSuspended  
-15060 kMailBadSlotInfo  
-15061 kMailMalformedContent a mailed structure is malformed
-15062 kMailNoSuchSlot no such slot
-15063 kMailBadLtrInfo bad info there, can't change
-15064 kMailSetFailed could not set letter info
-15065 kMailBadConfig MSAM has bad config info
-15066 kMailBadMSAM bad MSAM: not usable, reason unspec
-15067 kMailCannotLkupServerSlots cannot lookup adas for server mail slots
-15068 kMailBadState state specified is not in any of defined

AOCE Messaging Errors (-15090 to -15149)
-15090 kIPMCantCreateIPMCatEntry
-15091 kIPMInvalidMsgType bad msg hint
-15092 kIPMInvalidProcHint bad proc hint
-15093 kIPMInvalidOffset bad offset for read/write
-15094 kIPMUpdateCatFailed
-15095 kIPMMsgTypeReserved
-15096 kIPMNotInABlock
-15097 kIPMNestedMsgOpened
-15098 kIPMA1HdrCorrupt
-15099 kIPMCorruptDataStructures
-15100 kIPMAbortOfNestedMsg
-15101 kIPMBlockIsNotNestedMsg
-15102 kIPMCacheFillError
-15103 kIPMInvalidSender
-15104 kIPMNoRecipientsYet
-15105 kIPMInvalidFilter
-15106 kIPMAttrNotInHdr
-15107 kIPMBlkNotFound
-15108 kIPMStreamErr Error on stream (should this ever go out?)
-15109 kIPMPortClosed Port closed (should this ever go out?)
-15110 kIPMBinBusy
-15111 kIPMCorruptedBin
-15112 kIPMBadQName
-15113 kIPMEndOfBin
-15114 kIPMBinNeedsConversion
-15115 kIPMMgrInternalErr
-15116 kIPMEltBusy
-15117 kIPMEltClosedNotDeleted
-15118 kIPMBadContext
-15119 kIPMContextIsClosing
-15120 kIPMeoQ
-15121 kIPMQOutOfSpace
-15122 kIPMEltNotFound
-15123 kIPMBinOutOfSpace
-15124 kIPMeoCatEntry
-15125 kIPMeoElt
-15126 kIPMQBusy
-15127 kIPMNotSameBin
-15128 kIPMNoMoreServices
-15129 kIPMLookupAttrTooBig attribute in lookup is too big
-15130 kIPMUnknownUAM
-15131 kIPMUnsupportedLogin
-15132 kIPMLogInUnknown
-15133 kIPMNoMoreFilters
-15134 kIPMCouldNotReadInfoReply
-15135 kIPMInvalidUser
-15136 kIPMNoMoreSessions
-15137 kIPMNilUserProc
-15138 kIPMBadCatSize
-15139 kIPMIncompleteMsg
-15140 kIPMNoResponsibleTunnel
-15141 kIPMAccessDenied
-15142 kIPMReplyParamUnderrun too few reply parameters
-15143 kIPMReplyParamOverrun too many reply parameters
-15144 kIPMRequestParamUnderrun too few request parameters
-15145 kIPMOutOfSync protocol sync. error
-15146 kIPMNoAttrsFound couldn't find any attrs in lookup
-15147 kIPMWrongAttrTag wrong attr tag in adas lookup
-15148 kIPMNullCID null cid in enumerate
-15149 kIPMBadMailSlotAttrVal invalid mailslot attr value



Mac TCP Error Codes (-23000 to -23099)


Result code

-23000 ipBadLapErr Unable to initialize the local network handler.
-23001 ipBadCnfgErr The manually set address is configured improperly.
-23002 ipNoCnfgErr A configuration resource is missing.
-23003 ipLoadErr Not enough room in the application heap (Macintosh 512K enhanced only)
-23004 ipBadAddr Error in getting an address from a server or the address is already in use by another machine.
-23005 connectionClosing A TCPClose command was already issued so there is no more data to send on this connection.
-23006 invalidLength The total amount of data described by the WDS was either 0 or greater than 65,535 bytes.
-23007 connectionExists The TCP or UDP stream already has an open connection.
-23008 connectionDoesntExist The TCP stream has no open connection.
-23009 insuuficientResources 64 TCP or UDP streams are already open.
-23010 invalidStreamPtr The specified TCP or UDP stream is not open.
-23011 streamAlreadyOpen An open stream is already using the receive buffer area.
-23012 connectionTerminated The TCP connection was broken; the reason will be given a terminate ASR.
-23013 invalidBufPtr The receive buffer area pointer is 0 (nil).
-23014 invalidRDS The RDS refers to receive buffers not owned by the user.
-23014 invalidWDS The WDS pointer was 0 (nil).
-23015 openFailed The connection came halfway up and then failed.
-23016 commandTimeout The specified command action was not completed in the specified time period.
-23017 duplicateSocket A stream is already open using the local UDP port or a TC connection already exists between the local IP address and TCP port, and the specified remote IP address and TCP port.
-23032 ipDontFragErr The pack is too large to send without fragmenting and the Don't Fragment flag is set.
-23033 ipDestDeadErr The destination host is not responding to address resolution requests.
-23035 icmpEchoTimeoutErr The icmp echo packet was not responded to in the indicated timeout period.
-23036 ipNoFragMemErr Insufficient internal driver buffers available to fragment this packet on send.
-23037 ipRouteErr No gateway available to manage routing of packets to off-network destinations.
-23041 nameSyntaxErr The hostname field had a syntax error. The address was given in dot notation (that is, W.X.Y.Z) and did not conform to the syntax for an IP address.
-23042 cacheFault The name specified cannot be found in the cache. The domain name resolver will now query the domain name server and return the answer in the callback procedure.
-23043 noResultProc No result procedure is passed to the address translation call when the resolver must be used to find the address.
-23044 noNameServer No name server can be found for the specified name string.
-23045 authNameErr The domain name does not exist.
-23046 noAnsErr None of the known name servers are responding.
-23047 dnrErr The domain name server has returned an error.
-23048 outOfMemory Not enough memory is available to issue the needed DNR query or to build the DNR cache.



Open Transport/PPP, Error Codes (7100 to 7199)

Open Transport/PPP, Error Codes
7102 OT/PPP did not load properly at system start up.
7103 OT/PPP could not set up a port.
7104 OT/PPP is out of memory.
7105 The requested action is not supported.
7106 One or more resources are missing from OT/PPP's installed files.
7107 The Remote Access Connections file is not compatible with the installed version of OT/PPP.
7108 An action requiring a connection was requested when there was no connection.
7109 The connection attempt or established connection was terminated by the user.
7110 The user name is unknown.
7111 The password is invalid.
7112 An unexpected error with no useful information has occurred.
7113 One or more of the installed OT/PPP files is damaged.
7114 The requested action could not be performed because OT/PPP was busy.
7115 The OT/PPP logical port is in an unknown state.
7116 The OT/PPP logical port is in an invalid state.
7117 The OT/PPP logical port has detected an invalid serial protocol.
7118 Login is disabled for the given user.
7120 The server administrator requires the user to enter a password.
7122 OT/PPP could not initialize Open Transport.
7123 The requested action could not be performed because OT/PPP is not fully initialized yet.
7124 TCP/IP is inactive and cannot be loaded.
7125 TCP/IP is not yet configured.
7126 PPP is not selected as the TCP/IP interface in the current TCP/IP configuration.
7128 The requested PPP protocol was rejected by the PPP peer.
7129 PPP authentication failed.
7130 PPP negotiation failed.
7131 PPP was disconnected locally.
7132 The PPP peer disconnected unexpectedly.
7133 The PPP peer is not responding.
7134 The OT/PPP log file is not open.
7135 The OT/PPP log file is already open.
7136 The OT/PPP log entry could not be retrieved.
7138 OT/PPP can not locate the active System Folder.
7139 OT/PPP can not locate its Preferences folder.
7140 There is a preexisting file using an OT/PPP type or creator.
7141 There is a preexisting folder using an OT/PPP folder name and location.
7142 The Remote Access Connections file is not open.
7144 An unknown PPP control protocol type was received.
7145 PPP received a packet with an invalid length.
7146 PPP received a negotiable option with an invalid value.
7147 PPP received a negotiable option with invalid flags.
7148 PPP ran out of memory while negotiating with the peer.
7152 PPP encountered an error with no useful information.
7153 PPP is in an invalid state.
7163 The user canceled the password entry dialog.
7164 The user did not respond to the password entry dialog in time.
7165 An unknown Open Transport serial port was referenced.
7166 The OT/PPP logical port is not configured.
7167 No AppleTalk services endpoints are available.
7168 The user canceled the modem script ASK or the Manual Dialing dialog.



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.
The traditional Macintosh error codes are displayed like this:

Where F indicates an exception occurred, and 3 indicates an illegal instruction occurred. On the Macintosh SE and II, the display would appear:


Note: 0000003 is a hex number.
Power On
The new power-on error codes have the following format:


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.
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:
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.
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:
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 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 codes Power 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


0 Commenti:

Posta un commento

Related Posts Plugin for WordPress, Blogger...