Apple II Main Error List

Csa2 FAQs-on-Ground file: Csa2ERRLIST.txt  rev012

The Csa2 (comp.sys.apple2) usenet newsgroup Frequently Asked
 Questions files are compiled by the Ground Apple II site,
 1997 - 1999.

for on-line perusing via Netscape, etc. ... (double-spaced)

The Csa2 FAQs may be freely distributed.

Note: To correctly view tables and diagrams on a super-res display,
 use a mono-spaced Font such as CoPilot or PCMononspaced.


 001- What does error #___ mean?
 002- What does IIgs Diagnostic Self-Test Error Code ___ mean?
 003- What does RamFAST Fatal Memory Fault Error ___ mean?
 004- What is the explanation for getting a ___  error?
 005- Where can I find more information on Apple II series errors?

From: Jeff Hurlburt (in II Alive, 1996)

001- What does error #___ mean?

Error Codes

    Codes are in hexadecimal and are listed in numerical order. Except
for a few IIgs System Failure codes, the system or sub-system reporting
the error is shown along with the error description.

    Most IIgs tool set error 'descriptions'-- like divByZeroErr--
consist of just the error name as published in the Toolbox References.
When such an error is reported, the first two digits identify the Tool
Set; the last two identify the error# (sometimes this identifies the
individual Tool involved in the error). The name and number of each Tool
Set which reports errors is identified in the listing by labeling the
first error in each Tool Set group.

    Most of the descriptions for 00xx codes refer to GS/OS errors.
Usually, these codes have the same (or a very similar) meaning as ProDOS
16 (P16) codes, SmartPort codes, and 8-bit ProDOS 8 (P8) Machine
Language Interface (MLI) codes. When there is a significant difference,
other meanings are shown.

Note: Codes marked **** indicate that a more detailed discussion is
available in Question 004.

