Oliver Rath | 19 Apr 10:53 2014
Picon

cpuid-flags in cpuid.h maybe incomplete?

Hi list,

I try to test some flag in ipxe script. If i see right (depending on https://git.ipxe.org/mirror/memtest.git/blame/1abd405570a2692adcc3bef3845bfb9178a1d952:/cpuid.h), the following flag are recognized in this way:

cpuid --ext 6  = PAE Support
cpuid 26       = SSE2 Support
cpuid --ext 20 = NX Support

Is this correct?

Reffering the cpuid.h file line 166 = bit 0, line 196 = bit 31, but 166+31=197, so there seems one bit omitted, but Im not sure, that Im allowed to relate in this way.

Tfh!

Oliver

<div>
    Hi list, <br><br>
    I try to test some flag in ipxe script. If i see right (depending on
    <a class="moz-txt-link-freetext" href="https://git.ipxe.org/mirror/memtest.git/blame/1abd405570a2692adcc3bef3845bfb9178a1d952:/cpuid.h">https://git.ipxe.org/mirror/memtest.git/blame/1abd405570a2692adcc3bef3845bfb9178a1d952:/cpuid.h</a>),
    the following flag are recognized in this way:<br><br>cpuid --ext 6&nbsp; = PAE Support<br>cpuid 26&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = SSE2 Support<br>cpuid --ext 20 = NX Support<br><br>
            Is this correct?<br><br>
            Reffering the cpuid.h file line 166 = bit 0, line 196 = bit
            31, but 166+31=197, so there seems one bit omitted, but Im
            not sure, that Im allowed to relate in this way.<br><br>
            Tfh!<br><br>
            Oliver<br><br>
  </div>
Alex Davies | 17 Apr 14:10 2014
Picon

Re: serial arrow keys broken

A, B, C and D. Here I pressed the key after each word (e.g. “u”, “p”, <up arrow”):

 

iPXE> up A down B right C left D

up: command not found


The graphical console looked like the screenshot below when I entered the keys via SOL:







On Wed, Apr 9, 2014 at 11:48 AM, Peter Pickford <peter-7TcnlQJbpXVgj/lY1WyWEQ@public.gmane.org> wrote:
If you exit the menu and got to the ipxe command line what do you get when you press the arrow keys?


On 9 April 2014 03:41, Alex Davies <alex-7Vk2WWVZgQQ@public.gmane.org> wrote:
Hi All,

We had the same problem using SOL on Dell hardware.

I tried both your patch Michael and the divide by two suggested at the top of this thread, without joy.

Interestingly, pressing the arrow key does stop the countdown timer, but the menu selector does not move, so iPXE is getting something. What debug flag should I enable to see what it is getting?

The menu is working nicely with color and if I connect to the 'full console' via the DRAC, and move the arrow key, the SOL menu refreshes correctly.

Thanks!

-Alex


On Thu, Mar 27, 2014 at 2:46 PM, Michael Brown <mcb30-VUaoxwjD3yI@public.gmane.org> wrote:
On 27/03/14 08:36, Peter Pickford wrote:
The arrow keys would not work in my ipxe serial console.

The following seems to fix it but causes a busy wait while reading
escape sequences.

<snip>

Arrow keys over serial works for me.  Could you try the attached (untested) patch, which preserves the cpu_nap() while changing the ordering of events such that a keypress arriving during the cpu_nap() will be detected even if the timeout has expired?

Thanks,

Michael

_______________________________________________
ipxe-devel mailing list
ipxe-devel <at> lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel




--
Alex Davies

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail permanently.




--
Alex Davies

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail permanently.
<div>
<div dir="ltr">
<p class="MsoNormal"><span>A, B, C and D. Here I pressed the key after each word (e.g. &ldquo;u&rdquo;, &ldquo;p&rdquo;, &lt;up arrow&rdquo;):</span></p>

<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal">

<span>iPXE&gt; up A down B right C left D</span></p>
<p class="MsoNormal">

<span>up: command not found</span></p>
<p class="MsoNormal">

<span><br></span></p>
<p class="MsoNormal"><span>The graphical console looked like the screenshot below when I entered the keys via SOL:</span></p>

<div><span><br></span></div>
<div><br></div>
<div><br></div>
<div><br></div>
</div>
<div class="gmail_extra">

<br><br><div class="gmail_quote">On Wed, Apr 9, 2014 at 11:48 AM, Peter Pickford <span dir="ltr">&lt;<a href="mailto:peter@..." target="_blank">peter@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">

<div dir="ltr">If you exit the menu and got to the ipxe command line what do you get when you press the arrow keys?</div>
<div class="HOEnZb"><div class="h5">
<div class="gmail_extra">
<br><br><div class="gmail_quote">On 9 April 2014 03:41, Alex Davies <span dir="ltr">&lt;<a href="mailto:alex@..." target="_blank">alex@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div dir="ltr">Hi All,<div><br></div>
<div>We had the same problem using SOL on Dell hardware.<div><br></div>
<div>I tried both your patch Michael and the divide by two suggested at the top of this thread, without joy.</div>

<div><br></div>
<div>Interestingly, pressing the arrow key does stop the countdown timer, but the menu selector does not move, so iPXE is getting something. What debug flag should I enable to see what it is getting?</div>

<div>
<br>
</div>
<div>The menu is working nicely with color and if I connect to the 'full console' via the DRAC, and move the arrow key, the SOL menu refreshes correctly.</div>
<div><br></div>
<div>Thanks!</div>
<div><br></div>

<div>-Alex</div>
</div>
</div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">
<div><div>On Thu, Mar 27, 2014 at 2:46 PM, Michael Brown <span dir="ltr">&lt;<a href="mailto:mcb30@..." target="_blank">mcb30@...</a>&gt;</span> wrote:<br>
</div></div>
<blockquote class="gmail_quote">
<div><div>
<div>On 27/03/14 08:36, Peter Pickford wrote:<br>
</div>
<blockquote class="gmail_quote">
<div>
The arrow keys would not work in my ipxe serial console.<br><br>
The following seems to fix it but causes a busy wait while reading<br>
escape sequences.<br><br>
</div>
&lt;snip&gt;<br>
</blockquote>
<br>
Arrow keys over serial works for me. &nbsp;Could you try the attached (untested) patch, which preserves the cpu_nap() while changing the ordering of events such that a keypress arriving during the cpu_nap() will be detected even if the timeout has expired?<br><br>
Thanks,<br><br>
Michael<br><br>
</div></div>
<div>_______________________________________________<br>
ipxe-devel mailing list<br><a href="mailto:ipxe-devel@..." target="_blank">ipxe-devel <at> lists.ipxe.org</a><br><a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br><br>
</div>
</blockquote>
</div>
<span><br><br clear="all"><div><br></div>-- <br>Alex Davies<br><br><span>This email and any files transmitted with it are confidential and<br>

intended solely for the use of the individual or entity to whom they<br>

are addressed. If you have received this email in error please notify<br>the sender immediately by e-mail and delete this e-mail permanently.</span>
</span>
</div>
</blockquote>
</div>
<br>
</div>
</div></div>
</blockquote>
</div>
<br><br clear="all"><div><br></div>-- <br>Alex Davies<br><br><span>This email and any files transmitted with it are confidential and<br>intended solely for the use of the individual or entity to whom they<br>

are addressed. If you have received this email in error please notify<br>the sender immediately by e-mail and delete this e-mail permanently.</span>
</div>
</div>
Alex Davies | 16 Apr 18:35 2014

Re: serial arrow keys broken

A, B, C and D. Here I pressed the key after each word (e.g. “u”, “p”, <up arrow”):

 

iPXE> up A down B right C left D

up: command not found

 

-Alex

 

 

From: Alex Davies [mailto:alex-7Vk2WWVZgQQ@public.gmane.org]
Sent: 11 April 2014 23:18
To: Alex Davies
Subject: Fwd: [ipxe-devel] serial arrow keys broken

 

 

---------- Forwarded message ----------
From: Peter Pickford <peter-7TcnlQJbpXVgj/lY1WyWEQ@public.gmane.org>
Date: Wed, Apr 9, 2014 at 11:48 AM
Subject: Re: [ipxe-devel] serial arrow keys broken
To: Alex Davies <alex-7Vk2WWVZgQQ@public.gmane.org>

If you exit the menu and got to the ipxe command line what do you get when you press the arrow keys?

 

On 9 April 2014 03:41, Alex Davies <alex-7Vk2WWVZgQQ@public.gmane.org> wrote:

Hi All,

 

We had the same problem using SOL on Dell hardware.

 

I tried both your patch Michael and the divide by two suggested at the top of this thread, without joy.

 

Interestingly, pressing the arrow key does stop the countdown timer, but the menu selector does not move, so iPXE is getting something. What debug flag should I enable to see what it is getting?

 

The menu is working nicely with color and if I connect to the 'full console' via the DRAC, and move the arrow key, the SOL menu refreshes correctly.

 

Thanks!

 

-Alex

 

On Thu, Mar 27, 2014 at 2:46 PM, Michael Brown <mcb30-VUaoxwjD3yI@public.gmane.org> wrote:

On 27/03/14 08:36, Peter Pickford wrote:

The arrow keys would not work in my ipxe serial console.

The following seems to fix it but causes a busy wait while reading
escape sequences.

<snip>


Arrow keys over serial works for me.  Could you try the attached (untested) patch, which preserves the cpu_nap() while changing the ordering of events such that a keypress arriving during the cpu_nap() will be detected even if the timeout has expired?

Thanks,

Michael

_______________________________________________
ipxe-devel mailing list
ipxe-devel <at> lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel



 

--
Alex Davies

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail permanently.

 



 

--
Alex Davies

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail and delete this e-mail permanently.



This email is sent by Jump Trading International Limited ("Jump" or "JTIL"), a private limited company registered in England & Wales under No. 05976015, authorised and regulated by the Financial Conduct Authority. Registered office: 2nd Floor, 10 Chiswell Street, London EC1Y 4UQ. Tel: +44(0) 20 7382 4351. This email is for the confidential use of the named addressee(s) only and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this email is strictly prohibited, and to please notify the sender immediately and destroy this email and any attachments. Email transmission cannot be guaranteed to be secure or error-free. Jump Trading International Ltd, therefore, does not make any guarantees as to the completeness or accuracy of this email or any attachments. This email is for informational purposes only and does not constitute a recommendation, offer, request or solicitation of any kind to buy, sell, subscribe, redeem or perform any type of transaction of a financial product.
<div>
<div class="WordSection1">
<p class="MsoNormal"><span>A, B, C and D. Here I pressed the key after each word (e.g. &ldquo;u&rdquo;, &ldquo;p&rdquo;, &lt;up arrow&rdquo;):</span></p>
<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal"><span>iPXE&gt; up A down B right C left D</span></p>
<p class="MsoNormal"><span>up: command not found</span></p>
<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal"><span>-Alex</span></p>
<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-US">From:</span><span lang="EN-US"> Alex Davies [mailto:alex@...]
<br>Sent: 11 April 2014 23:18<br>To: Alex Davies<br>Subject: Fwd: [ipxe-devel] serial arrow keys broken</span></p>
<p class="MsoNormal">&nbsp;</p>
<div>
<p class="MsoNormal">&nbsp;</p>
<div>
<p class="MsoNormal">---------- Forwarded message ----------<br>
From: Peter Pickford &lt;<a href="mailto:peter@...">peter@...</a>&gt;<br>
Date: Wed, Apr 9, 2014 at 11:48 AM<br>
Subject: Re: [ipxe-devel] serial arrow keys broken<br>
To: Alex Davies &lt;<a href="mailto:alex@...">alex@...</a>&gt;<br><br></p>
<div>
<p class="MsoNormal">If you exit the menu and got to the ipxe command line what do you get when you press the arrow keys?</p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">&nbsp;</p>
<div>
<p class="MsoNormal">On 9 April 2014 03:41, Alex Davies &lt;<a href="mailto:alex@..." target="_blank">alex@...</a>&gt; wrote:</p>
<blockquote>
<div>
<p class="MsoNormal">Hi All,</p>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<div>
<p class="MsoNormal">We had the same problem using SOL on Dell hardware.</p>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<div>
<p class="MsoNormal">I tried both your patch Michael and the divide by two suggested at the top of this thread, without joy.</p>
</div>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<div>
<p class="MsoNormal">Interestingly, pressing the arrow key does stop the countdown timer, but the menu selector does not move, so iPXE is getting something. What debug flag should I enable to see what it is getting?</p>
</div>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<div>
<p class="MsoNormal">The menu is working nicely with color and if I connect to the 'full console' via the DRAC, and move the arrow key, the SOL menu refreshes correctly.</p>
</div>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<div>
<p class="MsoNormal">Thanks!</p>
</div>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<div>
<p class="MsoNormal">-Alex</p>
</div>
</div>
</div>
<div>
<p class="MsoNormal">&nbsp;</p>
<div>
<div>
<div>
<p class="MsoNormal">On Thu, Mar 27, 2014 at 2:46 PM, Michael Brown &lt;<a href="mailto:mcb30@..." target="_blank">mcb30@...</a>&gt; wrote:</p>
</div>
</div>
<blockquote>
<div>
<div>
<div>
<p class="MsoNormal">On 27/03/14 08:36, Peter Pickford wrote:</p>
</div>
<blockquote>
<div>
<p class="MsoNormal">The arrow keys would not work in my ipxe serial console.<br><br>
The following seems to fix it but causes a busy wait while reading<br>
escape sequences.</p>
</div>
<p class="MsoNormal">&lt;snip&gt;</p>
</blockquote>
<p class="MsoNormal"><br>
Arrow keys over serial works for me. &nbsp;Could you try the attached (untested) patch, which preserves the cpu_nap() while changing the ordering of events such that a keypress arriving during the cpu_nap() will be detected even if the timeout has expired?<br><br>
Thanks,<br><br>
Michael</p>
</div>
</div>
<div>
<p class="MsoNormal">_______________________________________________<br>
ipxe-devel mailing list<br><a href="mailto:ipxe-devel@..." target="_blank">ipxe-devel <at> lists.ipxe.org</a><br><a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span><br><br clear="all"></span></p>
<div>
<p class="MsoNormal"><span>&nbsp;</span></p>
</div>
<p class="MsoNormal"><span>-- <br>
Alex Davies<br><br></span><span>This email and any files transmitted with it are confidential and<br>
intended solely for the use of the individual or entity to whom they<br>
are addressed. If you have received this email in error please notify<br>
the sender immediately by e-mail and delete this e-mail permanently.</span><span>
</span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal">&nbsp;</p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br><br clear="all"></p>
<div>
<p class="MsoNormal">&nbsp;</p>
</div>
<p class="MsoNormal">-- <br>
Alex Davies<br><br><span>This email and any files transmitted with it are confidential and<br>
intended solely for the use of the individual or entity to whom they<br>
are addressed. If you have received this email in error please notify<br>
the sender immediately by e-mail and delete this e-mail permanently.</span> </p>
</div>
</div>
<br><br>
This email is sent by Jump Trading International Limited ("Jump" or "JTIL"), a private limited company registered in England &amp; Wales under No. 05976015, authorised and regulated by the Financial Conduct Authority. Registered office: 2nd Floor, 10 Chiswell Street,
 London EC1Y 4UQ. Tel: +44(0) 20 7382 4351. This email is for the confidential use of the named addressee(s) only and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you are hereby notified that any review,
 dissemination or copying of this email is strictly prohibited, and to please notify the sender immediately and destroy this email and any attachments. Email transmission cannot be guaranteed to be secure or error-free. Jump Trading International Ltd, therefore,
 does not make any guarantees as to the completeness or accuracy of this email or any attachments. This email is for informational purposes only and does not constitute a recommendation, offer, request or solicitation of any kind to buy, sell, subscribe, redeem
 or perform any type of transaction of a financial product.<br>
</div>
Oliver Rath | 17 Apr 09:45 2014
Picon

Howto evaluate needed WinPE-Files?

Hi list,

is there a list on a WinPE-CD, which files are needed to load for a
working WinPE? With WinPE-4 (referring to http://ipxe.org/howto/winpe)
works fine, but With WinPE-5 my screen remains dark.

Tfh!
Oliver

E-Blokos | 17 Apr 08:49 2014

BFO Fedora and IPXE

Hi,

I'm trying to boot BFO (boot.fedoraproject.org)
but I get
Could not boot: Requested memory not available

the text I put in my menu

:fedora-instbfo
echo Install Fedora from BFO
dhcp net0
imgfetch http://dl.fedoraproject.org/pub/alt/bfo/bfo.lkrn
imgload bfo.lkrn
boot bfo.lkrn || goto failed
goto start

I just git pulled and compiled successfully today on Fedora 18

any idea ?

Thank you very much

Franck
Ian Bannerman | 15 Apr 15:29 2014

Re: Issues chainbooting iPXE to WDS 2012R2

Ah, perfect! It's very straightforward. Pop into the Windows Deployment Services console, navigate to the Boot Images category and right click on a boot image and choose Create Discovery Image. This is also defined here: http://technet.microsoft.com/en-us/library/dd637996(v=ws.10).aspx . If you don't have any boot images, you can import them off of any Windows installation disc.

Follow the wizard steps and it will save a WIM file at the end. Now you just need to wimboot that wim file! For example, if your current wimboot setup is:

:wimboot
  cpuid --ext 29 && set arch amd64 || set arch x86
  kernel wimboot
  initrd winpe/${arch}/ISO/bootmgr       bootmgr
  initrd winpe/${arch}/ISO/boot/bcd      BCD
  initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
  initrd winpe/${arch}/winpe.wim         boot.wim
  boot || goto failed
  goto start 



You could put your Discover image next to winpe.wim as discover.wim and create a new script section with this modification:

[...]
  initrd winpe/${arch}/discover.wim         boot.wim
  boot || goto failed
  goto start 


This would work. If you wish, you can create more than one discover image, for example an x86 one and an x64 one.

The discover image is just a Windows Setup wim file with additional command line parameters passed to setup.exe, documented here: http://technet.microsoft.com/en-us/library/cc770495(v=ws.10).aspx

I hope this helps!

--Ian

From: nicholas.krouse <at> nccvt.k12.de.us
To: ian <at> internals.io
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 13:21:36 +0000

<!-- .ExternalClass .ecxshape { } --><!-- .ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink { color:blue; text-decoration:underline; } .ExternalClass span.ecxMsoHyperlinkFollowed { color:purple; text-decoration:underline; } .ExternalClass p { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsonormal, .ExternalClass li.ecxmsonormal, .ExternalClass div.ecxmsonormal { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsochpdefault, .ExternalClass li.ecxmsochpdefault, .ExternalClass div.ecxmsochpdefault { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsonormal1, .ExternalClass li.ecxmsonormal1, .ExternalClass div.ecxmsonormal1 { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsochpdefault1, .ExternalClass li.ecxmsochpdefault1, .ExternalClass div.ecxmsochpdefault1 { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxmsohyperlink { } .ExternalClass span.ecxmsohyperlinkfollowed { } .ExternalClass span.ecxmsohyperlink1 { } .ExternalClass span.ecxmsohyperlinkfollowed1 { } .ExternalClass span.ecxemailstyle181 { } .ExternalClass span.ecxemailstyle28 { } .ExternalClass p.ecxmsonormal2, .ExternalClass li.ecxmsonormal2, .ExternalClass div.ecxmsonormal2 { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxmsohyperlink2 { color:blue; text-decoration:underline; } .ExternalClass span.ecxmsohyperlinkfollowed2 { color:purple; text-decoration:underline; } .ExternalClass p.ecxmsochpdefault2, .ExternalClass li.ecxmsochpdefault2, .ExternalClass div.ecxmsochpdefault2 { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsonormal11, .ExternalClass li.ecxmsonormal11, .ExternalClass div.ecxmsonormal11 { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxmsohyperlink11 { color:#0563C1; text-decoration:underline; } .ExternalClass span.ecxmsohyperlinkfollowed11 { color:#954F72; text-decoration:underline; } .ExternalClass span.ecxemailstyle1811 { font-family:"Calibri","sans-serif"; color:#1F497D; } .ExternalClass p.ecxmsochpdefault11, .ExternalClass li.ecxmsochpdefault11, .ExternalClass div.ecxmsochpdefault11 { font-size:10.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxemailstyle281 { font-family:"Calibri","sans-serif"; color:#1F497D; } .ExternalClass span.ecxEmailStyle38 { font-family:"Calibri","sans-serif"; color:#1F497D; } .ExternalClass .ecxMsoChpDefault { font-size:10.0pt; } .ExternalClass div.ecxWordSection1 { } -->

How could I use wimboot to boot the discover image? That would be very excellent as my wimboot works great!

 

Nick

 

From: Ian Bannerman [mailto:ian <at> internals.io]
Sent: Tuesday, April 15, 2014 9:19 AM
To: Nicholas Krouse
Cc: ipxe-devel <at> lists.ipxe.org
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2

 

Perhaps there may be someone who will take you up on the screenshare; myself, I must work in bit :)

 

Since you can browse to the ftp share normally, I'm not sure what may be behind the error (I just don't have much experience with tftp :)

 

Is your :wimboot script entry work currently, can it start downloading files? If so, you could work around the issue by creating a discover image and using wimboot to boot the Discover Image wim file; you would not need to chain wdsnbp.com. 

--Ian

 

From: nicholas.krouse <at> nccvt.k12.de.us
To: ian <at> internals.io
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 13:11:08 +0000

I did everything is that thread to try to trouble shoot the issue, however I am running WDS 2012r2 without SCCM. Also Yes I have browsed to that tftp server and had no issues grabbing the file, my DHCP server is on a separate windows box. And it has no problem. If you would be interested we could set up a screen share and I could show you what I mean. I really appreciate your time! But the ipxe linux server running Ubuntu server has all the diag content and live content and I would like it to point to my WDS server to manage the win images.

 

Thanks

Nick Krouse

 

From: Ian Bannerman [mailto:ian <at> internals.io]
Sent: Tuesday, April 15, 2014 8:58 AM
To: Nicholas Krouse
Cc: F.Hummel <at> ads-tec.de; ipxe-devel <at> lists.ipxe.org
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2

 

I threw the photo on imgur so it wasn't lost in the chain here: http://i.imgur.com/TPcEOEb.png

 

I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling in various suggestions from the forum thread here: http://forum.ipxe.org/showthread.php?tid=7242 

 

 

How about this, have you confirmed that you can browse to the FTP server from another machine over the path ftp://10.200.0.74/boot/x86/ and see the file wdsnbp.com?

 

--Ian

From: nicholas.krouse <at> nccvt.k12.de.us
To: ian <at> internals.io
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 12:28:09 +0000

Ian

 

Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!

 

Thanks

Nick Krouse

 

From: Ian Bannerman [mailto:ian <at> internals.io]
Sent: Tuesday, April 15, 2014 8:14 AM
To: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2

 

I have systems downloading various wims to 'boot.wim' as he has without issue, yep! 

 

But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation / fourms discussions. For example, the iPXE documentation has examples on http://ipxe.org/howto/winpe and http://ipxe.org/howto/sccm where fonts are listed for older bootmgrs. 

 

Thanks,

--Ian

> Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> Date: Tue, 15 Apr 2014 14:08:06 +0200
> From: F.Hummel <at> ads-tec.de
> To: ian <at> internals.io; nicholas.krouse <at> nccvt.k12.de.us; ipxe-devel <at> lists.ipxe.org
>
> Well – found that sequence to be functional by trial-and-error.
> Did you try it?
>
> As far as the fonts are concerned - I do not use older bootmgr versions.
> If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.
> You will just see a black or blue (not BSOD) screen...
>
> mit freundlichen Grüßen
> with kind regards
>
> i. A. Dipl.Ing. (FH) Frank Hummel
> Systementwicklung
> System development
>
> ads-tec GmbH
> Raiffeisenstr.14
> 70771 Leinfelden-Echterdingen
> Germany
>
> Tel.:    +49 711 45894-220
> Fax:    +49 711 45894-987
> E-Mail: F.Hummel <at> ads-tec.de
> Web: www.ads-tec.de
>
>
>
>
> Von: Ian Bannerman [mailto:ian <at> internals.io]
> Gesendet: Dienstag, 15. April 2014 13:23
> An: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org
> Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
>
> That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!
>
> Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.
>
> My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.
>
> --Ian
> > Date: Tue, 15 Apr 2014 09:30:44 +0200
> > From: F.Hummel <at> ads-tec.de
> > To: nicholas.krouse <at> nccvt.k12.de.us; ipxe-devel <at> lists.ipxe.org
> > Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hi,
> >
> > :wds-server
> > dhcp
> > set wdsserver 10.200.0.74
> > set alternatetftp 10.200.0.74
> > set net0/dhcp-server ${wdsserver}
> > set net0/filename wdsbnp.com ← Typo, not the cause for the current prob
> > set net0/gateway ${wdsserver}
> > set net0/next-server ${wdsserver}
> > set net0/user-class PXEClient
> > -------------------------------------------------------------------
> > Your sequence:
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd BCD
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/winpe.wim boot.wim
> > boot || goto failed
> > goto start
> > -------------------------------------------------------------------
> > You are missing the fonts and left and right must look the same. Should look like this:
> >
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd bcd ← take care! Case sensitive!
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf
> > initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf
> > initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!
> > Imgstat ← enables you to see if all files have been loaded
> > prompt ← stops until you continue after reading imgstat output
> > boot || goto failed
> > goto start
> >
> > My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.
> > That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.
> > E.g.:
> > set sanboot-url http://123.456.789.012
> > initrd ${sanboot-url}/win7pe_x86.iso
> > chain syslinux/memdisk iso raw
> >
> >
> >
> > mit freundlichen Grüßen
> > with kind regards
> >
> > i. A. Dipl.Ing. (FH) Frank Hummel
> > Systementwicklung
> > System development
> >
> > ads-tec GmbH
> > Raiffeisenstr.14
> > 70771 Leinfelden-Echterdingen
> > Germany
> >
> > Tel.:    +49 711 45894-220
> > Fax:    +49 711 45894-987
> > E-Mail: F.Hummel <at> ads-tec.de
> > Web: www.ads-tec.de
> >
> >
> >
> >
> > Von: ipxe-devel-bounces <at> lists.ipxe.org [mailto:ipxe-devel-bounces <at> lists.ipxe.org] Im Auftrag von Nicholas Krouse
> > Gesendet: Montag, 14. April 2014 20:22
> > An: ipxe-devel <at> lists.ipxe.org
> > Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hello
> >
> > I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.
> >
> > Thanks
> > Nick Krouse
> > Computer Support Instructor
> > Delaware Skills Center
> > Deskillscenter.org
> > _______________________________________________
> > ads-tec GmbH
> > Sitz: 70771 Leinfelden-Echterdingen
> > Registergericht Stuttgart HRB 224527
> >
> > Geschaeftsfuehrer:
> > Dipl.-Ing. Thomas Speidel
> > _______________________________________________
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> > geschuetzte Informationen. Wenn Sie nicht der richtige
> > Adressat sind oder diese E-Mail irrtuemlich erhalten
> > haben, informieren Sie bitte sofort den Absender und
> > vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> > jegliche anderweitige Verwendung sowie die unbefugte
> > Weitergabe dieser Mail sind nicht gestattet.
> > _______________________________________________
> >
> > This e-mail may contain confidential and/or privileged
> > information. If you are not the intended recipient (or have
> > received this e-mail in error) please notify the sender
> > immediately and destroy this e-mail. Any unauthorized
> > copying, disclosure, distribution or other use of the
> > material or parts thereof are strictly forbidden.
> > _______________________________________________
> > _______________________________________________
> > ipxe-devel mailing list
> > ipxe-devel <at> lists.ipxe.org
> > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> _______________________________________________
> ads-tec GmbH
> Sitz: 70771 Leinfelden-Echterdingen
> Registergericht Stuttgart HRB 224527
>
> Geschaeftsfuehrer:
> Dipl.-Ing. Thomas Speidel
> _______________________________________________
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> geschuetzte Informationen. Wenn Sie nicht der richtige
> Adressat sind oder diese E-Mail irrtuemlich erhalten
> haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> jegliche anderweitige Verwendung sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
> _______________________________________________
>
> This e-mail may contain confidential and/or privileged
> information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender
> immediately and destroy this e-mail. Any unauthorized
> copying, disclosure, distribution or other use of the
> material or parts thereof are strictly forbidden.
> _______________________________________________

<div><div dir="ltr">Ah, perfect! It's very straightforward. Pop into the Windows Deployment Services console, navigate to the Boot Images category and right click on a boot image and choose Create Discovery Image. This is also defined here:&nbsp;http://technet.microsoft.com/en-us/library/dd637996(v=ws.10).aspx . If you don't have any boot images, you can import them off of any Windows installation disc.<div><br></div>
<div>Follow the wizard steps and it will save a WIM file at the end. Now you just need to wimboot that wim file! For example, if your current wimboot setup is:</div>
<div><br></div>
<div>
<div>:wimboot</div>
<div>&nbsp; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86</div>
<div>&nbsp; kernel wimboot</div>
<div>&nbsp; initrd winpe/${arch}/ISO/bootmgr &nbsp; &nbsp; &nbsp; bootmgr</div>
<div>&nbsp; initrd winpe/${arch}/ISO/boot/bcd &nbsp; &nbsp; &nbsp;BCD</div>
<div>&nbsp; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi</div>
<div>&nbsp; initrd winpe/${arch}/winpe.wim &nbsp; &nbsp; &nbsp; &nbsp; boot.wim</div>
<div>&nbsp; boot || goto failed</div>
<div>&nbsp; goto start&nbsp;</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>You could put your Discover image next to winpe.wim as discover.wim and create a new script section with this modification:</div>
<div><br></div>
<div>
<div><span>[...]</span></div>
<div><span>&nbsp; initrd winpe/${arch}/discover.wim &nbsp; &nbsp; &nbsp; &nbsp; boot.wim</span></div>
<div>&nbsp; boot || goto failed</div>
<div>&nbsp; goto start&nbsp;</div>
</div>
<div><br></div>
<div><br></div>
<div>This would work. If you wish, you can create more than one discover image, for example an x86 one and an x64 one.</div>
<div><br></div>
<div>The discover image is just a Windows Setup wim file with additional command line parameters passed to setup.exe, documented here:&nbsp;http://technet.microsoft.com/en-us/library/cc770495(v=ws.10).aspx</div>
<div><br></div>
<div>I hope this helps!</div>
<div><br></div>
<div>--Ian</div>
<br><div>From: nicholas.krouse <at> nccvt.k12.de.us<br>To: ian <at> internals.io<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>Date: Tue, 15 Apr 2014 13:21:36 +0000<br><br>&lt;!--
.ExternalClass .ecxshape {
}
--&gt;&lt;!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:blue;
text-decoration:underline;
}

.ExternalClass span.ecxMsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}

.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsonormal, .ExternalClass li.ecxmsonormal, .ExternalClass div.ecxmsonormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsochpdefault, .ExternalClass li.ecxmsochpdefault, .ExternalClass div.ecxmsochpdefault {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsonormal1, .ExternalClass li.ecxmsonormal1, .ExternalClass div.ecxmsonormal1 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsochpdefault1, .ExternalClass li.ecxmsochpdefault1, .ExternalClass div.ecxmsochpdefault1 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxmsohyperlink {
}

.ExternalClass span.ecxmsohyperlinkfollowed {
}

.ExternalClass span.ecxmsohyperlink1 {
}

.ExternalClass span.ecxmsohyperlinkfollowed1 {
}

.ExternalClass span.ecxemailstyle181 {
}

.ExternalClass span.ecxemailstyle28 {
}

.ExternalClass p.ecxmsonormal2, .ExternalClass li.ecxmsonormal2, .ExternalClass div.ecxmsonormal2 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxmsohyperlink2 {
color:blue;
text-decoration:underline;
}

.ExternalClass span.ecxmsohyperlinkfollowed2 {
color:purple;
text-decoration:underline;
}

.ExternalClass p.ecxmsochpdefault2, .ExternalClass li.ecxmsochpdefault2, .ExternalClass div.ecxmsochpdefault2 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsonormal11, .ExternalClass li.ecxmsonormal11, .ExternalClass div.ecxmsonormal11 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxmsohyperlink11 {
color:#0563C1;
text-decoration:underline;
}

.ExternalClass span.ecxmsohyperlinkfollowed11 {
color:#954F72;
text-decoration:underline;
}

.ExternalClass span.ecxemailstyle1811 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}

.ExternalClass p.ecxmsochpdefault11, .ExternalClass li.ecxmsochpdefault11, .ExternalClass div.ecxmsochpdefault11 {
font-size:10.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxemailstyle281 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}

.ExternalClass span.ecxEmailStyle38 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}

.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}

.ExternalClass div.ecxWordSection1 {
}

--&gt;<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span>How could I use wimboot to boot the discover image? That would be very excellent as my wimboot works great!</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<p class="ecxMsoNormal"><span>Nick</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<div>
<div>
<p class="ecxMsoNormal"><span>From:</span><span> Ian Bannerman [mailto:ian <at> internals.io]
<br>Sent: Tuesday, April 15, 2014 9:19 AM<br>To: Nicholas Krouse<br>Cc: ipxe-devel <at> lists.ipxe.org<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span></p>
</div>
</div>
<p class="ecxMsoNormal">&nbsp;</p>
<div>
<p class="ecxMsoNormal"><span>Perhaps there may be someone who will take you up on the screenshare; myself, I must work in bit :)</span></p>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>Since you can browse to the ftp share normally, I'm not sure what may be behind the error (I just don't have much experience with tftp :)</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>Is your :wimboot script entry work currently, can it start downloading files? If so, you could work&nbsp;around the issue by creating a discover image and using wimboot to boot the Discover Image
 wim file; you would not need to chain wdsnbp.com.&nbsp;<br><br>
--Ian</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<div>
<div class="ecxMsoNormal" align="center"><span>
</span></div>
<p class="ecxMsoNormal"><span>From:
<a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">nicholas.krouse <at> nccvt.k12.de.us</a><br>
To: <a href="mailto:ian <at> internals.io">ian <at> internals.io</a><br>
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
Date: Tue, 15 Apr 2014 13:11:08 +0000</span></p>
<div>
<p class="ecxMsoNormal"><span>I did everything is that thread to try to trouble shoot the issue, however I am running WDS 2012r2 without SCCM. Also Yes I have browsed to that tftp server
 and had no issues grabbing the file, my DHCP server is on a separate windows box. And it has no problem. If you would be interested we could set up a screen share and I could show you what I mean. I really appreciate your time! But the ipxe linux server running
 Ubuntu server has all the diag content and live content and I would like it to point to my WDS server to manage the win images.</span><span></span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span><span></span></p>
<p class="ecxMsoNormal"><span>Thanks</span><span></span></p>
<p class="ecxMsoNormal"><span>Nick Krouse</span><span></span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span><span></span></p>
<div>
<div>
<p class="ecxMsoNormal"><span>From:</span><span> Ian Bannerman [<a href="mailto:ian <at> internals.io">mailto:ian <at> internals.io</a>]
<br>Sent: Tuesday, April 15, 2014 8:58 AM<br>To: Nicholas Krouse<br>Cc: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a>; <a href="mailto:ipxe-devel <at> lists.ipxe.org">
ipxe-devel <at> lists.ipxe.org</a><br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span><span></span></p>
</div>
</div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<div>
<div>
<p class="ecxMsoNormal"><span>I threw the photo on imgur so it wasn't lost in the chain here:&nbsp;<a href="http://i.imgur.com/TPcEOEb.png" target="_blank">http://i.imgur.com/TPcEOEb.png</a></span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling
 in various suggestions from the forum thread here:&nbsp;<a href="http://forum.ipxe.org/showthread.php?tid=7242" target="_blank">http://forum.ipxe.org/showthread.php?tid=7242</a>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>How about this, have you confirmed that you can browse to the FTP server from another machine over the path
<a href="ftp://10.200.0.74/boot/x86/" target="_blank">ftp://10.200.0.74/boot/x86/≤/a> and see the file wdsnbp.com?</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>--Ian</span></p>
<div>
<div class="ecxMsoNormal" align="center"><span>
</span></div>
<p class="ecxMsoNormal"><span>From: <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">
nicholas.krouse <at> nccvt.k12.de.us</a><br>
To: <a href="mailto:ian <at> internals.io">ian <at> internals.io</a><br>
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
Date: Tue, 15 Apr 2014 12:28:09 +0000</span></p>
<div>
<p class="ecxMsoNormal"><span>Ian</span><span></span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span><span></span></p>
<p class="ecxMsoNormal"><span>Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments
 and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!</span><span></span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span><span></span></p>
<p class="ecxMsoNormal"><span>Thanks</span><span></span></p>
<p class="ecxMsoNormal"><span>Nick Krouse</span><span></span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span><span></span></p>
<div>
<div>
<p class="ecxMsoNormal"><span>From:</span><span> Ian Bannerman [<a href="mailto:ian <at> internals.io">mailto:ian <at> internals.io</a>]
<br>Sent: Tuesday, April 15, 2014 8:14 AM<br>To: Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel <at> lists.ipxe.org">
ipxe-devel <at> lists.ipxe.org</a><br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span><span></span></p>
</div>
</div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<div>
<p class="ecxMsoNormal"><span>I have systems downloading various wims to 'boot.wim' as he has without issue, yep!&nbsp;</span></p>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation / fourms
 discussions. For example, the iPXE documentation has examples on&nbsp;<a href="http://ipxe.org/howto/winpe" target="_blank">http://ipxe.org/howto/winpe</a> and&nbsp;<a href="http://ipxe.org/howto/sccm" target="_blank">http://ipxe.org/howto/sccm</a> where fonts are listed
 for older bootmgrs.&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>Thanks,</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>--Ian</span></p>
<div>
<p class="ecxMsoNormal"><span>&gt; Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; Date: Tue, 15 Apr 2014 14:08:06 +0200<br>
&gt; From: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; To: <a href="mailto:ian <at> internals.io">ian <at> internals.io</a>; <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">
nicholas.krouse <at> nccvt.k12.de.us</a>; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; <br>
&gt; Well &ndash; found that sequence to be functional by trial-and-error.<br>
&gt; Did you try it?<br>
&gt; <br>
&gt; As far as the fonts are concerned - I do not use older bootmgr versions.<br>
&gt; If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.<br>
&gt; You will just see a black or blue (not BSOD) screen...<br>
&gt; <br>
&gt; mit freundlichen Gr&uuml;&szlig;en<br>
&gt; with kind regards<br>
&gt; <br>
&gt; i. A. Dipl.Ing. (FH) Frank Hummel<br>
&gt; Systementwicklung<br>
&gt; System development<br>
&gt; <br>
&gt; ads-tec GmbH<br>
&gt; Raiffeisenstr.14<br>
&gt; 70771 Leinfelden-Echterdingen<br>
&gt; Germany<br>
&gt; <br>
&gt; Tel.:&nbsp;&nbsp;&nbsp; +49 711 45894-220<br>
&gt; Fax:&nbsp;&nbsp;&nbsp; +49 711 45894-987<br>
&gt; E-Mail: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Von: Ian Bannerman [<a href="mailto:ian <at> internals.io">mailto:ian <at> internals.io</a>]
<br>
&gt; Gesendet: Dienstag, 15. April 2014 13:23<br>
&gt; An: Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; <br>
&gt; That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim &larr; Names must match and must match the entry in your bcd!<br>
&gt; <br>
&gt; Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.<br>
&gt; <br>
&gt; My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.<br>
&gt; <br>
&gt; --Ian<br>
&gt; &gt; Date: Tue, 15 Apr 2014 09:30:44 +0200<br>
&gt; &gt; From: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; &gt; To: <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">nicholas.krouse <at> nccvt.k12.de.us</a>;
<a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; &gt; <br>
&gt; &gt; Hi,<br>
&gt; &gt; <br>
&gt; &gt; :wds-server<br>
&gt; &gt; dhcp<br>
&gt; &gt; set wdsserver 10.200.0.74<br>
&gt; &gt; set alternatetftp 10.200.0.74<br>
&gt; &gt; set net0/dhcp-server ${wdsserver}<br>
&gt; &gt; set net0/filename wdsbnp.com &larr; Typo, not the cause for the current prob<br>
&gt; &gt; set net0/gateway ${wdsserver}<br>
&gt; &gt; set net0/next-server ${wdsserver}<br>
&gt; &gt; set net0/user-class PXEClient<br>
&gt; &gt; -------------------------------------------------------------------<br>
&gt; &gt; Your sequence:<br>
&gt; &gt; :wimboot<br>
&gt; &gt; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86<br>
&gt; &gt; kernel wimboot<br>
&gt; &gt; initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/bcd BCD<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
&gt; &gt; initrd winpe/${arch}/winpe.wim boot.wim<br>
&gt; &gt; boot || goto failed<br>
&gt; &gt; goto start<br>
&gt; &gt; -------------------------------------------------------------------<br>
&gt; &gt; You are missing the fonts and left and right must look the same. Should look like this:<br>
&gt; &gt; <br>
&gt; &gt; :wimboot<br>
&gt; &gt; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86<br>
&gt; &gt; kernel wimboot<br>
&gt; &gt; initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/bcd bcd &larr; take care! Case sensitive!<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf<br>
&gt; &gt; initrd winpe/${arch}/winpe.wim winpe.wim &larr; Names must match and must match the entry in your bcd!<br>
&gt; &gt; Imgstat &larr; enables you to see if all files have been loaded<br>
&gt; &gt; prompt &larr; stops until you continue after reading imgstat output<br>
&gt; &gt; boot || goto failed<br>
&gt; &gt; goto start<br>
&gt; &gt; <br>
&gt; &gt; My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.<br>
&gt; &gt; That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.<br>
&gt; &gt; E.g.:<br>
&gt; &gt; set sanboot-url <a href="http://123.456.789.012" target="_blank">http://123.456.789.012</a><br>
&gt; &gt; initrd ${sanboot-url}/win7pe_x86.iso<br>
&gt; &gt; chain syslinux/memdisk iso raw<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; mit freundlichen Gr&uuml;&szlig;en<br>
&gt; &gt; with kind regards<br>
&gt; &gt; <br>
&gt; &gt; i. A. Dipl.Ing. (FH) Frank Hummel<br>
&gt; &gt; Systementwicklung<br>
&gt; &gt; System development<br>
&gt; &gt; <br>
&gt; &gt; ads-tec GmbH<br>
&gt; &gt; Raiffeisenstr.14<br>
&gt; &gt; 70771 Leinfelden-Echterdingen<br>
&gt; &gt; Germany<br>
&gt; &gt; <br>
&gt; &gt; Tel.:&nbsp;&nbsp;&nbsp; +49 711 45894-220<br>
&gt; &gt; Fax:&nbsp;&nbsp;&nbsp; +49 711 45894-987<br>
&gt; &gt; E-Mail: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; &gt; Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; Von: <a href="mailto:ipxe-devel-bounces <at> lists.ipxe.org">ipxe-devel-bounces <at> lists.ipxe.org</a> [<a href="mailto:ipxe-devel-bounces <at> lists.ipxe.org">mailto:ipxe-devel-bounces <at> lists.ipxe.org</a>] Im Auftrag von Nicholas Krouse<br>
&gt; &gt; Gesendet: Montag, 14. April 2014 20:22<br>
&gt; &gt; An: <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; &gt; <br>
&gt; &gt; Hello <br>
&gt; &gt; <br>
&gt; &gt; I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over
 wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.<br>
&gt; &gt; <br>
&gt; &gt; Thanks<br>
&gt; &gt; Nick Krouse<br>
&gt; &gt; Computer Support Instructor<br>
&gt; &gt; Delaware Skills Center<br>
&gt; &gt; Deskillscenter.org<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ads-tec GmbH<br>
&gt; &gt; Sitz: 70771 Leinfelden-Echterdingen<br>
&gt; &gt; Registergericht Stuttgart HRB 224527<br>
&gt; &gt; <br>
&gt; &gt; Geschaeftsfuehrer:<br>
&gt; &gt; Dipl.-Ing. Thomas Speidel<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
&gt; &gt; geschuetzte Informationen. Wenn Sie nicht der richtige<br>
&gt; &gt; Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
&gt; &gt; haben, informieren Sie bitte sofort den Absender und <br>
&gt; &gt; vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
&gt; &gt; jegliche anderweitige Verwendung sowie die unbefugte<br>
&gt; &gt; Weitergabe dieser Mail sind nicht gestattet.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; <br>
&gt; &gt; This e-mail may contain confidential and/or privileged<br>
&gt; &gt; information. If you are not the intended recipient (or have<br>
&gt; &gt; received this e-mail in error) please notify the sender<br>
&gt; &gt; immediately and destroy this e-mail. Any unauthorized<br>
&gt; &gt; copying, disclosure, distribution or other use of the<br>
&gt; &gt; material or parts thereof are strictly forbidden.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ipxe-devel mailing list<br>
&gt; &gt; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; <a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
&gt; _______________________________________________<br>
&gt; ads-tec GmbH<br>
&gt; Sitz: 70771 Leinfelden-Echterdingen<br>
&gt; Registergericht Stuttgart HRB 224527<br>
&gt; <br>
&gt; Geschaeftsfuehrer:<br>
&gt; Dipl.-Ing. Thomas Speidel<br>
&gt; _______________________________________________<br>
&gt; Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
&gt; geschuetzte Informationen. Wenn Sie nicht der richtige<br>
&gt; Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
&gt; haben, informieren Sie bitte sofort den Absender und <br>
&gt; vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
&gt; jegliche anderweitige Verwendung sowie die unbefugte<br>
&gt; Weitergabe dieser Mail sind nicht gestattet.<br>
&gt; _______________________________________________<br>
&gt; <br>
&gt; This e-mail may contain confidential and/or privileged<br>
&gt; information. If you are not the intended recipient (or have<br>
&gt; received this e-mail in error) please notify the sender<br>
&gt; immediately and destroy this e-mail. Any unauthorized<br>
&gt; copying, disclosure, distribution or other use of the<br>
&gt; material or parts thereof are strictly forbidden.<br>
&gt; _______________________________________________</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div> 		 	   		  </div></div>
Ian Bannerman | 15 Apr 15:19 2014

Re: Issues chainbooting iPXE to WDS 2012R2

Perhaps there may be someone who will take you up on the screenshare; myself, I must work in bit :)

Since you can browse to the ftp share normally, I'm not sure what may be behind the error (I just don't have much experience with tftp :)

Is your :wimboot script entry work currently, can it start downloading files? If so, you could work around the issue by creating a discover image and using wimboot to boot the Discover Image wim file; you would not need to chain wdsnbp.com. 

--Ian

From: nicholas.krouse <at> nccvt.k12.de.us
To: ian <at> internals.io
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 13:11:08 +0000

<!-- .ExternalClass .ecxshape { } --><!-- .ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink { color:blue; text-decoration:underline; } .ExternalClass span.ecxMsoHyperlinkFollowed { color:purple; text-decoration:underline; } .ExternalClass p { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsonormal, .ExternalClass li.ecxmsonormal, .ExternalClass div.ecxmsonormal { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass p.ecxmsochpdefault, .ExternalClass li.ecxmsochpdefault, .ExternalClass div.ecxmsochpdefault { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxmsohyperlink { } .ExternalClass span.ecxmsohyperlinkfollowed { } .ExternalClass span.ecxemailstyle18 { } .ExternalClass p.ecxmsonormal1, .ExternalClass li.ecxmsonormal1, .ExternalClass div.ecxmsonormal1 { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxmsohyperlink1 { color:#0563C1; text-decoration:underline; } .ExternalClass span.ecxmsohyperlinkfollowed1 { color:#954F72; text-decoration:underline; } .ExternalClass span.ecxemailstyle181 { font-family:"Calibri","sans-serif"; color:#1F497D; } .ExternalClass p.ecxmsochpdefault1, .ExternalClass li.ecxmsochpdefault1, .ExternalClass div.ecxmsochpdefault1 { font-size:10.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxEmailStyle28 { font-family:"Calibri","sans-serif"; color:#1F497D; } .ExternalClass .ecxMsoChpDefault { font-size:10.0pt; } .ExternalClass div.ecxWordSection1 { } -->

I did everything is that thread to try to trouble shoot the issue, however I am running WDS 2012r2 without SCCM. Also Yes I have browsed to that tftp server and had no issues grabbing the file, my DHCP server is on a separate windows box. And it has no problem. If you would be interested we could set up a screen share and I could show you what I mean. I really appreciate your time! But the ipxe linux server running Ubuntu server has all the diag content and live content and I would like it to point to my WDS server to manage the win images.

 

Thanks

Nick Krouse

 

From: Ian Bannerman [mailto:ian <at> internals.io]
Sent: Tuesday, April 15, 2014 8:58 AM
To: Nicholas Krouse
Cc: F.Hummel <at> ads-tec.de; ipxe-devel <at> lists.ipxe.org
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2

 

I threw the photo on imgur so it wasn't lost in the chain here: http://i.imgur.com/TPcEOEb.png

 

I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling in various suggestions from the forum thread here: http://forum.ipxe.org/showthread.php?tid=7242 

 

 

How about this, have you confirmed that you can browse to the FTP server from another machine over the path ftp://10.200.0.74/boot/x86/ and see the file wdsnbp.com?

 

--Ian

From: nicholas.krouse <at> nccvt.k12.de.us
To: ian <at> internals.io
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 12:28:09 +0000

Ian

 

Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!

 

Thanks

Nick Krouse

 

From: Ian Bannerman [mailto:ian <at> internals.io]
Sent: Tuesday, April 15, 2014 8:14 AM
To: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2

 

I have systems downloading various wims to 'boot.wim' as he has without issue, yep! 

 

But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation / fourms discussions. For example, the iPXE documentation has examples on http://ipxe.org/howto/winpe and http://ipxe.org/howto/sccm where fonts are listed for older bootmgrs. 

 

Thanks,

--Ian

> Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> Date: Tue, 15 Apr 2014 14:08:06 +0200
> From: F.Hummel <at> ads-tec.de
> To: ian <at> internals.io; nicholas.krouse <at> nccvt.k12.de.us; ipxe-devel <at> lists.ipxe.org
>
> Well – found that sequence to be functional by trial-and-error.
> Did you try it?
>
> As far as the fonts are concerned - I do not use older bootmgr versions.
> If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.
> You will just see a black or blue (not BSOD) screen...
>
> mit freundlichen Grüßen
> with kind regards
>
> i. A. Dipl.Ing. (FH) Frank Hummel
> Systementwicklung
> System development
>
> ads-tec GmbH
> Raiffeisenstr.14
> 70771 Leinfelden-Echterdingen
> Germany
>
> Tel.:    +49 711 45894-220
> Fax:    +49 711 45894-987
> E-Mail: F.Hummel <at> ads-tec.de
> Web: www.ads-tec.de
>
>
>
>
> Von: Ian Bannerman [mailto:ian <at> internals.io]
> Gesendet: Dienstag, 15. April 2014 13:23
> An: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org
> Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
>
> That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!
>
> Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.
>
> My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.
>
> --Ian
> > Date: Tue, 15 Apr 2014 09:30:44 +0200
> > From: F.Hummel <at> ads-tec.de
> > To: nicholas.krouse <at> nccvt.k12.de.us; ipxe-devel <at> lists.ipxe.org
> > Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hi,
> >
> > :wds-server
> > dhcp
> > set wdsserver 10.200.0.74
> > set alternatetftp 10.200.0.74
> > set net0/dhcp-server ${wdsserver}
> > set net0/filename wdsbnp.com ← Typo, not the cause for the current prob
> > set net0/gateway ${wdsserver}
> > set net0/next-server ${wdsserver}
> > set net0/user-class PXEClient
> > -------------------------------------------------------------------
> > Your sequence:
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd BCD
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/winpe.wim boot.wim
> > boot || goto failed
> > goto start
> > -------------------------------------------------------------------
> > You are missing the fonts and left and right must look the same. Should look like this:
> >
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd bcd ← take care! Case sensitive!
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf
> > initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf
> > initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!
> > Imgstat ← enables you to see if all files have been loaded
> > prompt ← stops until you continue after reading imgstat output
> > boot || goto failed
> > goto start
> >
> > My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.
> > That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.
> > E.g.:
> > set sanboot-url http://123.456.789.012
> > initrd ${sanboot-url}/win7pe_x86.iso
> > chain syslinux/memdisk iso raw
> >
> >
> >
> > mit freundlichen Grüßen
> > with kind regards
> >
> > i. A. Dipl.Ing. (FH) Frank Hummel
> > Systementwicklung
> > System development
> >
> > ads-tec GmbH
> > Raiffeisenstr.14
> > 70771 Leinfelden-Echterdingen
> > Germany
> >
> > Tel.:    +49 711 45894-220
> > Fax:    +49 711 45894-987
> > E-Mail: F.Hummel <at> ads-tec.de
> > Web: www.ads-tec.de
> >
> >
> >
> >
> > Von: ipxe-devel-bounces <at> lists.ipxe.org [mailto:ipxe-devel-bounces <at> lists.ipxe.org] Im Auftrag von Nicholas Krouse
> > Gesendet: Montag, 14. April 2014 20:22
> > An: ipxe-devel <at> lists.ipxe.org
> > Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hello
> >
> > I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.
> >
> > Thanks
> > Nick Krouse
> > Computer Support Instructor
> > Delaware Skills Center
> > Deskillscenter.org
> > _______________________________________________
> > ads-tec GmbH
> > Sitz: 70771 Leinfelden-Echterdingen
> > Registergericht Stuttgart HRB 224527
> >
> > Geschaeftsfuehrer:
> > Dipl.-Ing. Thomas Speidel
> > _______________________________________________
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> > geschuetzte Informationen. Wenn Sie nicht der richtige
> > Adressat sind oder diese E-Mail irrtuemlich erhalten
> > haben, informieren Sie bitte sofort den Absender und
> > vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> > jegliche anderweitige Verwendung sowie die unbefugte
> > Weitergabe dieser Mail sind nicht gestattet.
> > _______________________________________________
> >
> > This e-mail may contain confidential and/or privileged
> > information. If you are not the intended recipient (or have
> > received this e-mail in error) please notify the sender
> > immediately and destroy this e-mail. Any unauthorized
> > copying, disclosure, distribution or other use of the
> > material or parts thereof are strictly forbidden.
> > _______________________________________________
> > _______________________________________________
> > ipxe-devel mailing list
> > ipxe-devel <at> lists.ipxe.org
> > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> _______________________________________________
> ads-tec GmbH
> Sitz: 70771 Leinfelden-Echterdingen
> Registergericht Stuttgart HRB 224527
>
> Geschaeftsfuehrer:
> Dipl.-Ing. Thomas Speidel
> _______________________________________________
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> geschuetzte Informationen. Wenn Sie nicht der richtige
> Adressat sind oder diese E-Mail irrtuemlich erhalten
> haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> jegliche anderweitige Verwendung sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
> _______________________________________________
>
> This e-mail may contain confidential and/or privileged
> information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender
> immediately and destroy this e-mail. Any unauthorized
> copying, disclosure, distribution or other use of the
> material or parts thereof are strictly forbidden.
> _______________________________________________

<div><div dir="ltr">Perhaps there may be someone who will take you up on the screenshare; myself, I must work in bit :)<div><br></div>
<div>Since you can browse to the ftp share normally, I'm not sure what may be behind the error (I just don't have much experience with tftp :)</div>
<div><br></div>
<div>
<span>Is your :wimboot script entry work currently, can it start downloading files? If so, you could work&nbsp;</span>around the issue by creating a discover image and using wimboot to boot the Discover Image wim file; you would not need to chain wdsnbp.com.&nbsp;<br><br>--Ian</div>
<div>
<br><div>From: nicholas.krouse <at> nccvt.k12.de.us<br>To: ian <at> internals.io<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>Date: Tue, 15 Apr 2014 13:11:08 +0000<br><br>&lt;!--
.ExternalClass .ecxshape {
}
--&gt;&lt;!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:blue;
text-decoration:underline;
}

.ExternalClass span.ecxMsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}

.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsonormal, .ExternalClass li.ecxmsonormal, .ExternalClass div.ecxmsonormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass p.ecxmsochpdefault, .ExternalClass li.ecxmsochpdefault, .ExternalClass div.ecxmsochpdefault {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxmsohyperlink {
}

.ExternalClass span.ecxmsohyperlinkfollowed {
}

.ExternalClass span.ecxemailstyle18 {
}

.ExternalClass p.ecxmsonormal1, .ExternalClass li.ecxmsonormal1, .ExternalClass div.ecxmsonormal1 {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxmsohyperlink1 {
color:#0563C1;
text-decoration:underline;
}

.ExternalClass span.ecxmsohyperlinkfollowed1 {
color:#954F72;
text-decoration:underline;
}

.ExternalClass span.ecxemailstyle181 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}

.ExternalClass p.ecxmsochpdefault1, .ExternalClass li.ecxmsochpdefault1, .ExternalClass div.ecxmsochpdefault1 {
font-size:10.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxEmailStyle28 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}

.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}

.ExternalClass div.ecxWordSection1 {
}

--&gt;<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span>I did everything is that thread to try to trouble shoot the issue, however I am running WDS 2012r2 without SCCM. Also Yes I have browsed to that tftp server
 and had no issues grabbing the file, my DHCP server is on a separate windows box. And it has no problem. If you would be interested we could set up a screen share and I could show you what I mean. I really appreciate your time! But the ipxe linux server running
 Ubuntu server has all the diag content and live content and I would like it to point to my WDS server to manage the win images.</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<p class="ecxMsoNormal"><span>Thanks</span></p>
<p class="ecxMsoNormal"><span>Nick Krouse</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<div>
<div>
<p class="ecxMsoNormal"><span>From:</span><span> Ian Bannerman [mailto:ian <at> internals.io]
<br>Sent: Tuesday, April 15, 2014 8:58 AM<br>To: Nicholas Krouse<br>Cc: F.Hummel <at> ads-tec.de; ipxe-devel <at> lists.ipxe.org<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span></p>
</div>
</div>
<p class="ecxMsoNormal">&nbsp;</p>
<div>
<div>
<p class="ecxMsoNormal">I threw the photo on imgur so it wasn't lost in the chain here:&nbsp;<a href="http://i.imgur.com/TPcEOEb.png" target="_blank">http://i.imgur.com/TPcEOEb.png</a></p>
</div>
<div>
<p class="ecxMsoNormal">&nbsp;</p>
</div>
<div>
<p class="ecxMsoNormal">I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling in various suggestions from the forum thread
 here:&nbsp;<a href="http://forum.ipxe.org/showthread.php?tid=7242" target="_blank">http://forum.ipxe.org/showthread.php?tid=7242</a>&nbsp;</p>
</div>
<div>
<p class="ecxMsoNormal">&nbsp;</p>
</div>
<div>
<p class="ecxMsoNormal">&nbsp;</p>
</div>
<div>
<p class="ecxMsoNormal">How about this, have you confirmed that you can browse to the FTP server from another machine over the path
<a href="ftp://10.200.0.74/boot/x86/" target="_blank">ftp://10.200.0.74/boot/x86/≤/a> and see the file wdsnbp.com?</p>
</div>
<div>
<p class="ecxMsoNormal">&nbsp;</p>
</div>
<div>
<p class="ecxMsoNormal">--Ian</p>
<div>
<div class="ecxMsoNormal" align="center">
</div>
<p class="ecxMsoNormal">From: <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">
nicholas.krouse <at> nccvt.k12.de.us</a><br>
To: <a href="mailto:ian <at> internals.io">ian <at> internals.io</a><br>
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
Date: Tue, 15 Apr 2014 12:28:09 +0000</p>
<div>
<p class="ecxmsonormal"><span>Ian</span></p>
<p class="ecxmsonormal"><span>&nbsp;</span></p>
<p class="ecxmsonormal"><span>Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments
 and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!</span></p>
<p class="ecxmsonormal"><span>&nbsp;</span></p>
<p class="ecxmsonormal"><span>Thanks</span></p>
<p class="ecxmsonormal"><span>Nick Krouse</span></p>
<p class="ecxmsonormal"><span>&nbsp;</span></p>
<div>
<div>
<p class="ecxmsonormal"><span>From:</span><span> Ian Bannerman [<a href="mailto:ian <at> internals.io">mailto:ian <at> internals.io</a>]
<br>Sent: Tuesday, April 15, 2014 8:14 AM<br>To: Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel <at> lists.ipxe.org">
ipxe-devel <at> lists.ipxe.org</a><br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span></p>
</div>
</div>
<p class="ecxmsonormal">&nbsp;</p>
<div>
<p class="ecxmsonormal"><span>I have systems downloading various wims to 'boot.wim' as he has without issue, yep!&nbsp;</span></p>
<div>
<p class="ecxmsonormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxmsonormal"><span>But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation /
 fourms discussions. For example, the iPXE documentation has examples on&nbsp;<a href="http://ipxe.org/howto/winpe" target="_blank">http://ipxe.org/howto/winpe</a> and&nbsp;<a href="http://ipxe.org/howto/sccm" target="_blank">http://ipxe.org/howto/sccm</a> where fonts
 are listed for older bootmgrs.&nbsp;</span></p>
</div>
<div>
<p class="ecxmsonormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxmsonormal"><span>Thanks,</span></p>
</div>
<div>
<p class="ecxmsonormal"><span>--Ian</span></p>
<div>
<p class="ecxmsonormal"><span>&gt; Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; Date: Tue, 15 Apr 2014 14:08:06 +0200<br>
&gt; From: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; To: <a href="mailto:ian <at> internals.io">ian <at> internals.io</a>; <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">
nicholas.krouse <at> nccvt.k12.de.us</a>; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; <br>
&gt; Well &ndash; found that sequence to be functional by trial-and-error.<br>
&gt; Did you try it?<br>
&gt; <br>
&gt; As far as the fonts are concerned - I do not use older bootmgr versions.<br>
&gt; If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.<br>
&gt; You will just see a black or blue (not BSOD) screen...<br>
&gt; <br>
&gt; mit freundlichen Gr&uuml;&szlig;en<br>
&gt; with kind regards<br>
&gt; <br>
&gt; i. A. Dipl.Ing. (FH) Frank Hummel<br>
&gt; Systementwicklung<br>
&gt; System development<br>
&gt; <br>
&gt; ads-tec GmbH<br>
&gt; Raiffeisenstr.14<br>
&gt; 70771 Leinfelden-Echterdingen<br>
&gt; Germany<br>
&gt; <br>
&gt; Tel.:&nbsp;&nbsp;&nbsp; +49 711 45894-220<br>
&gt; Fax:&nbsp;&nbsp;&nbsp; +49 711 45894-987<br>
&gt; E-Mail: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Von: Ian Bannerman [<a href="mailto:ian <at> internals.io">mailto:ian <at> internals.io</a>]
<br>
&gt; Gesendet: Dienstag, 15. April 2014 13:23<br>
&gt; An: Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; <br>
&gt; That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim &larr; Names must match and must match the entry in your bcd!<br>
&gt; <br>
&gt; Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.<br>
&gt; <br>
&gt; My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.<br>
&gt; <br>
&gt; --Ian<br>
&gt; &gt; Date: Tue, 15 Apr 2014 09:30:44 +0200<br>
&gt; &gt; From: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; &gt; To: <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">nicholas.krouse <at> nccvt.k12.de.us</a>;
<a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; &gt; <br>
&gt; &gt; Hi,<br>
&gt; &gt; <br>
&gt; &gt; :wds-server<br>
&gt; &gt; dhcp<br>
&gt; &gt; set wdsserver 10.200.0.74<br>
&gt; &gt; set alternatetftp 10.200.0.74<br>
&gt; &gt; set net0/dhcp-server ${wdsserver}<br>
&gt; &gt; set net0/filename wdsbnp.com &larr; Typo, not the cause for the current prob<br>
&gt; &gt; set net0/gateway ${wdsserver}<br>
&gt; &gt; set net0/next-server ${wdsserver}<br>
&gt; &gt; set net0/user-class PXEClient<br>
&gt; &gt; -------------------------------------------------------------------<br>
&gt; &gt; Your sequence:<br>
&gt; &gt; :wimboot<br>
&gt; &gt; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86<br>
&gt; &gt; kernel wimboot<br>
&gt; &gt; initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/bcd BCD<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
&gt; &gt; initrd winpe/${arch}/winpe.wim boot.wim<br>
&gt; &gt; boot || goto failed<br>
&gt; &gt; goto start<br>
&gt; &gt; -------------------------------------------------------------------<br>
&gt; &gt; You are missing the fonts and left and right must look the same. Should look like this:<br>
&gt; &gt; <br>
&gt; &gt; :wimboot<br>
&gt; &gt; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86<br>
&gt; &gt; kernel wimboot<br>
&gt; &gt; initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/bcd bcd &larr; take care! Case sensitive!<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf<br>
&gt; &gt; initrd winpe/${arch}/winpe.wim winpe.wim &larr; Names must match and must match the entry in your bcd!<br>
&gt; &gt; Imgstat &larr; enables you to see if all files have been loaded<br>
&gt; &gt; prompt &larr; stops until you continue after reading imgstat output<br>
&gt; &gt; boot || goto failed<br>
&gt; &gt; goto start<br>
&gt; &gt; <br>
&gt; &gt; My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.<br>
&gt; &gt; That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.<br>
&gt; &gt; E.g.:<br>
&gt; &gt; set sanboot-url <a href="http://123.456.789.012" target="_blank">http://123.456.789.012</a><br>
&gt; &gt; initrd ${sanboot-url}/win7pe_x86.iso<br>
&gt; &gt; chain syslinux/memdisk iso raw<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; mit freundlichen Gr&uuml;&szlig;en<br>
&gt; &gt; with kind regards<br>
&gt; &gt; <br>
&gt; &gt; i. A. Dipl.Ing. (FH) Frank Hummel<br>
&gt; &gt; Systementwicklung<br>
&gt; &gt; System development<br>
&gt; &gt; <br>
&gt; &gt; ads-tec GmbH<br>
&gt; &gt; Raiffeisenstr.14<br>
&gt; &gt; 70771 Leinfelden-Echterdingen<br>
&gt; &gt; Germany<br>
&gt; &gt; <br>
&gt; &gt; Tel.:&nbsp;&nbsp;&nbsp; +49 711 45894-220<br>
&gt; &gt; Fax:&nbsp;&nbsp;&nbsp; +49 711 45894-987<br>
&gt; &gt; E-Mail: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; &gt; Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; Von: <a href="mailto:ipxe-devel-bounces <at> lists.ipxe.org">ipxe-devel-bounces <at> lists.ipxe.org</a> [<a href="mailto:ipxe-devel-bounces <at> lists.ipxe.org">mailto:ipxe-devel-bounces <at> lists.ipxe.org</a>] Im Auftrag von Nicholas Krouse<br>
&gt; &gt; Gesendet: Montag, 14. April 2014 20:22<br>
&gt; &gt; An: <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; &gt; <br>
&gt; &gt; Hello <br>
&gt; &gt; <br>
&gt; &gt; I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over
 wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.<br>
&gt; &gt; <br>
&gt; &gt; Thanks<br>
&gt; &gt; Nick Krouse<br>
&gt; &gt; Computer Support Instructor<br>
&gt; &gt; Delaware Skills Center<br>
&gt; &gt; Deskillscenter.org<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ads-tec GmbH<br>
&gt; &gt; Sitz: 70771 Leinfelden-Echterdingen<br>
&gt; &gt; Registergericht Stuttgart HRB 224527<br>
&gt; &gt; <br>
&gt; &gt; Geschaeftsfuehrer:<br>
&gt; &gt; Dipl.-Ing. Thomas Speidel<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
&gt; &gt; geschuetzte Informationen. Wenn Sie nicht der richtige<br>
&gt; &gt; Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
&gt; &gt; haben, informieren Sie bitte sofort den Absender und <br>
&gt; &gt; vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
&gt; &gt; jegliche anderweitige Verwendung sowie die unbefugte<br>
&gt; &gt; Weitergabe dieser Mail sind nicht gestattet.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; <br>
&gt; &gt; This e-mail may contain confidential and/or privileged<br>
&gt; &gt; information. If you are not the intended recipient (or have<br>
&gt; &gt; received this e-mail in error) please notify the sender<br>
&gt; &gt; immediately and destroy this e-mail. Any unauthorized<br>
&gt; &gt; copying, disclosure, distribution or other use of the<br>
&gt; &gt; material or parts thereof are strictly forbidden.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ipxe-devel mailing list<br>
&gt; &gt; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; <a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
&gt; _______________________________________________<br>
&gt; ads-tec GmbH<br>
&gt; Sitz: 70771 Leinfelden-Echterdingen<br>
&gt; Registergericht Stuttgart HRB 224527<br>
&gt; <br>
&gt; Geschaeftsfuehrer:<br>
&gt; Dipl.-Ing. Thomas Speidel<br>
&gt; _______________________________________________<br>
&gt; Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
&gt; geschuetzte Informationen. Wenn Sie nicht der richtige<br>
&gt; Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
&gt; haben, informieren Sie bitte sofort den Absender und <br>
&gt; vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
&gt; jegliche anderweitige Verwendung sowie die unbefugte<br>
&gt; Weitergabe dieser Mail sind nicht gestattet.<br>
&gt; _______________________________________________<br>
&gt; <br>
&gt; This e-mail may contain confidential and/or privileged<br>
&gt; information. If you are not the intended recipient (or have<br>
&gt; received this e-mail in error) please notify the sender<br>
&gt; immediately and destroy this e-mail. Any unauthorized<br>
&gt; copying, disclosure, distribution or other use of the<br>
&gt; material or parts thereof are strictly forbidden.<br>
&gt; _______________________________________________</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div> 		 	   		  </div></div>
Ian Bannerman | 15 Apr 14:58 2014

Re: Issues chainbooting iPXE to WDS 2012R2

<!-- .hmmessage P { margin:0px; padding:0px } body.hmmessage { font-size: 12pt; font-family:Calibri } -->
I threw the photo on imgur so it wasn't lost in the chain here: http://i.imgur.com/TPcEOEb.png

I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling in various suggestions from the forum thread here: http://forum.ipxe.org/showthread.php?tid=7242 


How about this, have you confirmed that you can browse to the FTP server from another machine over the path ftp://10.200.0.74/boot/x86/ and see the file wdsnbp.com?

--Ian

From: nicholas.krouse <at> nccvt.k12.de.us
To: ian <at> internals.io
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
Date: Tue, 15 Apr 2014 12:28:09 +0000

<!-- .ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink { color:#0563C1; text-decoration:underline; } .ExternalClass span.ecxMsoHyperlinkFollowed { color:#954F72; text-decoration:underline; } .ExternalClass p { font-size:12.0pt; font-family:"Times New Roman","serif"; } .ExternalClass span.ecxEmailStyle18 { font-family:"Calibri","sans-serif"; color:#1F497D; } .ExternalClass .ecxMsoChpDefault { font-size:10.0pt; } .ExternalClass div.ecxWordSection1 { } -->

Ian

 

Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!

 

Thanks

Nick Krouse

 

From: Ian Bannerman [mailto:ian <at> internals.io]
Sent: Tuesday, April 15, 2014 8:14 AM
To: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org
Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2

 

I have systems downloading various wims to 'boot.wim' as he has without issue, yep! 

 

But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation / fourms discussions. For example, the iPXE documentation has examples on http://ipxe.org/howto/winpe and http://ipxe.org/howto/sccm where fonts are listed for older bootmgrs. 

 

Thanks,

--Ian

> Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> Date: Tue, 15 Apr 2014 14:08:06 +0200
> From: F.Hummel <at> ads-tec.de
> To: ian <at> internals.io; nicholas.krouse <at> nccvt.k12.de.us; ipxe-devel <at> lists.ipxe.org
>
> Well – found that sequence to be functional by trial-and-error.
> Did you try it?
>
> As far as the fonts are concerned - I do not use older bootmgr versions.
> If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.
> You will just see a black or blue (not BSOD) screen...
>
> mit freundlichen Grüßen
> with kind regards
>
> i. A. Dipl.Ing. (FH) Frank Hummel
> Systementwicklung
> System development
>
> ads-tec GmbH
> Raiffeisenstr.14
> 70771 Leinfelden-Echterdingen
> Germany
>
> Tel.:    +49 711 45894-220
> Fax:    +49 711 45894-987
> E-Mail: F.Hummel <at> ads-tec.de
> Web: www.ads-tec.de
>
>
>
>
> Von: Ian Bannerman [mailto:ian <at> internals.io]
> Gesendet: Dienstag, 15. April 2014 13:23
> An: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org
> Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
>
> That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!
>
> Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.
>
> My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.
>
> --Ian
> > Date: Tue, 15 Apr 2014 09:30:44 +0200
> > From: F.Hummel <at> ads-tec.de
> > To: nicholas.krouse <at> nccvt.k12.de.us; ipxe-devel <at> lists.ipxe.org
> > Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hi,
> >
> > :wds-server
> > dhcp
> > set wdsserver 10.200.0.74
> > set alternatetftp 10.200.0.74
> > set net0/dhcp-server ${wdsserver}
> > set net0/filename wdsbnp.com ← Typo, not the cause for the current prob
> > set net0/gateway ${wdsserver}
> > set net0/next-server ${wdsserver}
> > set net0/user-class PXEClient
> > -------------------------------------------------------------------
> > Your sequence:
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd BCD
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/winpe.wim boot.wim
> > boot || goto failed
> > goto start
> > -------------------------------------------------------------------
> > You are missing the fonts and left and right must look the same. Should look like this:
> >
> > :wimboot
> > cpuid --ext 29 && set arch amd64 || set arch x86
> > kernel wimboot
> > initrd winpe/${arch}/ISO/bootmgr bootmgr
> > initrd winpe/${arch}/ISO/boot/bcd bcd ← take care! Case sensitive!
> > initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi
> > initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf
> > initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf
> > initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf
> > initrd winpe/${arch}/winpe.wim winpe.wim ← Names must match and must match the entry in your bcd!
> > Imgstat ← enables you to see if all files have been loaded
> > prompt ← stops until you continue after reading imgstat output
> > boot || goto failed
> > goto start
> >
> > My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.
> > That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.
> > E.g.:
> > set sanboot-url http://123.456.789.012
> > initrd ${sanboot-url}/win7pe_x86.iso
> > chain syslinux/memdisk iso raw
> >
> >
> >
> > mit freundlichen Grüßen
> > with kind regards
> >
> > i. A. Dipl.Ing. (FH) Frank Hummel
> > Systementwicklung
> > System development
> >
> > ads-tec GmbH
> > Raiffeisenstr.14
> > 70771 Leinfelden-Echterdingen
> > Germany
> >
> > Tel.:    +49 711 45894-220
> > Fax:    +49 711 45894-987
> > E-Mail: F.Hummel <at> ads-tec.de
> > Web: www.ads-tec.de
> >
> >
> >
> >
> > Von: ipxe-devel-bounces <at> lists.ipxe.org [mailto:ipxe-devel-bounces <at> lists.ipxe.org] Im Auftrag von Nicholas Krouse
> > Gesendet: Montag, 14. April 2014 20:22
> > An: ipxe-devel <at> lists.ipxe.org
> > Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2
> >
> > Hello
> >
> > I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.
> >
> > Thanks
> > Nick Krouse
> > Computer Support Instructor
> > Delaware Skills Center
> > Deskillscenter.org
> > _______________________________________________
> > ads-tec GmbH
> > Sitz: 70771 Leinfelden-Echterdingen
> > Registergericht Stuttgart HRB 224527
> >
> > Geschaeftsfuehrer:
> > Dipl.-Ing. Thomas Speidel
> > _______________________________________________
> > Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> > geschuetzte Informationen. Wenn Sie nicht der richtige
> > Adressat sind oder diese E-Mail irrtuemlich erhalten
> > haben, informieren Sie bitte sofort den Absender und
> > vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> > jegliche anderweitige Verwendung sowie die unbefugte
> > Weitergabe dieser Mail sind nicht gestattet.
> > _______________________________________________
> >
> > This e-mail may contain confidential and/or privileged
> > information. If you are not the intended recipient (or have
> > received this e-mail in error) please notify the sender
> > immediately and destroy this e-mail. Any unauthorized
> > copying, disclosure, distribution or other use of the
> > material or parts thereof are strictly forbidden.
> > _______________________________________________
> > _______________________________________________
> > ipxe-devel mailing list
> > ipxe-devel <at> lists.ipxe.org
> > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> _______________________________________________
> ads-tec GmbH
> Sitz: 70771 Leinfelden-Echterdingen
> Registergericht Stuttgart HRB 224527
>
> Geschaeftsfuehrer:
> Dipl.-Ing. Thomas Speidel
> _______________________________________________
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich
> geschuetzte Informationen. Wenn Sie nicht der richtige
> Adressat sind oder diese E-Mail irrtuemlich erhalten
> haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren,
> jegliche anderweitige Verwendung sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
> _______________________________________________
>
> This e-mail may contain confidential and/or privileged
> information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender
> immediately and destroy this e-mail. Any unauthorized
> copying, disclosure, distribution or other use of the
> material or parts thereof are strictly forbidden.
> _______________________________________________

<div><div dir="ltr">

&lt;!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--&gt;<div dir="ltr">I threw the photo on imgur so it wasn't lost in the chain here:&nbsp;http://i.imgur.com/TPcEOEb.png</div>
<div dir="ltr"><br></div>
<div dir="ltr">I don't have much experience with tftp myself, so I'm not particularly sure what steps to take to troubleshoot the error. From your previously sent out menu file I can see you've tried pulling in various suggestions from the forum thread here:&nbsp;http://forum.ipxe.org/showthread.php?tid=7242&nbsp;</div>
<div dir="ltr"><br></div>
<div dir="ltr"><br></div>
<div dir="ltr">How about this, have you confirmed that you can browse to the FTP server from another machine over the path ftp://10.200.0.74/boot/x86/ and see the file wdsnbp.com?</div>
<div dir="ltr"><br></div>
<div dir="ltr">--Ian<br><br><div>From: nicholas.krouse <at> nccvt.k12.de.us<br>To: ian <at> internals.io<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>Date: Tue, 15 Apr 2014 12:28:09 +0000<br><br>&lt;!--
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:#0563C1;
text-decoration:underline;
}

.ExternalClass span.ecxMsoHyperlinkFollowed {
color:#954F72;
text-decoration:underline;
}

.ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}

.ExternalClass span.ecxEmailStyle18 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}

.ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}

