omh@nancy.UUCP (04/22/87)
[Perhaps we should compile a compendium of hard disk fix techniques??]
Here's a fix which works for a particular problem. I can't guarantee it
will work, but it has worked on two occasions I know of. Use it when it
can't hurt to give it a try:
The symptoms:
Hard Disk goes through boot sequence, starts to open some windows (that
you left open last time), hits a particular window and bombs with an address
error. Usually caused by having some type of bad file on your disk. (causes
I know of: a Microsoft Word document bombed on *and* a trying to unpack
(using PackIt III) a bad file (became corrupted during a download).
Ok -> Let's fix it!
Tools: One disk with the latest system/Finder, a file utility DA which
allows you to delete files [or FEdit, etc.], and Disk First Aid. Set
DiskFirstAid to be your startup Application. (I keep a special disk around
just for this purpose.)
1) Rebuild the desktop by holding down Option-Command keys. Respond rebuild
to allow finder to try to patch it.
1a) Of course, if the above works, proceed no farther, but in the above two
cases, it didn't.
2) Boot from a known good disk containing the newest system and finder. It's
a good idea to use the "virgin" system that came with your mac, if it's the
latest version. The disk should have the application "Disk First Aid" from
Apple as the *startup* application. DFA is packaged with Apple HD20SCSIs and
can also be had from your Authorized Apple Dealer if you pester him/her
3) Allow DFA to repair the damaged disk. Wait, don't quit yet.
4) Use your file utility DA to delete the desktop file on the hard disk, along
with your suspected bad files. [if you don't delete the bad files, it will
happen again.] Alternatively, quit DFA, when you get the "minor errors"
dialog when it tries to mount your HD, choose "Cancel", then set your
startup to FEdit plus or anything that allows you to delete desktop & other
files, and delete them that way.
5) Voila. Good as new. (Be a good time to do that backup you've been putting
off, though).
I have seen this condition happen to both an Hyperdrive FX/20 and an
Apple HD 20 (non-SCSI), so the problem is a repeatable one which I suspect
many people will get.
Owen Hartnett
Brown University Computer Science
omh@cs.brown.edu.CSNET
omh%cs.brown.edu@relay.cs.net-relay.ARPA
{ihnp4,allegra}!brunix!omh