From: drew@netcom.com (Drew Wade)
Subject: Re: Norton killed my Mac (part 2)
Date: Sat, 11 Apr 92 19:46:39 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: usa

the manual says that holding down command-option-shift-delete during boot
will cause it to ignore the internal HD.  assuming daniel is right about
the driver/partitioning stuff, maybe this would work...instead of unplugging
the power cable.  maybe, because it might still load the driver...manual
doesn't say.

easy to try...well, maybe not easy...but with the
help of 3 or 4 friends you should be able to press all those keys.  :)

-drew wade
drew@objy.com

In article <1992Apr10.182122.23150@xstor.com> daniels@xstor.com (Daniel A. Segel) writes:
>In article <92093.1836069001648@awiwuw11.wu-wien.ac.at>, 9001648@awiwuw11.wu-wien.ac.at writes:
>> 
>> Sorry to bother you again, but in my last article I forgot to mention
>> that my Mac won't boot from a floppy. All the people who responded
>> (thanks for your replies||) suggested to boot from a System disk, then
>> backup/repair/reformat the HD. Problem is, my Mac won't do anything
>> but chime and show the sad Mac icon (no startup procedures at all).
>> So the question still remains:
>> Is there a way to resurrect the Mac on my own? What would an Apple dealer
>> do in this case? Is it possible to attribute the error to a specific
>> piece of hardware (most probably the HD, so why not swap drives?).
>> The error code again: 0000000F
>>                       0000000A
>> It's a IIci w/Quantum 105LPS (once) running System 7.0.1
>> 
>> All the smart guys out there, could you please shed some light on me.
>> (I don't wanna give it up yet)          ======
>> 
>
>This is probably one of two things:
>
>1. a corrupted partition map
>2. a corrupted driver
>
>I've seen both happen plenty of times, and it almost always causes the
>symptoms you describe. If the partition map is corrupted, then the Mac
>may be loading the driver incorrectly at startup, and when it jumps to
>the driver code to let it initialize itself, it crashes because it's 
>hitting garbage instead of properly written driver code. There is no
>error handling at this point in the boot cycle, so you get the chimes or
>a sad Mac screen. If the partition map is ok, but the driver itself is
>corrupted the same thing can happen.
>
>How can you fix this? Well, to begin with you have to make sure the Mac
>doesn't try to load the driver at boot time. For an external HD just turn
>the power off until after you have booted the Mac from a floppy or another
>hard drive. For an internal HD you need to pull the power cable out of the
>drive, then boot up, then put the power cable back in. Yes, this is a little
>dangerous, but I've never actually seen any damage caused by doing this, and
>it may be the only way to save the drive.
>
>After booting, go into your formatting/partitioning software and let it scan
>the SCSI bus. Your hard drive should appear. If you can, look at the partition
>structure (not all formatting software lets you do this). If it gives you an
>indication that it is messed up, you may be out of luck unless there is an
>option to rebuild the partition map. If the partition map is OK try to
>reinstall the driver. If that works, try re-booting.
>
>Actually, even if the partition map is corrupted and you have no way to fix
>it, you can still reformat the drive and make it work again, but you would
>lose all your data.
>
>If you have any problems or specific questions about how to do all this,
>or you want to try to fix the partition map yourself (and you have the
>appropriate SCSI software), please e-mail me at daniels@xstor.com.
>
>Good luck!
>
>Daniel A. Segel
>Macintosh Customer Engineering
>Storage Dimensions, Inc.
>
>daniels@xstor.com
>


Xref: sparky comp.sys.mac.hardware:9015 comp.sys.mac.system:7023 comp.sys.mac.misc:8963