4 ms·
You can easily add a DOS/Windows/Linux bootsector as an optional bootmenu entry in Windows, but usually you will need to enable the CSM/Legacy BIOS feature of t
by fuzzfactor 6y ago
You can easily add a DOS/Windows/Linux bootsector as an optional bootmenu entry in Windows, but usually you will need to enable the CSM/Legacy BIOS feature of the mainboard if all you have is a UEFI system.
Although UEFI actually requires booting to MBR-partitioned USB drives even without CSM enabled, often this does not work due to simple engineering failure.
Also the Windows NTLDR and/or BOOTMGR, will need to be present on an Actively Bootable Marked primary FAT or NTFS volume of non-GPT partitioned drive hardware, such as floppy, HDD, CDROM, SSD, USB stick or SD card. Proper MBR and Windows VBR would be expected to be in place according to whether you were using NT5 (ntldr) or NT6 (bootmgr) at the time. Plus the target bootsector(s) (each in the form of a file) will need to be available and accesible by the WindowsNT boot process.
Desired NT5 or NT6 bootsectors can be properly placed using BOOTSECT.EXE. The resulting bootsector can then be copied to a 512-byte binary file using a disk editor or the dd command in Linux.
With NTLDR you will also need NTDETECT.COM, and a BOOT.INI file which contains the bootmenu.
BOOT.INI is a plain text file which can be edited using NOTEPAD.
With BOOTMGR you will also need a \BOOT\BCD folder/file which contains the bootmenu.
BCD is a binary file which can be edited using BCDEDIT.
Either of these Windows bootmenus is always present, but bypassed on bootup if there is only one bootentry (such as the usual single Windows default entry), or if the TIMEOUT is set for zero or too few seconds. Adding a second entry to your already-present Windows bootmenu is what makes the menu visible upon bootup.
.
Therefore adding a bare-metal bootmine option to Windows NT5 PC's (while simultaneously enabling the NT5 multiboot menu) is quite easy and straightforward:
On a regular Wxp system, copy BOOTMINE.IMG to the root of your C: volume.
Edit your BOOT.INI something like this:
[Boot Loader]
timeout=10
Default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP" /noexecute=optin /fastdetect
C:\bootmine.img="Bootmine bootsector gaming"
Note: for DOS reference, a C:\bootsect.dos="DOS on FAT32 volume" entry in BOOT.INI can be _conveniently_ abbreviated as simply C:\="DOS on FAT32 volume". IOW (on the C: volume) if the bootsector file you wish to load is named anything other than BOOTSECT.DOS, you must specifiy the filename explicitly. C:\BOOTSECT.DOS is the filename given by Windows to the automatically saved DOS bootsector when an NT system is installed over a DOS/W9x system, before the DOS bootsector is overwritten with an NT bootsector.
.
The equivalent bare-metal bootmine option on an NT6 system is quite easy and straightforward also, provided (using CSM if necessary) you have installed W10 on a traditional MBR-partitioned (not GPT) drive:
On a MBR W10 system, copy BOOTMINE.IMG to the root of your C: volume.
Using an administrative command prompt, BCDEDIT to add a bootmine entry:
bcdedit /create /d "Bootmine bootsector gaming" /application bootsector
_Windows will reply with the GUID it automatically assigned to your new bootentry:
The entry {your-new-bootmine-guid-here} has been successfully created.
_use that guid to complete your new bootentry, add it to the items displayed upon bootup, and adjust the timeout with the following commands:
bcdedit /set {your-new-bootmine-guid-here} device partition=c:
bcdedit /set {your-new-bootmine-guid-here} path \bootmine.img
bcdedit /displayorder {your-new-bootmine-guid-here} /addlast
bcdedit /timeout 10
You may also need to disable Windows SecureBoot if present for a UEFI system to work, sometimes even with CSM enabled.
To later remove the new BCD bootentry use the following command in an administrative command prompt:
bcdedit /delete {your-new-bootmine-guid-here}