.ExternalClass div.ecxWordSection1 {
}

--&gt;<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span>Ian</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<p class="ecxMsoNormal"><span>Thanks for your help. Attached photo is the error I get when trying to boot ipxe then chain load a wds server. The ipxe server has all diags and live environments
 and I use wds 2012 r2 from my windows installs for students (its very easy for me to manage). I believe the issue is with my WDS server not having the correct tftp packet size. Thanks in advance for your time!</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<p class="ecxMsoNormal"><span>Thanks</span></p>
<p class="ecxMsoNormal"><span>Nick Krouse</span></p>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
<div>
<div>
<p class="ecxMsoNormal"><span>From:</span><span> Ian Bannerman [mailto:ian <at> internals.io]
<br>Sent: Tuesday, April 15, 2014 8:14 AM<br>To: Hummel Frank; Nicholas Krouse; ipxe-devel <at> lists.ipxe.org<br>Subject: RE: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2</span></p>
</div>
</div>
<p class="ecxMsoNormal">&nbsp;</p>
<div>
<p class="ecxMsoNormal"><span>I have systems downloading various wims to 'boot.wim' as he has without issue, yep!&nbsp;</span></p>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>But! I do not have personal experience using bootmgr without fonts (prior to Windows 8), nor info on the potential impact it has on errors. I just gleaned that from the documentation / fourms
 discussions. For example, the iPXE documentation has examples on&nbsp;<a href="http://ipxe.org/howto/winpe" target="_blank">http://ipxe.org/howto/winpe</a> and&nbsp;<a href="http://ipxe.org/howto/sccm" target="_blank">http://ipxe.org/howto/sccm</a> where fonts are listed for older bootmgrs.&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>&nbsp;</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>Thanks,</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span>--Ian</span></p>
