pcarew@stsusa.com (04/10/90)
Acording to 'Hard Drives International', there is a new SCSI controller available. This controller is the 'IN2000' and is made by 'Always Inc.'. The price for this controller ,acording to 'HDI', is $199 which is considerably cheaper than the 'Adaptek'. HDI says that they now reccomend the 'IN2000' because of a) Its price b) It is supposidly easer to use than the 'Adaptek' c) It is more compatible with other SCSI devices d) It is self configuring (whatever that means). Has anybody had any experience with this controller yet or is it too new? -- Paul Carew Tel w: (602)395 5203 Siemens Transmission Systems Inc., h: (602)375 8671 8620 N22nd Avenue, Email either: carew@paul.stsusa.com Phoenix Az 85022 or : "..!uunet!stsabq!pcarew"
neese@adaptex.UUCP (04/12/90)
> Acording to 'Hard Drives International', there is a new SCSI controller >available. This controller is the 'IN2000' and is made by 'Always Inc.'. >The price for this controller ,acording to 'HDI', is $199 which is >considerably cheaper than the 'Adaptek'. HDI says that they now reccomend the >'IN2000' because of > > a) Its price It is cheaper. It is also a PIO board, which means performance is somewhat limited to the speed of the CPU. Not true of the 154xA. > b) It is supposidly easer to use than the 'Adaptek' Don't know what that means. > c) It is more compatible with other SCSI devices Not true. > d) It is self configuring (whatever that means). So is the 154xA. > Has anybody had any experience with this controller yet or is it > too new? It is a decent PIO board, but if DOS is all you need, then the 152x is even cheaper and just as fast. The 152x will be in distribution very soon. Roy Neese Adaptec Central Field Applications Engineer UUCP @ {texbell,attctc}!cpe!adaptex!neese merch!adaptex!neese uunet!swbatl!texbell!merch!adaptex!neese
feustel@well.sf.ca.us (David Alan Feustel) (04/15/90)
I have the Adaptec 1542a SCSI controller and would like to use it with
OS/2 version 2.0. Unfortunately the Adaptec OS/2 device driver for v
1.1 doesn't quite work with v 2.0, apparently because of a missing
vdisk driver stuck in the v 2.0 disk01.sys which is needed during the
boot process. Does anyone know how to get around this problem?
--
Phone: (home) 219-482-9631
E-mail: feustel@well.sf.ca.us {ucbvax,apple,hplabs,pacbell}!well!feustel
USMAIL: Dave Feustel, 1930 Curdes Ave, Fort Wayne, IN 46805