Xref: utzoo comp.unix.aux:562 comp.sys.mac:24608 comp.periphs:1429 Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!ucsd!rutgers!apple!xanadu!michael From: michael@xanadu.COM (Michael McClary) Newsgroups: comp.unix.aux,comp.sys.mac,comp.periphs Subject: Re: A/UX generic SCSI driver and Syquest 44Mb removable drives Summary: Disk firmware is suspect. Keywords: A/UX SCSI driver Syquest Message-ID: Date: 3 Jan 89 06:35:29 GMT References: <4370@portia.stanford.edu> <40443764.1285f@maize.engin.umich.edu> Reply-To: michael@xanadu.UUCP (Michael McClary) Organization: Xanadu Operating Company, Palo Alto, CA Lines: 33 In article <4370@Portia.Stanford.EDU>, name@Portia.Stanford.EDU (tony cooper) writes: > But the generic SCSI driver that A/UX uses does not work with the Syquest. > It produces the error "More data than SCSI device requested" when trying > to read or write to the drive. > > Thanks, > Tony Cooper > > name@portia.stanford.EDU Are you hanging the Syquest and another drive on the SCSI bus at the same time? I saw that same error message under 1.0 when I mixed a Jasmine (300 MB Wren) with a Quantum (80 MB 3-1/2"). (I'm not sure if the non-disclosure agreement covers posting the symptoms under 1.1 Beta 3.) Turned out the Quantum firmware (6.8 00) had a bug. When disconnecting, it neglected to tell the initiator to save pointers. Come the reconnect, blooie! Solution was to get new firmware from Quantum. ((7.9 00) fixes that bug, but poses another: It runs a 20+ second self-test. Mix it with a drive that wakes up faster and the finder decides it isn't there.) Suggestion for Apple: Think seriously about having the SCSI driver save the pointers even if the drive doesn't ask you to. Sure, it means a little more code, to support somebody else's bug. But the bug doesn't manefest under finder, so when it shows up under A/UX it looks like YOUR fault, not the drive's. - - - - - - - - - - - michael@xanadu.com (Haveta move my .signature one of these daze...) - - - - - - - - - - -