<div>
<p class="ecxMsoNormal"><span>&gt; Subject: AW: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; Date: Tue, 15 Apr 2014 14:08:06 +0200<br>
&gt; From: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; To: <a href="mailto:ian <at> internals.io">ian <at> internals.io</a>; <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">
nicholas.krouse <at> nccvt.k12.de.us</a>; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; <br>
&gt; Well &ndash; found that sequence to be functional by trial-and-error.<br>
&gt; Did you try it?<br>
&gt; <br>
&gt; As far as the fonts are concerned - I do not use older bootmgr versions.<br>
&gt; If you don't load the fonts (there are other sets for older bootmgr) you will not see error messages if the PE does not boot successfully.<br>
&gt; You will just see a black or blue (not BSOD) screen...<br>
&gt; <br>
&gt; mit freundlichen Gr&uuml;&szlig;en<br>
&gt; with kind regards<br>
&gt; <br>
&gt; i. A. Dipl.Ing. (FH) Frank Hummel<br>
&gt; Systementwicklung<br>
&gt; System development<br>
&gt; <br>
&gt; ads-tec GmbH<br>
&gt; Raiffeisenstr.14<br>
&gt; 70771 Leinfelden-Echterdingen<br>
&gt; Germany<br>
&gt; <br>
&gt; Tel.:&nbsp;&nbsp;&nbsp; +49 711 45894-220<br>
&gt; Fax:&nbsp;&nbsp;&nbsp; +49 711 45894-987<br>
&gt; E-Mail: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Von: Ian Bannerman [<a href="mailto:ian <at> internals.io">mailto:ian <at> internals.io</a>]
<br>
&gt; Gesendet: Dienstag, 15. April 2014 13:23<br>
&gt; An: Hummel Frank; Nicholas Krouse; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; Betreff: RE: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; <br>
&gt; That's odd. I have not encountered any issues using a similar set up to this - initrd winpe/${arch}/winpe.wim winpe.wim &larr; Names must match and must match the entry in your bcd!<br>
&gt; <br>
&gt; Are you sure that's a requirement? If boot.wim matches the reference in the BCD this should be fine.<br>
&gt; <br>
&gt; My understanding is also that fonts are only required for Windows 8 and newer WIM/bootmgr combos.<br>
&gt; <br>
&gt; --Ian<br>
&gt; &gt; Date: Tue, 15 Apr 2014 09:30:44 +0200<br>
&gt; &gt; From: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; &gt; To: <a href="mailto:nicholas.krouse <at> nccvt.k12.de.us">nicholas.krouse <at> nccvt.k12.de.us</a>;
<a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; Subject: Re: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; &gt; <br>
&gt; &gt; Hi,<br>
&gt; &gt; <br>
&gt; &gt; :wds-server<br>
&gt; &gt; dhcp<br>
&gt; &gt; set wdsserver 10.200.0.74<br>
&gt; &gt; set alternatetftp 10.200.0.74<br>
&gt; &gt; set net0/dhcp-server ${wdsserver}<br>
&gt; &gt; set net0/filename wdsbnp.com &larr; Typo, not the cause for the current prob<br>
&gt; &gt; set net0/gateway ${wdsserver}<br>
&gt; &gt; set net0/next-server ${wdsserver}<br>
&gt; &gt; set net0/user-class PXEClient<br>
&gt; &gt; -------------------------------------------------------------------<br>
&gt; &gt; Your sequence:<br>
&gt; &gt; :wimboot<br>
&gt; &gt; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86<br>
&gt; &gt; kernel wimboot<br>
&gt; &gt; initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/bcd BCD<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
&gt; &gt; initrd winpe/${arch}/winpe.wim boot.wim<br>
&gt; &gt; boot || goto failed<br>
&gt; &gt; goto start<br>
&gt; &gt; -------------------------------------------------------------------<br>
&gt; &gt; You are missing the fonts and left and right must look the same. Should look like this:<br>
&gt; &gt; <br>
&gt; &gt; :wimboot<br>
&gt; &gt; cpuid --ext 29 &amp;&amp; set arch amd64 || set arch x86<br>
&gt; &gt; kernel wimboot<br>
&gt; &gt; initrd winpe/${arch}/ISO/bootmgr bootmgr<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/bcd bcd &larr; take care! Case sensitive!<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/boot.sdi boot.sdi<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segmono_boot.ttf segmono_boot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segoe_slboot.ttf segoe_slboot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/segoen_slboot.ttf segoen_slboot.ttf<br>
&gt; &gt; initrd winpe/${arch}/ISO/boot/wgl4_boot.ttf wgl4_boot.ttf<br>
&gt; &gt; initrd winpe/${arch}/winpe.wim winpe.wim &larr; Names must match and must match the entry in your bcd!<br>
&gt; &gt; Imgstat &larr; enables you to see if all files have been loaded<br>
&gt; &gt; prompt &larr; stops until you continue after reading imgstat output<br>
&gt; &gt; boot || goto failed<br>
&gt; &gt; goto start<br>
&gt; &gt; <br>
&gt; &gt; My experience with wimboot is that it is quite unreliable. Sometimes it works, sometimes not - depending on the boot.wim file. But I could not find out why it fails with some wim-files and succeeds with others.<br>
&gt; &gt; That's why I use syslinux memdisk and the ISO file containing the very same wim-file failing with wimboot which always works.<br>
&gt; &gt; E.g.:<br>
&gt; &gt; set sanboot-url <a href="http://123.456.789.012" target="_blank">http://123.456.789.012</a><br>
&gt; &gt; initrd ${sanboot-url}/win7pe_x86.iso<br>
&gt; &gt; chain syslinux/memdisk iso raw<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; mit freundlichen Gr&uuml;&szlig;en<br>
&gt; &gt; with kind regards<br>
&gt; &gt; <br>
&gt; &gt; i. A. Dipl.Ing. (FH) Frank Hummel<br>
&gt; &gt; Systementwicklung<br>
&gt; &gt; System development<br>
&gt; &gt; <br>
&gt; &gt; ads-tec GmbH<br>
&gt; &gt; Raiffeisenstr.14<br>
&gt; &gt; 70771 Leinfelden-Echterdingen<br>
&gt; &gt; Germany<br>
&gt; &gt; <br>
&gt; &gt; Tel.:&nbsp;&nbsp;&nbsp; +49 711 45894-220<br>
&gt; &gt; Fax:&nbsp;&nbsp;&nbsp; +49 711 45894-987<br>
&gt; &gt; E-Mail: <a href="mailto:F.Hummel <at> ads-tec.de">F.Hummel <at> ads-tec.de</a><br>
&gt; &gt; Web: <a href="http://www.ads-tec.de" target="_blank">www.ads-tec.de</a><br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; Von: <a href="mailto:ipxe-devel-bounces <at> lists.ipxe.org">ipxe-devel-bounces <at> lists.ipxe.org</a> [<a href="mailto:ipxe-devel-bounces <at> lists.ipxe.org">mailto:ipxe-devel-bounces <at> lists.ipxe.org</a>] Im Auftrag von Nicholas Krouse<br>
&gt; &gt; Gesendet: Montag, 14. April 2014 20:22<br>
&gt; &gt; An: <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; Betreff: [ipxe-devel] Issues chainbooting iPXE to WDS 2012R2<br>
&gt; &gt; <br>
&gt; &gt; Hello <br>
&gt; &gt; <br>
&gt; &gt; I use iPXE for my main boot menu in my classroom for my students. When I attempt to chainboot to my WDS Server 2012 r2 I get error 0x3d126001 and the boot fails. I have searched google and ipxe forums high and low looking for a solution. I use wds over
 wimboot as it make management of my wim files quick and easy for me and my students. If there is any way you could help me it would be greatly appreciated! Attached is my current menu.ipxe. Thanks for your time in advance.<br>
