Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!wwarner
From: wwarner@en.ecn.purdue.edu (William A Warner)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Hardrives and the A3000
Message-ID: <1991Apr4.194821.3115@en.ecn.purdue.edu>
Date: 4 Apr 91 19:48:21 GMT
References: <20247@cbmvax.commodore.com> <1991Apr2.223300.19258@en.ecn.purdue.edu> <20350@cbmvax.commodore.com>
Organization: Purdue University Engineering Computer Network
Lines: 24

In article <20350@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
 I wrote:
>>  I did find that changing the SCSI id# for the drives did make difference.
>>I still have not completely solved the problem yet, but I am able to cold-
>>boot the 3000 and have the 2nd HD recognized now.  The problem, every
>>other warm-reboot not recognizing the 2nd HD, still exists though.
>
>	It sounds very strongly like some wierd reset-behavior on the drive's
>part.  Putting the drive at a higher address (especially combined with the
>longer timeout) gives the drive longer to come up to "normal".

Like I said before, changing the timeout to 2 secs only made the startup
time increase by 2 secs for each HD attached.  This did NOT change my 
problematic symtoms AT ALL.  Now can you tell me what timing difference
there is between SCSI ID#s ?  How can I increase this time?  It is not
just a matter of increasing the timeout.  I think the increase in timeout
is only good for those drives that are a slow in spinning-up to speed,
like Seagates.


-- 
Art Warner
wwarner@en.ecn.purdue.edu
Amiga makes it happen.......IBM, Mac, Sun, and Next make it expensive!