Copying Bootable Drive C: to Second Hard drive

In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger drive.

This is not working on XP. I did the same thing, but the new drive will
not boot. (No system files error). I have tried doing this several
times, once I ended up with a dual boot creation, which was a major pain
in the ass to remove. I'm guessing that this type of operation is not
possible with XP, and I'll have to completely reinstall XP to the new
drive from scratch.

Anyone know any other way to do this?

On 03/08/2014 05:13 PM, wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger drive.

This is not working on XP. I did the same thing, but the new drive will
not boot. (No system files error). I have tried doing this several
times, once I ended up with a dual boot creation, which was a major pain
in the ass to remove. I'm guessing that this type of operation is not
possible with XP, and I'll have to completely reinstall XP to the new
drive from scratch.

Anyone know any other way to do this?




It absolutely should work.

Since it does not, I'd first check to make sure the partition is marked
active.


If it is and still does not boot,
try issuing the command: fixmbr


You will need to boot with your XP cd and enter the repair console.

wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger drive.

This is not working on XP. I did the same thing, but the new drive will
not boot. (No system files error). I have tried doing this several
times, once I ended up with a dual boot creation, which was a major pain
in the ass to remove. I'm guessing that this type of operation is not
possible with XP, and I'll have to completely reinstall XP to the new
drive from scratch.

Anyone know any other way to do this?


A dual boot might have resulted from doing two installations sequentially.
Less like to have happened purely by copying a partition. Of course,
Partition Magic, being magic and all, might have done something in
the process.

I would use Macrium Reflect Free while the good copy of WinXP is running.
It can process C: while C: is in usage, without rebooting. It uses the
VSS service in WinXP, as part of the solution. It supports cloning, possible
as of Version 5 (it's been out for a while).

(Download link lower left corner)

http://www.macrium.com/reflectfree.aspx

The following advice is custom to you and your situation. Macrium comes
with a Linux appliance type boot CD built into the main download. The
main download would be on the order of 20MB or so, and a lot of that
is the Linux CD that comes with it.

A second option, is to create a WinPE CD, using a second downloaded file.
This download is around 100MB or so, which is a bit too much for a dialup
connection.

The CNET link, that is a "stub installer". When the stub installer is
run on the computer, it presents a dialog that offers the above described
two download options (one or both). In your case, you'd disable the
WAIK/WinPE component, to keep the download to a reasonable size. Once
you've configured what you want from the stub, you can then start the
download. You'd want the 20MB file.

Now, the difference between the Linux appliance CD (dedicated single
application) and the WinPE one, is the WinPE one supports backup/restore/clone,
while the Linux one is more backup/restore. For the current job, of
cloning C:, you can actually do that with no CDs at all in hand. You
don't need either CD to solve your current dilemma.

It would be nice if Macrium had a "no-CD" option, but that
would conflict with their ability (like most good backup/restore
programs), to be able to do a bare metal restore to an empty
hard drive. You would need a CD to do that. But your
current problem is simpler.

There are other utilities you could use. But "everything
in life, starts with a download from somewhere", and
most every tool I can think of, is pudgy and overweight.
You just can't seem to find anyone in the developer
community, on a bandwidth diet, able to craft software
that fits on a floppy.

*******

The mechanical portion of a copy, can be done with
a tiny utility like this one. Only a 170KB download or so.

http://www.chrysocome.net/downloads/dd-0.6beta3.zip

The problem with using that, is it doesn't know about VSS,
and can't copy C: while the OS is running. So close and
yet so far.

I'd gladly point you at a Linux boot OS, as a way to work
on C: without needing VSS, but then the Linux download
would not be a candidate for dialup. It's just too big.
Even the small distros are too big.

So Macrium is going to have to do.

There is a list of cloning programs on Wikipedia.
I checked Clonezilla, and it's over 100MB (as it is a
bootable Linux approach). Even researching the download
size of these, is going to take all day.

http://en.wikipedia.org/wiki/List_of...oning_software

