Windows xp does not show slave, but CMOS does

Shinnen

Member
Hi,
I'm running Windows XP on an old Asus P4PE2-X. I have my hard drive and DVD on the primary cable. I have been trying to put another hard drive on the secondary cable but Windows refuses to recognize it. The CMOS sees it, but neither Windows explorer nor disk management list it, and Windows will not detect it. The drive works. I can boot into it from the boot menu.
Any suggestions are appreciated.
....... john
 

johnb35

Administrator
Staff member
You should have both HDD's on the primary cable and the DVD on the secondary cable. Not sure why your current setup doesn't show though.
 

Shinnen

Member
Hi John,
I tried that, but then the DVD doesn't show up in Windows, although it does show in the boot menu.
..... john
 

Shinnen

Member
Alright, here's the latest. At this point I have the Western Digital drive, in the master position on the primary cable and the DVD rom in the slave position. The Seagate drive is in the slave postion on the secondary cable. All drives are configured as C.S. If I boot into the Seagate drive (whether it's on the primary or secondary cable) I can see the WD drive. If I boot into the WD drive (whether it's on the primary or secondary cable) I cannot see the Seagate drive. The Seagate drive in 40 gig and the WD drive in 250 gig.
Is it possible that there is something on, or about, the WD drive that prevents the Seagate drive from showing up in Windows XP?
Thanks,
....... john
P.S. I can see all drives, no matter what configurations, in the bios
 

OmniDyne

Active Member
Your drive likely isn't being recognized by XP because you haven't initialized it.

Start Menu > right click My Computer > Manage > Storage > Disk Management

Find the newly added drive and initialize it.
 

strollin

Well-Known Member
If the OP can boot from that drive, then it is initialized. If OP initializes it now, all current info will be lost.

Since the drive is on the 2nd cable, it needs to be jumpered as master (there needs to be a master selected on EACH cable). If there is already an optical drive on that cable, make sure it is jumpered as slave and the hdd as master.
 

OmniDyne

Active Member
If the OP can boot from that drive, then it is initialized. If OP initializes it now, all current info will be lost.

Since the drive is on the 2nd cable, it needs to be jumpered as master (there needs to be a master selected on EACH cable). If there is already an optical drive on that cable, make sure it is jumpered as slave and the hdd as master.

The Seagate would still need to be initialized by the WD XP install before the UI will see it.

If OP initializes it now, all current info will be lost.

That's news to me. Never had that happen. I didn't say format.
 

Shinnen

Member
Hi again,
I have the WD disk and my DVD on the primary cable (master and slave postions respectively). I have the Seagate drive on the secondary cable (slave position). Everything is jumpered to cable select. I have tried jumping the drives using the traditional configurations, WD - master, DVD - slave, Seagate - slave, it doesn't make any difference. All of the drives have always been detected in the CMOS. By default the system boots into the WD drive, where neither Windows explorer, the device manager, nor disk management show the presence of the Seagate drive. I have also tried the Add Hardware option without luck, and I cannot see any signs of it in the Installed Hardware Windows.
On the other hand, if I go to the boot menu, and choose to boot into the Seagate drive, I can see the WD drive in Windows explorer. I have many drives here, and have tried others in place of the WD drive, and at no time has the second drive been invisible (to windows)........ this only happens when I boot into the WD drive. To me, it looks like there's something in, or about, the WD that prevents other drives from showing up when it is the boot medium.
Thank you all for your help.
......... john
 

strollin

Well-Known Member
The Seagate would still need to be initialized by the WD XP install before the UI will see it.



That's news to me. Never had that happen. I didn't say format.
What does initialize mean to you? Initialize means to partition and FORMAT a drive, either of which delete everything on the drive.
 

beers

Moderator
Staff member
What do you see in diskpart? You can run that from command prompt.

C:\Users\beers>diskpart

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 0 B *
Disk 1 Online 3726 GB 0 B *
 

Shinnen

Member
Hi,
If I use the Seagate drive as master I won't be able to use the WD drive which has my OS with all it's customizations.
Is there a consensus as to whether initializing the Seagate drive will wipe the OS?
Beers ..... what do you think dispart will do for me?
..... john
 

Shinnen

Member
OK. In my attempts to 'fix' the WD drive I have screwed up the OS. I'm currently running the Lazesoft patition recovery option. If that doesn't work I'll be 'initializing' it and cloning my backup drive onto it. At this point I'm intested in knowing why other drives are invisible to XP when I boot into the WD drive. I'll keep you posted.
Thank you all for your help.
... john
 

johnb35

Administrator
Staff member
It's most likely because of the master/slave/cable select settings. As long as there is data on this drive windows will see it as long as the settings are correct.
 

Shinnen

Member
Well, I've initiated the WD drive and cloned my backup onto it. At first XP recognized the old backup with the WD drive as master, but after a restart it did not. So, the same problem came back. Now I have shelved the WD drive and am using a couple of my old 40gig drives, which give me NO problems at all. I still think there's something not right with the WD drive.
...... john
 
Top