Seems an eternity ago I did a two 2K migration from old to new machine, but was actually less than two weeks. I got the images transferred, the boots working, but paths to components in the registries of the two old systems are now all stale, and CCleaner shows dlls that are "missing" by the hundreds. The partitions are maybe 50 percent functional.
I'm looking seriously at MS Virtual PC 07 as an alternative. But to paraphrase old Bones McCoy, "Damit Jim, I'm a programmer, not an OS guy." I'm on thin ice here, so here are my dumb questions:
All the discussion I find on MS and sites like eHow describe fresh install of OS on the virtual machines. Is implementing an image of an existing installation a simple variant of that?
Will the virtual machine boot as though it is mapped to an "original" drive? That is, would my current 2K, with registry entries pointing to a D drive, think that it is a D: drive? Or am I missing something basic, such as that the virtual machines don't boot, you just run them?
What about drivers? Getting the 2K images to play nice with the new chipset was not trivial, and the 2K repair didn't get it all right. Would not that same circle of Hell remain in the virtual machine approach?
Thanks for any help.