&gt; &gt; <br>
&gt; &gt; Thanks<br>
&gt; &gt; Nick Krouse<br>
&gt; &gt; Computer Support Instructor<br>
&gt; &gt; Delaware Skills Center<br>
&gt; &gt; Deskillscenter.org<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ads-tec GmbH<br>
&gt; &gt; Sitz: 70771 Leinfelden-Echterdingen<br>
&gt; &gt; Registergericht Stuttgart HRB 224527<br>
&gt; &gt; <br>
&gt; &gt; Geschaeftsfuehrer:<br>
&gt; &gt; Dipl.-Ing. Thomas Speidel<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
&gt; &gt; geschuetzte Informationen. Wenn Sie nicht der richtige<br>
&gt; &gt; Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
&gt; &gt; haben, informieren Sie bitte sofort den Absender und <br>
&gt; &gt; vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
&gt; &gt; jegliche anderweitige Verwendung sowie die unbefugte<br>
&gt; &gt; Weitergabe dieser Mail sind nicht gestattet.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; <br>
&gt; &gt; This e-mail may contain confidential and/or privileged<br>
&gt; &gt; information. If you are not the intended recipient (or have<br>
&gt; &gt; received this e-mail in error) please notify the sender<br>
&gt; &gt; immediately and destroy this e-mail. Any unauthorized<br>
&gt; &gt; copying, disclosure, distribution or other use of the<br>
&gt; &gt; material or parts thereof are strictly forbidden.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ipxe-devel mailing list<br>
&gt; &gt; <a href="mailto:ipxe-devel <at> lists.ipxe.org">ipxe-devel <at> lists.ipxe.org</a><br>
&gt; &gt; <a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
&gt; _______________________________________________<br>
&gt; ads-tec GmbH<br>
&gt; Sitz: 70771 Leinfelden-Echterdingen<br>
&gt; Registergericht Stuttgart HRB 224527<br>
&gt; <br>
&gt; Geschaeftsfuehrer:<br>
&gt; Dipl.-Ing. Thomas Speidel<br>
&gt; _______________________________________________<br>
&gt; Diese E-Mail enthaelt vertrauliche und/oder rechtlich<br>
&gt; geschuetzte Informationen. Wenn Sie nicht der richtige<br>
&gt; Adressat sind oder diese E-Mail irrtuemlich erhalten<br>
&gt; haben, informieren Sie bitte sofort den Absender und <br>
&gt; vernichten Sie diese E-Mail. Das unerlaubte Kopieren,<br>
&gt; jegliche anderweitige Verwendung sowie die unbefugte<br>
&gt; Weitergabe dieser Mail sind nicht gestattet.<br>
&gt; _______________________________________________<br>
&gt; <br>
&gt; This e-mail may contain confidential and/or privileged<br>
&gt; information. If you are not the intended recipient (or have<br>
&gt; received this e-mail in error) please notify the sender<br>
&gt; immediately and destroy this e-mail. Any unauthorized<br>
&gt; copying, disclosure, distribution or other use of the<br>
&gt; material or parts thereof are strictly forbidden.<br>
&gt; _______________________________________________</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
 		 	   		  </div></div>
