This isn't the desired behavior, I want G4D to be the first bootloader to load, so it needs to be in the MBR. I think the best way to accomplish this is to:ġ. Install and encrypt with BCVE, while first only having original Windows 10 boot code in the MBRĢ. Make a copy of the BCVE MBR with BootIce.ģ. Reinstall original Windows 10 MBR boot code by running the 'bootrec /fixmbr' command from a 10 setup ISOĤ. Create a menu.lst entry that chainloads the BCVE MBR file Install G4D by following steps 1-4 aboveĥ.

This attempt has failed, every time I try to chainload this MBR nothing happens, G4D goes to boot the entry and then hangs on a '_' cursor, no error is given. I also know that BCVE has an option to move the encrypted volume's key to either external storage or an ISO, but this seems overly complex in contrast to just chainloading an MBR image.Īm I correct in assuming that the G4D bootloader is little more than a command interpreter, that just reads the menu.lst and executes the commands line by line? If so, then wouldn't it be sufficient to write out the contents of menu.lst instead? I am not familiar with doing the commands manually. The point is that each single command may (or may not) give feedback in the form of:ġ) actual feedback from the command interpreter (such as an error or a diagnostic message)

When you use the menu.lst you have no way to know which command did what, all you can see is - maybe - the last feedback by the last command that either succeeded and provided the feedback or hanged, but you have no way to know WHICH was the last command that created the *whatever* you obtained as result of a menu.lst entry. You could enable debug or even better single-stepping however, see: The contents of menu.lst are good enough (in a request for help/assistance), as an example if one of the commands in the menu.lst is evidently wrong someone may spot the problem, but for actual experimenting and troubleshooting the approach on command line, with commands one at the time and related feedback are the best way to proceed.īesides, this way you can issue/insert 'diagnostic/lookup' commands (such as - only as an example - 'map -status' or 'set var') to see if the environment is correct, etc. It looks like BCVE doesn't install any PBR code into the C drive.

Ptedit32 download