Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!nstar!larry From: larry@nstar.rn.com (Larry Snyder) Newsgroups: comp.unix.sysv386 Subject: Re: AT&T SysV Rel 4.0 - SCSI Complaints Message-ID: <1991May10.194010.15408@nstar.rn.com> Date: 10 May 91 19:40:10 GMT References: <1991May10.134245.5524@ux1.cso.uiuc.edu> Organization: NSTAR, Indiana's BBS 219-289-0287/317-251-7391 Lines: 18 brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: >Well at a site I do some consulting for, we were really pissed at this >also. It seems that AT&T looks for the SCSI ident string on the drive, and >that is how it determines whether or not it is a supported device. This also >includes all SCSI tape drives too. As for the fix, you might as well forget >it. It was obviously hardcoded so f**king AT&T could sell more of their own >equipment. we had the same problem originally with Intel SVR4 2.0 now with Dell SVR4 we haven't had this problem -- -- Larry Snyder, NSTAR Public Access Unix 219-289-0287/317-251-7391 HST/PEP/V.32/v.32bis/v.42bis regional UUCP mapping coordinator {larry@nstar.rn.com, ..!uunet!nstar.rn.com!larry}