WD & IBM HD's won't live peacefully as slave and master on IDE 1.

[Glytzhkof]

It was said: "Let there be a new hard drive. With 2MB cache, 7200rpm and ATA 66." And there was a new hard drive, and there was much rejoicing... For a while...

To cut the ****: I am unable to get my old Western Digital Cavier 33100 and my new IBM Deskstar 22GXP (DJNA-370910) to live happily together on an IDE. The old WD is set up as slave, but is not detected even when I use the "slave present" setting on the IBM disk. If I put the WD as slave on the secondary IDE my BIOS still doesn't detect it, but Win98 does. I'm confused http://www.sysopt.com/forum/frown.gif.

[Bleeding Edge]

I remember back when, there were drives from different manufacturers where one brand had to be the master drive and would not work as a slave to the other. It was Maxtor and something else. A Fujitsu or Seagate...

You may have a different issue. The IBM's ATA66 function may be incompatible with your hardware and/or Bios. You may need to disable it with a utility available from their site as a download. (I assuming your using the onboard ATA33 controller.)

There's something else that needs verifying. Is a 80 wire ATA66 ribbon cable being used?

[This message has been edited by Bleeding Edge (edited 08-19-99).]

[Glytzhkof]

Ah! I've downloaded the program, and I'll test it later tonight. I'll let you know how it turns out. Thanks http://www.sysopt.com/forum/smile.gif.

[Glytzhkof]

I disabled ATA 66 (it was enabled), set the old drive as slave on the primary IDE and the result was the same: the BIOS doesn't recognize the drive (neither does windows). When using IBM's tool to disable ATA 66 the WD drive was visible however. Unfortunately there is no bios upgrade available for my mother board.

I can probably put the drive as slave on the secondary IDE, but that would create a strange system: IDE 1: IBM HD master, Matu****a CD-ROM slave. IDE 2: Mistumi CD-RW master, WD HD slave.

[Mitch]

Hi' Try no jumper on the WD..Hope this helps ..Mitch

[Glytzhkof]

Ouch! The problem was me and not the disks http://www.sysopt.com/forum/redface.gif. I'd been messing around in the BIOS and screwed up the CMOS settings. Setting everything back to auto solved the problem. Man, how stupid!

Thanks for the help guys.