I also observed a change of the host disk signature after a boot failure
under WinXP SP3 with a BSOD 0xC000021A.

This error was raised because I added another HDD.

Using the (UUID=) syntax in grub.cfg lead to a BSOD 0x0000007B.

The solution to both errors was to adjust the values under
HKLM\System\MountedDevices and to delete the LoadOrderGroup value
from Services\vbootmp.

For the "WinXP-has-only-500MB-available"-problem I described earlier in
this thread, I found that it is triggered by the enabled onboard
graphics of the I7. Using a PCI-E card and disabeling onboard,
the memory is fully available.

yes, we noted v2 introduced a new bug on (UUID=), fixed now. Next update will contain the fix. Still investigate on the disk signature change cause. Probably, we will update the binary over the weekend.

Hi

First: I have my vboot in clean SDD without OS (just the vboot and files) and I boot right away to my vhd's like that, no problem, BUT: today I updated my vboot to vboot 2 (removed previous vboot 1.1 folder and copied vboot 2 folder to SDD root (folder name: "vboot"), also copied files "vbootldr" and "vbootldr.mbr" to SDD root as obvious, finaly I copied my grub.cfg from v1.1 with all the settings to my v2 folder), I did update all my vhd's (vbootctl update <PATH_TO_MY_VHD>) with success, it shows vboot loader screen OK, I choose my vhd (OS - W7 32bit) and it strats booting, but as it come to welcome screen it restarts automaticaly and I am again presented at vboot loader screen (blue background and white letters) - in v1.1 there wa sno such problem, so isn't it a bug??? Please, help!

are you using UUID format? if so, try to change it to (hd) format. we just discovered a serious bug on this for v2.

are you using UUID format? if so, try to change it to (hd) format. we just discovered a serious bug on this for v2.

sorry, no: I am using LABEL format