We did a custom wimboot that looks for the image in /SMS/Boot/Boot.sdi folder if not populated by an INITRD. Maybe something to look into. Just realized I haven’t uploaded this to the ipxe.git, will try to get that done ASAP.
Same with the boot fonts, which are always present in any media. Think Michaels issue with that was that the code change was duplicate for BIOS/EFI. As per the BCD, even if we did something to use vanilla BCD if not provided, that could make troubleshooting hard when a custom BCD (We generate ours on the fly) were not provided, causing issues down the line. //A -----Original Message----- From: ipxe-devel-boun...@lists.ipxe.org [mailto:ipxe-devel-boun...@lists.ipxe.org] On Behalf Of Vasyl Melnyk Sent: den 21 juni 2016 00:56 To: Michael Brown <mc...@ipxe.org> Cc: ipxe-devel@lists.ipxe.org Subject: Re: [ipxe-devel] wimboot improvement > Are those files present: > > a) in the standard Windows installation .iso images for Win7/8/8.1? > > b) in the standard Windows installation .iso images for Win2008/2012? > > c) in standard WinPE images created by the WAIK or WADK? > > Michael After doing some research I found that those files are present in boot.wim in all standard Windows installation .iso images for windows 7, 8, 8.1, 10, server 2008, and 2012 but they are not present in standard WAIK winpe.wim. Therefore, a) yes b) yes c) no but Win10PESE constructor from theoven.org adds those files if "file copy" setting set to "SmartFull" or "Full". My custom win10pe was built that way. _______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel _______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
