Sign in with
Sign up | Sign in
Your question

Help - Failing C: Drive, how to I transfer OS to new hard ..

Last response: in Windows XP
Share
August 26, 2005 5:24:57 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Why is this not straightforward?....



I purchased a Packard Bell "imedia" PC from PC World UK in about 2002. AMD
1.3Ghz. 20Gb C: drive with Windows XP home edition (OEM I assume) (SP2) and
a 40Gb D: drive added by myself a couple of years ago.



Ok, the C: drive starts reporting bad sectors and is on the way out. So I
purchased a replacement hard drive (Same manufacturer WD) 80 Gb. Then comes
the problem of transferring the OS to the new drive.



I don't have the original OEM XP disks (thanks PC world).



The new drive was installed (as a slave on IDE 2), formatted and partitioned
(NTFS) and set as drive E:



I first tried using NTBackup to backup the C drive (to the D drive), then
restoring this to E: However, NT Backup did not seem to backup and restore
every file (It missed several in the Windows\System32\Config folder). But
some hacking about with the recovery console (from an XP Home CD, not OEM) I
got these transferred across.



When I swap cables and jumpers to replace the C: drive with the E: drive, I
can get XP to display the boot.ini menu, and it will start loading the OS
Kernel, HAL and boot services. But it gets to MUP.SYS and just halts.



Having read some chat on similar problems, it seems that I shouldn't blame
MUP.SYS, it might be the next thing that loads. Trouble is, even with the
/sos switch, nothing else is displayed. Have tried safe mode etc.



I don't know if this is because the new drive/partition is labelled as E: ?



Anybody got any suggestions short of reinstalling XP and all the Apps? I
could obtain an OEM disk if absolutely necessary, but I feel frustrated that
something as common as replacing a failing system disk should prove so
painful.



Before anyone suggests using a drive image application, the C: drive seems
to have a 2Mb "unknown" partition at the start - preventing any simple
partition copy from working. I assume this is part of some
PCWorld/OEM/Microsoft anti piracy thing. Which I'm all in favour of, until
it stops me legitimately rescuing my failing system

Charlie
--
Anonymous
August 26, 2005 5:24:58 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

If you have a new Western Digital drive, you can download their free Data Lifeguard Tools
which includes "drive-to-drive copy capability".

Ref: http://support.wdc.com/download/index.asp?cxml=n&pid=99...

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

-------------------------------------------------------------------------------------------

"Charlie" wrote:

in message news:JKEPe.452$kE2.149@newsfe3-gui.ntli.net...
| Why is this not straightforward?....
|
| I purchased a Packard Bell "imedia" PC from PC World UK in about 2002. AMD
| 1.3Ghz. 20Gb C: drive with Windows XP home edition (OEM I assume) (SP2) and
| a 40Gb D: drive added by myself a couple of years ago.
|
| Ok, the C: drive starts reporting bad sectors and is on the way out. So I
| purchased a replacement hard drive (Same manufacturer WD) 80 Gb. Then comes
| the problem of transferring the OS to the new drive.
|
| I don't have the original OEM XP disks (thanks PC world).
|
| The new drive was installed (as a slave on IDE 2), formatted and partitioned
| (NTFS) and set as drive E:
|
| I first tried using NTBackup to backup the C drive (to the D drive), then
| restoring this to E: However, NT Backup did not seem to backup and restore
| every file (It missed several in the Windows\System32\Config folder). But
| some hacking about with the recovery console (from an XP Home CD, not OEM) I
| got these transferred across.
|
| When I swap cables and jumpers to replace the C: drive with the E: drive, I
| can get XP to display the boot.ini menu, and it will start loading the OS
| Kernel, HAL and boot services. But it gets to MUP.SYS and just halts.
|
| Having read some chat on similar problems, it seems that I shouldn't blame
| MUP.SYS, it might be the next thing that loads. Trouble is, even with the
| /sos switch, nothing else is displayed. Have tried safe mode etc.
|
| I don't know if this is because the new drive/partition is labelled as E: ?
|
| Anybody got any suggestions short of reinstalling XP and all the Apps? I
| could obtain an OEM disk if absolutely necessary, but I feel frustrated that
| something as common as replacing a failing system disk should prove so
| painful.
|
| Before anyone suggests using a drive image application, the C: drive seems
| to have a 2Mb "unknown" partition at the start - preventing any simple
| partition copy from working. I assume this is part of some
| PCWorld/OEM/Microsoft anti piracy thing. Which I'm all in favour of, until
| it stops me legitimately rescuing my failing system
|
| Charlie
Anonymous
August 26, 2005 6:22:49 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I believe the source/destination partition numbers have to match, since
boot.ini points to the relative boot drive (rdisk(0), usually) and
partition number.

Your new drive doesn't have the "unknown" partition on it, but is this a
partition or just unallocated space? You can check this with disk
management under My Computer->Manage. This partition/space might
contain utilities that the vendor put there for things like restoring
Windows.

If your system is on partition 2 and you clone it to partition 1 on the
new drive, boot.ini (on the new drive) won't reference the correct
partition.

A quick check of your current boot.ini will verify the partition that
your system is in. As long as you have a (primary) partition on the new
drive with the same number - and you clone your drive to that partition
- it should boot okay.

