Re: Norton Ghost 2003 cloned disk crashes when booted
- From: "Anna" <myname@xxxxxxxxx>
- Date: Thu, 7 Dec 2006 09:37:55 -0500
"kimwal" <kim.walden@xxxxxxxxx> wrote in message
news:1165492141.935065.9840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Anna:
Thank you very much for your long and detailed answer.
Regarding Ghost 2003 I already used a bootable CD and did perfrom the
steps you describe below.
(Since I just bought a full license for Ghost 10 and downloaded it
electronically, I assumed I would be entitled to the old Ghost 2003
also, but couldn't find a way to download it from Symantec's web pages,
and the only phone number I could find to call Symantec in Sweden had a
$40 charge per call (!!). So what I did was borrowing a bootable CD
from the vendor who put my computer together.
By the way, it is a silent computer built into a Zalman TNN 500AF
cabinet using heatpipe technology instead of fans, which makes it
totally noiseless. The motherboard is ASUS P5B Deluxe/WiFi-AP, Intel
P965 Chipset, 1 Intel Core Duo Extreme processor).
The only difference from the interface you describe below was that a
USB mouse was enabled, so I could click instead of moving with the
tab-key.
Other than that I did exactly as you describe, taking the extra
precaution to actually delete the partitions on my target disk before
starting the Ghost procedure, not to leave the slightest risk of
choosing the wrong source or target disk during the clone.
I then connected my source disk (same type and size as the built-in
internal disk, both brand new) to the SATA 6 socket on the motherboard
(with the internal disk connected to SATA 1) and the cable for the
source disk sticking just outside the cabinet so the source disk could
rest on a box with the cabinet door slightly ajar, using an ordinary
table fan for temporary cooling of the source disk.
Since I was going to boot the cloned disk by just disconnecting the
source drive and switching to the internal drive, I did leave my usual
UBS periferals, such as scanner and printers and USB-hubs as they were
(no USB disks attached though), the idea being that if Windows found
all external units (except the source disk) in the same place as when
the clone was done, everything would be fine when the clone was booted.
Reading your final remarks makes me wonder if this could be the
problem. Should I rather disconnect EVERYTHING except the two disks,
the keyboard and the mouse, before doing the clone, and then
immediately boot the clone and after a (hopefully) successful startup,
adding the periferals one-by-one and let Windows detect them anew?
As you mention, I have sometimes had messages like "Your system
settings have changed. Do you want to restart your computer now?".
However, since the crash leading to the message "Generic Host Process
for Win32 services has encountered a problem and must terminate" always
occurs, I have never gotten as far as being able to do a clean restart.
On the other hand, why would leaving other equipment attached during
cloning and subsequent reboot of the clone, make any difference?
If the cloned disk is an exact copy of the source disk, then how is
booting the clone with all external devices attached (except the
disconnected target disk) different from just booting the source disk
one more time with everything attached (except the disconnected source
disk), which obviously works. How is Windows even able to tell the
difference?
There is something I don't understand here (actually, there are many
things I do not understand)..
Do you have any more clues in light of this message?
Best regards,
-- KW
kimwal:
Insofar as deleting the partitions on your destination (target) HDD prior to
the disk cloning operation, this is unnecessary. While there's no harm in
doing so, there is no need to do so.
Similarly, there is no need to disconnect any peripheral devices, e.g.,
printer, scanner, either prior to or subsequent to the disk cloning
operation. As I've indicated in the step-by-step instructions for using the
Ghost 2003 program, it's important that *only* the HDDs that will be used in
the disk cloning operation be connected - no other *storage* devices such as
zip drives, flash drives, etc. should be connected.
And most important - immediately following the disk cloning operation the
source HDD should be disconnected from the system and the initial boot to
the destination HDD (the recipient of the clone - we're assuming it's an
internal HDD) be performed with *only* that HDD connected. (If the recipient
of the clone was a USB/Firewire external HDD there would be no need to
disconnect that device).
You mention you've been getting that "Generic Host Process..." error message
but it's not clear to me if this message is a result of the disk cloning
problem you've been experiencing or whether this message appeared on your
day-to-day working HDD *prior to* the disk cloning operation. If the latter,
might this account for the problem you've been experiencing? On the other
hand if the message appeared on only the newly-cloned HDD *following* the
disk cloning operation then obviously something went awry as a consequence
of the disk cloning operation.
Just to confirm we're "starting on the same page" as it were...
1. Your source HDD, presumably your day-to-day working HDD, boots without
incident and functions without any problems?
2. You've no reason to believe one of your HDDs is defective in any way?
3. You've properly connected your source & destination disks so that the
Ghost program correctly detects both?
4. The disk cloning process proceeds smoothly and without incident?
5. Immediately following the disk cloning operation you disconnect your
source HDD and make the initial boot *only* with the destination HDD
connected?
Hopefully, you've answered "yes" to all the above. If so, I really can't
explain why you're experiencing the problem you describe.
Anna
.
- Follow-Ups:
- References:
- Norton Ghost 2003 cloned disk crashes when booted
- From: kimwal
- Re: Norton Ghost 2003 cloned disk crashes when booted
- From: Anna
- Re: Norton Ghost 2003 cloned disk crashes when booted
- From: kimwal
- Norton Ghost 2003 cloned disk crashes when booted
- Prev by Date: Re: Event ID - DHCP error
- Next by Date: Re: How can I sort my favourites by modified date?
- Previous by thread: Re: Norton Ghost 2003 cloned disk crashes when booted
- Next by thread: Re: Norton Ghost 2003 cloned disk crashes when booted
- Index(es):
Relevant Pages
|
