Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!iphase!steve From: steve@iphase.UUCP (Steve Kappes PER) Newsgroups: comp.sys.amiga Subject: Re: 3000 autobooting a 1096N Message-ID: <232@iphase.UUCP> Date: 22 Aug 90 16:23:37 GMT References: <760.26C795C2@weyr.FIDONET.ORG> Reply-To: steve@iphase.UUCP (Steve Kappes PER) Organization: Interphase Corp. Dallas TX Lines: 18 In article rps2@amoeba2.UUCP (Rick Stevens) writes: >In article <760.26C795C2@weyr.FIDONET.ORG> Randy.Coghill@f70.n140.z1.FIDONET.ORG (Randy Coghill) writes: >>Dave what I would like is to find out if Commodore is going to fix the >>problem (as far as I know there scsi routines are the only ones that >First off, it's not a Commodore glitch, it's Seagate's. Seagate drives >do not fully conform to the SCSI specification. If they did, the drives >would show up as "not ready" on the bus after the specified bus delay >time, and the 3000 would wait for them to go ready. > Rick Stevens, Small Scale Systems of Southern California The Seagates are not in violation of the spec. The spec recommends a time of 10 seconds but devices are not required to respond to selection in that time. This problem is just one of those SCSI things system people have to watch out for. For instance, what synchronous transfer speed does the 3000 negotiate with a wren V, VI, or VII? Steve Kappes Interphase Corp. !uunet!iphase!steve