rom-o-matic js error

[cckp]

I think there's a little spelling mistake in this file:
https://rom-o-matic.eu/js/ui.js

line 23:

var options = '<option value="all" selected>all-drivers</option>\n<option valeu="undionly">undionly</option>\n<option value="undi">undi</option>';

valeu ?

I think it must be "value"

p.s.s does wimboot support booting x86 pe under UEFI now? (using bootia32.efi, not bootx64.efi)

[robinsmidsrod]

You should report that problem here: https://github.com/xbgmsharp/ipxe-buildweb/issues

I'm not sure about your wimboot question. But with the newest wimboot it should extract the correct version of bootmgr.exe (or bootx64.efi) from boot.wim automatically. What kind of error do you see if you try to use a 32-bit boot.wim on a 32-bit UEFI system? (you should use the pause cmdline argument to wimboot to see details).

[cckp]

nothing special

only two line error:
Could not boot: Error 0x7f048283 (http://ipxe.org/7f048283)
Could not boot: Error 0x7f048283 (http://ipxe.org/7f048283)


http://ipxe.org/7f048283 ：

Error: Could not start image

(Error code 7f048283)
Possible sources

This error originated from one of the following locations within the iPXE source code:

image/efi_image.c (line 234)


script:
kernel ${base}/wimboot224 pause

initrd ${base}/efi/boot/bootia32.efi
initrd ${base}/efi/microsoft/boot/bcd
initrd ${base}/boot/boot.sdi
initrd ${base}/sources/boot.wim

imgstat
prompt

boot

--

[mcb30]

(2014-09-21 07:22)cckp Wrote:  p.s.s does wimboot support booting x86 pe under UEFI now? (using bootia32.efi, not bootx64.efi)

Yes, but you will (for now) have to use the 32-bit UEFI build of wimboot, which is available as the prebuilt "wimboot.i386" binary in the wimboot source tree.

You can use iPXE's ${buildarch} variable to automatically select the correct version:

Code:

kernel wimboot.${buildarch}

This limitation will go away when iPXE gains native bzImage support under UEFI (at which point I can release a single wimboot binary which simultaneously supports 32-bit BIOS, 32-bit UEFI, and 64-bit UEFI).

Michael

[cckp]

tried wimboot.i386 , now there's no previous 0x7f048283 error
but there's another issue:

Windows Boot Manager
Windows failed to start. A recent hardware or ...
file
File: \efi\microsoft\boot\BCD
Status: 0xc000000d
Info:The Boot Configuration Data for your PC is missing or contains errors.

both 4 files are from windows DVD.
and can boot from PXE if boot file set to bootia32.efi.

initrd ${base}/bootia32.efi
initrd ${base}/boot/bcd
initrd ${base}/boot/boot.sdi
initrd ${base}/sources/boot.wim

[mcb30]

(2014-09-23 03:42)cckp Wrote:  tried wimboot.i386 , now there's no previous 0x7f048283 error
but there's another issue:

Windows Boot Manager
Windows failed to start. A recent hardware or ...
file
File: \efi\microsoft\boot\BCD
Status: 0xc000000d
Info:The Boot Configuration Data for your PC is missing or contains errors.

I finally got around to building a 32-bit UEFI VM to test in, and was able to reproduce this issue.

The problem was a missing compiler flag for the 32-bit build. Now fixed and released as v2.3.0.

Thanks for finding this!

Michael