![]() ![]() If the bcdedit.exe and BootICE utilities had a * nix alternative, the entire process of deploying the system could be done in general under Linux. Instead of the installation disc, you can use WinPE-based bootable media. At the same time, we need the installer functionality in general to run the setup program for the BCD repository of the bootloader configuration. You can install the system both in the HDD section and on the VHD. The method works for the case of Windows versions 7/8 / 8.1 / 10, as in the case of the MBR + BIOS of the system, so in the case of EFI + GPT. And it is based on the Windows installation technology that we have in its distributions starting with the "seven". don't use the standard installer ?! Well, or almost never use. There are no options in the settings of the regular installer to customize the bootloader installation process. ![]() So the GBUB functionality still has to be restored. ![]() In the case of EFI, there is no danger of rewriting MBR, but there is one nuance that I personally don’t like - the Windows installer in EFI mode does not overwrite the disk sectors with its code, but redefines NVRAM by slipping the path to its bootloader there. Surely almost every user of Linux OS and Windows OS, and I mean precisely those who, for a number of reasons, have both systems installed, the question arose from time to time: “Is it possible, damn it, to come up with a way, using Which could install these systems in any order? Without spoiling the bootloader settings? ”After all, if we install Windows first and then Linux, everything is fine - a Linux bootloader (for example GRUB) usually picks up bootmgr. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |