Norton Ghost - Clone Won't Work

[Bob Davis]

Hmm. I can't be sure because I can't see your registry but I suspect it's
because of how Windows XP serializes the drives and the new drive isn't
what it thinks should be the system drive (actually, it isn't 'anything'
when it first boots because it hasn't been identified and serialized yet,
but it may be by now, to whatever XP thought it should be).

I've cloned many a drive with Ghost and haven't run across this
problem--using IDE, SATA, and Firewire--as XP should pick it up readily,
even though the drive letter may be different. This can be easily changed.

On a single drive system it would normally figure out that the 'new' drive
is the 'new' C (if one removes the old one completely, else the OLD one
remains C and the new one gets a new letter, which causes all sorts of
problems) but with an existing drive as your boot drive I'm not sure how
it's resolving the new drive's letter, and that's what I suspect is going
wrong. Somehow it's getting confused as to which should be the 'C' drive
and which is the 'D' (or whatever).

I've restored C: (boot) drives on numerous occasions and have never had a
problem booting from the newly created drive.

 

[David Maynard]

I've cloned many a drive with Ghost and haven't run across this
problem--using IDE, SATA, and Firewire--as XP should pick it up readily,
even though the drive letter may be different.

Pick up what?

This can be easily changed.

Changing it doesn't fix anything.

I don't think you're talking about the same situation. I'm talking about
both drives having the installation on them, the new cloned one and the old
one still intact, and both operating.

It'll boot from the new drive but it'll end up still using the old one as
the sysroot drive because it's still C, regardless of having been 'moved'
to the IDE slave, and everything in windows tells it to use C.

I've restored C: (boot) drives on numerous occasions and have never had a
problem booting from the newly created drive.

I've restored many a drive too, with no problems.

 

[John Johnson]

I did the same thing successfully about 6 months ago, Did it again 2
months ago and had the same problem you had. Have no idea what I did
differently.

I posted to this group and someone suggested it might be a Volume
label problem but you said you cloned to a new drive which shouldn't
have had that problem.

I had planned on trying again but I will wait to see if someone comes
up with a solution

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message saying
the drive needs to be checked and it goes through three chkdsk checks,
all of which pass, then it reboots and the same thing happens again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a warning
message about another OS being there and that it is a bad idea to
install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo

So far it looks like you did everything right, which would lead me to
suspect that there might be something wrong with the new drive, or the
BIOS has the disk configured incorrectly. It's been awhile, but does
Ghost have an option to verify the contents of the cloned drive? If it
does I would use it to see if it checks out. If you have Partition
Magic, you can use it to check the new drive. It should be able to
detect any partition or BIOS configuration errors.

Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any partitions
on it.

Suggestions?

jimbo

 

[David Maynard]

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message saying
the drive needs to be checked and it goes through three chkdsk
checks, all of which pass, then it reboots and the same thing happens
again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a
warning message about another OS being there and that it is a bad
idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo

So far it looks like you did everything right, which would lead me to
suspect that there might be something wrong with the new drive, or the
BIOS has the disk configured incorrectly. It's been awhile, but does
Ghost have an option to verify the contents of the cloned drive? If
it does I would use it to see if it checks out. If you have Partition
Magic, you can use it to check the new drive. It should be able to
detect any partition or BIOS configuration errors.

Well, I did a WinXP installation on the new drive with no problems. But
interesting, when I checked everything out with Partition Magic, it
reports "Bad Disk" for the old "D" drive! Even though it works perfectly
with my system, now and in the past. It shows up in Device Manager as
working, etc. No errors of any kind, boots the WinXP installation, etc,
etc. But for some reason Partition Magic thinks there is something wrong
with it and does not even show any partitions on it.

Suggestions?

jimbo

Well, Partition Magic not liking the partition is disturbing. But, for now,

I see above you say you put the drive in a USB enclosure and cloned it. I'm
not concerned with that particular clone attempt but want to know if you've
had the new drive in the machine, regardless of the interface, with your
existing XP system running. And if you HAVE then it's been 'installed' by
XP, given a unique GUID, and assigned a drive letter; which will be
faithfully copied to the new drive when you do a clone so it will not be a
'new' drive when booting from that clone but will be whatever letter it was
assigned, so it won't be assigned the missing 'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which letter the
two old drives are assigned. You are assuming the win98 boot drive is c? So
XP is installed on D and SAYS itself that D is it's system drive? I.E. the
XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the same
order, you need to get the new drive back to 'virgin' status. And the
easiest way to do that is put the new drive as master on the primary IDE
port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with a
Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the win98
master, and see if it boots up right (while crossing fingers that it
detects the drives in the original order).

 

