Troubleshooting Power Macintosh Type 11 Errors
Article ID: Q140445
Creation Date: 30-NOV-1995
Revision Date: 26-NOV-1996
The information in this article applies to:
- Apple Macintosh System Software versions 7.5.x
- Microsoft Bookshelf for the Power Macintosh, 1996-97 edition
- Microsoft Cinemania for the Power Macintosh, 1997 edition
- Microsoft Close Combat for the Power Macintosh, version 1.0, 1.0a
- Microsoft Encarta Encyclopedia for the Power Macintosh, 1997 edition
- Microsoft Excel for the Power Macintosh, version 5.0
- Microsoft Internet Explorer for the Power Macintosh, version 2.0, 2.1
- Microsoft Music Central for the Power Macintosh, 1997 edition
- Microsoft Word for the Power Macintosh, version 6.0
- Microsoft Works for the Power Macintosh, version 4.0b, 4.0c
SUMMARY
If you are using a Power Macintosh computer with System 7.5.0, 7.5.1,
7.5.2, 7.5.3, or 7.5.5 you may experience a "Type 11" (hardware exception)
error. As with other general system errors, a Type 11 error does not
identify a particular hardware or software cause. A Type 11 error has many
possible causes. The "More Information" section of this article contains
steps you can follow to help identify the cause of a Type 11 error.
NOTE: Type 11 errors are not common on earlier models of Macintosh
computer.
MORE INFORMATION
When you search for the cause of a Type 11 error, start by looking for
software problems and then look for hardware problems.
To check for possible causes of Type 11 errors, use the following steps:
- If you are using System 7.5, install the latest system, currently System
7.5.5. System 7.5.5 includes a modified memory manager that speeds up
memory-intensive operation and adds stability to the System.
- If the problem only occurs in one program, and you can reproduce it
consistently, try turning off the Modern Memory Manger, and contact the
program's vendor for information about its compatibility with Modern
Memory Manager.
- Turn on Virtual Memory. Power Macintosh applications run more
effectively with Virtual Memory enabled.
- Use Extension Manager to turn off all extensions and control panels.
Check the program again. If the problem goes away, then enable the
extensions and control panels a few at a time to isolate the one that is
causing the problem.
- If you have a large number of fonts in the Fonts folder, move them from
the Fonts folder to another folder.
- Remove the General Controls file from the Control Panel folder of the
System Folder. This control panel device will work outside of the System
Folder; removing this device prevents damage that occurs to the
Parameter RAM area of memory with System 7.5.x. Once you remove this
file, use the following steps to clear and repair damage that may have
occurred in the parameter RAM area of memory. This procedure is called
"zapping the PRAM."
To zap the PRAM:
a In the Finder, restart the computer by clicking Restart on the Special
menu.
b. While the computer is restarting, press COMMAND+OPTION+P+R. Continue
to hold these keys down while the Macintosh attempts to restart.
c. Hold the keys down through five repetitions of the Macintosh startup
noise (the computer will make a "ding" noise each time it attempts
to restart).
d. After five start noises, release the COMMAND+OPTION+P+R keys.
NOTE: When you use this procedure, you will need to reset some Control
Panel settings such as the highlight color, the type of network you
access, and the screen resolution.
Note also that this procedure has been used successfully with
customers using MacOS 7.5.1 and 7.5.2 with Type 10 errors, random
freezes, failures while printing, and errors that are not
specifically Type 11 on non-Power Macintoshes.
- Update the Hard Disk driver to the most recent version for your version
of the system software.
- Perform a clean installation of the System Software, follow Step 5, and
then test the system performance for a few days (Press
COMMAND+SHIFT+K in the Installer).
If the Type 11 errors continue, you may have a hardware problem. If you
think that you have a hardware problem, contact your hardware repair
service. Three areas for which you might suggest further testing include:
SCSI connections, Cache SIMM, or third-party RAM. These hardware tests
require appropriate tools and specialized knowledge and should be performed
only by those with the proper tools and experience to do them.
INFORMATION FROM APPLE COMPUTER SUPPORT ABOUT TYPE 11 ERRORS
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 earlier versions of Macintosh software. If the emulator
gets corrupted while loading into in RAM, some of the failures caused by
this are reported as Type 11 or Hardware Exception errors. The emulator can
get corrupted by incompatible software or faulty hardware. That implies
that the chance of Type 11 errors occurring increase with memory intensive
programs (such as PhotoShop, and so on) or with larger SIMMs. Some
modifications have been made to the design of the logic board of the
8100/100 and 8100/110 models to decrease the sensitivity for third-party
SIMMs.
Your Apple Service & Support Team
13 April 1995 Copyright 1995 Apple Computer
Known Causes of Type 11 Errors
System 7.5 and QuickDraw GX: "Finder:error type 11"
If System 7.5 with QuickDraw GX is installed, the message "Finder:error
type 11" might occur whenever the system boots after a system crash.
Solution: Throw away the Desktop Printer icon. This icon contains
settings that could have gotten corrupted when your system crashed.
SoftWindows Previous to Version 1.0.2
SoftWindows 1.0.2 fixes bugs where CBT, NOBEER, and others consistently
(and repeatedly) created errors of type 11.
PhotoShop 3.0.1
Workaround: Remove the "Enable Async I/O" plug-in extension. (It's located
in PhotoShop Plug-Ins folder.)
Microsoft Office 4.2
There have been reports of users receiving Type 11 errors when printing
with Microsoft Office 4.2 (which includes Microsoft Excel 5.0 and Word 6.0
native) from systems using System 7.5 with QuickDraw GX 1.1.1. The same
programs do not produce this error when printing under QuickDraw GX 1.0.1.
Currently, the workaround for this problem is to turn off Modern Memory
Manager.
|