XP Does not recognize Slaved Hard Drive

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just put a new hard drive and reinstalled XP (upgrade through ME) on my
system, I then reinstalled the old drive as a slave to recover some data and
XP doesn't show it. I checked and the BIOS found the drive as a slave
without any problems. I tried looking for it in disk manager but it wasn't
there. Both drives are FAT32.

Thanks
 
Have you tried to attach the drive on the second IDE interface as a Master or
Slave?

It is unusual that BIOS would identify the device, but that Disk Manager
would not. It may be related to the Master Boot Record and having two
distinct XP systems.

The use of the second IDE interface [if only temporarily] may get around
these issues.

Once you have copied your data across, then try to format the disk drive.
It may then be happy as a slave to the new master Disk.
 
I can try that.

Thanks

BAR said:
Have you tried to attach the drive on the second IDE interface as a Master or
Slave?

It is unusual that BIOS would identify the device, but that Disk Manager
would not. It may be related to the Master Boot Record and having two
distinct XP systems.

The use of the second IDE interface [if only temporarily] may get around
these issues.

Once you have copied your data across, then try to format the disk drive.
It may then be happy as a slave to the new master Disk.

HAZMINK said:
I just put a new hard drive and reinstalled XP (upgrade through ME) on my
system, I then reinstalled the old drive as a slave to recover some data and
XP doesn't show it. I checked and the BIOS found the drive as a slave
without any problems. I tried looking for it in disk manager but it wasn't
there. Both drives are FAT32.

Thanks
Click to expand...
Click to expand...
 
BAR said:
Have you tried to attach the drive on the second IDE interface as a
Master or
Slave?

It is unusual that BIOS would identify the device, but that Disk
Manager
would not. It may be related to the Master Boot Record and having
two
distinct XP systems.

The use of the second IDE interface [if only temporarily] may get
around
these issues.

Once you have copied your data across, then try to format the disk
drive.
It may then be happy as a slave to the new master Disk.

:
Click to expand...

You also have to pay attention to which connector the primary and
which the secondary is connected to on ATA100 and ATA133 cables.
 
In the BIOS they are listed as master (PM) and slave (PS) so it seems that
they are being correctly identified. I loaded the OS with only the new drive
installed and then added the second drive once the installation was finished
(wanted to make sure not to load the wrong drive).

Thanks

Slippery_one said:
BAR said:
Have you tried to attach the drive on the second IDE interface as a
Master or
Slave?

It is unusual that BIOS would identify the device, but that Disk
Manager
would not. It may be related to the Master Boot Record and having
two
distinct XP systems.

The use of the second IDE interface [if only temporarily] may get
around
these issues.

Once you have copied your data across, then try to format the disk
drive.
It may then be happy as a slave to the new master Disk.

:
Click to expand...

You also have to pay attention to which connector the primary and
which the secondary is connected to on ATA100 and ATA133 cables.
Click to expand...
 
Back
Top