P
psych0surfr
Please help!!!
After repairing my system and reinstalling WinXP, it boots and I can
login, but the drive is on d:. There is no c: in the system. There are
no other drives or partitions (except CD burner on 2nd IDE as e. The
desktop shortcuts also refer to d: paths. But very little of the
software actually runs.
How do I move the drive back to c:?
Once it's there, do I reinstall XP with the repair option again to fix
the paths?
Background info:
WinXP is loaded on a single drive using a single, full partition as c:
(I'll call this drive1). The system became flaky - it would reset itself
randomly. It seemed to happen when drive1 would do a recalibrate, so I
installed a new drive (drive2) and copied drive1 to it. Near the end,
but before it finished copying (I think) the system reset itself. Then
disk1 wouldn't boot. I removed and swapped things around to isolate the
problem until I finally found that it was the CPU overheating. I
replaced the CPU, put an old 5GB drive (drive3) in, reformatted and
installed a clean copy of WinXP. I used that to put drive1 in as a slave
on d:. I could see that most of the files were there, so I put drive1
back as master and removed drive3. Then I reinstalled WinXP using the
"repair existing" option (not Windows Recovery console). I don't think I
tried to repair or reinstall XP while drive1 was set up as a slave, but
at this point I can't think of any reason why this would have happened
except that.
TIA,
-Roy
After repairing my system and reinstalling WinXP, it boots and I can
login, but the drive is on d:. There is no c: in the system. There are
no other drives or partitions (except CD burner on 2nd IDE as e. The
desktop shortcuts also refer to d: paths. But very little of the
software actually runs.
How do I move the drive back to c:?
Once it's there, do I reinstall XP with the repair option again to fix
the paths?
Background info:
WinXP is loaded on a single drive using a single, full partition as c:
(I'll call this drive1). The system became flaky - it would reset itself
randomly. It seemed to happen when drive1 would do a recalibrate, so I
installed a new drive (drive2) and copied drive1 to it. Near the end,
but before it finished copying (I think) the system reset itself. Then
disk1 wouldn't boot. I removed and swapped things around to isolate the
problem until I finally found that it was the CPU overheating. I
replaced the CPU, put an old 5GB drive (drive3) in, reformatted and
installed a clean copy of WinXP. I used that to put drive1 in as a slave
on d:. I could see that most of the files were there, so I put drive1
back as master and removed drive3. Then I reinstalled WinXP using the
"repair existing" option (not Windows Recovery console). I don't think I
tried to repair or reinstall XP while drive1 was set up as a slave, but
at this point I can't think of any reason why this would have happened
except that.
TIA,
-Roy