Any decent cloning utility, should copy MBR, boot flags,
and the entire C: partition, so they really shouldn't be
dropping the ball and making un-bootable disks. I think
Philo, in his answer, is assuming a not-very-good clone,
where C: partition is copied, but the MBR wasn't copied
properly. To copy the MBR properly, means copying the
440 byte boot code, as well as the 16 byte partition definition.
And in the 16 byte partition definition, is a byte that
holds the boot flag. (The boot flag exists on all four
primary partitions in the MBR, but by convention, only
one boot flag is asserted at a time.)

A "fixmbr", done from WinXP recovery console, reloads the 440 byte
area. I don't know if it bothers with the boot flag or not.
You could probably use "diskpart" to correct the boot flag.

Doing a "fixboot" is another command, but that fixes
a couple sectors at the start of C:. Those are sectors
related to booting as well. Only if you "cloned" C: by using
XXCOPY or Robocopy, would you have "lost" the Partition Boot Sector
in the header of the file system. And I don't think that's
what happened to you. As Philo says, you could use the
installer CD, boot to recovery console, and do the fixmbr
from there.

When using the recovery console, it looks at all the disks, and
lists all the WinXP OSes it sees. If both of your hard drives
are connected, you'll have to select one and enter the password.
I consider this interface to be obnoxious at best. To make
your life simpler, if you want to follow up on Philo's idea
(and save yourself hours of downloading for Macrium), you would
disconnect the good drive, and just leave the non-booting
drive connected. When you boot your WinXP CD and enter the recovery
console, there will only be one OS showing, and you can confidently
select it, type the administrator password, and get to work.

"Starting the Windows Recovery Console from... CD"
http://support.microsoft.com/kb/314058

Paul

What else is on the other drive? You mentioned
a dual boot creation. You also didn't say what
you used to copy the partition. In addition to
making sure the partition is set active, you'll
need to edit boot.ini if the partition is not in the
same location on the drive. When you boot to
a Win98 partition it boots that partition. When you
boot to an XP partition it boots whatever partition
is specified in boot.ini. That was probably disk 0,
partition 1 originally. If it's not still disk 0, partition 1
then while you may succeed in starting the boot
process in the new XP partition, XP may be trying
to boot a non-bootable partition elsewhere, in which
case you're likely to get something like an error saying
hal.dll is missing.


wrote in message
...
| In Win98se, I could take "Partition Magic 8" and simply copy c: to the
| next drive, shut down, unplug the original drive, and set the jumper on
| the new (bigger) drive to Master, and I'd have a bootable bigger drive.
|
| This is not working on XP. I did the same thing, but the new drive will
| not boot. (No system files error). I have tried doing this several
| times, once I ended up with a dual boot creation, which was a major pain
| in the ass to remove. I'm guessing that this type of operation is not
| possible with XP, and I'll have to completely reinstall XP to the new
| drive from scratch.
|
| Anyone know any other way to do this?
|

On Sat, 08 Mar 2014 18:17:48 -0600, philo* wrote:

On 03/08/2014 05:13 PM, wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger drive.

This is not working on XP. I did the same thing, but the new drive will
not boot. (No system files error). I have tried doing this several
times, once I ended up with a dual boot creation, which was a major pain
in the ass to remove. I'm guessing that this type of operation is not
possible with XP, and I'll have to completely reinstall XP to the new
drive from scratch.

Anyone know any other way to do this?




It absolutely should work.

Since it does not, I'd first check to make sure the partition is marked
active.


If it is and still does not boot,
try issuing the command: fixmbr


You will need to boot with your XP cd and enter the repair console.


It was set active. I have spent half the day trying it different ways.
Either I get a non-system error, or it boots to the XP logo and dont
continue, or for awhile it just kept rebooting. I finally just got
****ed and used my dos floppy, and using fdisk, I wiped the whole hard
drive.

I cant boot from my CD. As I mentioned a week ago, I had to copy the CD
to a flash drive, then copy it to the harddrive, and install it from a
dos prompt off the HD.

