Newsgroups: comp.sys.amiga.hardware
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!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)
Subject: Re: Hardrives and the A3000
Message-ID: <1991Apr2.223300.19258@en.ecn.purdue.edu>
Organization: Purdue University Engineering Computer Network
References: <1991Mar22.160827.28210@msuinfo.cl.msu.edu> <20247@cbmvax.commodore.com>
Date: Tue, 2 Apr 91 22:33:00 GMT

In article <20247@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>>In article <1991Mar22.064048.12805@en.ecn.purdue.edu>, wwarner@en.ecn.purdue.edu (William A Warner) writes...
>
>>>One small thing that I have noticed is that different types of reboots affect
>>>the 2nd HD problem.  
>>>Here are my current symptoms again:
>>>  Cold boot-up:  No 2nd HD recognized.  Both HD's spinup no problem.
>>>   1st warm rb:     2nd HD recognized.
>>>   2nd  "   rb:  Not recognized  
>>>   3rd  "   rb:        "  "
>>>   4th  "   rb:  Not   "  "
>>>   etc .......etc.......etc   forever and forever.......AMEN.
>>> 
>>>Now does this sound like a sporatic occurence to you?
>
>	Hmmm.  Are you _certain_ that the reset line is connected to both
>drives, and that both drives are set up to reset properly?  (have you
>tested the reset connection with a VOM?)  It can be hard to tell, but does
>the second drive appear to reset when you reboot?  Drives/cables designed/
>modified for use with macs often ignore the reset signal.  I also advise
>getting the NVRAM program to set the "seagate" bit.  (It's called BattMem,
>or some such, and has been mentioned here before.  If you can't find it,
>I might be persuaded to whip a rough one up, but I know it's been done
>already.)
>
I have used the Battmem program to set the "Seagate bit" to 2 secs, but
this did not change the symptoms whatsoever. (other than add 4 secs to my
startup!)  I also changed the SCSI to synchronous.  I did this because I 
was told that both of my HDs support this.  Was this the right thing to 
do?  It did seem to speed up my drives though! 
  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.

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