Having Boot Issues Setting IDE as Slave.

I have an HD that I want to slave to my other HD which is running XP.  I have my XP HD set to Master and the other HD as Slave.  When I start the PC I get a Boot Disk error.  I go into BIOS and it sees my good XP HD as the primary master.  I'm able to slave other drives without issue.  Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try using the cable select option on both of the drives.  Then the hardware will automatically assign master and slave status based on which drive is hooked to the cable first.

Also, try making the slave a master and only hooking it up just to see if you get any errors.  This way if it doesn't work you will know that the drive has a problem.
Or, if you dont need the CDRom for a bit, just set it there as a master....

What kinds of Drives?

Some older (maybe currrent even)WD drives had a "Master", AND a "Master w/ Slave Present" jumper.....
vsllcAuthor Commented:
My master is a Seagate ST340810A and the slave is a WD1200.  When I just hook up the HD I want to slave with no jumpers set and the other HD unhooked I get the Boot Disk error.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

vsllcAuthor Commented:
OK.  The Seagate HD had a second configuration.  I had to add a second jumper to setup "Master with a Non-ATA Compatible Slave".  Unfortunately, I can't see anything on the slaved HD.  Any ideas?
Does it who up in Windows>Start>run>compmgmt.msc>Disk Management?
vsllcAuthor Commented:
No.  Just my C and two CD-ROMs.  Nothing in BIOS either.  The drive was not working in an old PC so I was hoping to slave and pull the data off.
Sounds like you have a bad drive.  One more thing you might try though is to go to your local computer store and buy a dongle that will allow you to hook up your hard drive directly to a usb port.
vsllcAuthor Commented:
Got that.  Recognizes the USB device but does not see the HD to view the files.
Yeah, sounds like a bad hard drive then :(
vsllcAuthor Commented:
Anyway to retrieve the data short of sending it off for $$$$ to some specialty shop?
Well, you could learn how to do what the specialty shop guys do for yourself... but that's not really a better solution.  As Forest Gump once said: shit happens :-\
dbruntonQuid, Me Anxius Sum?  Illegitimi non carborundum.Commented:
You may wish to see what this person did


Essentially he obtained a similar logic board and swapped it in and tried that.  Try eBay for logic boards.
Hey, the master needs to be on the end of the IDE cable, the slave needs to be on the middle connector.

Set them both to cs or cable select, or if they don't identify that way, turn down the ATA level to ata-33 as the older drive won't identify at ata-100.

You MUST set a jumper on the slave to CS or slave.
If you choose SLAVE on the slave drive, you must select master on the master drive.

Alternatively, you can just get an external USB to IDE adaptor for about 15.00 including shipping from your local shop or ebay.

You most likely Do Not need professional help with this type of data retrieval.

If you cannot get your drive to identify with this information above, attach the slave drive on the middle connector right below the cd-rom. (or disconnect the cdrom.)

The problem with not jumpering the secondary drive is that both want to become master and will argue, this confuses the IDE controller.
vsllcAuthor Commented:
dbrunton - Nice link!  I've swapped the logic board with a known working drive that I successfully slaved.  The bad HD is spinning, there is no unusual knocking, grinding or other troublesome sounds.  However the system still does not see the drive.

coredatarecovery - I can successfully slave (I say successful because I don't get errors on boot anymore) but the drive is still unrecognizable to the system.  See my response to dbrunton.  I also tried the USB and CD hookup as you suggested.  No luck with either.  Of course I don't think I have the USB method working right because I can't get any disk to recognize with it.  Even ones I can slave and see the data files.
If the circuit board does not match exactly (Model and firmware) the drive may not identify.
vsllcAuthor Commented:
Visually, they are the same and the numbers I can find on them match but I could be missing some other identifiers or stickers.  I tried Western Digitals site but kept getting 0 results on the search.  Here's the HD model #'s:

Bad - WD1200BB-22CAA0
Good - WD400BB-00CAA0
you can't use the circuit board from a 40 gig drive to run the 120 gig drive.
and the firmware is different.
(part after the dash.)


is a circuit board for you that should work.

Hope this helps,
Chuck House
Core Data Recovery

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vsllcAuthor Commented:
Thanks.  I'll keep the link in case I can't find a replacement locally.  I appreciate all the help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.