Discussion:
[ipxe-devel] Using wimboot with iPXE to boot Windows PE via HTTP
DPN
2013-02-27 12:19:35 UTC
Permalink
Hello.

I am experiencing some difficulty with using wimboot with iPXE to boot
Windows PE via HTTP.

I have 2 machines.

Machine 1 is a laptop with the following installed:
Windows 7
IIS (default settings)
Tftpd32 running dhcp server only
A directory named "/inetpub/wwwroot/win7/" with the following files:
bootmgr
BCD
boot.sdi
boot.wim
boot.ipxe
wimboot

Machine 2 is a Desktop set up for PXE booting. I am using an image of iPXE
on CD to boot from.

On machine 2, I press "ctrl+b" to get the prompt and then enter the
commands:
dhcp
"boot http://my.web.server/<path-to-boot.ipxe-file>boot.ipxe"
(without quotes)

I followed the steps in the wimboot section and am getting a "Connection
timed out" message after I type:
"boot http://my.web.server/inetpub/wwwroot/win7/boot.ipxe"

Am I typing in the 2nd command correctly ?

Does the "Timed Out" message mean the script file "boot.ipxe" was partially
read before the time out OR that the script file "boot.ipxe" could not be
accessed ?

Cheers
Dee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20130227/5e9911a0/attachment.html>
Malte Starostik
2013-02-28 14:07:41 UTC
Permalink
Post by DPN
IIS (default settings)
"boot http://my.web.server/inetpub/wwwroot/win7/boot.ipxe"
^^^^^^^^^^^^^^^^

Shouldn't that be http://my.web.server/win7/boot.ipxe?

Cheers,
Malte
Michael Brown
2013-03-01 17:11:57 UTC
Permalink
Post by DPN
On machine 2, I press "ctrl+b" to get the prompt and then enter the
dhcp
"boot http://my.web.server/<path-to-boot.ipxe-file>boot.ipxe"
(without quotes)
I followed the steps in the wimboot section and am getting a "Connection
"boot http://my.web.server/inetpub/wwwroot/win7/boot.ipxe"
Am I typing in the 2nd command correctly ?
Just a quick check: what are you actually typing? In particular,
"my.web.server" is placeholder text; you're supposed to replace that
with the DNS name (or IP address) of your actual web server.

Michael
Duane Voth
2013-03-20 21:22:42 UTC
Permalink
I'm also having wimboot troubles. My ipxe script is:

#!ipxe
kernel tftp://192.168.0.1/wimboot/wimboot
...

but my error message is:
...
tftp://192.168.0.1/wimboot/wimboot... ok
Could not select: Exec format error (http://ipxe.org/2e008001)
Could not boot: Exec format error (http://ipxe.org/2e008001)

I'm using the wimboot in
http://git.ipxe.org/releases/wimboot/wimboot-latest.zip. Is wimboot able
to execute in both uEFI and Legacy mode? I don't see a uEFI specific
version of wimboot. Or perhaps http://ipxe.org/wimboot is not meant for
uEFI?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20130320/2839d450/attachment.html>
Michael Brown
2013-03-21 01:08:04 UTC
Permalink
Post by Duane Voth
#!ipxe
kernel tftp://192.168.0.1/wimboot/wimboot
...
...
tftp://192.168.0.1/wimboot/wimboot... ok
Could not select: Exec format error (http://ipxe.org/2e008001)
Could not boot: Exec format error (http://ipxe.org/2e008001)
I'm using the wimboot in
http://git.ipxe.org/releases/wimboot/wimboot-latest.zip. Is wimboot able
to execute in both uEFI and Legacy mode? I don't see a uEFI specific
version of wimboot. Or perhaps http://ipxe.org/wimboot is not meant for
uEFI?
There's no support for wimboot in UEFI at present. There is a lot of work
currently going in to improving iPXE's UEFI support, and wimboot is likely to
receive a UEFI upgrade as part of this.

Michael

Loading...