Thanks for everyone's help, I QUIT!

I'm not usually a quitter, but everything I try to do with XP is like
being in a fight, or a "world war" might better describe it. I spent 3
datys trying to get XP to connect to the internet and could not so it,
now I spent the last 2 days trying to simply copy the installed OS to a
bigger HD. I NEVER have these problems with Win98. I have copied 98 to
at least 8 HDs, I can connect to the internet with any modem, and since
I normally lose at least one modem every year from lightning, I
regularly change them.

I thought XP was supposed to be fairly easy to use, and maybe it is, as
long as it's installed and left alone, as MS created it, but any
modifications (other than changing the appearance of the desktop), seem
near impossible. It seems as bad if not worse than when I once tried
Linux.

I guess this is the end of the road. I'll stick with Win98, and keep
struggling with the crappy browsers it runs, which is far less trouble
than the last week of completely wasted time I have spent fighting with
XP. I'm not trying to cut down anyone that used XP, I'm just being
honest. 10 or 12 years ago, was the first time I ever touched XP, and I
hated it. I really tried this time, tried to be patient and thorough,
and all I can say in the end is that I hate it more than before.

I'll stick with Win98, and start saving my pennies for a Macintosh
computer. I want no part of any MS operating systems beyond Win98.

Again, THANK ALL OF YOU FOR THE HELP. I'm just too frustrasted to fight
with XP any further.

I'll probably install 98 on this spare computer too, that way it wont
just collect dust in my closet.

By the way, there is a program called dixmlsetup.exe, which is supposed
to make a clone of a partition. Dont waste your time with it. after
installing it, it kept complaining about some missing file..... well,
duhhhh, why didnt it install that file????

On Sat, 08 Mar 2014 20:14:38 -0500, Paul wrote:


When using the recovery console, it looks at all the disks, and
lists all the WinXP OSes it sees. If both of your hard drives
are connected, you'll have to select one and enter the password.
I consider this interface to be obnoxious at best. To make
your life simpler, if you want to follow up on Philo's idea
(and save yourself hours of downloading for Macrium), you would
disconnect the good drive, and just leave the non-booting
drive connected. When you boot your WinXP CD and enter the recovery
console, there will only be one OS showing, and you can confidently
select it, type the administrator password, and get to work.

"Starting the Windows Recovery Console from... CD"
http://support.microsoft.com/kb/314058

Paul

Thanks Paul. You sure do know your stuff, but I wont touch anything
Linux. Fighting with XP is bad enough. I tried linux once, and vowed
to never go anywhere near it again. On top of that, i have never burned
a CD, and have no clue how to even begin. This who mess has me so damn
frustrated that I'm taking this XP computer out to the garage right now,
before I take a hammer to it, which I already came close to, when the
damn floppy refused to come out of the floppy drive.

THANKS FOR TRYING to help!

wrote:
On Sat, 08 Mar 2014 20:14:38 -0500, Paul wrote:

When using the recovery console, it looks at all the disks, and
lists all the WinXP OSes it sees. If both of your hard drives
are connected, you'll have to select one and enter the password.
I consider this interface to be obnoxious at best. To make
your life simpler, if you want to follow up on Philo's idea
(and save yourself hours of downloading for Macrium), you would
disconnect the good drive, and just leave the non-booting
drive connected. When you boot your WinXP CD and enter the recovery
console, there will only be one OS showing, and you can confidently
select it, type the administrator password, and get to work.

"Starting the Windows Recovery Console from... CD"
http://support.microsoft.com/kb/314058

Paul

Thanks Paul. You sure do know your stuff, but I wont touch anything
Linux. Fighting with XP is bad enough. I tried linux once, and vowed
to never go anywhere near it again. On top of that, i have never burned
a CD, and have no clue how to even begin. This who mess has me so damn
frustrated that I'm taking this XP computer out to the garage right now,
before I take a hammer to it, which I already came close to, when the
damn floppy refused to come out of the floppy drive.

