Ok guys let's figure this out: how do I find where the windows install iso stores it's bootloader code, because that's what I need to find. Afaict they basically nuked the hell out of iso9660 for windows 10 bootable CDs, but the bootloader is there somewhere.
-
Except that the windows boot iso does not seem to have anything resembling a file structure and I am a novice at PC bootchains
It definitely has a file structure (at least a recent Windows Server 2016 image I'm looking at does). Try 7-zip to extract the ISO, it usually knows how to pull out El Torito images IIRC. For my image the EFI floppy images wind up at efi/microsoft/boot/efisys[_noprompt].bin
-
-
I think the way 7-zip handles it is that if the El Torito boot images are *not* referenced from the ISO9660 filesystem they wind up in a '[BOOT]' pseudo-directory, but if they *are* referenced then they show up under the respective filename.
-
For example, an Arch Linux ISO image has both an unreferenced BIOS mode isolinux boot entry ([BOOT]/1-Boot-NoEmul.img) and an EFI FAT image that sits at EFI/archiso/efiboot.img, as well as EFI/boot/bootx64.efi directly in the ISO fs. Windows ISOs seem to always have file entries.
End of conversation
New conversation -
-
-
Dude see newest tweet, didn't need infodump just needed different machine.
-
Yeah, sorry, I saw it after the replies. Weird, what tool were you using to extract the contents?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.