Trouble cloning XP with Ghost 2003

The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the jumpers,
but get a "boot failure from previous device" error on startup (after BIOS
screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

Thanks,
Kevin

Did you boot XP after you have installed a 2nd drive, before using Ghost
2003 (booted from DOS/floppy)?

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the
jumpers,
but get a "boot failure from previous device" error on startup (after BIOS
screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

Thanks,
Kevin

Yes, I drive was installed prior to installing ghost.

I followed the directions in Ghost's readme, and have tried using both -FDSZ
and -FDSP.

- Kevin

"Peter" wrote in message
...
Did you boot XP after you have installed a 2nd drive, before using Ghost
2003 (booted from DOS/floppy)?

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the
jumpers,
but get a "boot failure from previous device" error on startup (after
BIOS
screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

Thanks,
Kevin

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector problems
lately, so I decided to try to clone it to a new drive. I installed a 2nd
drive, formatted it, and used Norton Ghost 2003 to do a clone of the boot (C
drive to it.

When the clone is complete, I power off, swap the cable and set the jumpers,
but get a "boot failure from previous device" error on startup (after BIOS
screen but before Windows).

I can verify that the clone worked by booting off the original drive with the
clone as a slave-- all the files seem to be there.

What might I be doing wrong?

You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

I don't give XP a chance to see the clone-- I've been powering off and
removing the original drive as soon as Ghost completes.

"Rod Speed" wrote in message
...

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the
jumpers, but get a "boot failure from previous device" error on startup
(after BIOS screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

Kevin wrote in message
...

I don't give XP a chance to see the clone-- I've been powering off and
removing the original drive as soon as Ghost completes.

Then presumably the clone isnt successful because
of the state of the original drive, partially failed.

"Rod Speed" wrote in message
...

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the jumpers,
but get a "boot failure from previous device" error on startup (after BIOS
screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

But the original drive can boot. If the clone is a bitwise copy of the
original, shouldn't it be able to boot?

"Rod Speed" wrote in message
...

Kevin wrote in message
...

I don't give XP a chance to see the clone-- I've been powering off and
removing the original drive as soon as Ghost completes.

Then presumably the clone isnt successful because
of the state of the original drive, partially failed.

"Rod Speed" wrote in message
...

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the
jumpers, but get a "boot failure from previous device" error on startup
(after BIOS screen but before Windows).

I can verify that the clone worked by booting off the original drive
with the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

Kevin wrote in
message ...

But the original drive can boot. If the clone is a bitwise copy of the
original, shouldn't it be able to boot?

In theory, yes. In practice the different detail on sector access may
see the sector contents not copied properly when the clone is made,
but be good enough on retrys to allow it to boot in the original.

You did say you got an error message that complained
about a boot failure before the win screens show up.

You could also try repairing the bad clone. I wouldnt
personally because you dont know what else didnt clone
properly apart from the boot stuff, and that can bit late,
but its less work that a completely clean reinstall.


"Rod Speed" wrote in message
...

Kevin wrote in message
...

I don't give XP a chance to see the clone-- I've been powering off and
removing the original drive as soon as Ghost completes.

Then presumably the clone isnt successful because
of the state of the original drive, partially failed.

"Rod Speed" wrote in message
...

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the
jumpers, but get a "boot failure from previous device" error on startup
(after BIOS screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

"Rod Speed" wrote in message
...

"Kevin" wrote in message
...
The boot disk for my XP system has been having a number of bad sector
problems lately, so I decided to try to clone it to a new drive. I
installed a 2nd drive, formatted it, and used Norton Ghost 2003 to do a
clone of the boot (C drive to it.

When the clone is complete, I power off, swap the cable and set the
jumpers, but get a "boot failure from previous device" error on startup
(after BIOS screen but before Windows).

I can verify that the clone worked by booting off the original drive with
the clone as a slave-- all the files seem to be there.

What might I be doing wrong?

You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

This is very interesting. For years I've heard that you can't/shouldn't
have a clone of XP running together with the normal boot drive housing the
OS, although I've booted many times with a clone attached with no adverse
effects.

What you've said hear makes it more clear that if booted with a new clone
with the original boot drive attached, as described above, the OS may think
the old drive is the boot device since the ID matches. However, after the
new drive is booted, new hardware installed, and the drive's ID established
as the proper boot device, all is well. Thus, once this first boot with a
new copy is accomplished without the original attached, this original can be
subsequently run in the system with no ill effects.

With my old Win98SE machine I cloned C: to D: once per week and left D: in
the system at all times. It would then seem that you could still do this
with XP since the hardware configuration will not have changed. Does this
make sense?

"Bob Davis" wrote:
"Rod Speed" wrote :
You basically have to unplug the original drive for the first
boot after the drive has been cloned and boot off the copy.

XP will claim to have detected new hardware and ask to
be allowed to reboot. Once you have allowed that, you
can put the original drive back in the system if you want,
if you say want to use it for video capture etc.

If XP can see both the original and the copy during
the first boot after the original has been cloned, it
gets seriously confused, even if you boot off the
copy and it uses files off the original for the boot.

This is very interesting. For years I've heard that you
can't/shouldn't have a clone of XP running together with
the normal boot drive housing the OS, although I've booted
many times with a clone attached with no adverse effects.

What you've said hear makes it more clear that if booted
with a new clone with the original boot drive attached, as
described above, the OS may think the old drive is the
boot device since the ID matches. However, after the new
drive is booted, new hardware installed, and the drive's ID
established as the proper boot device, all is well. Thus,
once this first boot with a new copy is accomplished without
the original attached, this original can be subsequently run
in the system with no ill effects.


It's more complicated than that. The "proper boot device"
is established by the BIOS's boot sequence and the
"active" partition on the 1st HD in that boot sequence, not
by having successfully booted for the 1st time in isolation.
A clone booted for the 1st time with the "parent" in view
continues to function (in my experience), but it needs the
continued presence of its "parent" to do so. This seems
to be a feature added my Microsoft to thwart copying of
it OSes, starting with the WinNT/Win2K/WinXP family of
OSes.


With my old Win98SE machine I cloned C: to D: once per week
and left D: in the system at all times. It would then seem that you
could still do this with XP since the hardware configuration will
not have changed. Does this make sense?


No. Under WinXP, you can do this with no problem as long
as the new OS (the one in drive D hasn't been loaded and
started. You can start up the old OS all you want, and it can
see the files in drive D: with no problem. The problem appears
when the new clone OS in drive D: is started up with the old
OS in drive C: visible to it. Somehow the new clone recognizes
its "parent" and that it's a "child" in this world. But if it starts up
in isolation for the 1st time that it's started, it decides it's a
different beast and becomes an "adult".

Microsoft doesn't document this behavior and it offers no
method (such as initial isolation) to get around it, and the
MS Professional Volunteers in the MS newsgroups don't
know much if anything about it. At least they seem to avoid
writing about it. The MVPs even get quite abusive and hostile
if you so much as say that running two installations of one OS
CD in *the same machine* is legal. Obviously, MS has them
toeing the company line when it comes to gray areas in its
EULA. I expect that cloning Longhorn will be even more
difficult.

*TimDaniels*