THANKS FOR TRYING to help!

There's nothing Linux there. Trust me.

I was explaining what some of them use, for emergency boot media.
You're not in an emergency, so you won't be burning any CDs. Simple.

Download Macrium Reflect Free while you're in WinXP.
Select the "least" set of files to download. That would
be 18-20MB or so. You don't need WinPE/WAIK at the moment,
and options like that are too big to download on dialup.

You then install the program, run it from the Program menu.
Select the source drive, and clone it to the other drive. Done.

Now, shut down, disconnect the original drive. You're not supposed
to leave the original drive connected, while booting the new clone.
You can only re-connect the original drive, once the clone has
successfully booted at least once. Then, it won't do anything
freaky.

So try again, it's probably just a finger problem, like
forgetting the "clones boot alone the first time" rule.
And, I learned of that rule the hard way, and had to clone
over again. It's not like I got that one right on the
first try. I suffered the problem, then looked it up :-)

Paul

On Sat, 08 Mar 2014 21:20:38 -0500, Paul wrote:

wrote:
On Sat, 08 Mar 2014 20:14:38 -0500, Paul wrote:

Thanks Paul. You sure do know your stuff, but I wont touch anything
Linux. Fighting with XP is bad enough. I tried linux once, and vowed
to never go anywhere near it again. On top of that, i have never burned
a CD, and have no clue how to even begin. This who mess has me so damn
frustrated that I'm taking this XP computer out to the garage right now,
before I take a hammer to it, which I already came close to, when the
damn floppy refused to come out of the floppy drive.

THANKS FOR TRYING to help!

There's nothing Linux there. Trust me.

I was explaining what some of them use, for emergency boot media.
You're not in an emergency, so you won't be burning any CDs. Simple.

Download Macrium Reflect Free while you're in WinXP.
Select the "least" set of files to download. That would
be 18-20MB or so. You don't need WinPE/WAIK at the moment,
and options like that are too big to download on dialup.

You then install the program, run it from the Program menu.
Select the source drive, and clone it to the other drive. Done.

Now, shut down, disconnect the original drive. You're not supposed
to leave the original drive connected, while booting the new clone.
You can only re-connect the original drive, once the clone has
successfully booted at least once. Then, it won't do anything
freaky.

So try again, it's probably just a finger problem, like
forgetting the "clones boot alone the first time" rule.
And, I learned of that rule the hard way, and had to clone
over again. It's not like I got that one right on the
first try. I suffered the problem, then looked it up :-)

Paul

Thanks Paul. I put the computer away for now. I'll try it again in a
day or two when I calm down. I've been working on this damn thing
around the clock and have had enough. Right now, I'm going out to get a
much needed drink These computers are designed to drive peiople
nuts, or lead them to drink I'm at that point.

PS. I did remove the original drive after trying to clone with Part
Magic. Like I said, either I got a "no system found" error, or it hangs
on the "welcome " screen, or it kept rebooting over and over and over.

The good news is that it still boots from the original HD, and I removed
the dual boot crap, by simply removing the last line from BOOT.INI. And
more good news, the floppy was NOT stuck in the drive. I was getting so
frustrated that I forgot I removed it. No wonder it did not come out no
matter how hard I pushed the button and after I unplugged the drive
while it was still running.

Time for that drink or two or three!!!!

Thanks

wrote:


Thanks Paul. I put the computer away for now. I'll try it again in a
day or two when I calm down. I've been working on this damn thing
around the clock and have had enough. Right now, I'm going out to get a
much needed drink These computers are designed to drive peiople
nuts, or lead them to drink I'm at that point.

PS. I did remove the original drive after trying to clone with Part
Magic. Like I said, either I got a "no system found" error, or it hangs
on the "welcome " screen, or it kept rebooting over and over and over.

