Released a maintenance buid, that expires on Sep 15, 2011. After that, we will push out v2 for testing.

This build has these changes:

(1) include another boot file "vboot-black-screen" file to be used if you are getting black screens or other boot loader problems. You need to rename this file to "vboot", read more on the readme.html file.

(2) fixed a rare vhd corruption error

Why is the XP boot loader placed on my real HDD instead of the VHD? I followed exactly the guide. I had to use the Windows 7 DVD to repair the bootloader.

Vista setup from ISO/DVD no longer fails with "CD driver missing", but fails at 76%. I checked the setuperr.log and saw this:



inside the VHD, the bootloader is also missing. So my does the updated version no longer copies the bootmgr into the VHD?

Is it possible to update grub to 1.99?
The new version has a good manual.
And maybe release a version without the hotkeys... so that you can't accidentally push those buttons?!?

Suppose I made a VHD backup of an existing Win7 install, and then want to boot Win7 from that VHD on the same PC, or simply mount the VHD after booting to an original Win7 HD. Since Windows can't tolerate several disks with the same disk ID Signature, will it try to change my original disk ID after booting from VHD, or try to change VHD disk ID after mounting it?

What will happen after that - will I be able to boot again from the original HD or VHD after its ID has been changed by Windows and will no longer match the ID recorded in that disk Windows Registry at OS install?

yes, this is very good question.

Windows doesn't allow two disks to have same disk signature, so you will have to modify it. Windows will automatically modify the signature if a conflict is discovered.

If you mount with vboot, vboot actually restores back the original signature back to vhd after disk is dismounted.

In short, you will have to modify one disk's signature, and also sync it up with the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

You can modify either the real hd or the vhd.

Thanks!

That prompted some other questions:

- If I boot to VHD by using Vboot, my original HD sig will be changed by Windows. Can Vboot return HD Sig back to original at system shutdown or next Win reboot from the HD? The reason is, many users won't be able to do it manually due to lack of skills.

- If I manually modify system HD Sig (by what means?) to avoid the collision, will I be able to boot again from that HD: all I need for that is to update the above Registry key with new Sig - how exactly?

- In that MountedDevices subkey, volume drive letters can change from boot to boot depending on number of disks present and recognized at boot time. Also mounted devices are not easy to recognize. I think, the collision question should be answered in detail in Vboot FAQ, and also such anti-collision solution should possibly be integrated into Vboot. AFAIK, Paragon BR Suite does it quite well at System Volume Restore stage onto a different HD - are there other tools doing it similarly well?