Ben Hildred | 15 Apr 05:41 2014
Picon

Re: script failure caused by adding one line

the line you want is
iseq ${vodserver} 6 && set bu http://10.109.0.165/


On Mon, Apr 14, 2014 at 6:02 PM, Larry Brigman <larry.brigman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
I'm finding it difficult to troubleshoot failing ipxe scripts.
Even with DEBUG=script on I'm getting a message that states image too large to load
and it ipxe jumps back to local boot without stopping a the prompts or executing
the error paths

Here is the script:
-----------------------------------------
#!ipxe

:vod_menu
menu Vod Server Install [installing to IP: ${netX/ip}]
item --gap
item --key 0 5.0.8 Vod Server 5.[0].8
item --key 2 5.2.7 Vod Server 5.[2].7
item  5.2.8 Vod Server 5.2.8
item --key 3 5.3.2 Vod Server 5.[3].2
item --key 4 5.4.0 Vod Server 5.[4].0
item  5.4.1 Vod Server 5.4.1
item  5.4.2 Vod Server 5.4.2
item --key 5 5.5.0 Vod Server 5.[5].0
item 6 Vod Server 5.5.0 on RHEL[6]
choose vodserver || goto vod_error
iseq vodserver 6 && set bu http://10.109.0.165/
goto vodload

