I imaged a Windows 2000 machine I was working on with Ghost 7 DOS
program so I could easily restore it if things went wrong. They did, so
I tried re-imaging and got a message about the machine's BIOS when I
started the re-imaging. I stupidly went ahead anyway - overwriting the
original machines Win 2000. When I booted it said the drive
configuration was a problem. Is there anything I can do? Are the images
useless? FDISK shows it's all there, and GHOSTWALKER says there is no
bootable drive!
--
David Longley

In message <2nlyYKFnK2NAFw3M@longley.demon.co.uk>, David Longley
<David@longley.demon.co.uk> writes


I found this on the web. Problem is of course, even if I had done this
first, I don't have the win 2000 CD key! What's annoying is that in my
case, the original drive has been overwritten with the cloned image!

Response Number 4
Name: ja
Date: August 13, 2001 at 08:22:33 Pacific
Subject: PC Hangs on 1st boot of Ghost clone

Reply:
To Mike, I don't know where you got the info that Ghost 7 is the only
version that is compatible with Win2k, cos ghost has been fine with
Win2k since v6.03. Allgire, I would suggest you use MS Sysprep which can
be found on the Win2k cd or v1.1 can be dl from microsoft. It's a very
small app that you run from within Win2k which will reboot your pc and
reset the sid. You then run Ghost and create your image onto your new
hd. Then reboot with your new hd and a mini setup wizard will be invoked
asking you for name, adress, cd key, etc and creates a new sid. The
problem you are having simply sounds like a hardware conflict that is
common with ghost and Win2k and is solved by using Sysprep. Win98 did
not have this problem because the 9x kernell is very different to NT.


--
David Longley

Nah, the CD key ain't your problem ... BIOS is. Solve your BIOS problem and
the machine will boot and run just fine.

I restore a Ghost image at least three times per day on a test machine and
never have a problem with it. Never.

"David Longley" <David@longley.demon.co.uk> wrote in message
news:V4bK$lBei4NAFwTu@longley.demon.co.uk...

In message <V4bK$lBei4NAFwTu@longley.demon.co.uk>, David Longley
<David@longley.demon.co.uk> writes
Thanks.

I had actually seen that. In the end, I did manage to restore the image
by using the -FDSP command line switch.
--
David Longley