[spodosaurus]

Wow, confusing time trying to understand your procedure. You want to
clone your Windows XP drive, which is your D drive (not the boot drive)
to your new drive, which you want to install as C, right? So you can
boot up Windows XP, right?

No, he wants the new larger drive to be D drive with XP on it. Why he's
removing C: drive to do this, I don't know. I would have tried:

1. Leave both drives as they are.
2. Connect the new drive, disconnecting any cdroms as necessary.
3. Ghost D: to the new drive.
4. Swap the new drive with the old D: drive.
5. try booting from there.

Well, if you D drive is not your boot drive, Windows XP on it won't be
set up to boot as C, will it?

No, he still wants win98 to be the c drive. That's why he resintalled
the c drive.

It will be booting from the boot loader in
the boot partition on your C drive, with Windows 98. Unless I'm even
more confused than I think. ??? So when you clone the original D drive
(W XP) to your new, empty C drive, no wonder it won't boot.

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. To jump to the end
of the story, as a result of this I need a bone marrow transplant. Many
people around the world are waiting for a marrow transplant, too. Please
volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

I don't understand. If I read correctly, I leave "C" as is at the end of
the ribbon cable, and change the jumper on "D" to be master,

NO! Leave both hard drives as they are. Then physically install the new
hard drive. S.B. is assuming that you have 2 cdroms or some such in that
computer, which is why he's telling you to disconnect those so you can
have all three hard disks installed at the same time. Then clone D: to
the new drive.

but leave
it on the middle cable connector.

NO! Leave the hard drives that are already in there ALONE!

If that works, put the new drive on
the middle ribbon cable connector? But that is where "D" is, no?

Aren't you trying to clone D: and then replace it with the cloned
copy???????????????? After you clone it, replace it.

I must be missing something?

jimbo

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. To jump to the end
of the story, as a result of this I need a bone marrow transplant. Many
people around the world are waiting for a marrow transplant, too. Please
volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[spodosaurus]

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message saying
the drive needs to be checked and it goes through three chkdsk
checks, all of which pass, then it reboots and the same thing happens
again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a
warning message about another OS being there and that it is a bad
idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo

So far it looks like you did everything right, which would lead me to
suspect that there might be something wrong with the new drive, or the
BIOS has the disk configured incorrectly. It's been awhile, but does
Ghost have an option to verify the contents of the cloned drive? If
it does I would use it to see if it checks out. If you have Partition
Magic, you can use it to check the new drive. It should be able to
detect any partition or BIOS configuration errors.

Well, I did a WinXP installation on the new drive with no problems. But
interesting, when I checked everything out with Partition Magic, it
reports "Bad Disk" for the old "D" drive! Even though it works perfectly
with my system, now and in the past. It shows up in Device Manager as
working, etc. No errors of any kind, boots the WinXP installation, etc,
etc. But for some reason Partition Magic thinks there is something wrong
with it and does not even show any partitions on it.

Suggestions?

jimbo

Why are you playing around with a partitioning program? After you ghost
something properly, there's no need to play with partitioning programs:
all the data including the partition table is cloned.

--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. To jump to the end
of the story, as a result of this I need a bone marrow transplant. Many
people around the world are waiting for a marrow transplant, too. Please
volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[David Maynard]

No, he wants the new larger drive to be D drive with XP on it. Why he's
removing C: drive to do this, I don't know.

For the same reason you say "disconnecting any cdroms as necessary." It was
just the place he picked to temporarily put the new drive that also leaves
the old 'D' in the system to clone from.

Doesn't matter if you unplug a CD or hard drive to do it, just as long as D
is still there to clone from.

 

[Peter]

I think XP looks for boot image on the C drive and that is looking for
the old D drive not the new drive.

Why wouldn't that 'boot image' not be looking for the new D drive.
Surely there should be no difference between the old and new drive,
unless, that is, Norton Ghost doesn't create an 'exact' copy (sector for
sector) of the original D drive. Haven't used NG so don't know how it
works exactly.

 

