The rest of the Windows boot happens just as it would if grub hadn't been there. When you select that, grub loads bootmgr and then gets out of the way. grub gives you a menu that includes "Windows boot manager". With grub installed, EFI loads grub instead. Normally your machine's firmware (EFI, looks like) would load bootmgr.
For XP and earlier the program that displays the menu is ntldr, and the menu is defined by a text file boot.ini.) When you select a Windows version from the BCD menu, bootmgr loads and runs winload.exe, which loads the rest of Windows from the drive. Early in the Windows startup sequence, bootmgr displays the Windows boot menu as you see in your second screen. It is displayed by bootmgr, which came with Windows. Your second screen is not being displayed by EasyBCD. (n.b.: The BCD is actually a registry hive, just like the "system" or "software" hive, but it is not normally loaded while Windows is running.)īut even after EasyBCD is installed, it does not establish any new "Windows bootloader".
EasyBCD lets you modify Windows' boot configuration database (BCD) more easily than with Windows' built-in tools. It is merely a GUI tool that you can use once Windows is booted - a replacement for the command-line tool bcdedit and for the "boot" tab in msconfig. If nothing else, maybe this answer will prod someone who knows better into answering.įirst, EasyBCD is not the Windows bootloader, and it does not install a Windows bootloader. I have little familiarity with Linux or grub, but since you have had no answers in months, I'll try to answer based on what I know about the Windows boot environment.
0 kommentar(er)