The good news is that it still boots from the original HD, and I removed
the dual boot crap, by simply removing the last line from BOOT.INI. And
more good news, the floppy was NOT stuck in the drive. I was getting so
frustrated that I forgot I removed it. No wonder it did not come out no
matter how hard I pushed the button and after I unplugged the drive
while it was still running.

Time for that drink or two or three!!!!

Thanks

Taking a break, will put things in perspective.

I only pull long sessions now, if I have a reasonable
expectation they'll finish. For example, I started a plumbing
project one day, I'd done a ton of prep work and "nothing
could go wrong". When I hit midnight, I stuck with it, because
I could see all the nasty stuff was done. I could barely
drag myself out of the basement at 3 A.M. in the morning
when it was finished (my back was giving out). I wouldn't
have tried that, if I thought it was going to go south
on me again :-)

Back in my working days, I pulled a couple of 36 hour
stints at work, but that's really counterproductive.
You have to be really careful what you eat when you do that,
because one heavy meal, and you're done for.

Paul

wrote:
On Sat, 08 Mar 2014 21:20:38 -0500, Paul wrote:

wrote:
On Sat, 08 Mar 2014 20:14:38 -0500, Paul wrote:

Thanks Paul. You sure do know your stuff, but I wont touch anything
Linux. Fighting with XP is bad enough. I tried linux once, and vowed
to never go anywhere near it again. On top of that, i have never burned
a CD, and have no clue how to even begin. This who mess has me so damn
frustrated that I'm taking this XP computer out to the garage right now,
before I take a hammer to it, which I already came close to, when the
damn floppy refused to come out of the floppy drive.

THANKS FOR TRYING to help!

There's nothing Linux there. Trust me.

I was explaining what some of them use, for emergency boot media.
You're not in an emergency, so you won't be burning any CDs. Simple.

Download Macrium Reflect Free while you're in WinXP.
Select the "least" set of files to download. That would
be 18-20MB or so. You don't need WinPE/WAIK at the moment,
and options like that are too big to download on dialup.

You then install the program, run it from the Program menu.
Select the source drive, and clone it to the other drive. Done.

Now, shut down, disconnect the original drive. You're not supposed
to leave the original drive connected, while booting the new clone.
You can only re-connect the original drive, once the clone has
successfully booted at least once. Then, it won't do anything
freaky.

So try again, it's probably just a finger problem, like
forgetting the "clones boot alone the first time" rule.
And, I learned of that rule the hard way, and had to clone
over again. It's not like I got that one right on the
first try. I suffered the problem, then looked it up :-)

Paul

Thanks Paul. I put the computer away for now. I'll try it again in a
day or two when I calm down. I've been working on this damn thing
around the clock and have had enough. Right now, I'm going out to get a
much needed drink These computers are designed to drive peiople
nuts, or lead them to drink I'm at that point.

PS. I did remove the original drive after trying to clone with Part
Magic. Like I said, either I got a "no system found" error, or it hangs
on the "welcome " screen, or it kept rebooting over and over and over.

The good news is that it still boots from the original HD, and I removed
the dual boot crap, by simply removing the last line from BOOT.INI. And
more good news, the floppy was NOT stuck in the drive. I was getting so
frustrated that I forgot I removed it. No wonder it did not come out no
matter how hard I pushed the button and after I unplugged the drive
while it was still running.

Time for that drink or two or three!!!!

Thanks

Partition Magic is also a bit old and long in the tooth, so you'll probably
have better results with Macrium Reflect Free, as Paul has suggested. Just
because it didn't work with PM doesn't mean you'll get the same results.

In ,
typed:
On Sat, 08 Mar 2014 21:20:38 -0500, Paul wrote:

wrote:
On Sat, 08 Mar 2014 20:14:38 -0500, Paul wrote:

Thanks Paul. You sure do know your stuff, but I wont touch anything
Linux. Fighting with XP is bad enough. I tried linux once, and
vowed to never go anywhere near it again. On top of that, i have
never burned a CD, and have no clue how to even begin. This who
mess has me so damn frustrated that I'm taking this XP computer out
to the garage right now, before I take a hammer to it, which I
already came close to, when the damn floppy refused to come out of
the floppy drive.