:vod_error
echo selection error in vod menu file
prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... && shell ||
chain boot.ipxe ||
echo Chaining back to main menu failed. Reverting to local boot.
exit 0

:vodload
echo Loading VodServer ${vodserver} ....
initrd ${base_url}${vodserver}/isolinux/initrd.img || goto vodload_error
kernel ${base_url}${vodserver}/isolinux/vmlinuz ramdisk_size=32705 noipv6 dns=10.109.3.240 ks=${base_url}bko/ks/nvs-${vodserver}.cfg nompath syslog=134.242.160.43 ksdevice=bootif BOOTIF=01-${netX/mac} || goto vodload_error
boot

:vodload_error
echo An error occurred during the vodload section
prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... && shell ||
echo Reverting to local boot.
exit 0
---------------------------------------------------------
If I remove the iseq line or comment it out things work.

I'm using git master to build undionly.kpxe which is getting chain loaded from the pxerom.

I'm needing to switch the server url to a different server if a the selection is made but
all of my old selection loads also break. 

Any clues provided would be great.



_______________________________________________
ipxe-devel mailing list
ipxe-devel-Ajx3hB6KsW1nerjlECmc1w@public.gmane.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel




--
--
Ben Hildred
Automation Support Services
303 815 6721
<div>
<div dir="ltr">the line you want is<div>iseq ${vodserver} 6 &amp;&amp; set bu <a href="http://10.109.0.165/">http://10.109.0.165/</a>
</div>
</div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 6:02 PM, Larry Brigman <span dir="ltr">&lt;<a href="mailto:larry.brigman@..." target="_blank">larry.brigman@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>I'm finding it difficult to troubleshoot failing ipxe scripts.<br>
</div>Even with DEBUG=script on I'm getting a message that states image too large to load<br>
</div>and it ipxe jumps back to local boot without stopping a the prompts or executing<br>the error paths<br><br>
</div>Here is the script:<br>-----------------------------------------<br>#!ipxe<br><br>:vod_menu<br>menu Vod Server Install [installing to IP: ${netX/ip}]<br>

