New answers tagged

2

The names bootx64.efi and bootia32.efi refer to the EFI fallback boot loader program. This program can be anything -- GRUB, the Windows boot loader, an EFI shell, malware, etc. Thus, you should not search for a program by that name; rather, you should search for a program by its actual name (GRUB in your question) and rename it to EFI\BOOT\bootx64.efi or EFI\...


0

Just have been there too (where you are right now) And if you tablet is a Toshiba 10"... we are brothers in arms... ;-) Just add this entry to your GRUB2 menu menuentry "Windows 7" { insmod part_msdos insmod ntldr insmod ntfs ntldr (hd0,msdos1)/bootmgr }


0

Grub is definitely more complicated in most respects to bootmgr, but it also offers far more capabilities as well, like a very capable and customizable GUI front end. It CAN boot all Windows OS variants via chainloading as pointed out by terdon, but a Windows boot loader of some type is always required, such as ntldr and bootmgr. Grub just invokes them to ...


0

From the TrueCrypt encryption scheme, system volume header resides at the end of the volume, and should still be there, even if you have overwritten the boot loader. The first 512 bytes of the volume (i.e., the standard volume header) are read into RAM, out of which the first 64 bytes are the salt (see TrueCrypt Volume Format Specification). For ...


0

I found the answer on how to do this: 1) Download the source for the latest version of grub2 from git: git clone git://git.sv.gnu.org/grub.git cd grub 2) Graft the "grub-extras" source code into the grub2 source tree: git clone git://git.sv.gnu.org/grub-extras.git 3) Edit autogen.sh to add grub-extras into the build by adding this: export ...



Top 50 recent answers are included