NOTE: Not working fine yet, but chainloading to grub2 first, then it can can be called, and we get MS Boot Menu. The standard MS Windos: /EFI/Microsoft/Boot/bootmgfw.efi > Not working fine yet, see NOTE.Grub4dos for UEFI: On \EFI\grub\menu.lst there are entries to chainload to: grub4dos for UEFI: /EFI/Boot/boot圆4_g4d.efi.The standard MS Windos: /EFI/Microsoft/Boot/bootmgfw.efi.Grub2: On \grub\grub.cfg there are entries to chainload to: grub4dos for UEFI: \EFI\Boot\boot圆4_g4d.efi > Created using BootIce.Grub2: \EFI\Boot\BOOTX64.EFI > Created using BootIce.The standard MS Windos: \EFI\Microsoft\Boot\bootmgfw.efi (unmodified). ![]() The second HD (MBR formated too) first primary partition is FAT-32 for UEFI booting, by means of BootIce I created 2 additional entries so now using the boot override key (F8) there are 3 options to boot on UEFI ![]() The first HD first primary active Partition is NTFS for MBR booting Win7, Win10 and several VHDs, ISOs & WIMs files, that can be ran by means of Win bootmgr, grub4dos or agFM. I was thinking in chainloading to Ventoy from grub4dos or grub2, not in installing it as the main bootmanager and loose al info on one of the the internal HDs, in fact on this PC I have 2 internal HDs, both MBR formated. ![]() Thanks for your answer, but ufortunatelly it is not what I would like to do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |