Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!virtech!cpcahil From: cpcahil@virtech.uucp (Conor P. Cahill) Newsgroups: comp.unix.sysv386 Subject: Re: AT&T SysV Rel 4.0 - SCSI Complaints Message-ID: <1991May11.180401.28483@virtech.uucp> Date: 11 May 91 18:04:01 GMT References: <1991May10.134245.5524@ux1.cso.uiuc.edu> Organization: Virtual Technologies Inc. Lines: 21 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 You can fix this several ways. 1. use a binary editor to replace the AT&T strings on the boot disketttes so that it recognizes your devices. 2. Get the system loaded on a supported device and then change the SCSI id tables in /etc/conf/pack.d/{scsi driver directories}. There are two directories (one for tapes and one for disks). -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc. uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170