Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!widener!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.hardware Subject: Re: Hardrives and the A3000 Message-ID: <20350@cbmvax.commodore.com> Date: 4 Apr 91 02:43:34 GMT References: <1991Mar22.160827.28210@msuinfo.cl.msu.edu> <20247@cbmvax.commodore.com> <1991Apr2.223300.19258@en.ecn.purdue.edu> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 27 In article <1991Apr2.223300.19258@en.ecn.purdue.edu> wwarner@en.ecn.purdue.edu (William A Warner) writes: >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 don't think the synchronous bit is actually read by the driver right now... The driver does support it if the other side initiates, and I could be wrong about the bit. > 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". -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Disclaimer: Nothing I say is anything other than my personal opinion. Thus spake the Master Ninjei: "To program a million-line operating system is easy, to change a man's temperament is more difficult." (From "The Zen of Programming") ;-)