S
smcroy
I have a computer I'm upgrading with a new motherboard and
120G WD hard drive. The old system was running ME with a
2+ yr old 40G WD hard drive as the master and only hard
drive. I want that 40G drive to become my slave drive on
the new system. I've installed it with the proper jumper
settings (master on 120G, slave on 40G) and both on the
same IDE channel. The bios recognizes the drive, and so
does Windows Disk Management in the new XP installation,
but it does not assign a drive letter to it. In Disk
Management, the disk shows as Healthy (Active) with a
FAT32 Basic Partition, but when I try to assign a letter
by right-clicking on the drive, every choice is gray'ed
out except "Delete Partition". Capacity shows 37.26 GB,
with 17.40 GB free. (As expected, the master C drive shows
NTFS, 111.78 GB capacity, Healthy (System)). I want the
40G drive to be a slave drive so I can move files from my
old installation to the new one. I've looked through the
entire Knowledge Base of both Microsoft and Western
Digital, but found nothing applicable. Western Digital
support calls this a Windows issue. Any ideas?
120G WD hard drive. The old system was running ME with a
2+ yr old 40G WD hard drive as the master and only hard
drive. I want that 40G drive to become my slave drive on
the new system. I've installed it with the proper jumper
settings (master on 120G, slave on 40G) and both on the
same IDE channel. The bios recognizes the drive, and so
does Windows Disk Management in the new XP installation,
but it does not assign a drive letter to it. In Disk
Management, the disk shows as Healthy (Active) with a
FAT32 Basic Partition, but when I try to assign a letter
by right-clicking on the drive, every choice is gray'ed
out except "Delete Partition". Capacity shows 37.26 GB,
with 17.40 GB free. (As expected, the master C drive shows
NTFS, 111.78 GB capacity, Healthy (System)). I want the
40G drive to be a slave drive so I can move files from my
old installation to the new one. I've looked through the
entire Knowledge Base of both Microsoft and Western
Digital, but found nothing applicable. Western Digital
support calls this a Windows issue. Any ideas?