Michael Solomon (MS-MVP Windows Shell/User) wrote:
The problem occurs when you try to boot the slave, is that correct? Even if
you change the slave to the master, the former slave drive has a cloned
image from a different hard drive of an OS installation that was installed
while the slave drive was not installed. I'm not sure if even having it
installed would make a difference but the error you mention is typical of
trying to image to a different computer than the one on which XP was
originally installed.

I can only deduce from that and what you have described and the fact the
slave hard drive was not connected to this computer when the OS was
installed that it is being seen as a different computer.

No, that is not correct, Michael.
I have a hard drive.
I make a drive image of it.
That image happens to be on a different hard drive,
but it could just as well have been on a set of CDs.
I want to make an operating system out of that
image. You've stated that the error I mentioned is
typical of trying to image to a different computer than the
one on which XP was originally installed.

You are implying that no error would occur if I put
the OS back on the 'computer' where it was. That does
not make sense to me, because Drive Images and Ghosts
are used daily in cases where a drive fails altogether
and the Ghost or Dive Image is used to recreate the
system on a totally new drive. I don't think the
instructions imply any restrictions on the physical
medium to which the Image is restored.

I think that Sharon or somebody gave us a different
line of reasoning, that D-I can't handle this complicated
an MBR, one with a choice of OS or RC. That's why I asked
you to help me restore my original master OS to the
condition where, in boot-up, it acts as though there is
no such thing as a Recovery Console. That's the way it was
when you helped me install the RC.

--
William B. Lurie