Norton Ghost / XP problems...

[RJK]

A friends just phoned me, I'll try to relay what he's told me but, it may
not make much sense because I've never used Norton Ghost, I use Powerquest.
I tried reading up on Norton Ghost but, all I could find was talk about
creating image files on cd, and there was mention of two floppies required /
prepared before undertaking any restoring any "ghost" images.

His "old" hd had drives c: d: e: f: XP on NTFS living on c:
He hooked on an extra slave drive and "ghosted" the "old" hd to the slave
hd.

Now when he boots from the new drive, XP is not happy because it thinks it's
on drive g: (that was the gist of his message)

Is this a simple repair console fixboot /fixmbr or has he got to edit
ascii boot.ini , or goodness knows what else ?

Any clues gratefully received.

regards, Richard

 

[RJK]

....perhaps he meant that he'd used "clone" in Norton Ghost, am currently
scouring the web for "procedures" using Norton Ghost.

regards, Richard

 

[Me help U?]

....perhaps he meant that he'd used "clone" in Norton
Ghost, am currently

scouring the web for "procedures" using Norton Ghost.

Try going over to the Symantec site & their forums.

I'm going to guess that he has both the original C:
partition and his new ghosted partition hooked up at the
same time.

The cloning / ghosting probably copies the hard drive
serial number (which is just stored in the first sector),
so now you have a computer with the same ID number.
Windows (and any OS) can get confused by that.

Fixing it would requiring going in with a sector editor
(or some comparable utility, which exist but I can't
remember where) to change the seial id on the drive to
something new.

That's all I can think of right off hand.

 

[RJK]

Thanx for that but, I did cover that point while I was talking to him, he
disconnected the "old" hard disk a soon as "ghost" or "clone" or whatever he
did to it, finished.

I'e currently intirgued by the terrific number of people out there who have
used fixboot /fixmbr from the repar console, and who have ended up with a
brand new FAT !

http://www.tek-tips.com/gpviewthread.cfm/qid/308210/pid/528/lev2/7/lev3/50
made me smile !

regards, Richard

 

[RJK]

....just had another chat with him and his new cloned drive will boot up and
pass the black XP pro screen, and up to the pale blue one, where it then
hangs. His XP pro is having a problem thinking that his two partitions on
the new drive are g: and h: where the first one should be c: I suppose
....liek it used to be on his source drive b4 he ghosted it.

regards, Richard

 

[NFJimc]

I just added a new HD also, and man oh man what problems I
had. My original drive is set up as C & D, with my CDR as
F and my CDRW as G. First I tried the utility that came
with my WD HD to clone it and that didn't work. Kept
getting the dreaded NTLDR Not Found message. WD was no
help. I then went out and purchased a program called Drive
Clone. Same problem. I then obtained a copy of another
cloning program...same problem. As a last resort a friend
of mine told me to try imaging the drive using Ghost. I
was about to try that but noticed that it did provide for
cloning either a partition or a drive. Well I cloned the
drive tried booting from it as a single primary and bingo
away it went. Hooked up my old drive as slave and no
problems. My BIOS automatically detected the drives and
reassigned them the proper letters. My new drive is now C,
D and E, (3 partitions) and my old drive is now H and I.
My only suggestion is to make sure that his BIOS is set up
to auto-detect the drives, otherwise he may have to go in
and manually reassign the letters. Good luck.

 

[RJK]

http://fdisk.radified.com/fdisk_02.htm
Looks like I'll make him a Partition Magic 6 boot disk - perhaps Drivemapper
will get him started.

regards, Richard

 

[Me Help U?]

Thanx for that but, I did cover that point while I was
talking to him, he

disconnected the "old" hard disk a soon as "ghost" or "clone" or whatever he
did to it, finished.

Then the only thing left that I can think of is that the
new drive is still hooked as the 'slave' and the old drive
is still 'master'.

So XP is reading all the old partitions first and then
assigning the new drive the last partition.

