POWERMAC:

UP & RUNNING Version b0.90, July 1995

What This File Is: A listing of SOME of the things one can do to avoid or remove
Type 11, Coprocessor Not Installed, or other errors and crashes. Some information
from Apple Techinical Library was used as a starter for this file. Most of it is
garnered from various, real-world experiences.

What This File Is NOT: An offical or empirical technical discussion of how or why
these errors come up. I'm a Mac end-user - I don't have the time to care. I just
need to be productive.

CONTENTS:

A. Setup and preventative measures for new machines or installations
B. Practial error tracking C. Some application-specific do's and don'ts
D. Help wanted

A. If you've bought a new PowerMac, here are a list of things that could
eliminate some problems right off the bat. These measures do not specifically
take into account new machines with the PPC603, PPC604, or PCI bus, but should
still be good common practices.

1. For the seriously anal, reformat the hard drive using the latest HDSC Setup
and freshly install system 7.5 even if it's already on the HD. Be certain to
install all software and updates with extensions off (shift key during start-up).

2. Obtain System 7.5 Update 1 and install that as well. If on a network, get
NSI 1.5.1 or better. - If MacTCP 2.04 hasn't been updated to 2.06 automatically,
rename it just "MacTCP" before the update or do a custom install of just MacTCP
after the update. - If you've clock-chipped, get the update patcher from your
respective chipper vendor. Otherwise, the Updater will mis-recognize your PMac
and not perform a full or proper update.

3. Do not install some of Apple's buggier, less than functional, or memory
hungry extras like: - Quickdraw GX unless you have a QD GX printer - Plaintalk
unless you really like talking to your computer and can spare 4MB of system RAM.
- Powertalk unless you use Powertalk-based communication managers.

4. Strip out some of Apple's buggier or less than functional system items: -
Menu items or cdevs like Stickies, Puzzle, Windowshade, Auto Power On/Off, Energy
Saver, Mac Easy Open, Desktop Patterns and Easy Access for example...they're not
necessarily buggy however. - Launcher - just use a desktop folder with aliases in
it instead. - Extensions like Worldscript, unused printer extensions and PDFs,
unused network extensions, unused Appleguide extensions, etc. - Foreign keyboard
layouts in your System File like Flemish, French Canadian, etc. if those
languages are foreign to you.

5. Obtain the latest versions of essential 3rd party extensions: - ATM 3.8.2
or later can be found at www.adobe.com. You'll also find various PMac-updated
plugins for Photoshop and Illustrator there. - Disinfectant 3.6, Extensions
Manager 3.0+ (or Conflict Catcher 3), Basic Black 1.41, RamDoubler 1.52, latest
Kodak PhotoCD, Laserwriter 8.3, Sound Manager 3.1, new Apple PDFs, and Apple
Multimedia Tuner updates can all be found in these or later versions at either
info-mac or Apple archives.

6. Remove buggy 3rd party extensions: - Old ATMs, any Type Reunion, old
RAMDoubler, etc - After Dark will most likely cause you problems. Can replace
with Basic Black (small, stable, free) - SAM had also caused us problems. Can
replace with Disinfectant and a good dose of common sense and herd immunity.

7. Finally, reinstall all application software from scratch, making sure to
custom install PMac versions where possible. Do not copy the contents of your old
computer, lock-stock-&-barrel! (whatever that means) Be wary of extensions that
these may toss into your system folder (especially Microsoft (!) but also things
like extra Teach Text and Macintosh Easy Open copies). Be careful to use proper
updaters on the proper application. For example, use Fat-specific updates on a
Fat-installed app only, etc.

8. After all this, zap your Parameter RAM by pressing option-command-P-R at
startup. Let it zap three times to try to get full clean-out of the PRAM (you're
Mac will blank-out three times and give three start-up chimes). Also rebuild your
desktop file by starting up with option-command pressed down until you get the
rebuild message. You can keep TechTool around for this as well.

9. A disk diagnosis by MacTools or Norton may be necessary after all your
installs are complete. PowerMac installations seem to sometimes play havoc with
various catalog and directory data.

10. Think about creating application-specific minimum extension sets. For
example, any serious Photoshop production work should be done using some sort of
"PS-minimun" set that doesn't include communications or other gadety stuff. A
"StudioPro-minimum" set shouldn't include RamDoubler, or the new Mathlib, .
Conflict Catcher is very useful for grouping extension sets, like all Microsoft
extensions or all Photo-CD extensions.

B. If you're having freeze-up or error code problems, read the following.
There are innumerable causes to the Type 11/Type 1/"Coprocessor Not Installed"
fiasco's that PMac users have been experiencing and no single solution for them
all. The goal is figuring out what your particular cause is. Here's my personal
checklist from easiest to hardest to diagnose...