Charlie wrote:
> Why is this not straightforward?....
>
>
>
> I purchased a Packard Bell "imedia" PC from PC World UK in about 2002. AMD
> 1.3Ghz. 20Gb C: drive with Windows XP home edition (OEM I assume) (SP2) and
> a 40Gb D: drive added by myself a couple of years ago.
>
>
>
> Ok, the C: drive starts reporting bad sectors and is on the way out. So I
> purchased a replacement hard drive (Same manufacturer WD) 80 Gb. Then comes
> the problem of transferring the OS to the new drive.
>
>
>
> I don't have the original OEM XP disks (thanks PC world).
>
>
>
> The new drive was installed (as a slave on IDE 2), formatted and partitioned
> (NTFS) and set as drive E:
>
>
>
> I first tried using NTBackup to backup the C drive (to the D drive), then
> restoring this to E: However, NT Backup did not seem to backup and restore
> every file (It missed several in the Windows\System32\Config folder). But
> some hacking about with the recovery console (from an XP Home CD, not OEM) I
> got these transferred across.
>
>
>
> When I swap cables and jumpers to replace the C: drive with the E: drive, I
> can get XP to display the boot.ini menu, and it will start loading the OS
> Kernel, HAL and boot services. But it gets to MUP.SYS and just halts.
>
>
>
> Having read some chat on similar problems, it seems that I shouldn't blame
> MUP.SYS, it might be the next thing that loads. Trouble is, even with the
> /sos switch, nothing else is displayed. Have tried safe mode etc.
>
>
>
> I don't know if this is because the new drive/partition is labelled as E: ?
>
>
>
> Anybody got any suggestions short of reinstalling XP and all the Apps? I
> could obtain an OEM disk if absolutely necessary, but I feel frustrated that
> something as common as replacing a failing system disk should prove so
> painful.
>
>
>
> Before anyone suggests using a drive image application, the C: drive seems
> to have a 2Mb "unknown" partition at the start - preventing any simple
> partition copy from working. I assume this is part of some
> PCWorld/OEM/Microsoft anti piracy thing. Which I'm all in favour of, until
> it stops me legitimately rescuing my failing system
>
> Charlie
Anonymous
August 27, 2005 4:11:04 AM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Charlie" <none@ntlworld.com> wrote in message
news:JKEPe.452$kE2.149@newsfe3-gui.ntli.net...
> Why is this not straightforward?....
>
>
>
> I purchased a Packard Bell "imedia" PC from PC World UK in about 2002.
AMD
> 1.3Ghz. 20Gb C: drive with Windows XP home edition (OEM I assume) (SP2)
and
> a 40Gb D: drive added by myself a couple of years ago.
>
>
>
> Ok, the C: drive starts reporting bad sectors and is on the way out. So I
> purchased a replacement hard drive (Same manufacturer WD) 80 Gb. Then
comes
> the problem of transferring the OS to the new drive.
>
>
>
> I don't have the original OEM XP disks (thanks PC world).
>
>
>
> The new drive was installed (as a slave on IDE 2), formatted and
partitioned
> (NTFS) and set as drive E:
>
>
>
> I first tried using NTBackup to backup the C drive (to the D drive), then
> restoring this to E: However, NT Backup did not seem to backup and
restore
> every file (It missed several in the Windows\System32\Config folder). But
> some hacking about with the recovery console (from an XP Home CD, not OEM)
I
> got these transferred across.
>
>
>
> When I swap cables and jumpers to replace the C: drive with the E: drive,
I
> can get XP to display the boot.ini menu, and it will start loading the OS
> Kernel, HAL and boot services. But it gets to MUP.SYS and just halts.
>
>
>
> Having read some chat on similar problems, it seems that I shouldn't blame
> MUP.SYS, it might be the next thing that loads. Trouble is, even with the
> /sos switch, nothing else is displayed. Have tried safe mode etc.
>
>
>
> I don't know if this is because the new drive/partition is labelled as E:
?
>
>
>
> Anybody got any suggestions short of reinstalling XP and all the Apps? I
> could obtain an OEM disk if absolutely necessary, but I feel frustrated
that
> something as common as replacing a failing system disk should prove so
> painful.
>
>
>
> Before anyone suggests using a drive image application, the C: drive seems
> to have a 2Mb "unknown" partition at the start - preventing any simple
> partition copy from working. I assume this is part of some
> PCWorld/OEM/Microsoft anti piracy thing. Which I'm all in favour of,
until
> it stops me legitimately rescuing my failing system
>
> Charlie
> --

There are several ways to clone a hard disk. Here are a few:
- Use the cloning program that your disk supplier might make
available on his home site.
- Use a disk imaging program such as Acronis TrueImage,
Ghost, or PQMagic DriveImage.
- Boot the machine with a Bart PE boot CD (www.bootdisk.com),
then use xcopy.exe with the appropriate switches to copy
everything from the old disk to the new disk.
- Temporarily install both disks in some other Win2000/XP
PC, then use xcopy as before.

The last two methods require some knowledge about the WinXP
boot process, to make the new disk bootable.
Related resources
!