OK, here's the specs, to get that out of the way...
P166MMX (incidentally running at 187, but prob independant)
ASUS TX97X / 64MB SDRAM
Matrox Mystique 220 PCI
Monster 3D V1
IDE Current setup:
Primary Master -- IBM 8.4GB DHEA8451 DeskStar
Primary Slave -- None
Secondary Master -- Samsung 1231 12x ATAPI CD
Secondary Slave -- None
Primary Master -- Seagate ST52520 2.5GB EIDE (non UDMA)
Primary Slave -- none
Secondary Master -- Samsung 12x
Secondary Slave -- none
OK, I ran this box with the Seagate 2.5GB for over a year with no problems, until I hit the need for more space (moving into an open 10bT network from a modem can do that to you... ;-). I researched for awhile and decided on the excellent IBM DeskStar 8.4GB drive. I was aware that my TX97-X had a detection problem with the 8451, but a BIOS flash fixed that. Anyway, I DriveCopied all my data over and got the 8.4 up and running beautifully as my sys drive, complete with UDMA enabled in Win95.
When I tried to add back my 2.5GB drive, however, Win95 choked on it. Now, regardless of where I put the old drive, Win95 forces that channel into compatability mode. That is, if I put the Seagate on Primary Slave (ideal), the primary controller listing in Device Manager shows an unspecified conflict and *both* drives on that channel run in Compatability mode. The same effect occurs whichever master/slave position I put the drive in on the Secondary channel -- both drives run in compatability mode.
*Anyone* know how to work around this?? I've been through ASUS, Seagate, and Microsoft tech support, as well as several forums and Usenet groups. This really irks me since I have years of tech support experience and I can't even get my own system to work right. Grr.
Please respond on here or email me at firstname.lastname@example.org