Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!giza.cis.ohio-state.edu!erd From: erd@giza.cis.ohio-state.edu (Ethan R Dicks) Newsgroups: comp.sys.amiga.tech Subject: Re: Apple SCSI not compatible with standard SCSI? Message-ID: <74147@tut.cis.ohio-state.edu> Date: 20 Nov 89 06:46:19 GMT References: <1410034@hpcvca.CV.HP.COM> <8608@cbmvax.UUCP> Sender: news@tut.cis.ohio-state.edu Reply-To: Ethan R Dicks Organization: Ohio State University Computer and Information Science Lines: 33 In article <8608@cbmvax.UUCP> steveb@cbmvax.UUCP (Steve Beats) writes: >In article <1410034@hpcvca.CV.HP.COM> charles@hpcvca.CV.HP.COM (Charles Brown) writes: >>[stuff deleted] >> [ more stuff deleted ] > However, SCSI drivers have to check 7 distinct >SCSI bus addresses to see if drives are hooked up (there is a way under >the new RDB scheme to shortcut this check, but that`s not important here). [ still more stuff deleted ] > > Steve So could Steve or someone else tell us the order that C= controllers use in querying the SCSI bus? Theoretically, you could set the naughty device toward the end of the chain so that several device numbers must time out before getting to the valid device, giving it time to pay attention... I.e. If the order is 0 - 7, and there is a 4 second timeout per device and a Seagate takes up to 12 seconds to pay attention to the bus after a reset, then the drive should be set to at least 3, giving the drive time to wait for the controller to timeout on 0, 1 and 2. Is this a valid workaround? -ethan -- Ethan R. Dicks | ###### This signifies that the poster is a member in Software Results Corp| ## good sitting of Inertia House: Bodies at rest. 940 Freeway Drive N. | ## Columbus OH 43229 | ###### "You get it, you're closer."