Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!gatech!ncar!noao!arizona!arizona.edu!cerritos.edu!orion.oac.uci.edu!ucivax!ucla-cs!elroy.jpl.nasa.gov!sdd.hp.com!th ink.com!linus!agate!shelby!portia.stanford.edu!earthsea.stanford.edu!gyugyi From: gyugyi@earthsea.stanford.edu (Paul Gyugyi) Newsgroups: comp.windows.ms Subject: Message-ID: <1990Nov21.204930.13067@portia.Stanford.EDU> Date: 22 Nov 90 03:43:20 GMT References: <824@VAX1.CC.UAKRON.EDU> <430@nwnexus.WA.COM> Sender: news@portia.Stanford.EDU (USENET News System) Organization: AIR, Stanford University Lines: 23 GMT Message-ID: <1990Nov21.124320@earthsea.stanford.edu> Reply-To: gyugyi@earthsea.stanford.edu (Paul Gyugyi) Organization: Stanford University Subject: Re: SCSI drives with WIN3 Keywords: I have a computer with an 8 bit bus, and I i've used both the segate SCSI controller and the future domain controller, and I can't say I'd recommend either. The segate SCSI works fine if you only have one other MFM/RLL hard disk. Since I had two MFM disks, I had to get the future domain controller (the only other 8 bit controller I know) which has a driver that lets the SCSI disks run as drive e:. The problem is that the driver installs the SCSI disks as block devices, rather than installing the disks on the int13 chain. Since smartdrv and hyperdsk only cache int13 devices, my SCSI disk just doesn't get cached, which is really bad if you've got an 8 bit bus (I've got an Intel Inboard386/PC card). Overall, it looks like the Adaptec controller is going to be a standard. -- Paul Gyugyi gyugyi@earthsea.stanford.edu