Sharon F wrote:
On Wed, 02 Jun 2004 07:40:05 -0400, William B. Lurie wrote:


For one thing, I'd like
to take Recovery Console out of the picture, and not by
reducing its delay time to zero, but just remove that option.
If any of the MVPs told me how to do that, I missed it.


It was at the end of my other post to you:

"To remove the recovery console, delete the cmdcons folder from the root
(usually C and edit the boot.ini file to remove the reference to it."

You can also delete the cmldr file that is added by the recovery console
installation - also in the root folder.

William, the term image is used interchangeably for a cloned hard drive and
for an image set that is restored using the imaging software. Usually which
type of image is being discussed is noted very early in a discussion so
that both parties are on the same page. This is why I made the effort to
define the distinction at the beginning of my previous message.

Vanguard picked up on what I was trying to say and did a great job
expanding on the two different meanings. Thanks, Vanguard!

Sharon, it's indeed unfortunate that the software designer,
in PQ, chose to leave the words 'copy' and 'image' mixed
up. What they call a "drive image" is indeed a bunch of code
which their own recovery program is supposed to convert to
a clone or exact copy or duplicate of the original. Neither
they nore anybody else has made it clear to tired, muddled old
me, why that two-step capability is necessary or even desirable.

So I went back to where I was a month ago, when I tried making
what PowerQuest describes as a "copy". I installed my Slave
drive as Master and formatted it anew, as Active and Primary,
and empty. I then jumpered it as Slave, put it in Slave
position, put my Master on as Master, and used Drive Image 7.0
to "Copy One Drive to Another This copes the contents of
your Drive directly to another drive". Actually, I copied only
the first (Master) partition of my Master Drive to the Slave.

I used Partition Magic to verify that the Slave Drive contained
very close to the same number of bytes as the Master OS. I then
shut down, jumpered the Slave Drive as a Single Drive, put it in
Master position on the cable, no other drive present, and booted
up. It got to where I was when I did this same thing a month
ago, so at least it's reproducible. It booted through BIOS, to
the place where I could select XP Pro or Recovery Console, I
picked XP, and got the black Windows logo screen, and then after
the usual wait, the light blue Windows logo screen, which should
say "loading your personal settings"........and there it hangs.
So Windows copied nicely, and all my data and files and programs
and applications copied nicely, but it doesn't get to the "Loading
your personal settings" place. Those words are missing from the
light blue screen, and that's where I was when one of the MVPs
(who shall remain nameless) convinced me that I should not use
the "Drive Copy" path, that I really wanted the Image.

Well, he couldn't get me past that road block, in the XP
boot-up procedure, Sharon, maybe you can? Or maybe I need the other
piece of software that somebody just suggested here.

By the way, I searched for cmdcons folder on C:\ and can't find
it. Yes, I told it to seek hidden files. I did find it in boot.ini,
however.

--
William B. Lurie