So, make the new drive 'master' and the old one 'slave'.

That's the last idea I have. Sorry.

 

[Harry Ohrn]

I do this often. Connect old drive and ensure it boots properly. Shutdown.
Connect new drive as Master and recoonet old drive as Slave. Boot with a
Ghost floppy and select Local->Disk->Disk. Ensure that he identifies the
Source correctly as the "old drive" and Destination correctly as the "new
drive. Let Ghost do it's thing. When finished it prompts you to "Reset". Do
not rest instead Exit Ghost back to the command prompt. Shut down the
computer. Disconnect the old drive. Now start the computer and ensure it
boot to the desktop. If you want to use the old drive as slave you can
shutdown and reconnect it, reboot and then repartition and format it as
desired.

 

[Chris Holden]

...just had another chat with him and his new cloned drive will boot up and
pass the black XP pro screen, and up to the pale blue one, where it then
hangs. His XP pro is having a problem thinking that his two partitions on
the new drive are g: and h: where the first one should be c: I suppose
...liek it used to be on his source drive b4 he ghosted it.

regards, Richard

Has he tried changing the systemroot of the system in the recovery console?

 

[RJK]

Thanx for that, have passed it on to him.

regards, Richard

 

[RJK]

Thanx for that, have passed it on to him.

regards, Richard

I do this often. Connect old drive and ensure it boots properly. Shutdown.
Connect new drive as Master and recoonet old drive as Slave. Boot with a
Ghost floppy and select Local->Disk->Disk. Ensure that he identifies the
Source correctly as the "old drive" and Destination correctly as the "new
drive. Let Ghost do it's thing. When finished it prompts you to "Reset". Do
not rest instead Exit Ghost back to the command prompt. Shut down the
computer. Disconnect the old drive. Now start the computer and ensure it
boot to the desktop. If you want to use the old drive as slave you can
shutdown and reconnect it, reboot and then repartition and format it as
desired.

--

Harry Ohrn - MS MVP [Shell/User]
www.webtree.ca/windowsxp

A friends just phoned me, I'll try to relay what he's told me but, it may
not make much sense because I've never used Norton Ghost, I use Powerquest.
I tried reading up on Norton Ghost but, all I could find was talk about
creating image files on cd, and there was mention of two floppies

required

/
prepared before undertaking any restoring any "ghost" images.

His "old" hd had drives c: d: e: f: XP on NTFS living on c:
He hooked on an extra slave drive and "ghosted" the "old" hd to the slave
hd.

Now when he boots from the new drive, XP is not happy because it thinks it's
on drive g: (that was the gist of his message)

Is this a simple repair console fixboot /fixmbr or has he got to edit
ascii boot.ini , or goodness knows what else ?

Any clues gratefully received.

regards, Richard

 

[RJK]

Thanx for that, have passed it on.

regards, Richard

 

[RJK]

An extra thanx to Harry Ohrn, I spoke to Dave on the 'phone tonight, and
asked him how he got on. He said he re-did his hd "clone" with Norton," and
did not allow a reset, and all is Ok with his new, larger hd !

......do you know, when you stop and think about it, there is very HIGH
number of instances, while on the phone, and one is asking questions and
attempting to diagnose a problem, somewhere along the way ones gets an
incorrect answer, resulting in both sailing STRAIGHT past the most likely
problem. i.e. if the OS sees two active partitions at startup, registry is
destroyed. I had asked him at one point, yesterday, if he had allowed the
system to reboot with both drives connected and he said "no" ...what can
you say ?

Obviously he didn't grasp that the "reset" in Norton after the "copy"
procedure was actually a software initiated reboot ?! ...or was that just
a label prompting the user to reboot ? .....as I said I've never used
Norton Ghost, I use Powerquest.

regards, Richard

Thanx for that, have passed it on to him.

regards, Richard

