Partiion Magic can COPY a bootable mirror image on any unallocate space in
your hard drive.

Boot up with the emergency disks you created when you installed PM
Delete the new second hard drive to create an unallocated space, and copy
the operating system from the !st hard drive.

Then change the jumpers from slave to master on the new drive.
and master to slave on the old drive.

"The Toyman" <o1nyx@hotmail.unspam.com> wrote in message
news:OHinf.641561$xm3.606445@attbi_s21...
> My new neighbor had a supplemental 160 GB HD installed by his brother -
> the
> original 11 GB drive was full and had related problems. Problem is when
> he
> made the new drive C: (faster & bigger), he moved some of the boot files
> to
> it, but left many, including applications, etc. on the old drive (now D.
> The Registry shows most of key files on the old drive (now D, and the
> machine is hiccupping all over the place - unable to load apps, hanging,
> etc. Additionally, when I check the Drive Settings under System Restore,
> the old drive (now D is referred to as the 'System Drive'.
>
> Norton Utilities (Win Doctor) finds the problems, but I'm not interested
> in
> editing the Registry to correct the 292 problems it found - some are
> probably beyond my ability anyhow.
>
> Adding insult to injury, the neighbor recently moved here and lost some
> boxes of software (among other things) during the move, including the XP
> PRO, O/S disk, so I can't just wipe the drives and reload them. The
> neighbor's not interested in buying a new disk from MS.
>
> Question: can I use Partition Magic's (v8.0) Drive Mapper to reverse the
> drive's names - i.e. change D: to C:, and C: to D:? I guess the real
> question is, even if Drive Mapper will make the change, will that change
> result in the Registry becoming discombobulated to the point the machine
> won't boot? Or is the only to find out to try it?
>
> Is another option to uninstall the new drive to (hopefully) put the beast
> back to its original condition, test it to see if it will run, and then
> re-install the new drive as a slave to the original drive. This PC isn't
> going to be used for much beyond web stuff, a little word processing, and
> iTunes downloads.
>
> As I look at the BIOS setup, the new (160 GB) drive is set as the Primary
> Master (Type: User), the CDROM is set as Primary Slave, and the old (11
> GB)
> drive is set as Secondary Master (Type: User). The person who installed
> the
> new drive said he had some problems getting the machine to recognize it.
> He
> also couldn't get the beast to recognize more than 127 GB of the 160, but
> I
> found that XP SP 1 hasn't been installed either. I also believe the
> system
> must have a 48-bit LBA-compatible BIOS installed. Not sure where to find
> that information.
>
> Anyone have any thoughts about the best way to proceed?
>
> Toyman
>
>