1. Application software - Is it PowerMac native?; if not, upgrade - if it's
some small utility, game or app that's not worth having or upgrading, toss it; -
if necessary, give apps more ram in "get info"; some apps routinely crash on
PMacs without extra - If you have lots of 68k apps, try running without Modern
Mem Manager but this is not a satisfactory solution as you want MMM to be on.

2. Disk Drivers/Formatters - update to the latest SCSI Manager 4.3 compliant
versions! This means Apple's latest HDSC Setup, FWB's HDTK 1.7, or Charismac's
Anubis 1.5.2x of better to name three.

3. Extension conflicts - disable 'em; swap 'em around; do whatever you have
to do to weed 'em out; you know there's a bad seed in there so don't go past this
until you find it!

4. Corrupt System Items - toss your application prefs, run MacTools, Norton
or even TechTool; try reinstalling fonts from a fresh archive or installer disks;
if that doesn't work, do a full and clean system reinstall; for clock-chippers,
get the respective patches if you're updating to 7.5.1.

5. Corrupt PRAM - unplug the computer, open up that motherboard and lift out
the battery for a few minutes before putting it back in; don't half-ass it by
zapping it from the keyboard if you're having serious trouble.

6. SCSI problems - - disconnect external devices and run for awhile this way
to check. - if that works, get new cables and/or active terminators - reset IDs
and/or place your devices in different order. My Mac likes both internals are set
to ID 0 (on a dual bus) with the scanner in the middle of the external chain.. -
some CPU-type devices, i.e. scanners rather than drives, seem to like being on
the end but this is totally nonemprical observation. - make sure your cables are
short; some devices won't behave past 24" - if you have over 6 feet in cables,
add an extra terminator in-between (I know this is oxymoronic to the word
"termination" and doesn't sound kosher, but it is, in fact, official Apple advice
and also corroborated by some old Unix vets); - do whatever you can with the SCSI
before moving on.

7. Surge protection - if errors occur across several machines, check if your
building is prone to surges, lapses, or spikes. If so, consider getting
uninteruptible and constant-power power supplies.

8. 3rd Party RAM - if you've added some, reseat them or pull them out; if
pulling does the trick, get new matched, non-composite, fast refresh,
80ns-minimum simms (I like 60ns).

9. Cache card - if you have one, pull it out then run for awhile; some early
Apple and 3rd party ones were reportedly buggy. If under warranty, have your
"authorized Apple dealer" pull it out and replace.

10. If you still get glitches, you might finally have a motherboard problem.
This is RARE...most likely you aren't the one in whatever many who has this
problem. If you've done the above and documented it thoroughly however, you
should have no trouble getting the Apple dealer to eventually say "Okay, we'll
run the diagnostic then get you a new motherboard." Make sure that any diagnostic
is run recursively several times or overnight...some things just don't show up in
one pass. Good luck.

C. Some common application specific "do's", "don'ts" and "try if you're
desperate's" . This section is new and very incomplete.

1. Photoshop 3 - try disabling the Asynch i/o plugin...shouldn't be a concern
if everything else is 100%. - try tossing your prefs (you can keep a lock version
seperately for convenience). - try disabling Photo-CD plugins when not in
use...again, not a real solution. - keep it's memory partition below real memory
minus system memory minus about 10%. - keep disk cache fairly small (below 256k?)
despite Mod Mem Manager being improved. - defragment or swap scratch disk(s).

2. Netscape 1.1N - try keeping your cache low (2megs?). Remember that 10megs
of 20k files is 500...gag! - try flushing the prefs, cache and/or followed links.
- give it 1 or 2 more megs of RAM...many have seen significant crash reduction.

3. Strata StudioPro 1.5 - it doesn't like RamDoubler - some have reported
problems with 7.5.1's new MathLib - the 1.5.2 updater only works with the Fat
Binary

4. Quark Xpress 3.3 - get update 3.31r5

D. Please Help. If you have other suggestions, modifications, corrections or
requests, I'd love to hear about them at myirwin@uci.edu. Once corroborated, I
will add them to the list. Part C especially needs to be beefed up. However, Part
C won't become a huge repository for app-specific information...just the major
points the seem to get repeated over and over in the newsgroups and mailing
lists.

© July, 1995 by Michael Irwin, UC Irvine, Dept Microbio & Molecular
Genetics/Minotaur Design. Feel free to distribute this file as is. I only ask
that any major modifications either delete my name or be brought to my attention.
All and any advice expressed above are merely Mike's opinions and in no way
represent an authoritative view on how you should set up your computer. These
views do not in any way express Apple or UC Irvine's views. In no way, do these
views express any implied warranty or liability should you have problems with
your computer. In no way does any mention of a commercial company promote or
disparage it's products...they are simply what my and my colleagues' experiences
have been with them.

Back to HyperWisdom

Original file name: PowerMac-Up&Running