previous page: 08.003 What does RamFAST Fatal Memory Fault Error ___ mean?
page up: Apple II Csa2 FAQs
next page: 08.005 Where can I find more information on Apple II series errors?

08.004 What is the explanation for getting a ___ error?


This article is from the Apple II Csa2 FAQ, by Jeff Hurlburt with numerous contributions by others.

08.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
  0512 (FATAL SYSTEM ERROR 0512) "badNdaTitleString"
  0681 and 0682 "bad event que" and "bad que handler"
  0682 "bad que handler"
  0911 and 09010001 (FATAL SYSTEM ERROR 0911)
  1102 "OMF version error"
  1104 "file is not a load file"
  1301 "Unknown error $1301"
  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. --Rubywand


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 exists.

     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

     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 des

ktop 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 means?

     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


O512 (FATAL SYSTEM ERROR 0512) "badNdaTitleString"-- comes from FixAppleMenu
(in the Desk Manager).  It means that one of your installed New Desk
Accessories does not have a well-formed menu title string.  In particular, the
required backslash (\) character was not found (make sure bit seven is off). --
IIgs TechNotes


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 FATAL SYSTEM

     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. --Rubywand


0682 "bad que handler"-- My IIgs crashes with a Fatal Error $0682 whenever I
have my expansion memory card plugged in and try to access the Control Panel.
Also the Alternate Display mode seems to be missing and stuff won't boot.
What's wrong?

     Error $0682 indicates a data structure maintained by the Event Manager is
corrupted.  It is either the Event Queue itself, or something related to it.
The most common cause for this is buggy software which has overwritten memory.

     The second most common cause is a faulty or incorrectly configured memory
expansion card (or bad RAM on that card).  The event queue normally lives near
the top of "fast" memory, so it is always located in the memory expansion card
if you have one.

     Similarly, the list of items in the Desk Accessories menu is in RAM, so
lack of Alternate Display Mode points to memory corruption of some kind. -
- David Empson


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, seems to relate to a hardware malfunction.

     See Csa2HDWHACK.txt for more discussion and possible fixes.

--Rubywand, David Kopper, Guenther Unger, Gabriel Hawkins


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 System 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. --Jim


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

     It looks like RamFAST thinks there is a problem with the on-board memory.
Before calling 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. --Rubyw



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 computer.

 | Row
 |  E
 |                 Bit  0   1   2   3   4   5   6   7   |
 |                      _   _   _   _   _   _   _   _   |
 | Row                 | | | | | | | | | | | | | | | |  |
 |  F                  |_| |_| |_| |_| |_| |_| |_| |_|  |
 |                 IC#  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. --

David Empson


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 utility!?

     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

     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

     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 IIgs System,
copy the file named "P8" (in the SYSTEM/ folder) to your diskette and rename it
to "PRODOS". --Adam Myrow

     The error message means that enough of boot track (e.g. Track 0) was read
to tell that the disk is formatted for ProDOS; but, for some reason, the system
file named "PRODOS" is failing to load. Possibly, PRODOS is not present on the
disk or the file is corrupted or there is a problem with the drive which
prevents reading the file.

     If the disk boots okay from a different drive, this usually indicates that
your original drive has dirty heads, may be poorly connected, has a problem
with head alignment, or (5.25") needs a speed adjustment. If the disk is a
5.25" diskette created on a newer model 5.25" ("40-track") drive, it may be an
HD (high-density) diskette. Standard Apple 5.25" drives cannot reliably read HD
diskettes-- see the Diskettes FAQs page. --Rubywand


"CHECK STARTUP DEVICE" - Why do I get this message when I try to boot a disk?

     This error message usually means that there is no diskette in the boot
drive, the drive door is not closed, or that the disk is not bootable. On a
system which has several drives-- e.g. 3.5" and 5.25" drives and/or a hard
disk-- the message indicates that no bootable disk was found on any of the
drives tried.

     If you know that a bootable disk is present, the indication is a problem
with the drive (see Q&A above) or with the drive controller (which may be a
card plugged into a Slot) or with a cable connecting the drive or with settings
which affect recognition of the drive with a bootable disk.

     The problem may be that the bootable disk is not detected because the IIgs
Control Panel is not set correctly-- e.g. the Startup Slot is set below the
number of the Slot associated with the drive and/or the Slot with an interface
card is not set to "Your Card". Note: After changing a Slot setting in the
Control Panel, especially for a SCSI interface, it may be necessary to turn Off
the computer and do a fresh power-up for the new setting to be in effect.

     If the expectation is to boot from /RAM5 RAM disk, make sure that /RAM5 is
initialized before copying files to it. (/RAM5 is normally automatically
formatted as a ProDOS volume when you first power up; but, it will not have the
required boot block unless it is initialized or unless you do a whole-disk copy
to /RAM5 of a bootable disk.) --Rubywand

By:  Rubywand


Continue to:

previous page: 08.003 What does RamFAST Fatal Memory Fault Error ___ mean?
page up: Apple II Csa2 FAQs
next page: 08.005 Where can I find more information on Apple II series errors?