rcook@ncsa.uiuc.edu (Robert Cook) (05/03/91)
I'm having a problem with my (NEW) hard drive. When I first boot after being
down for more than about 6 hours, the drive hangs while loading the inits.
The select light stays on until I reset, then everything comes up fine.
At first I thought: ok, init conflict, because it seems to happen while loading
the same init everytime (by noticing which icon's are displayed and which ones
aren't). But since this only happens when the machine is "cold", I thought
maybe "stiction". But as someone pointed out to me, stiction went out with
disco, and since I just bought this drive 2 weeks ago this "shouldn't" be
the problem.
So, my question is: Can there be an init conflict only when a drive is cold
and resolve itself after a reset?
Since I can only play with the inits once a day (maybe twice if I stay up real
late), an init conflict may take days or even weeks to figure out.
Oh, btw, it seems to hang right after Norton directory assistance and before
easy acces and Norton filesaver.
Any help on this is greatly appreciated, and thanks in advance.
System: Classic w/ 4MB and Quantum Pro 105 (from APS)
various assortment of inits
--
-------------------------------------------------------------
You wont find any fancy .signature here
-------------------------------------------------------------
Robert Cook (rcook@ncsa.uiuc.edu)peter@suntan.viewlogic.com (Peter Colby) (05/09/91)
In article <1991May2.230817.6784@ncsa.uiuc.edu>, rcook@ncsa.uiuc.edu (Robert Cook) writes: |> I'm having a problem with my (NEW) hard drive. When I first boot after being |> down for more than about 6 hours, the drive hangs while loading the inits. |> The select light stays on until I reset, then everything comes up fine. |> At first I thought: ok, init conflict, because it seems to happen while loading |> the same init everytime (by noticing which icon's are displayed and which ones |> aren't). But since this only happens when the machine is "cold", I thought |> maybe "stiction". But as someone pointed out to me, stiction went out with |> disco, and since I just bought this drive 2 weeks ago this "shouldn't" be |> the problem. |> So, my question is: Can there be an init conflict only when a drive is cold |> and resolve itself after a reset? |> Robert Cook (rcook@ncsa.uiuc.edu) I have had the same type of problem... I would power up my mac+ and the boot sequence would follow through until just before the disks would mount on the desktop. The machine would then "freeze" with my hard drive sequencing "tick tick (pause) tick tick (pause) ... " forever. I would hard reset (you know, the programmer's switch) and the mac would reboot normally and come up to the finder with no problems. I removed one (or more) inits - I don't remember which ones or which ones I was using at the time - and the problem stopped. The point here is that yes, an init conflict or problem could cause a cold boot failure but not a warm boot failure. Peter C -- (O)(O)(O)(O)(O)(O)(O)(O)(O) (O)(O)(O)(O)(O)(O)(O)(O)(O) (O) !the doctor is out! (O) (0) peter@viewlogic.com (0) (O)(O)(O)(O)(O)(O)(O)(O)(O) (O)(O)(O)(O)(O)(O)(O)(O)(O)