I have an XP-32 volume which is 10GB of a 1TB drive. It will boot when the drive is given priority in BIOS/CMOS Setup.
However, when using Disk2vhd to make a VHD of the volume (running W7-64), the result is an "internal" size of 1TB (even though not selected for inclusion, the other volumes are shown when mounted, albeit blank, and counted towards the total) thus exceeding the capacity that VirtualPC is capable of running (127GB?).
Okay, so the solution is to shrink the faux size. But first the faux volumes must be deleted but in any case the VHD cannot be mounted before first removing the original disk due to a signature conflict. Even then, it is necessary to process with VhdResizer.
However, after all that the VHD still will not boot (it loops after the Windows loading bar). Is this still a signature conflict? Does the VHD need to be created on another system and if so can it co-exist (running) together with the original disk?
However, when using Disk2vhd to make a VHD of the volume (running W7-64), the result is an "internal" size of 1TB (even though not selected for inclusion, the other volumes are shown when mounted, albeit blank, and counted towards the total) thus exceeding the capacity that VirtualPC is capable of running (127GB?).
Okay, so the solution is to shrink the faux size. But first the faux volumes must be deleted but in any case the VHD cannot be mounted before first removing the original disk due to a signature conflict. Even then, it is necessary to process with VhdResizer.
However, after all that the VHD still will not boot (it loops after the Windows loading bar). Is this still a signature conflict? Does the VHD need to be created on another system and if so can it co-exist (running) together with the original disk?
Facebook
Twitter