🚀 go-pugleaf

In article <1434@mindlink.UUCP> a544@mindlink.UUCP (Rick McCormack) writes:
>Yeah but that wait only happens when I boot.  I really don't have to wait long
>during the rest of the day with those 4 megs ready to do my bidding.  If you
>schedule right, and start your machine before you get out your projects, you
>won't even notice that delay while those lovely 4 megs do their warm-up!

I believe that this thread was started by an SE (?) owner who added memory
to his system, and afterwards experienced longer cold startup times.

I have encountered the same wait that he expressed, but only when I upgraded
from 1M to 2.5M.  When I subsequently upgraded to 4M, I no longer experienced
this wait.  I would like to note, however, that the memory test seemed to run
just long enough for the SCSI bus to timeout.  I am using an internal 45M
Seagate 157N.  While the system was doing the memory test, the drive would
become ready.  For some reason, the SCSI bus check would have to try a second
time to find the drive.  I never, however, experienced a situation where this
would make my system un-bootable.

My guess is that whichever SCSI drive you are using is ready some given time
_before_ the memory test is done.  This, in turn, causes a time lapse between
the completion of the memory test and the recognition of your drive.

BTW, does anyone believe this could be a problem with the driver itself?  I have
also changed drivers since my upgrade to 4M... possibly this could have had
something to do with this.

Bill Taroli
WWTAROLI@RODAN.acs.syr.edu

-- 
*******************************************************************************
* Bill Taroli (WWTAROLI@RODAN.acs.syr.edu)    | "You can and must understand  *
* Syracuse University, Syracuse NY            | computers NOW!" -- Ted Nelson *
*******************************************************************************