I have 2 old-style MBR partitions (non-GPT, non-EFI):
- An "active" partition containing
Windows 7 OS
and itsbootmgr
- the Windows Boot Manager and its BCD.. - The second partition contains an exotic non-Windows OS, which has its own bootloader code in its Partition Boot Record (PBR/VBR) - the 1st sector of the 2nd partition (512 bytes).
I can successfully boot the Exotic OS through the Windows7's Boot Manager (bootmgr) by creating a Boot Menu entry with the following steps:
Copy the first sector of the Exotic OS' partition into the file named `exotic.bin` in the Windows7's filesystem.
Execute:
bcdedit /create /d ExoticOS /application bootsector
bcdedit /set {**guid**} device partition=c:
bcdedit /set {**guid**} path \exotic.bin
However, this method of booting is imperfect because the Exotic OS often updates its own boot sector (in the 1st sector of its own partition) and then the file exotic.bin
becomes outdated.
I tried:
bcdedit /create /d ExoticOS /application bootsector
bcdedit /set {**guid**} device partition=\Device\HarddiskVolume2
...and these commands executed successfully, but I do not know how to specify the 1st sector number on this partition.
QUESTION: How to instruct the Windows Boot Manager (bootmgr) to load & execute the Exotic OS' boot sector, DIRECTLY from the 1st sector of the 2nd partition - not from the outdated copy exotic.bin
?