THANKS FOR TRYING to help!

There's nothing Linux there. Trust me.

I was explaining what some of them use, for emergency boot media.
You're not in an emergency, so you won't be burning any CDs. Simple.

Download Macrium Reflect Free while you're in WinXP.
Select the "least" set of files to download. That would
be 18-20MB or so. You don't need WinPE/WAIK at the moment,
and options like that are too big to download on dialup.

You then install the program, run it from the Program menu.
Select the source drive, and clone it to the other drive. Done.

Now, shut down, disconnect the original drive. You're not supposed
to leave the original drive connected, while booting the new clone.
You can only re-connect the original drive, once the clone has
successfully booted at least once. Then, it won't do anything
freaky.

So try again, it's probably just a finger problem, like
forgetting the "clones boot alone the first time" rule.
And, I learned of that rule the hard way, and had to clone
over again. It's not like I got that one right on the
first try. I suffered the problem, then looked it up :-)

Paul

Thanks Paul. I put the computer away for now. I'll try it again in a
day or two when I calm down. I've been working on this damn thing
around the clock and have had enough. Right now, I'm going out to
get a much needed drink These computers are designed to drive
peiople nuts, or lead them to drink I'm at that point.

PS. I did remove the original drive after trying to clone with Part
Magic. Like I said, either I got a "no system found" error, or it
hangs on the "welcome " screen, or it kept rebooting over and over
and over.

The good news is that it still boots from the original HD, and I
removed the dual boot crap, by simply removing the last line from
BOOT.INI. And more good news, the floppy was NOT stuck in the drive.
I was getting so frustrated that I forgot I removed it. No wonder it
did not come out no matter how hard I pushed the button and after I
unplugged the drive while it was still running.

Time for that drink or two or three!!!!

Thanks

Hi Casey! I've seen this dozens of times. The problem is XP (NT really)
saw the clone drive and it remembers that isn't the system drive. So it
thinks it is the same drive letter it was the first time and now it is
all confused. The fix is to make XP forget that it ever saw this drive
before and it will work just fine. How?

One way is by using Win98 "FDISK /MBR". Yes this creates a new MBR on
the new clone drive, but Win98 FDISK also has a bug that wipes out part
of the volume identifier (or whatever they call it). Don't boot up the
original with the clone connected after doing this or this problem will
reoccur again.

Another way is to use XXClone (the free one) which runs under your
original drive and create your clone that way. Don't worry XXClone makes
the clone drive forget. Also many other clone software should work too,
since most developers knows about this clone system drive problem.

