SCO 2 Harddisk controllers

[Mark J. DeFilippis]

I want to thank Dave Dillabough for his article, however I lost the last
two days news due to a blunder on my part in doing the installation.
It is nice that MSDOS looks at the drives as 1 and 2, and Xenix 0 and 1.
What disk you want to format? ...1.... ARGGGGGG!  Goodbye spool partition
and root system!  Now that I broadcast my stupidity, on with the problem:

I tried to get the two controllers working, and I did, somewhat.
The two controllers are a WD-1006-WAH and a WD-1006VMM1.  The 10006VMM1
is the one I am running int. 14, standard address, and works fine.
The WD-1006WAH is the one I did the mod on for int. 14, and address change
0x170.  On boot the second controller shows up at its proper address,
and mounts after it does a seekout.  The drives are all Miniscribe 6085
72 meg, 28 ms drives.  The problem occurs sporatically.  If I access the
drive it may/maynot be ready.  It does that seekout and then reads the data
fine.

Western Digitals Guru's said it may be the Miniscribe drive going to sleep
when it is not selected, and to change the jumpers to disable autopark.
The only jumber on the drive is drive select, and besides the heads are not
parking.  SCO says, hum.. sounds like a hardware problem, sorry.
According to WD, neither of the boards have ROM BIOS. They did say that the
older WD-1006 may be giving me trouble, but all this info is pretty sketchy.

I ordered an Adaptec ACB2310 whih allows jumper controlled interrupt and
address modifications to replace the 1006-WAH in an attempt to rectify the
problem, but I am just stabbing in the dark.

Any help out there, please?

-- 
Adelphi University, Garden City, NY 11530                   (516) 663-1170
Department of Mathematics and Computer Science
                                 markd at adelphi.UUCP  or  mark at promark.UUCP
                      UUCP:      ...philabs!sbcs!bnlux0!adelphi!markd