XP does not see an installed hard drive, the BIOS does.

I have a Maxtor 200Gig with a 120Gig partition and an 80Gig partition. I installed a Seagate 160Gig as a slave. The BIOS sees the Segate but Windows XP SP1 Pro does not see it.

Does anybody have any solutions?

Who is Participating?
tosh9iiiConnect With a Mentor Commented:
It sounds like you did everything right, maybe you need to replace the ata cord or the drive is defective.

I'm not sure you're going to like the next suggestion, but when you run into a brick wall, you should be willing to try just about anything.

Set the Seagate 160gb as the Master "WITHOUT a slave", be sure to set the jumpers correctly.  Then pop in you Windows XP CD and go thru the typical installation process, but not all of it.  Basically, you'll come upon a screen where you choose which partition to install windows.  From there, create the partitions that you want.  After you create the partitions, STOP.  Just turn off the computer and set the Maxtor up as Master and Seagate as Slave.
right click my computer -> manage -> disk management -> and initiale,format it or something else
awilson11Author Commented:
It doesn't show up in disk management.
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

Are the jumpers configured correctly
An MSKB article to look at:

Hard Disk Does Not Appear in My Computer or in Windows Explorer

You said that it doesn't show up in disk management, but can you access it by using Start Menu>Run>cmd> then typing the drive letter (i.e. D:)?

awilson11Author Commented:
LeeTutor, the article referes to Roxio Goback, this is a brand new disk.

Also I have tried setting the jumpers using Cable select on both, then setting the 200 as Master and the 160 as slave. In each case the BIOS detects the drives but XP does not, the second (Segate 160) is not listed in the Device Manager. I tried Add Hardware but it isn't detected.

tosh9ii - neither of the articles provides any insight.

More info would help narrow the problem.  Here's an example of a VIA chipset not recognizing 160mb SATA drive due supposedly bad code.  If you''ll post chipset and/or mb model and drive model, might be able to narrow down further.  There may also be a firmware update for the drive as well as BIOS updates and chipset updates.


I'm agreeing with timothyfryer, if you have a 200gig being seen just fine but a 160 that isn't, you are most likely looking at a issue with the firmware on your motherboard. Even though it sees both drives there's a good chance that it's still missing something. I had the same problem with my Seagate 160 and not with my 180. Updated my firmware and never had a problem since.
Following is excerpt from the user manual for killdisk available from the link above.  They say its safe.  LucF, the guy who recommended it as the accepted answer in the
EE link above, is pretty sharp.  I doubt he would recommmend it if it were dangerous or a piece of junk.  If it were me, I would go with this one.

4.7. Will I be able to use my Hard Disk Drive after Active@ KillDisk erase operation?
To be able to use HDD again you need to:

repartition HDD using standard utility like FDISK

reformat partitions using standard utility like FORMAT

reinstall Operating System using bootable CD-ROM or floppy

awilson11Author Commented:

I am not sure if what you suggested, partially installing Windows XP on the new drive did the trick as at the same time I also replaced the ribbon cable with a brand new cable at the same time as doing what you suggested. But now it is working, so I will give you the points.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.