Quote:
" Yes, the registry says C:. However, the identification of C: with your new drive is deficient. There is a drive table in the registry, and that table doesn't include the new drive when you do the ghosting - that's logical, right? Then during boot, the system looks for c:\...userinit.exe but the drive registered as C is not there - that is the drive you removed.
Arconis may know enough to tweak the registry and fix this, kudos to them. But Ghost is doing the right thing, and it's Microsoft who are at fault. "
Bologna!!!
A clone is a clone. It copies ones and zeros from one disk to another, Bit by bit copy. Ghost is hosing up the copy period. The registry in the first disk should match the second disk bit for bit REGARDLESS of how the drive is attached during the cloning process. I have used Acronis TrueImage to clone a drive to a USB enclosure... removed the drive from the enclosure and booted from it. If what you are saying is true that would never work either..... because the drive would be " Marked " as a USB drive. Acronis is just a much better product. Ghost is just that sometimes it works sometimes it doesn't. Acronis doesn't fix anything it just does it properly to begin with. It has nothing to do with Microsoft or Windows. If it looks for anything that would be missing it would be the "G" drive, as it is now "C". This drive list is Dynamic and is refreshed at boot time, That is why you can install a drive then shut down and remove it then reboot without any ill effects.
pcgeek11