[Ed Coolidge]

Why are you playing around with a partitioning program? After you ghost
something properly, there's no need to play with partitioning programs:
all the data including the partition table is cloned.

If you read the post he replied to you would already know. Its not to change
the partitions, but to verify that they're correct as configuration errors or
disk errors can mess up a clone.

 

[David Maynard]

Why wouldn't that 'boot image' not be looking for the new D drive.

What makes you think the new drive is 'D'?

 

[jimbo]

I think XP looks for boot image on the C drive and that is looking for
the old D drive not the new drive. With the new D drive installed try
booting from your WinXP CD go into repair XP and run fixboot. If that
doesn't fix the problem then you'll need to boot the XP CD go into install
mode and then repair the installed XP.

When I clone a drive I use the drive vendor's utility to make a
clone of the drive.

Did that. Fixboot does not fix the proglem. And Install does not give
an option to repair, only to do a new install. So, for some reason,
the Ghost clone is not being recognized as a WinXP installation,
although it is being recognized as a Windows installation of some kind.

jimbo

 

[jimbo]

jimbo wrote:

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message
saying the drive needs to be checked and it goes through three
chkdsk checks, all of which pass, then it reboots and the same thing
happens again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a
warning message about another OS being there and that it is a bad
idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo




So far it looks like you did everything right, which would lead me to
suspect that there might be something wrong with the new drive, or
the BIOS has the disk configured incorrectly. It's been awhile, but
does Ghost have an option to verify the contents of the cloned
drive? If it does I would use it to see if it checks out. If you
have Partition Magic, you can use it to check the new drive. It
should be able to detect any partition or BIOS configuration errors.

Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any partitions
on it.

Suggestions?

jimbo

Well, Partition Magic not liking the partition is disturbing. But, for now,

I see above you say you put the drive in a USB enclosure and cloned it.
I'm not concerned with that particular clone attempt but want to know if
you've had the new drive in the machine, regardless of the interface,
with your existing XP system running. And if you HAVE then it's been
'installed' by XP, given a unique GUID, and assigned a drive letter;
which will be faithfully copied to the new drive when you do a clone so
it will not be a 'new' drive when booting from that clone but will be
whatever letter it was assigned, so it won't be assigned the missing
'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which letter
the two old drives are assigned. You are assuming the win98 boot drive
is c? So XP is installed on D and SAYS itself that D is it's system
drive? I.E. the XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the
same order, you need to get the new drive back to 'virgin' status. And
the easiest way to do that is put the new drive as master on the primary
IDE port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with a
Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the
win98 master, and see if it boots up right (while crossing fingers that
it detects the drives in the original order).

Yes, Win98 is on "C" and WinXP is on "D". And "C" partition is on the
HD jumpered as master and is at the end of the ribbon cable and "D"
partition is on the HD jumpered as slave and is on the middle of the
ribbon cable.

Thanks for all of the help and suggestions. I will be away for a day,
so I will reply again when I get back and have a chance to do some
more work on this problem.

jimbo

 

[David Maynard]

Ed Coolidge wrote:

jimbo wrote:

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message
saying the drive needs to be checked and it goes through three
chkdsk checks, all of which pass, then it reboots and the same
thing happens again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a
warning message about another OS being there and that it is a bad
idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo





So far it looks like you did everything right, which would lead me
to suspect that there might be something wrong with the new drive,
or the BIOS has the disk configured incorrectly. It's been awhile,
but does Ghost have an option to verify the contents of the cloned
drive? If it does I would use it to see if it checks out. If you
have Partition Magic, you can use it to check the new drive. It
should be able to detect any partition or BIOS configuration errors.




Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any
partitions on it.

Suggestions?

jimbo

Well, Partition Magic not liking the partition is disturbing. But, for
now,

