Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!ubc-cs!alberta!herald.usask.ca!weyr!f70.n140.z1.FIDONET.ORG!David.Plummer
From: David.Plummer@f70.n140.z1.FIDONET.ORG (David Plummer)
Newsgroups: comp.sys.amiga
Subject: Re: 3000 autobooting a 1096N
Message-ID: <756.26C795A3@weyr.FIDONET.ORG>
Date: 11 Aug 90 06:20:38 GMT
Sender: ufgate@weyr.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:140/70 - Double Check, Regina Sask
Lines: 26

Well, this autoboot/SeaGate problem has been addressed before, and I own
a couple of Seagates, so here's the problem:
 
- Seagates take about 14 days to boot from a cold boot.  The A2091
controller doesn't wait long enough, so from a cold boot it won't work.
You say autobooting doesn't work, but I bet it does from a warm boot,
right?
 
- The A2091 ROMS have a function for this (nicknamed Seagate Wait or
something like that).  On an A590, there's a DIP-switch on the back to
enable it, but currently no way to activate it on the 3000.  I have
the switch, but don't use it because it takes too damn long on warm
boots.  I just CTRL-A-A about 5 secs after I turn on my machine.  Since
the only time it's really critical for you (with the BBS) would be
from a power failure, I don't know what you'd want to do, but for me,
I just live with it.
 
Sorry, no solutions, just an explanation.  Didn't mean to get your
hopes up!


--  
David Plummer - via FidoNet node 1:140/22
UUCP: ...!alberta!dvinci!weyr!70!David.Plummer
Domain: David.Plummer@f70.n140.z1.FIDONET.ORG
Standard Disclaimers Apply...