item --gap<br>item --key 0 5.0.8 Vod Server 5.[0].8<br>item --key 2 5.2.7 Vod Server 5.[2].7<br>item&nbsp; 5.2.8 Vod Server 5.2.8<br>item --key 3 5.3.2 Vod Server 5.[3].2<br>item --key 4 5.4.0 Vod Server 5.[4].0<br>item&nbsp; 5.4.1 Vod Server 5.4.1<br>

item&nbsp; 5.4.2 Vod Server 5.4.2<br>item --key 5 5.5.0 Vod Server 5.[5].0<br>item 6 Vod Server 5.5.0 on RHEL[6]<br>choose vodserver || goto vod_error<br>iseq vodserver 6 &amp;&amp; set bu <a href="http://10.109.0.165/" target="_blank">http://10.109.0.165/</a><br>

goto vodload<br><br>:vod_error<br>echo selection error in vod menu file<br>prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... &amp;&amp; shell ||<br>chain boot.ipxe ||<br>echo Chaining back to main menu failed. Reverting to local boot.<br>

exit 0<br><br>:vodload<br>echo Loading VodServer ${vodserver} ....<br>initrd ${base_url}${vodserver}/isolinux/initrd.img || goto vodload_error<br>kernel ${base_url}${vodserver}/isolinux/vmlinuz ramdisk_size=32705 noipv6 dns=10.109.3.240 ks=${base_url}bko/ks/nvs-${vodserver}.cfg nompath syslog=134.242.160.43 ksdevice=bootif BOOTIF=01-${netX/mac} || goto vodload_error<br>

