Hacker News new | ask | show | jobs
by RulerOf 482 days ago
I may have written one of those dusty guides in my younger days.

>I've seen none that even hinted at making the DVD ISO a target, leading me to believe it wasn't well supported 20 years ago.

iPXE has always supported this, but the devil is always in the details.

Windows Setup has a disk-bootability-validation step that it runs before it'll let you install Windows. It checks that the firmware can actually see the drive (i.e. it was present during system boot) and understands the boot chain, looking for the ESP or MBR that will actually load Windows once Setup completes.

There's something about loading more than one disk into the iBFT[1] and hooking those disks into INT13 on a BIOS-based system that very frequently breaks one of those checks. You try to select a disk and Windows Setup complains about not being able to verify that it's bootable.

It'd all likely work just fine on a typical UEFI system these days.

Of course, since it's Windows, there's no "I checked and it's okay please install anyway" button. But I'm pretty sure you can just apply the wim manually from the command line and install the bootloader, but I was never clear if that process implemented the driver reflection step necessary to ensure the NIC would start on boot...

It's unfortunate that Windows Setup itself isn't open-source. It'd probably have made the time I spent doing this stuff a lot more interesting.

[1]: iSCSI Boot Firmware Table is a memory structure used to pass iSCSI disks from a firmware-level software initiator to the OS-level software initiator after the kernel takes over the hardware

[2]: https://ipxe.org/wimboot

1 comments

Thanks, I skimmed some details about iBFT (mostly reading what the Linux kernel does with it) before writing the post, and came away with it likely being a difference in how things were hooked up in BIOS vs UEFI systems. Thanks for your perspective on it!