From: moncrg@aix02.ecs.rpi.edu (Gregory Donald Moncreaff)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: microsoft fixes/updates -> compuserve vs ftp
Date: 13 Aug 92 12:56:23 GMT
Organization: Rensselaer Polytechnic Institute, Troy, NY

Are there drivers updates on any of the compuserve
libraries that have take case of any of the problems
listed on the 0692 hardware compatability list?

specifically for the tmc-16x0 future domain controllers?

from the 0692 hardware compatability list...

SCSI(R)

Adaptec
AHA-1540b
AHA-1542b
AHA-1640
AHA-1740

Future Domain
TMC-845
TMC-850, TMC-850M(ER)
MCS-700 (7)
TMC-1660 (8) 
TMC-1680 (9)
TMC-7000EX

IBM
IBM SCSI Host Adapter (10)

Maynard
16 Bit SCSI Adapter (11)

NCR
NCR 53C700 

(7)  A driver that supports both Setup and File I/O for the Future
Domain MCS-700, and TMC-16X0 series controllers will be posted to
CompuServe in the WINNT forum, Lib 2 "Fixes and Updates".
(8)  Same as Footnote 7
(9)  Same as Footnote 7
(10) Earlier versions of this controller have proven to have problems
with various CD-Rom drives.  The Chinon CDX-431 and NEC Intersect
CDR-73 are known to work with this version of controller.
(11) The Maynard SCSI Adapter can be used as a general purpose SCSI
controller for all tasks but graphical setup.

... without eisa or mca the AHA-1[67]40, TMC-7000ex, MCS-700
and presuably the IBM adapters are useless. the AHA-154x
series don't work very well (see below) and have horror
stories about them screwing up sound cards, possibly due
to the fact that they are bus-mastering controllers. the
TMC-8xx contollers are 8bit cards and thus are probably
nightmares to configure IRQ wise. the only item without a flag
againsdt it it the ncr. is that a contoller or a chipset?
i hear that corelscsi uses an ncr chipset, is it the same?

************************************************************************

Adaptec AHA 1542B Driver Can Cause Fatal System Error:

Summary:
There is a known problem with the Adaptec AHA-1542B driver which 
causes fatal system errors under some circumstances.

More Info:
The problem is triggered by simultaneous I/O with the floppy and the hard 
disk.  This will be corrected in the next release.  To avoid this you may 
want to use an alternative floppy controller and disable he one on the 
Adaptec.

************************************************************************

*** Fatal System Error:  0x00000069
*** Phase 1 I/O initialization failed.

************************************************************************

Error  0x00000069

This is a phase one initialization error, which happens when Windows NT 
tries to talk with the HD controller.  It can be caused by any number of 
things.  Things to try:

* If the card allows, slow down the DMA transfer rate.

* Make sure both ends of the SCSI bus are terminated.

* Make sure there are no IRQ, or memory address conflicts.

* Make sure you're aren't using a faulty or un-supported driver i.e. the FD 
1680 SCSI controller is supported, but there is a problem with that driver 
which will be fixed and posted on WinNT, Lib 2.
 

************************************************************************

btw, if you managed to make it this far, the contoller i
am currently using is a wd7000fast, which uses a
wd33c93a protocol chip. there does seem to be a driver,
/i386/wd33c93.sys on the cd-rom but i still get
the 0x0..069 error when starting up NT right
after it loads all the scsi drivers. the driver
probably isn't mature yet...

(i wish IDE had matured 3 years earlier so i would
never have had to make contact with the hellish
world of scsi)
Newsgroups: comp.os.ms-windows.programmer.win32