#16 Need a Windows 10 boot

[Todd]

ms-sys -v
ms-sys version 2.5.3

ms-sys no longer will create a bootable flash drive from both Fredora Core 25 and Scientific Linux 7.3. Also, would you include MBR/UEFI for Windows 10?

Many thanks,
-T

[Henrik Carlqvist]

Maybe the "no longer will create a bootable flash drive..." should be a bug report or support request, but if so more info is needed. Did this work before in some other environment? What exactly does the commands you are using look like? What is the expected outcome? What did you get instead?

Anyone trying to implement a new boot record for Windows 10 UEFI MBR will need the same information that is allways needed to implement a new boot record in ms-sys: Some kind of documentation describing the boot record to implement. Something like the description of boot records you can find here:
http://thestarman.pcministry.com/asm/mbr/95BMEMBR.htm

regards Henrik

[Todd]

Hi Henrik,

I am using a Kangugu Flash Blu III 8 GB stick.
https://kanguru.com/storage-accessories/flash-blu30.shtml

The command tht does not work is (user = root)
ms-sys -7 /dev/sdX and
ms-sys -i /dev/sdX

The drive was preformatted as Fat32 with its boot flag set. Only one primary partition. I used several command line utilities (fdisk, mkfs -t vfat, gparted, etc.). None made any difference.

Afterwards, it does not boot. (Not a bootable device)

I FINALLY have a bootable Windows 10 PE flash drive (made from Windows 10). I can do a "dd" of the front of it for you to look at. Just tell me how many bytes you want and starting from where (zero, I presume).

I can also send you a dd of one that does not work as well

Thank you for helping with this.
-T

[Henrik Carlqvist]

Only writing an MBR to the disk will not be enough to boot a drive. The partition with the boot flag set will also need some boot record (possible to create with flags like -2, -e or -3). Also the partition will need to contain some files that the boot record points to. Such files might have names like io.sys and msdos.sys.

A dd of a boot record will not be enough to create support for such a boot record. Information about different parts of the boot record is needed. In the case of an MBR information is needed about which part of the MBR contains the partition table. Also info about data of any other variable information like disk geometries is needed. If data didn't vary between different systems it would be easy to copy boot records by simply using dd instead of ms-sys.

regards Henrik