I do this often. Connect old drive and ensure it boots properly. Shutdown.
Connect new drive as Master and recoonet old drive as Slave. Boot with a
Ghost floppy and select Local->Disk->Disk. Ensure that he identifies the
Source correctly as the "old drive" and Destination correctly as the "new
drive. Let Ghost do it's thing. When finished it prompts you to "Reset". Do
not rest instead Exit Ghost back to the command prompt. Shut down the
computer. Disconnect the old drive. Now start the computer and ensure it
boot to the desktop. If you want to use the old drive as slave you can
shutdown and reconnect it, reboot and then repartition and format it as
desired.

--

Harry Ohrn - MS MVP [Shell/User]
www.webtree.ca/windowsxp

A friends just phoned me, I'll try to relay what he's told me but, it may
not make much sense because I've never used Norton Ghost, I use Powerquest.
I tried reading up on Norton Ghost but, all I could find was talk about
creating image files on cd, and there was mention of two floppies

required

/
prepared before undertaking any restoring any "ghost" images.

His "old" hd had drives c: d: e: f: XP on NTFS living on c:
He hooked on an extra slave drive and "ghosted" the "old" hd to the slave
hd.

Now when he boots from the new drive, XP is not happy because it

thinks
it's

on drive g: (that was the gist of his message)

Is this a simple repair console fixboot /fixmbr or has he got to edit
ascii boot.ini , or goodness knows what else ?

Any clues gratefully received.

regards, Richard

 

[Harry Ohrn]

Glad to hear your buddy sorted it out.

--

Harry Ohrn MS-MVP [Shell/User]
www.webtree.ca/windowsxp

An extra thanx to Harry Ohrn, I spoke to Dave on the 'phone tonight, and
asked him how he got on. He said he re-did his hd "clone" with Norton,"
and
did not allow a reset, and all is Ok with his new, larger hd !

.....do you know, when you stop and think about it, there is very HIGH
number of instances, while on the phone, and one is asking questions and
attempting to diagnose a problem, somewhere along the way ones gets an
incorrect answer, resulting in both sailing STRAIGHT past the most likely
problem. i.e. if the OS sees two active partitions at startup, registry
is
destroyed. I had asked him at one point, yesterday, if he had allowed the
system to reboot with both drives connected and he said "no" ...what can
you say ?

Obviously he didn't grasp that the "reset" in Norton after the "copy"
procedure was actually a software initiated reboot ?! ...or was that
just
a label prompting the user to reboot ? .....as I said I've never used
Norton Ghost, I use Powerquest.

regards, Richard

Thanx for that, have passed it on to him.

regards, Richard

I do this often. Connect old drive and ensure it boots properly. Shutdown.
Connect new drive as Master and recoonet old drive as Slave. Boot with
a
Ghost floppy and select Local->Disk->Disk. Ensure that he identifies
the
Source correctly as the "old drive" and Destination correctly as the "new
drive. Let Ghost do it's thing. When finished it prompts you to
"Reset". Do
not rest instead Exit Ghost back to the command prompt. Shut down the
computer. Disconnect the old drive. Now start the computer and ensure
it
boot to the desktop. If you want to use the old drive as slave you can
shutdown and reconnect it, reboot and then repartition and format it as
desired.

--

Harry Ohrn - MS MVP [Shell/User]
www.webtree.ca/windowsxp


A friends just phoned me, I'll try to relay what he's told me but, it may
not make much sense because I've never used Norton Ghost, I use
Powerquest.
I tried reading up on Norton Ghost but, all I could find was talk about
creating image files on cd, and there was mention of two floppies required
/
prepared before undertaking any restoring any "ghost" images.

His "old" hd had drives c: d: e: f: XP on NTFS living on c:
He hooked on an extra slave drive and "ghosted" the "old" hd to the slave
hd.

Now when he boots from the new drive, XP is not happy because it thinks
it's
on drive g: (that was the gist of his message)

Is this a simple repair console fixboot /fixmbr or has he got to
edit
ascii boot.ini , or goodness knows what else ?

Any clues gratefully received.

regards, Richard