���������������������������[  Here are your words ]��������������������������
> You'd need to turn off 32-bit disk access in Windows. And it will work.
> (And what the hell does being a 386 have to do with it?)
>  ���������������������������[  This is my response ]�����������������������
> It has to do with DMA channel capability differences between the 386 and th
> 486's.. the 386's have 0,1,3 the 486's have 4,5 as well. This is why you
> succeed when turning 32bit disk access off, since DMA access was just
> disabled.
> However, when did you ever know a customer that wanted you to DISABLE a
> feature to correct a problem?
Not hardly.
DMAs above 3 are available on all AT class computers, this is any 286 or
above, with a 16 bit bus.
The 32bit diskaccess must be disabled, because ATAPI devices are accessed in
a way that is not compatible with the 32bit disk access driver (WDCTRL).  It
has nothing to do with EIDE or DMA channels.  It is a windows kludge to
 ���������������������������[  This is my response ]��������������������������

Ok.. I'll agree on that, however, there are TONS of 386 boards out with
defective DMA 4,5 combinations. Try getting one of em to work with a SB16 on
DMA 5 and see what I mean. If 'WDCTRL' is the cause, then wouldn't a newer 32
bit driver from the drive maker solve the problem?

     *****Merlin*****
     ================

        Excaliber BBS  �     VNET@1610025 VBBS Ver. 7.00.02
        �������������������������������������������������
         Supra 28.8V34 � (610)488-0299 USR VEverything(488-9194)