boot<br><br>:vodload_error<br>echo An error occurred during the vodload section<br>prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... &amp;&amp; shell ||<br>echo Reverting to local boot.<br>exit 0<br>

---------------------------------------------------------<br>
</div>If I remove the iseq line or comment it out things work.<br><br>
</div>I'm using git master to build undionly.kpxe which is getting chain loaded from the pxerom.<br>
</div>
<div><br></div>I'm needing to switch the server url to a different server if a the selection is made but<br>
</div>all of my old selection loads also break.&nbsp; <br><br>
</div>Any clues provided would be great.<br><br><br>
</div>
<br>_______________________________________________<br>
ipxe-devel mailing list<br><a href="mailto:ipxe-devel@...">ipxe-devel@...</a><br><a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br><br>
</blockquote>
</div>
<br><br clear="all"><div><br></div>-- <br><div>--</div>
<div>
<div>Ben Hildred</div>
<div>Automation Support Services</div>
</div>
<div>303 815 6721</div>
</div>
</div>
Larry Brigman | 15 Apr 02:02 2014
Picon

script failure caused by adding one line

I'm finding it difficult to troubleshoot failing ipxe scripts.
Even with DEBUG=script on I'm getting a message that states image too large to load
and it ipxe jumps back to local boot without stopping a the prompts or executing
the error paths

Here is the script:
-----------------------------------------
#!ipxe

:vod_menu
menu Vod Server Install [installing to IP: ${netX/ip}]
item --gap
item --key 0 5.0.8 Vod Server 5.[0].8
item --key 2 5.2.7 Vod Server 5.[2].7
item  5.2.8 Vod Server 5.2.8
item --key 3 5.3.2 Vod Server 5.[3].2
item --key 4 5.4.0 Vod Server 5.[4].0
item  5.4.1 Vod Server 5.4.1
item  5.4.2 Vod Server 5.4.2
item --key 5 5.5.0 Vod Server 5.[5].0
item 6 Vod Server 5.5.0 on RHEL[6]
choose vodserver || goto vod_error
iseq vodserver 6 && set bu http://10.109.0.165/
goto vodload

:vod_error
echo selection error in vod menu file
prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... && shell ||
chain boot.ipxe ||
echo Chaining back to main menu failed. Reverting to local boot.
exit 0

:vodload
echo Loading VodServer ${vodserver} ....
initrd ${base_url}${vodserver}/isolinux/initrd.img || goto vodload_error
kernel ${base_url}${vodserver}/isolinux/vmlinuz ramdisk_size=32705 noipv6 dns=10.109.3.240 ks=${base_url}bko/ks/nvs-${vodserver}.cfg nompath syslog=134.242.160.43 ksdevice=bootif BOOTIF=01-${netX/mac} || goto vodload_error
boot

:vodload_error
echo An error occurred during the vodload section
prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... && shell ||
echo Reverting to local boot.
exit 0
---------------------------------------------------------
If I remove the iseq line or comment it out things work.

I'm using git master to build undionly.kpxe which is getting chain loaded from the pxerom.

I'm needing to switch the server url to a different server if a the selection is made but
all of my old selection loads also break. 

Any clues provided would be great.


<div><div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>I'm finding it difficult to troubleshoot failing ipxe scripts.<br>
</div>Even with DEBUG=script on I'm getting a message that states image too large to load<br>
</div>and it ipxe jumps back to local boot without stopping a the prompts or executing<br>the error paths<br><br>
</div>Here is the script:<br>-----------------------------------------<br>#!ipxe<br><br>:vod_menu<br>menu Vod Server Install [installing to IP: ${netX/ip}]<br>
item --gap<br>item --key 0 5.0.8 Vod Server 5.[0].8<br>item --key 2 5.2.7 Vod Server 5.[2].7<br>item&nbsp; 5.2.8 Vod Server 5.2.8<br>item --key 3 5.3.2 Vod Server 5.[3].2<br>item --key 4 5.4.0 Vod Server 5.[4].0<br>item&nbsp; 5.4.1 Vod Server 5.4.1<br>
item&nbsp; 5.4.2 Vod Server 5.4.2<br>item --key 5 5.5.0 Vod Server 5.[5].0<br>item 6 Vod Server 5.5.0 on RHEL[6]<br>choose vodserver || goto vod_error<br>iseq vodserver 6 &amp;&amp; set bu <a href="http://10.109.0.165/">http://10.109.0.165/</a><br>
goto vodload<br><br>:vod_error<br>echo selection error in vod menu file<br>prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... &amp;&amp; shell ||<br>chain boot.ipxe ||<br>echo Chaining back to main menu failed. Reverting to local boot.<br>
exit 0<br><br>:vodload<br>echo Loading VodServer ${vodserver} ....<br>initrd ${base_url}${vodserver}/isolinux/initrd.img || goto vodload_error<br>kernel ${base_url}${vodserver}/isolinux/vmlinuz ramdisk_size=32705 noipv6 dns=10.109.3.240 ks=${base_url}bko/ks/nvs-${vodserver}.cfg nompath syslog=134.242.160.43 ksdevice=bootif BOOTIF=01-${netX/mac} || goto vodload_error<br>
boot<br><br>:vodload_error<br>echo An error occurred during the vodload section<br>prompt --key 0x02 --timeout 10000 Press Ctrl-B for the iPXE command line... &amp;&amp; shell ||<br>echo Reverting to local boot.<br>exit 0<br>
---------------------------------------------------------<br>
</div>If I remove the iseq line or comment it out things work.<br><br>
</div>I'm using git master to build undionly.kpxe which is getting chain loaded from the pxerom.<br>
</div>
<div><br></div>I'm needing to switch the server url to a different server if a the selection is made but<br>
</div>all of my old selection loads also break.&nbsp; <br><br>
</div>Any clues provided would be great.<br><br><br>
</div></div>
Mike Harris | 15 Apr 01:08 2014
Picon

Hang during 'establishing link' using ASIX USB dongle and undi driver

Hi, I was in IRC earlier discussing this, but we figured the mailing list would be better.

I'm trying to get a ASIX USB dongle booting with iPXE using chainloading and the UNDI drivers. It's hanging during the 'Establishing link' step. This is on a Lenovo X1 Carbon, an ultrabook with no onboard NIC, and this device is the only one Lenovo supports for PXE booting, going so far as to blacklist other USB device IDs in the BIOS.

I've attached two screenshots, one with DEBUG=undinet:15 and one without. For some reason, when I enable debugging, the hang happens at a slightly earlier spot (during 'Enumerating devices'). Both were built with the same embedded script, which I've attached as 'debug.ipxe'. I think the hang is in the 'dhcp' line. Initially the link lights on the device are off, and iPXE prints 'Establishing link', which a dot every few seconds. The link lights turn on, and the iPXE dots stop. Maybe a bug in the return from the USB device's ROM?

Let me know what else you need, and thanks for the help.


-mike
Attachment (debug.ipxe): application/octet-stream, 599 bytes
<div><div dir="ltr">
<div>Hi, I was in IRC earlier discussing this, but we figured the mailing list would be better.</div>
<div><br></div>
<div>I'm trying to get a ASIX USB dongle booting with iPXE using chainloading and the UNDI drivers. It's hanging during the 'Establishing link' step. This is on a Lenovo X1 Carbon, an ultrabook with no onboard NIC, and this device is the only one Lenovo supports for PXE booting, going so far as to blacklist other USB device IDs in the BIOS.</div>

<div><br></div>
<div>I've attached two screenshots, one with DEBUG=undinet:15 and one without. For some reason, when I enable debugging, the hang happens at a slightly earlier spot (during 'Enumerating devices'). Both were built with the same embedded script, which I've attached as 'debug.ipxe'. I think the hang is in the 'dhcp' line. Initially the link lights on the device are off, and iPXE prints 'Establishing link', which a dot every few seconds. The link lights turn on, and the iPXE dots stop. Maybe a bug in the return from the USB device's ROM?</div>

<div><br></div>
<div>Let me know what else you need, and thanks for the help.</div>
<div><br></div>
<div><br></div>
<div>-mike</div>
</div></div>

Gmane