I see above you say you put the drive in a USB enclosure and cloned
it. I'm not concerned with that particular clone attempt but want to
know if you've had the new drive in the machine, regardless of the
interface, with your existing XP system running. And if you HAVE then
it's been 'installed' by XP, given a unique GUID, and assigned a drive
letter; which will be faithfully copied to the new drive when you do a
clone so it will not be a 'new' drive when booting from that clone but
will be whatever letter it was assigned, so it won't be assigned the
missing 'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which
letter the two old drives are assigned. You are assuming the win98
boot drive is c? So XP is installed on D and SAYS itself that D is
it's system drive? I.E. the XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the
same order, you need to get the new drive back to 'virgin' status. And
the easiest way to do that is put the new drive as master on the
primary IDE port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with
a Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the
win98 master, and see if it boots up right (while crossing fingers
that it detects the drives in the original order).

Yes, Win98 is on "C" and WinXP is on "D". And "C" partition is on the HD
jumpered as master and is at the end of the ribbon cable and "D"
partition is on the HD jumpered as slave and is on the middle of the
ribbon cable.

I'm apparently not being clear. "C" and "D" are letters that Windows
assigns and the two flavors of Windows don't so it the same way. So, when
you simply say "C" and "D" I am not sure which O.S. you're talking about.

It is specifically whether they both have them assigned the same, or
different, drive letters that I'm trying to get confirmed.

But I think the bigger issue right now is whether the new drive was
installed into XP before you did the clone, though, and get the GUID
cleaned off of it.

Btw, fixboot doesn't remove the GUID. fdisk /mbr does.

 

[jaster]

Did that. Fixboot does not fix the proglem. And Install does not give an
option to repair, only to do a new install. So, for some reason, the
Ghost clone is not being recognized as a WinXP installation, although it
is being recognized as a Windows installation of some kind.

jimbo

Maybe when you restored the Ghost image to the new drive you set as a
primary partition and not as a logical partition?

When you go through the installation menu you should select install and
you should be presented with another menu asking if you want to install or
repair the existing XP installation.

At this point in your exercise does it make sense to continue the
frustration or is it the learning process? If not learning and you know
the other software and data has been cloned to the new drive, just install
XP on the new drive. The install process "repair installation" is pretty
much the same as a new install of XP anyway except it saves
re-installation of most programs.

 

[jimbo]

Maybe when you restored the Ghost image to the new drive you set as a
primary partition and not as a logical partition?

When you go through the installation menu you should select install and
you should be presented with another menu asking if you want to install or
repair the existing XP installation.

At this point in your exercise does it make sense to continue the
frustration or is it the learning process? If not learning and you know
the other software and data has been cloned to the new drive, just install
XP on the new drive. The install process "repair installation" is pretty
much the same as a new install of XP anyway except it saves
re-installation of most programs.

Well, as I just said, that option is not given to me when I select the
WinXP install option from the first menu. For some reason, the program
is not seeing the WinXP installation. It is seeing something because
if I select istall, it gives a message about it being a bad idea to
install two OSs on the same partition.

jimbo

 

[jimbo]

jimbo wrote:

Ed Coolidge wrote:

jimbo wrote:

Still no go. I cloned again using the external USB2.0 case with
the new drive mounted. No error messages from Ghost, but when I
try to boot to WinXP using the newly cloned drive, it gives a
message saying the drive needs to be checked and it goes through
three chkdsk checks, all of which pass, then it reboots and the
same thing happens again.

And when I boot from the WinXP CD, it asks which Windows to use
and has "D:\" as the only option. "Repair" takes me to the "D:\"
prompt which doesn't provide much. "Install" doesn't give a repair
option, only a new installation and if I start that option, it
gives a warning message about another OS being there and that it
is a bad idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another
post, fails to boot.

jimbo






So far it looks like you did everything right, which would lead me
to suspect that there might be something wrong with the new drive,
or the BIOS has the disk configured incorrectly. It's been awhile,
but does Ghost have an option to verify the contents of the cloned
drive? If it does I would use it to see if it checks out. If you
have Partition Magic, you can use it to check the new drive. It
should be able to detect any partition or BIOS configuration errors.





Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any
partitions on it.

Suggestions?

jimbo




Well, Partition Magic not liking the partition is disturbing. But,
for now,