0000 No error
0001 GS/OS: bad system call
0001 Tool Locator: dispatcher does not find toolset
0001 P16: System Failure- unclaimed interrupt
0001 P8: Invalid MLI function number
0002 Tool Locator: routine not found
0004 GS/OS: bad parameter count
0004 System Failure- division by zero
0006 SmartPort: bus error in IWM chip
0007 GS/OS is busy
000A P16: System Failure- unusable Volume Control Block
000B P16: System Failure- unusable File Control Block
000C P16: System Failure- Block Zero allocated illegally
000D P16: System Failure- interrupt occurred while I/O shadowing off
0010 GS/OS: device not found
0010 Tool Locator: specified Version not found
0011 GS/OS: bad device number
0011 P16: System Failure- wrong OS version
0015 System Failure- Segment Loader error
0017-0024 System Failure- Can't load a package
0020 GS/OS: invalid driver request
0021 GS/OS: invalid driver control or status code
0022 GS/OS: bad call parameter
0023 GS/OS: character device not open
0024 GS/OS: character device already open
0025 GS/OS: interrupt table full
0025 System Failure- Out of Memory
0026 GS/OS: resources not available
0026 System Failure- Segment Loader error
0027 GS/OS: I/O error   ****
0027 System Failure- File map destroyed
0028 GS/OS: no device connected
0028 System Failure- Stack overflow
0029 GS/OS: driver is busy
002B GS/OS: disk write protected
002C GS/OS: invalid byte count
002D GS/OS: invalid block address
002E GS/OS: disk/volume switched
002F GS/OS: device offline or no disk in drive
0030 System Failure Alert- Please Insert Disk
0040 GS/OS: bad pathname syntax
0042 GS/OS: max number of files already open
0042 P8: too many files open (can lead to NO BUFFERS AVAILABLE)
0043 GS/OS: bad file reference number
0044 GS/OS: directory not found
0045 GS/OS: volume not found
0046 GS/OS: file not found
0047 GS/OS: duplicate filename/pathname   ****
0048 GS/OS: disk/volume full   ****
0049 GS/OS: volume directory full   ****
004A GS/OS: incompatible file format
004A P8: incompatible ProDOS version
004B GS/OS: unsupported (or incorrect) storage type
004C GS/OS: End Of File encountered
004D GS/OS: position out of range
004D P8: position past End Of File
004E GS/OS: access not allowed
004F GS/OS: buffer too small
0050 GS/OS: file is already open
0051 GS/OS: directory damaged   ****
0051 P8: file count is bad
0052 GS/OS: unknown volume type
0053 GS/OS: parameter out of range
0054 GS/OS: out of memory
0055 P8: Volume Control Block table full
0056 P8: bad buffer address (can lead to NO BUFFERS AVAILABLE) ****
0057 GS/OS: duplicate volume name
0058 GS/OS: not a block device
0058 P8: bad volume bit map
0059 GS/OS: file level out of range
005A GS/OS: bad bitmap address (block# too large/ damaged disk) ****
005B GS/OS: invalid pathnames for ChangePath
005C GS/OS: not an executable file
005D GS/OS: Operating system/file system not available
005F GS/OS: too many applications on stack/ stack overflow
0060 GS/OS: data unavailable
0061 GS/OS: end of directory
0062 GS/OS: invalid FST call class
0063 GS/OS: file doesn't have a resource fork
0064 GS/OS: invalid FST ID
0065 GS/OS: invalid FST operation
0066 GS/OS: FST Caution- weird result
0067 GS/OS: device Name error/ internal error
0068 GS/OS: device List full
0069 GS/OS: supervisor List full
006A GS/OS: FST Error (generic)
0070 GS/OS: resource exists, cannot expand file
0071 GS/OS: cannot Add resource to this type file
0088 network error   ****
0100 System Failure- can not mount sys startup volume

0103 [01] TOOL LOCATOR: invalid StartStop record
0104 tool cannot load
0110 specified minimum Version not found
0111 specified message not found
0112 no message numbers available
0113 message name too long
0120 request not accepted
0121 duplicate name
0122 invalid send request

0201 [02] MEMORY MANAGER: could not allocate memory  ****
0202 emptyErr
0203 notEmptyErr
0204 lockErr
0205 purgeErr
0206 handleErr
0207 idErr
0208 attrErr

0301 [03] MISCELLANEOUS TOOL SET: bad input parameter
0302 noDevParamErr
0303 taskInstlErr
0304 noSigTaskErr
0305 queueDmgdErr
0306 taskNtFdErr
0307 firmTaskErr
0308 hbQueueBadErr
0309 unCnctdDevErr
030B idTagNtAvlErr
034F mtBuffTooSmall
0381 invalidTag
0382 alreadyInQueue
0390 badTimeVerb
0391 badTimeData

0401 [04] QUICKDRAW II: QD II already initialized
0402 cannotReset
0403 notInitialized
0410 screenReserved
0411 badRect
0420 notEqualChunkiness
0430 rgnAlreadyOpen
0431 rgnNotOpen
0432 rgnScanOverflow
0433 rgnFull
0440 polyAlreadyOpen
0441 polyNotOpen
0442 polyTooBig
0450 badTableNum
0451 badColorNum
0452 badScanLine

0510 [05] DESK MANAGER: Desk Acessory not available
0511 notSysWindow
0520 deskBadSelector

0601 [06] EVENT MANAGER: EM startup already called
0602 emResetErr
0603 emNotActErr
0604 emBadEvtCodeErr
0605 emBadBttnNoErr
0606 emQSiz2LrgErr
0607 emNoMemQueueErr
0681 emBadEvtQErr
0682 emBadQHndlErr

0810 [08] SOUND: no DOC or RAM found
0811 docAddrRngErr
0812 noSAppInitErr
0813 invalGenNumErr
0814 synthModeErr
0815 genBusyErr
0817 mstrIRQNotAssgnErr
0818 sndAlreadyStrtErr
08FF unclaimedSntIntErr- "UNCLAIMED SOUND INTERRUPT" ****

0910 [09] APPLE DESKTOP BUS: command not completed
0911 cantSync- "FATAL SYSTEM ERROR 0911"  ****
0982 adbBusy
0983 devNotAtAddr
0984 srqListFull

0B01 [11] INTEGER MATH: bad input parameter
0B02 imIllegalChar
0B03 imOverflow
0B04 imStrOverflow

0C01 [12] TEXT TOOL SET: illegal device type
0C02 badDevNum
0C03 badMode
0C04 unDefHW
0C05 lostDev
0C06 lostFile
0C07 badTitle
0C08 noRoom
0C09 noDevice
0C0B dupFile
0C0C notClosed
0C0D notOpen
0C0E badFormat
0C0F ringBuffOFlo
0C10 writeProtected
0C40 devErr

0E01 [14] WINDOW MANAGER: parm list first word is wrong size
0E02 allocateErr
0E03 taskMaskErr

0F01 [15] MENU MANAGER: menu started
0F02 menuItemNotFound
0F03 menuNoStruct
0F04 dupMenuID

1001 [16] CONTROL MANAGER: Window Manager not initialized
1002 cmNotInitialized
1003 noCtlInList
1004 noCtlError
1005 notExtendedCtlError
1006 noCtlTargetError
1007 notExtendedCtlError
1008 canNotBeTargetError
1009 noSuchIDError
100A tooFewParmsError
100B noCtlToBeTargetError
100C noFrontWindowError

1101 [17] LOADER: id not found / segment not found
1102 OMF version error   ****
1103 idPathnameErr
1104 idNotLoadFile (often: file incompatible with system)   ****
1105 idBusyErr
1107 idFilVersErr
1108 idUserIDErr
1109 idSequenceErr
110A idBadRecordErr
110B idForeignSegErr

1210 [18] QUICKDRAW AUX: pic empty
1211 badRectSize
1212 destModeError
121F bad picture opcode
1221 badRect
1222 badMode
1230 badGetSysIconInput

1301 [19] PRINT MANAGER: driver not in DRIVERS folder   ****
1302 portNotOn
1303 noPrintRecord
1304 badLaserPrep
1305 badLPFile
1306 papConnNotOpen
1307 papReadWriteErr
1308 ptrConnFailed
1309 badLoadParam
130A callNotSupported
1321 startUpAlreadyMade

1401 [20] LINE EDIT: LE startup already called
1402 leResetErr
1403 leNotActiveErr
1404 leScrapErr

150A [21] DIALOG MANAGER: bad item type
150B newItemFailed
150C itemNotFound
150D notModalDialog

1610 [22] SCRAP MANAGER: scrap type does not exist
1701 [23] STANDARD FILE OPERATIONS: bad prompt description
1702 badOrigNameDesc
1704 badReplyNameDesc
1705 badReplyPathDesc
1706 badCall

1901 [25] NOTE SYNTHESIZER: NS already initialized
1902 nsSndNotInit
1921 nsNotAvail
1922 nsBadGenNum
1923 nsNotInit
1924 nsGenAlreadyOn
1925 soundWrongVer

1A00 [26] NOTE SEQUENCER: no room for MIDI NoteOn
1A01 noCommandErr
1A02 noRoomErr
1A03 startedErr
1A04 noNoteErr
1A05 noStartErr
1A06 instBndsErr
1A07 nsWrongVer

1B01 [27] FONT MANAGER: duplicate FM startup call
1B02 fmResetErr
1B03 fmNotActiveErr
1B04 fmFamNotFndErr
1B05 fmFontNtFndErr
1B06 fmFontMemErr
1B07 fmSysFontErr
1B08 fmBadFamNumErr
1B09 fmBadSizeErr
1B0A fmBadNameErr
1B0B fmMenuErr
1B0C fmScaleSizeErr

1C02 [28] LIST MANAGER: listRejectEvent

1D01 [29] AUDIO COMPRESSION EXPANSION: ACE already started
1D02 aceBadDP
1D03 aceNotActive
1D04 aceNoSuchParam
1D05 aceBadMethod
1D06 aceBadSrc
1D07 aceBadDest
1D08 aceDataOverlap

1E01 [30] RESOURCE MANAGER: resource fork used, not empty
1E02 resBadFormat
1E03 resNoConverter
1E04 resNoCurFile
1E05 resDupID
1E06 resNotFound
1E07 resFileNotFound
1E08 resBadAppID
1E09 resNoUniqueID
1E0A resIndexRange
1E0B resSysIsOpen
1E0C resHasChanged
1E0D resDiffConverter
1E0E resDiskFull
1E0F resInvalidShutDown
1E10 resNameNotFound
1E11 resBadNameVers
1E12 resDupStartUp
1E13 resInvalidTypeOrID

2000 [32] MIDI: MIDI tool set not started
2001 miPacketErr
2002 miArrayErr
2003 miFullbufErr
2004 miToolsErr
2005 miOutOffErr
2007 miNoBufErr
2008 miDriverErr
2009 miBadFreqErr
200A miClockErr
200B miConflictErr
200C miNoDevErr
2080 miDevNotAvail
2081 miDevSlotBusy
2082 miDevBusy
2083 miDevOverrun
2084 miDevNoConnect
2085 miDevReadErr
2086 miDevVersion
2087 miDevIntHndlr

2110 [33] VIDEO OVERLAY: no Video device
2111 vdAlreadyStarted
2112 vdInvalidSelector
2113 vdInvalidParam
21FF vdUnImplemented

2201 [34] TEXT EDIT: TE already started
2202 teNotStarted
2203 teInvalidHandle
2204 teInvalidDescriptor
2205 teInvalidFlag
2206 teInvalidPCount
2208 teBufferOverflow
2209 teInvalidLine
220B teInvalidParameter
220C teInvalidTextBox2
220D teNeedsTools

2301 [35] MIDI SYNTHESIZER: MS already started
2302 msNotStarted
2303 msNoDPMem
2304 msNoMemBlock
2305 msNoMiscTool
2306 msNoSoundTool
2307 msGenInUse
2308 msBadPortNum
2309 msPortBusy
230A msParamRangeErr
230B msMsgQueueFull
230C msRecBufFull
230D msOutputDisabled
230E msMessageError
230F msOutputBufFull
2310 msDriverNotStarted
2311 msDriverAlreadySet
2380 msDevNotAvail
2381 msDevSlotBusy
2382 msDevBusy
2383 msDevOverrun
2384 msDevNoConnect
2385 msDevReadErr
2386 msDevVersion
2387 msDevIntHndlr

2601 [38] MEDIA CONTROLLER: MC unimplemented
2602 mcBadSpeed
2603 mcBadUnitType
2604 mcTimeOutErr
2605 mcNotLoaded
2606 mcBadAudio
2607 mcDevRtnError
2608 mcUnrecStatus
2609 mcBadSelector
260A mcFunnyData
260B mcInvalidPort
260C mcOnlyOnce
260D mcNoResMgr
260E mcItemNotThere
260F mcWasShutDown
2610 mcWasStarted
2611 mcBadChannel
2612 mcInvalidParam
2613 mcCallNotSupported

4201 [66] FINDER: bad input
4202 fErrFailed
4203 fErrCancel
4204 fErrDimmed
4205 fErrBusy
4206 fErrNotPrudent
4207 fErrBadBundle
42FF fErrNotImp


002- What does IIgs Diagnostic Self-Test Error
     Code ___ mean?

IIgs Diagnostic Self-Test Error Codes

From: a list by Jeff Tarr, Jr., Apple IIgs Technical Reference
      by M. Fischer, and IIgs TechNote #095 by Dan Strnad

     The IIgs self-test is activated by pressing Open-Apple and Option
on power up, or Open-Apple, Option, and Reset. During the test, the test
number (in hexadecimal) is visible on the bottom of the screen followed
by six zeros. After all tests are complete, a continuous 6 KHz
one-second beep sounds and the screen displays a System Good message. 
If any test fails, the screen displays a message of the form System Bad:
AABBCCDD on the lower left hand side and a staggered AABBCCDD on the
upper left hand side to help read the error code in the event of a RAM
failure. In the event of video failure, the failure code is also sent to
the printer port.

Note: There may be a few differences in the GS diagnostic self-test
depending upon ROM version. For example, earlier GS's may not include
Test $0C (AA= 0C).

Error Codes are displayed in the format 'AABBCCDD'.

ROM Test:G         
AA= 01   BB= Failed checksum      DD= 01: RAM error

Note: A ROM failure will also be denoted by "RM" in the top left hand
corner of the screen.

RAM 1 Test:H       
AA= 02   BB= __: Bank number      CC= Bit(s) failed
             FF: ADB Tool error

Soft Switches:M    
AA= 03   BB= State Register bit   CC= Read addr. Low Byte

Address Test:K     
AA= 04   BB= __: Bank number    CCDD= Failed RAM Address
             FF: ADB Tool error

Speed Test (FPI):  
AA= 05   BB= 01: Stuck slow
             02: Stuck fast

Note: If a ZipGS accelerator card is installed and DIP Switch 1-4
(Counter Delay) is set OFF (the normal, default setting), your GS will
bomb on Test 05. This does not indicate any malfunction.

Serial Test:1      
AA= 06   BB= 01: Register R/W
             04: Tx Buffer empty status
             05: Tx Buffer empty failure
             06: All Sent Status fail
             07: Rx Char available
             08: Bad data

Clock Test:H       
AA= 07   DD= 01: Fatal error occurred - test aborted

Bat RAM Test:F     
AA= 08   BB= 01: Addr. unique    CC= bad addr
             02: NV RAM pattern  CC= bad patt DD= bad addr

ADB Test:J         
AA= 09   BBCC= Bad checksum      DD= 01: Fatal error

Shadow Register:   
AA= 0A   BB= 01: Text page 1 fail
             02: Text page 2 fail
             03: ADB Tool call error
             04: Power on Clear bit error

Interrupts Test:   
AA= 0B   BB= 01: VBL interrupt time-out
             02: VBL IRQ status full
             03: 1/4 sec interrupt
             04: 1/4 sec interrupt
             06: VGC IRQ
             07: Scan line

Sound Test:3       
AA= 0C   DD= 01: RAM data error
             02: RAM address error
             03: Data register failed
             04: Control register failed
             05: Oscillator interrupt timeout

Note: There are reports that if a ZipGS accelerator card is installed
and not disabled, then, your GS may fail parts of this test depending
upon DIP Switch settings. Such a failure does not necessarily indicate a
hardware fault.


From: Paul Creager

003- What does RamFAST Fatal Memory Fault Error ___ mean?

 $00     Unknown, probably means that the RamFAST is very confused
 $01-08  DRAM memory test failure
 $09     EPROM checksum failure
 $0C     Z180 processor crashed, indicates some hardware fault
 $0D     Error writing cache data to disk
 $0E     Termination power error


004- What is the explanation for getting a ___  error?

  0027 (ProDOS Error $27, ...)
  0047 (ProDOS Error $47, ...)
  0048 or 0049 (e.g. ProDOS Error $48, ...)
  004B (ProDOS Error $4B, ...)
  0051 (ProDOS Error $51, ...)
  005A (ProDOS Error $5A ...)
  0088 "network error"
  0201 "could not allocate memory" error
  0681 and 0682 "bad event que" and "bad que handler"
  0911 and 09010001 (FATAL SYSTEM ERROR 0911)
  1102 "OMF version error"
  1104 "file is not a load file"
  IIe Self-Test RAM error display
  RamFAST MLI Error!
  0C000003 GS Diagnostic Self-Test error
  RamFAST: RAMFAST.SYSTEM "Incompatible configure.dat"

0027 (ProDOS Error $27, ...)- In trying to access an apple SCSI hard
drive hooked up to a GS I keep getting a $27 error!?

     This is an I/O error (input/ouput error).  It may indicate that
there is a problem on the SCSI chain, such as a loose connector, SCSI
ID# conflict, absence of termination at the end of the chain, or absence
of termination power. Another possibility is that one or more hard disk
files have become corrupted. Replacing a few files may fix things; or,
you may need to repartition or, even, low-level re-format the hard disk.

0047 (ProDOS Error $47, ...)-  A "Duplicate pathname" error indicates
that an attempt has been made to create a file which already exists or
to rename a file to one which already exists-- i.e. the full pathname of
a new or renamed file equals the full pathname of a file which already

     Note that it is okay to have a file or folder named, say, "PICS"
inside a folder named "PICS"; and, you can have files named "PICS" in
different folders. Also, ProDOS will permit overwriting a file with a
file with the same name so long as the original and replacement file
have the same filetype.

     What ProDOS does not like is an operation which tries to _create_ a
file or folder whose _full_ _ pathname_ is the same as an existing file
or folder. For example, you cannot create a "GAMES" folder on /RAM5
(i.e. /RAM5/GAMES) if there is already a file or folder there named
"GAMES"-- i.e. one whose pathname is /RAM5/GAMES.

     This error might easily occur when running a self-extracting file
if the self-extracing file has a name which matches the name of a
contained file-- a solution for this problem would be to rename the
self-extracting file. A more general solution for duplicate name
creation is to create a new folder and use the extraction utility (e.g.
ShrinkIt-GS), instead of doing a self-extraction, to extract files from
the source file to the folder. --Rubywand


0048 or 0049 (e.g. ProDOS Error $48, ...)-  Error $48, of course, means
"volume full"-- you are out of space on the target volume. 
Unfortunately, "volume full" is, sometimes, incorrectly reported when
the actual problem is too many entries in the volume's main directory.
(see below)

     A $49 "volume directory full" error means the main or "root"
directory of the target volume has 51 entries and that an attempt has
been made to create a 52nd entry. When it is incorrectly reported as
"volume full" it can be very confusing to a user who CATALOGs the volume
and discovers plenty of free blocks. The solution is to move some of the
files in the main directory to folders. Only a volume's main directory
has this low limit on number of entries. You can have many more than 51
files in a folder. --Rubywand

004B (ProDOS Error $4B, ...)-  is an "unsupported (or incorrect) storage
type" error. I suspect you are on the GS and that the game or whatever
you are trying to run is supposed to have a forked file and now the
program can not find it. This has happend to me when Dragging files
around.  I recommend you recopy the game from your original disk, or
re-unShrinkIt to the location you wish it be. If you believe a file may
have a resource fork, avoid copying it with Copy-II Plus or moving it
around on the GS desktop under an old operating system-- either process
could result in losing the resource part of the file.  --thedm


0051 (ProDOS Error $51, ...)- My 3.5 copy of AppleWorks 3 said "Error
loading ATINIT" (on my //c, no less), so I tried using Copy ][+ 9.1 to
copy ProDOS 2.0.3 over the top of the apparently broken copy of ProDOS
1.7 on the AppleWorks disk. It then ran the drive, cleared the screen,
and informed me so: Error $51.  Does anybody know what the heck this

     The error indicates the directory is damaged.  You MIGHT be able to
salvage stuff by doing a FILE copy, rather than a disk copy. --Jim Lowe


005A (ProDOS Error $5A ...)- Today, I discovered that one of my 
Appleworks files had been overwritten by nulls. Luckily, I have a backup
copy of that file. When I tried to delete the bad file and rename the
backup I got ProDOS error $5A. Any insight into what this error message
means and what I can do about it?

     Error $5A "block number out of range" (sometimes known as "baked
bit-map") means there's a bit set in the bit map which corresponds to a
nonexistent block on that volume. You could try taking a block editor
and writing zeroes to the upper bit map blocks on the volume to cure it.
--Randy Shackelford


0088 "network error"- Can anyone enlighten me as to why Copy-II Plus and
ProSel-8 are unable to work with a network volume that the Apple utility
(and plain-old Basic) has no trouble with?

     Simple answer. Copy-II Plus and ProSel-8 bypass the file system and
do direct block I/O to disk volumes. This is verboten with server
volumes, and you get error $88 for your trouble when you try. You'll
have to use network friendly apps whenever you access the server volume.
--Randy Shackelford       


0201 "could not allocate memory" error- After using the installer to
install the basic Sys6 over Sys 5.04 on my hard drive, I couldnt run a
ProDOS-8 program. Before the ProDOS 2.0.1 sign comes up, it says "Error
$201". I have more than 4MB! What's wrong?

     A $0201 error when switching to ProDOS-8 usually means some utility
has left part of bank 0 or bank 1 allocated. You have enough memory
free, but some particular memory that ProDOS 8 needs is not available.

     I have seen occasional $0201's after using Find File 1.0 (included
with 6.0) before switching to ProDOS-8. --Dave Lyons


0681 and 0682 "bad event que" and "bad que handler"-- What do these
error codes mean? How does the GS determine if an error is FATAL (as in

     The errors are 'Event Manager errors'. A key press and mouse button
press are examples of "events". The errors indicate a record of events
was messed up. One of many places this might occur is while you are
typing-in text. "FATAL" usually means that System believes that things
are so messed up in memory that restarting is necessary. Sometimes,
"FATAL" means that System suspects that there may be a hardware failure.


08FF "UNCLAIMED SOUND INTERRUPT"-- A sound interrupt has occurred but
none of the available interrupt handlers were willing to deal with it.
The Sound tool set thinks this is pretty serious; so, it notifies the
System Failure Manager and you get the error message. A possible cause
is that the table of interrupt vectors or the pointer to the table has
been messed up in memory. --Rubywand 


0911 and 09010001 (FATAL SYSTEM ERROR 0911)-  Fatal System Error 0911
and Self-Diagnostic Test 09010001 mean the same thing: You are
experiencing an ADB "can't sync" problem which, usually, relates to an
ADB Controller malfunction.

     A guess would be that you are running a ROM-01 GS, probably a
ROM-00 machine which has the ROM-01 upgrade. If this is the first time
you've noticed the '0911 problem, it is likely that this is the first
summer you've owned and used this particular machine.

     Chronic occurance of Fatal System Error 0911 almost always
indicates a faulty ADB Controller IC. The failure mechanism was first
identified and described in Computist #58 back in 1988.

     Many early GS's come with an ADB IC which malfunctions over a
narrow range of relatively low temperatures. Rooms are normally cooler
during summer; so, this is when the error pops up most frequently. Some
users first notice a plague of '0911 crashes after adding a System
Saver-GS (which increases cooling).

    '0911 bombs can occur 'any time' but they usually happen at startup
and when doing OpenApple-CTRL-ESC accesses to the Desk Accessories
(CDA's, Control Panel, ...) menu. As the machine warms up, '0911 crashes
tend to become less likely. (See Csa2HDWHACK FAQs for more discussion
and a possible fix.) --Rubywand


1102 "OMF version error"- When trying to launch some GS programs I am
encountering the following error message:
Sorry, system error $1102 occurred
while trying to run the next
application.  Return to launching
application or restart system.
So, whats wrong with my IIgs and how do I fix it?
     Probably, there is nothing wrong with your IIgs. The "incompatible
Object Module Format" error appears to indicate that your versions of
the problem programs are, in some ways, not compatible with your
operating system. Try launching the program from an earlier version of
GS/OS or after booting an old "ProDOS-16" diskette. --Rubywand


1104 "file is not a load file"- I downloaded some GS Desk Accessories
fine; but, when I try to use them I get this error. How come?

     Error $1104 is reported by tool $0B11 LoadSegNum (tool $0B in
toolset $11).  The error is reported if a check of a file's directory
entry shows that the file is not file type $B3-$BE.

     If an NDA or CDA were downloaded and its file type were not
preserved, then the file might be okay, but it would not be recognized
as a load file. Try changing the file type ($B9 for a CDA; $B8 for an
NDA).  An NDA named "File.Manager" by Jeff Hartkopf and Glen Bredon's
ProSel-16 are two utilities that allow changing file type. --Rubywand


1301 "Unknown error $1301"- When I tried to open a file in Platinum
Paint, I got this error message. What's wrong?

     I got the same error message when I tried to run Platinum Paint
with Bernie ][ The Rescue on a G3 Power Mac. The error code refers to a
missing driver; but, even if the correct printer driver is present, what
Platinum Paint really wants is for the D C Printer Control Panel
settings to be correct.


RAMFAST-SCSI FATAL MEMORY FAULT CODE=08- Could it be a problem with my
SSCI card?

     It looks like RamFAST thinks there is a problem with the on-board
memory. Before calling Sequential or Alltech, you might try pulling the
board from the Slot-- do this only with GS power turned OFF-- and
wedging-up and re-seating each memory IC. (This assumes the mem IC's are
socketed.)  If you're not sure which IC's are memory chips, do them all.
Re-seating the IC's may reestablish a pin-to-socket contact which has
been broken due to oxidation coating on an IC pin or due to the IC
working loose over time. --Rubywand


IIe Self-Test RAM error display: RAM   0 1 0 0 0 0 0 0- I get this 
error message when doing a selftest on my //e enhanced boot up. What's
it mean?

     The indication is a bad or loose RAM chip in the Bit 6 position.
The RAM chips are in Row F at the front of the motherboard starting with
Bit 0 and running to the right when viewed from the front of the

 | Row
 |  E
 |                  Bit 0   1   2   3   4   5   6   7   |
 |                      _   _   _   _   _   _   _   _   |
 | Row                 | | | | | | | | | | | | | | | |  |
 |  F                  |_| |_| |_| |_| |_| |_| |_| |_|  |
 |                      6   7   8   9  10  11  12  13   |

                   Front of Apple IIe

     If your RAM chips are in sockets, try removing and re-socketing the
second chip from the right. If this does not work or if your chips are
soldered in place, the chip is probably bad and will need to be
replaced. --Rubywand

RamFAST MLI Error!
Command: 04-03 86 00 60 05 00 00 00 00
Status: 2F

     I have a new 530MB hard drive, and a ROM 03 GS with a RamFAST (ROM
F, I think).  From the Ramfast utilities, I could do a low-level format
on the drive with no problem. However, when I attempted to partition it,
I saw the error message listed above.

     As it turns out, this drive has a place for a jumper documented to
"Disable TI Negotiation." Before giving up all hope, I put a jumper in
there. This apparently made it possible to partition the disk, and
things look good now. -- John David Duncan


0C000003 GS Diagnostic Self-Test error/ Sound Test: Data register failed

There is one possible reason for this failure code being reported by the
self-test: do you have a ZIP GS accelerator in the machine?  The ZIP GS,
if enabled, causes the IIgs to fail some of its self-tests (only because
the tests are relying on the speed at which the processor normally
operates, and get confused because the CPU is running faster than
expected).  If this is the case, you must turn off the computer and
disable the ZIP GS by setting switch 1-6 OFF before you can run the
self-test properly.


RamFAST: RAMFAST.SYSTEM "Incompatible configure.dat"- My 10 year old
came to me this weekend upset because of something that's happened to
his GS.  When he boots it up, he is getting a message about an
incompatible configure.dat file, then ends up in the ramfast scsi

     If the GS ends up displaying the RamFAST.System screen, and
"Incompatible ..." message, click on the error message to clear it and
then click Options. Set these according to your system-- mainly, click
TransWarp to "No" if you do not have a TransWarp installed. Probably,
you will want Password, RomDISK, HD Backup, and Short Timeout set to
"No", as well. (You can experiment with Short Timeout and DMA; but, for
now, set them to "No".) The other options should be "Yes".

     Click Save, then Quit. If you get the <<BOOT>> prompt, click it. If
you end up looking at a BASIC prompt, try entering PR#7 (assuming your
SCSI interface is in Slot 7)  to see if the hard disk will boot.

     If either of the above gets you into the Finder where you can copy
files, then you will have a way to make backups.

     To check that the config has been correctly written to hard disk
you will need to turn OFF the machine. (i.e. from the Finder, do a
Shutdown and then turn OFF the GS.)

     After 10-20 seconds, turn ON the computer and see if it boots
correctly. If it does, fine. If it does not, you may have to reformat
the hard disk. --Rubywand


"NO BUFFERS AVAILABLE" error message.  What does this mean?

     This message often indicates that there has been an attempt to load
into an area protected by ProDOS. For example, many old DOS 3.3 programs
like to directly load a text message or lo-res pic into Text Page 1
($400-$7FF), an area protected by ProDOS.  Running such a program under
ProDOS would be likely to produce the "NO BUFFERS AVAILABLE" message.
You can recover from the error via a CALL48888. --Rubywand


"UNABLE TO LOAD PRODOS" - Why do I get this message when I try to boot a
ProDOS diskette?

     For a ProDOS disk to boot properly, you need a good copy of the
PRODOS file. It can be copied from any bootable ProDOS diskette. Or,
from GS/OS, copy the file named "P8" (in the SYSTEM/ folder) to your
diskette and rename it to "PRODOS". --Adam Myrow

     The error message means that the disk was formatted for ProDOS,
but, for some reason,  the system file (usually named "PRODOS") fails to
load. Possibly, ProDOS is not present on the disk or it is corrupted. If
the diskette boots okay on another Apple II, the indication is that your
drive has dirty heads, may be poorly connected, has a problem with head
alignment, or (5.25") needs a speed adjustment. --Rubywand


From: Rubywand

005- Where can I find more information on Apple II
     series errors?

Resources & Credits

IIgs Diagnostic
  Jeff Tarr, Jr.
  Apple IIgs Technical Reference by M. Fischer (pg. 213-217)
  IIgs TechNotes #95: ROM Diagnostic Errors by Dan Strnad  Sep, 1990

  Apple IIGS GS/OS Reference (pg. 438-439). 
  For info on Expressload and System Loader refer to pg. 200-234.

ProDOS 16 and System Loader
  Apple IIgs ProDOS 16 Reference (pg. 302-311)

ProDOS 8
  ProDOS Technical Reference Manual (pg. 77-79)
  Beneath Apple ProDOS by Worth & Lechner (pg. 6.59-6.61)

  Paul Creager (

  Apple IIGS Firmware Reference (pg. 156).

Tool Sets
  Volumes 1-3 of the Apple IIGS Toolbox Reference set.

     A good on-screen listing of errors encountered on the IIgs (plus
lots of other toolbox, softswitch, etc. info) is available via Dave
Lyons's NiftyList CDA package ($15, Shareware).  Another good on-screen
list is Jeff Tarr Jr.'s ErrorCodes CDA v1.7 ($5, Shareware).

     Applesoft, DOS 3.3, ProDOS BASIC.SYSTEM, and ErrorWindow error
codes are not listed because errors are reported directly in text
messages. For codes and descriptions see ...

  Basic Programming Reference Manual  (pg. 81)

DOS 3.3
  The DOS Manual  (pg. 114-115)
  Beneath Apple DOS by Worth & Lechner  (pg. 8.20)

  Exploring Apple GS/OS and ProDOS 8 by Little  (pg. 249)

 'Toolbox Reference: Volume 3  (pg. 52.53-52.56)