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

so basically you want the biger hard drive as the sytem drive? if so,
why not duplicate the old hard drive to the new hard drive? that' way,
the new hard drive will have everything from the old drive


--
cuoctinhtay3

.. . . and the way to do that is . . . ???

Toyman
_________________________

"cuoctinhtay3" <cuoctinhtay3.1zy229@pcbanter.net> wrote in message
news:cuoctinhtay3.1zy229@pcbanter.net...
:
: so basically you want the biger hard drive as the sytem drive? if so,
: why not duplicate the old hard drive to the new hard drive? that' way,
: the new hard drive will have everything from the old drive
:
:
: --
: cuoctinhtay3

Make PM boot diskette, boot from it. Use the copy function.

--
Jonny
"The Toyman" <o1nyx@hotmail.unspam.com> wrote in message
news:bYynf.643158$xm3.316363@attbi_s21...
> . . . and the way to do that is . . . ???
>
> Toyman
> _________________________
>
> "cuoctinhtay3" <cuoctinhtay3.1zy229@pcbanter.net> wrote in message
> news:cuoctinhtay3.1zy229@pcbanter.net...
> :
> : so basically you want the biger hard drive as the sytem drive? if so,
> : why not duplicate the old hard drive to the new hard drive? that' way,
> : the new hard drive will have everything from the old drive
> :
> :
> : --
> : cuoctinhtay3
>
>

48 bit LBA is not required until 132GB is surpassed in hard drive capacity.
SP1 and SP2 offer this, but not for the bios.

You bios is immaterial if SP1 or SP2 is not installed on your XP.

--
Jonny
"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
>
>

Once I get the thing to boot from C: and otherwise cleaned up, I'll install
SP1/SP2. Since he paid for 160 GB drive, I suppose he'd probably like to be
able to use it all. I seem to recall hearing about some folks having
trouble installing SP1. I installed SP2 on mine without problems a couple
of years ago, but don't have 1st hand knowledge about installing SP1. But
that sounds like a topic for some web searching on my part. However that
takes me back to the 48-bit LBA-compatible BIOS. Where would I look to see
if it's there?

And thanks for the 'insight' about using PM to make things right (or at
least better).

Toyman
___________________________

"Jonny" <billgates@scampublic.net> wrote in message
news:efcCyc%23$FHA.328@TK2MSFTNGP14.phx.gbl...
: 48 bit LBA is not required until 132GB is surpassed in hard drive
capacity.
: SP1 and SP2 offer this, but not for the bios.
:
: You bios is immaterial if SP1 or SP2 is not installed on your XP.
:
: --
: Jonny
: "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
: >
: >
:
:

If you installed SP2, it has all the files SP1 had but is now updated.


"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
>
>

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
>
>

On Tue, 13 Dec 2005 21:28:41 GMT, "The Toyman"
<o1nyx@hotmail.unspam.com> wrote:

>Once I get the thing to boot from C: and otherwise cleaned up, I'll install
>SP1/SP2. Since he paid for 160 GB drive, I suppose he'd probably like to be
>able to use it all. I seem to recall hearing about some folks having
>trouble installing SP1. I installed SP2 on mine without problems a couple
>of years ago, but don't have 1st hand knowledge about installing SP1. But
>that sounds like a topic for some web searching on my part. However that
>takes me back to the 48-bit LBA-compatible BIOS. Where would I look to see
>if it's there?

Contrary to popular opinion, 48-bit LBA BIOS capability is not an
absolute requirement. It's only necessary if, during the boot-up
process, the BIOS has to access past the 137GB (GB = 10^9) point on
the hard drive. For a 160GB drive, that can only happen if the
partition you're booting into begins at about 114GB and continues to
the end of the drive.
Once Windows XP has been booted and is running, the BIOS is no longer
used to access the hard drive, so its LBA capability becomes
irrelevant.

>
>And thanks for the 'insight' about using PM to make things right (or at
>least better).
>
>Toyman
>___________________________
>
>"Jonny" <billgates@scampublic.net> wrote in message
>news:efcCyc%23$FHA.328@TK2MSFTNGP14.phx.gbl...
>: 48 bit LBA is not required until 132GB is surpassed in hard drive
>capacity.
>: SP1 and SP2 offer this, but not for the bios.
>:
>: You bios is immaterial if SP1 or SP2 is not installed on your XP.
>:
>: --
>: Jonny
>: "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
>: >
>: >
>:
>:
>

Let me check my understanding of what you said (not arguing, just want to
make sure I understand):

- Currently the new (160GB) drive is set as the primary master, so I
shouldn't have to change the jumpers there.
- Boot from the P/M floppies, and delete the new (160 GB) drive (C:\) - i.e.
remove everything from it.
- Using a 'COPY' function within the bootable P/M, copy the old (11 GB)
drive (now drive d:\) and paste it onto the new (160 GB) drive C:\.
That will make the new (160 GB) drive identical to the old (11 GB)
drive.
- Change the jumper settings on the old (11 GB) drive from (secondary)
Master to Primary Slave.

- Where does the CD-ROM plug into this sequence?

Hmmmmm. Looks like I'm going to have some other work to do first. Just
tried to boot the P/M floppies, and got a nastygram:
"Error #91
Disk Manager has been detected on drive 0, but Disk Manager is not
running. If you are booting from a floppy, remove the floppy disk and
reboot. Press and hold the <SPACE BAR> key as you computer restarts. When
prompted insert your boot floppy and continue booting." That's followed by
"Error #87 - Unable to initialize the engine", followed by a return to the
A:\ prompt.

I see on the BIOS, that "S.M.A.R.T. for Hard Disks" is Disabled. Does
that have something to do with the 'nastygram'?

It appears that when the bigger drive was installed, the software to run the
thing wasn't activated, or installed incorrectly (or there's another
problem). Looks like a re-install is needed. And since my neighbor is
out-of-state until next week, I can't get the documentation until then.

Before I reinstall the drive, I'll install SP2, and then set up the new
drive with a bootable partition, make the correct Master/Slave settings,
figure out what to do with the CD-ROM, and cross my fingers. If all works
at that point, then I'll use the (floppy P/M) mirror function to get the old
drive data to the new drive.

I have Norton (Systemworks) Ghost. Any thoughts about that being any easier
or more effective than P/M to mirror drive contents? I haven't used Ghost
before.

Thanks to all for the help-to-date.

Toyman
_______________________________________

"Squire" <jerrym526@msn.org> wrote in message
news:Ox1kJqGAGHA.360@TK2MSFTNGP09.phx.gbl...
: 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
: >
: >
:
: