mcb30
commented
3 years ago Simply commenting out or omitting the lines should work and is exactly what happens in the automated test runs - see e.g. https://github.com/ipxe/wimboot/blob/master/test/testwimboot#L69-L76 for the code that generates the script. You can see the corresponding output in the test artifacts (e.g. at https://github.com/ipxe/wimboot/runs/1922794909):
wimboot v2.7.1 -- Windows Imaging Format bootloader -- https://ipxe.org/wimboot
Found initrd at [0x5c258000,0x7fef2074)
Placing initrd at [0x5c345000,0x7ffdf074)
Using qr.txt via 0x5c345078 len 0x6e8
Using boot.wim via 0x5c346078 len 0x23c93ef2
...found WIM file boot.wim
Using winpeshl.ini via 0x7ffda07c len 0x21
Using BCD via 0x7ffdb074 len 0x4000
...patching WIM boot.wim
...patching WIM header at [0x0,0xd0)
...patching WIM qr.txt at [0x23c93ef2,0x23c945da)
...patching WIM winpeshl.ini at [0x23c945da,0x23c945fb)
...patching WIM lookup.copy at [0x23c94600,0x23d35ff0)
...patching WIM lookup.boot at [0x23d35ff0,0x23d36022)
...patching WIM lookup.file at [0x23d36022,0x23d36054)
...patching WIM lookup.file at [0x23d36054,0x23d36086)
...patching WIM boot.copy at [0x23d36088,0x241df330)
...patching WIM directory at 0x23d470b0 from [0x23db1b40,0x23ddd310)
...patching WIM dir.file at [0x241df330,0x241df3d6)
...patching WIM dir.file at [0x241df3d8,0x241df47e)
...patching WIM \Windows\System32 at [0x241df480,0x2420ac50)
...patching WIM dir.subdir at [0x23d470c0,0x23d470c8)
...patching WIM length 0x23c93ef2->0x2420ac58
...found file "\Windows\Boot\PXE\bootmgr.exe"
Using bootmgr.exe via 0x53860 len 0xa3538
...extracted bootmgr.exe
...found file "\Windows\Boot\DVD\PCAT\boot.sdi"
Using boot.sdi via 0x5394c len 0x306000
...found file "\Windows\Boot\Fonts\segmono_boot.ttf"
Using segmono_boot.ttf via 0x53a38 len 0xaed8
...found file "\Windows\Boot\Fonts\segoen_slboot.ttf"
Using segoen_slboot.ttf via 0x53b24 len 0x14f04
...found file "\Windows\Boot\Fonts\segoe_slboot.ttf"
Using segoe_slboot.ttf via 0x53c10 len 0x1503d
...found file "\Windows\Boot\Fonts\wgl4_boot.ttf"
Using wgl4_boot.ttf via 0x53cfc len 0xbf60
Emulating drive 0x80
Placing initrd at physical [0x5c345000,0x7ffdf074)
Entering bootmgr.exe with parameters at 0x2df80I'd suggest adding the pause option to the command line so that you can see the equivalent output from your .wim file. You're also welcome to make your .wim available to me privately for debugging, if that's viable.
PicoMitchell
Awesome to see new releases of
wimboot, thanks so much! I'm glad to have to newquietoption for our production boot :-)I also saw "Extract BCD, boot.sdi, and standard boot font files automatically from the .wim image." in the 2.7.1 release notes, which sounds like an awesome addition. But, I am not sure how to take advantage of that or if I've encountered a bug. I tried simply commenting out my
initrdlines in my iPXE menu with theBCDandboot.sdifiles, but WinPE fails to load with an error saying that the BCD file is unavailable (photo attached).Is this a bug, or do I need to supply some argument to
wimbootfor it extract these files automatically? I double checked that theBCDandboot.sdifiles are within\Windows\Boot\DVD\[EFI & PCAT]\in mywimfile.