Tried that, Geoff. Cannot get to Recovery Console. I put in the XP-CD,
rebooted. It gave me choice of going to XP or to RC. I chose RC, and
instead of finding it on the hard drive (where it was on the drive I did
the Image of), or on the CD, it stopped with message "file missing
or corrupt system32/hal.dll ......Please install a copy of that file."
Of course, it didn't tell me how to install it, even assuming I can find
in on the CD, where, if I find it, I expect it to be a ".dl_" file and
not .dll..
Bill L.

Geoffw wrote:

boot from your cd and go to recovery console from there, I
assume it recognises the new clone as the OS when you search
for it via RC

use fixmbr and fixboot

I had a similar problem and this has resolved them for me

good luck

Geoff

"William B. Lurie" wrote in message
...


I think this leads back to my discussions with, and
advice from, Michael Solomon a while back.......

Since 'solving' the problems of creating a drive image
of my master hard drive with Drive Image 7, and creating
a clone of that drive with its PowerQuest Recovery
Environment software, I've been living is a fool's
paradise. I discovered this when I went to create the
monthly Drive Image yesterday, and create the clone on
a newly purchased hard drive.

I've been living with my Master drive booting to a
choice between normal start-up and Recovery Console,
a minor annoyance because after a ten-second countdown
it goes to normal boot, automatically. No problem there.

I believe that the main part of the problem is now that
the new exact clone does not have Master Boot Record
correct, because the 'Normal Boot' path leads to the
choices of Safe Mode or Normal etcetera, and no choice
gets to anything other than a repeat of that set of
choices. If I select Recovery Console, I get a short
DOS-type message saying that file 'xxxxx.dll' is missing,
and to reload it somehow from somewhere. I suspect that
more than one '.dll' file will be in the list of what it
needs. I tried selecting Recovery Console, hoping that I
could somehow do a FIXMBR there, but I can't get to RC.

Incidentally, in running Drive Image, I've repeated the
whole image-and-recreate process, with and without the
'keep the MBR' option, with no apparent difference in
results. I've tried to solve the problem without going to
you experts, but what I've considered all logical paths
haven't solved it.

William B. Lurie










--
William B. Lurie