Path: utzoo!attcan!uunet!munnari.oz.au!brolga!bunyip.cc.uq.oz.au!iceman!chma
From: chma@iceman.jcu.oz (Michael Antolovich)
Newsgroups: comp.sys.mac.hardware
Subject: Re: Help !! SE 30 dead (Hard drive ?)
Keywords: Gulp, wimper, sympathy ?
Message-ID: <1209@iceman.jcu.oz>
Date: 6 Nov 90 09:12:56 GMT
References: <1207@iceman.jcu.oz>
Reply-To: chma@iceman.UUCP (Michael Antolovich)
Organization: James Cook University, Qld
Lines: 34

In article <1207@iceman.jcu.oz> chma@iceman.jcu.oz (Michael Antolovich) writes:
>Well,
>     The story goes like this (it's long so bear with me)

  Lots of stuff deleted

>	Michael.
>PS mail to chma@groper.jcu.edu.au gets to me a little faster than
>           chma@iceman.jcu.edu.au (I don't know why, it just does.)
>

	Well, here I am typing on my disembowelled Mac, the hard drive
is sitting on the edge of my desk, wires hanging out everywhere (very
interesting!).  What I ended up doing was disconnecting the power to the drive
and booting off a floppy.  Carefully I reconnected the power to the drive,
and Silverling found the drive.  Quiting the application, the drive appeared on
the desk-top and I could switch launch to it. Rebooting still gave Sad Mac
sounds and code.  So I repeated the disconnect and live reconnect and
I then installed a Silverlining driver, using the Standard Mac "Handshake"
SCSI Read/write loops.  (I don't know what it means, but "blind" loops keep
failing now ie they didn't before ! Any ideas ?)
        This didn't help much till I ran Disk First Aid v1.4.3 on the drive.
It found an error, I clicked Repair and now everything is well again !  As
a test I tried reinstalling the Rodime driver but I get back the terrible
hardware errors (I guess Rodime defaults to "Blind" loops ?).  So I'm back
to the Silverlining Driver.
	Now the big question, will this last (I have nothing to lose, and I
didn't have to fork out $80 per hour for a tech) ?  I looked at SCSI loops
before these troubles and everything worked well, suddenly they don't.
Should I back everything up (I will anyway!) and do a full Reinitialisation ?
Should this fix the apparent hardware problem or will I be wasting time ?
Will things get worse (please say no :-) ? Am I as lucky as I think I am ?
			Thanks to everyone that will try and help me,
			Michael