--
Bill
Gateway M465e ('06 era) - OE-QuoteFix v1.19.2
Centrino Core2 Duo T5600 1.83GHz - 4GB - Windows XP SP2

On 03/08/2014 07:45 PM, wrote:
On Sat, 08 Mar 2014 18:17:48 -0600, philo wrote:

On 03/08/2014 05:13 PM, wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger drive.




snip


It really does look like Partition Magic failed but I did think of one
more thing.

Some manufacturers have different jumper settings for "master"


Master with slave present

Master with no slave present

On 3/9/2014 2:22 PM, philo wrote:
On 03/08/2014 07:45 PM, wrote:
On Sat, 08 Mar 2014 18:17:48 -0600, philo wrote:

On 03/08/2014 05:13 PM, wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger drive.

snip

It really does look like Partition Magic failed but I did think of one
more thing.

Some manufacturers have different jumper settings for "master"

Master with slave present

Master with no slave present

Well I think Partition Magic did okay and all. But Partition Magic
didn't know and correct the cloning under Windows NT (in this case XP)
problem. Nothing bad happens if the original Windows never sees the
clone drive. Like cloning from booting from a CD or something.

The problem happens when you boot the original with the clone connected
and the original notes that new drive and assigns a drive letter to it.
It remembers this because it is stored in the registry.

Now remove the original and boot up the cloned copy and Windows thinks
it is original but also recalls this cloned drive is drive letter so and
so. What is weird if you reverse the drives after you cloned (making the
clone the boot/system drive) and the original as some other drive. And
if you have drive lights, Windows will boot normally in this condition,
but you will see both drives being accessed while booting. Since Windows
sees some parts as the original drive as the real boot and system drive
and parts of the new clone as the boot/system drive. Weird.

Microsoft could have easily wrote a small amount of code to fix this,
but they didn't. I know why personally I think their reason is stupid
myself, but I digress. Anyway the trick is to make Windows to believing
it never saw this cloned drive before. Then everything works as it
should. This problem only pops up with NT and not with Windows 9x (ME).

So cloning software that deals with NT should already know about this
problem and then knows how to remove the registry entry about this
cloned drive. Thus Windows sees it as an unknown new drive and not
something it has seen before.

Partition Magic is a partitioning program and an old one at that. It
isn't meant to be used for cloning per se, but it can. And back when
Windows 2000/XP first came out, this problem was very common. Later
software got smart to this and worked around the problem.

--
Bill
Dell Latitude Slate Tablet 128GB SSD ('12 era) - Thunderbird v24.3.0
Intel Atom Z670 1.5GHz - 2GB RAM - Windows 8 Pro

On 03/09/2014 03:20 PM, BillW50 wrote:
On 3/9/2014 2:22 PM, philo wrote:
On 03/08/2014 07:45 PM, wrote:
On Sat, 08 Mar 2014 18:17:48 -0600, philo wrote:

On 03/08/2014 05:13 PM, wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c: to the
next drive, shut down, unplug the original drive, and set the
jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger
drive.

snip

It really does look like Partition Magic failed but I did think of one
more thing.

Some manufacturers have different jumper settings for "master"

Master with slave present

Master with no slave present

Well I think Partition Magic did okay and all. But Partition Magic
didn't know and correct the cloning under Windows NT (in this case XP)
problem. Nothing bad happens if the original Windows never sees the
clone drive. Like cloning from booting from a CD or something.

The problem happens when you boot the original with the clone connected
and the original notes that new drive and assigns a drive letter to it.
It remembers this because it is stored in the registry.



I think the OP did not reboot with the drive attached...

it looks to me like he did it properly

In ,
philo typed:
On 03/09/2014 03:20 PM, BillW50 wrote:
On 3/9/2014 2:22 PM, philo wrote:
On 03/08/2014 07:45 PM, wrote:
On Sat, 08 Mar 2014 18:17:48 -0600, philo
wrote:
On 03/08/2014 05:13 PM, wrote:
In Win98se, I could take "Partition Magic 8" and simply copy c:
to the next drive, shut down, unplug the original drive, and set
the jumper on
the new (bigger) drive to Master, and I'd have a bootable bigger
drive.

snip

It really does look like Partition Magic failed but I did think of
one more thing.

Some manufacturers have different jumper settings for "master"

Master with slave present

Master with no slave present

Well I think Partition Magic did okay and all. But Partition Magic
didn't know and correct the cloning under Windows NT (in this case
XP) problem. Nothing bad happens if the original Windows never sees
the clone drive. Like cloning from booting from a CD or something.

The problem happens when you boot the original with the clone
connected and the original notes that new drive and assigns a drive
letter to it. It remembers this because it is stored in the registry.

I think the OP did not reboot with the drive attached...

it looks to me like he did it properly

Actually if the original is booted with the clone drive (even before it
is cloned) it is now marked by the original XP (NT really). Now when you
clone it under the original OS, all of the original information is also
now on the clone, even knowledge of this cloned drive. So it is too late
to disconnect and reboot. The problem is already there. I have seen this
more times than I care to recall. Win98 FDISK's bug is an easy way to
fix it.

--
Bill
Gateway M465e ('06 era) - OE-QuoteFix v1.19.2
Centrino Core2 Duo T5600 1.83GHz - 4GB - Windows XP SP2