Xref: utzoo comp.os.os2.misc:1101 comp.periphs.scsi:2456
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!haven.umd.edu!umd5!bchin
From: bchin@umd5.umd.edu (Bill Chin)
Newsgroups: comp.os.os2.misc,comp.periphs.scsi
Subject: Re: Adaptec SCSI and OS/2
Message-ID: <8485@umd5.umd.edu>
Date: 26 Apr 91 02:43:08 GMT
References: <8472@umd5.umd.edu> <1991Apr25.033305.10133@netcom.COM>
Reply-To: bchin@umd5.umd.edu (Bill Chin)
Organization: University of Maryland, College Park
Lines: 28

In article <1991Apr25.033305.10133@netcom.COM> feustel@netcom.COM (David Feustel) writes:
>I strongly recommend forgetting SCSI if you want to run OS/2.
>Think IDE drives instead.

Wait a minute here...  There are very strong reasons to go to SCSI...
IBM itself has gone from ESDI to SCSI (their new 80s, 90s, & 95s),
as well as a large part of the computing world (Sun, Dec, Apple, NeXT).
Beyond the technical and user advantages of using SCSI over IDE,
such as daisy chaining 7 devices, high speed, flexibility of 
using the bus for more than just hard drives, and more,
SCSI is a major standard.  For OS/2 to ignore it is to shoot
itself in its foot.  SCSI has *major* advantages in multi-platform
environments, or where a number of devices need to be hooked up
to a machine. 

Anyways, it seems that the reason Adaptec hasn't updated its
drivers is because its waiting for Microsoft to finalize some
things.  I believe that they didn't just write a driver for the
Adaptec line, but implemented the ASPI (Advanced SCSI Programming
Interface), thus causing the delays.  So for now, I'm using
1.1 drivers w/ FAT partitions.  And I had just gotten used
to HPFS too.  :-)

--
Bill Chin			internet:bchin@umd5.umd.edu
PC/IP, Computer Science Center	NeXTmail:bchin@is-next.umd.edu
U-Maryland, College Park        *Standard Disclaimers Apply*