Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.hardware Subject: Re: Amiga 3000 Hard Drives Message-ID: <19961@cbmvax.commodore.com> Date: 18 Mar 91 23:24:25 GMT References: <27230@uflorida.cis.ufl.EDU> <1991Mar7.161536.16200@en.ecn.purdue.edu> <1991Mar7.191825.26824@javelin.es.com> <1991Mar7.205003.8951@en.ecn.purdue.edu> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 42 In article <1991Mar7.205003.8951@en.ecn.purdue.edu> wwarner@en.ecn.purdue.edu (William A Warner) writes: >In article <1991Mar7.191825.26824@javelin.es.com> blgardne@javelin.sim.es.com writes: >>[Second drive, which just happens to be a Seacrate, is not recognized by >>the A3000 at boot time.] >> >>The problem is most likely Seagate's LONG spinup time. You can work >>around that by getting hold of the program "BattMem" which will let you >>change the A3000 controller's timeout from the standard setting to the >>long "seagate" setting. > >Let me clarify something for a few people: > The A3000 2nd HD problem is NOT: > spinup time > hardware hookup Actually, it may be a combination of seagate spinup time and seagate taking the scsi select timout period to the limit (or beyond). Both problems should be fixed by the infamous "seagate" setting in BattMem. > I can't speak for the other people having 2nd HD problems, but I am also >having problems making the 1.3 side acknowledge the existence of the 2nd HD. >I have to do the same two warm reboots in order to get them recognized. >Then when they do show up on the workbench, they are not recognized as a >Dos disk! I went back to 2.0, ran HDtoolbox, and changed one of the partitions >on the 2nd HD to the old filesystem (non FFS). I then went back to 1.3, and >after 2nd warm reboot, still could not open that partition. ("Not a dos disk") >But, after formating that partition (in 1.3 "noffs") the partition was then >useable and could be opened. (now it is not fastfile!) ie. SLOWER! Check in HDToolBox that there is a fastfilesystem in the "Add/ Update Filesystems" area (advanced options). It should look something like "0x444f5301 202 21992 Fast File System". (The size and version may be slightly different. If it says ~12K, then it's the old 1.3 FFS. The 2.0 FFS should be on your install disk in the l: directory.) -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)