I see above you say you put the drive in a USB enclosure and cloned
it. I'm not concerned with that particular clone attempt but want to
know if you've had the new drive in the machine, regardless of the
interface, with your existing XP system running. And if you HAVE then
it's been 'installed' by XP, given a unique GUID, and assigned a
drive letter; which will be faithfully copied to the new drive when
you do a clone so it will not be a 'new' drive when booting from that
clone but will be whatever letter it was assigned, so it won't be
assigned the missing 'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which
letter the two old drives are assigned. You are assuming the win98
boot drive is c? So XP is installed on D and SAYS itself that D is
it's system drive? I.E. the XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the
same order, you need to get the new drive back to 'virgin' status.
And the easiest way to do that is put the new drive as master on the
primary IDE port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with
a Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the
win98 master, and see if it boots up right (while crossing fingers
that it detects the drives in the original order).

Yes, Win98 is on "C" and WinXP is on "D". And "C" partition is on the
HD jumpered as master and is at the end of the ribbon cable and "D"
partition is on the HD jumpered as slave and is on the middle of the
ribbon cable.

I'm apparently not being clear. "C" and "D" are letters that Windows
assigns and the two flavors of Windows don't so it the same way. So,
when you simply say "C" and "D" I am not sure which O.S. you're talking
about.

It is specifically whether they both have them assigned the same, or
different, drive letters that I'm trying to get confirmed.

But I think the bigger issue right now is whether the new drive was
installed into XP before you did the clone, though, and get the GUID
cleaned off of it.

Btw, fixboot doesn't remove the GUID. fdisk /mbr does.

Thanks for all of the help and suggestions. I will be away for a day,
so I will reply again when I get back and have a chance to do some
more work on this problem.

Okedoke.


jimbo

Well, on XP, "C" partition is Win98 and "D" partition is WinXP. On
Win98, Win98 is on "C" and Win98 can't see the "D" NTFS partition.

jimbo

 

[jimbo]

I have physical hard drive "C" with Win98 and physical hard drive "D"
with WinXP in a dual boot setup. I want to injstall a new, larger
physical hard drive "D". I have tried to follow the procedure for
cloning a drive using Norton Ghost. I disconnected the cables from "C"
and connected the new hard drive. (I set the new drive's jumper to
"master" the same as the "C" drive.) Then Norton Ghost was booted from
floppies and I cloned drive 2 to drive 1. This all seemed to OK. Then I
disconnected the new drive and changed the jumper to "slave". Then I
reconnected the "C" drive. Then I disconnected the "D" drive and
connected the new drive in it's place. Now when I boot to WinXP it fails
just after the WinXP splash screen. A blue screen with an error message
appears and the system reboots.

Any insight will be appreciated.

jimbo

Well, the next thing I will try when I get back to my desktop is to do
the fdisk /mbr from Win98. But I am very concerned about Partition Magic
not seeing any partitions on my WinXP hard drive. And the WinXP
installation CD doesn't see the WinXP installation, so it doesn't offer
an option for a "repair" installation. And another wrinkle, Windows
Explorer sees a third hard drive "G" with 0 byte size and no file
system. I have physical drives "C" 40 GB HD, "D" 40 GB HD, "E" DVD
reader and "F", DVD burner. And then this fanthom "G" drive that doesn't
show up anyplace except in Windows Explorer.

jimbo

 

[Ed Coolidge]

I was just curious. What error did Partition Magic give?
Also, have you tried installing the new drive XP with the other two? If so was
the new drive accessible?

 

[David Maynard]

Well, the next thing I will try when I get back to my desktop is to do
the fdisk /mbr from Win98. But I am very concerned about Partition Magic
not seeing any partitions on my WinXP hard drive. And the WinXP
installation CD doesn't see the WinXP installation, so it doesn't offer
an option for a "repair" installation.

I'm not entirely sure how XP determines whether there's a 'valid'
installation on a disk but since you have the boot files on C, then the
rest of the system on D, perhaps it doesn't think it's all there.

Perhaps caused by this mystery partition of yours.

And another wrinkle, Windows
Explorer sees a third hard drive "G" with 0 byte size and no file
system. I have physical drives "C" 40 GB HD, "D" 40 GB HD, "E" DVD
reader and "F", DVD burner. And then this fanthom "G" drive that doesn't
show up anyplace except in Windows Explorer.

jimbo

That could be the problem. If the existing D drive has some sort of
'mystery' partition on it then XP could be assigning the drive letters
differently than you expect when the new drive comes up.

Try doing a partition to partition copy, not the 'whole (old) drive'. You
can still tell it to make the new partition fill the new drive so it's one
big partition.

Or do you have one of those CD emulator software packages installed?