🚀 go-pugleaf

I had this problem happen on a 5400 on friday it froze when I was compiling
a C++ program and on the warm boot I got blinking ? then happy mac then
blinking ? updating the drivers and using nortons did nothing. try
reinstalling the finder and the system. start from the cd drag the finder
and system files but not the system folder to the trash. start the installer
then go through the steps when it comes time to choose the install choices
(easy,custom) use custom then check system software fro this macintosh. make
sure every thing else under that is un checked. then click on customize then
uncheck everything that is there except 7.6.1 update (unless it is 8.0) and
make sure everything below that is unchecked. some stuff is hidden. you
should let it install then on restart everything should be fine.
----------
>From: maedward@orednet.org (Mark Edwards)
In article <1da8gb6.ydaec0irbyp0N@a101.son144.microweb.net>,
maedward@orednet.org (Mark Edwards) wrote:


>I am suffering from the bug that is reported in several places on the
>Apple Support web site currently.
>
>Apparently, the drivers in Drive Setup that come with OS 7.6 through 8.0
>cause macs with IDE drives (such as the Performa 6360 with 1.2 gig IDE
>that I am dealing with) to become unable to mount the disk out of the
>blue.  The problem can be fixed by installing the driver from Drive
>Setup 1.3.1, or so the site claims.
>
>Unfortunately, by the time I found this out, I had already butchered my
>drive using Norton 3.5.1.  I was able to get the drive to mount with
>repeated Disk Doctor passes, but the directory shows only garbage (i.e.
>the desktop file has become all screwed up).  Rebuilding does nothing,
>and both Disk First Aid and Norton say the disk is fine now.
>
>I am attempting to salvage some of the files on the drive using Norton
>Unerase.  Directory scan brings up nothing.  The only way I am able to
>find files is by using File Type scan or Text scan.  File Type brings up
>a ton of stuff -- evidence that everything is pretty much still on there
>somewhere -- but it only brings up files that it recognizes, and
>resource files (and plenty of them!)
>
>Can anyone suggest a course of action?  Am I pretty much stuck with the
>above methods?  Is there any hope of salvaging a map of the files that
>on the drive in limbo?
>
>Please help!  Please!  Thank you...
>
>-Mark Edwards
>maedward@orednet.org