Hi Peter et al, Just wanted to let you know my heartfelt appretiation of what you and the other devs have done in integrating gpxe and pxelinux... it works wonderfully well for me... I simply swapped my pxelinux.0 for my gpxelinux.0 and modified my pxelinux.cfg/default to use urls to refer to the kernel and initial ram disk images and it worked perfectly (dns resolution and all). This is a huge step forward and wonderful thing! I thank you!!! Cheers, Doug
When using gpxelinux.0, pxeboot.com keeps looping, but when I use pxelinux.0, I
do not have the same problem.
Trying to load: pxelinux.cfg/default
Downloaded WDSNBP...
WDSNBP started using DHCP Referral.
Contacting Server: 10.1.1.20 (Gateway: 0.0.0.0).
Architecture: x64
TFTP Download: Boot\x86\wdsnbp.com
.
TFTP Download: boot\x64\pxeboot.com
.
TFTP Download: boot\x64\pxeboot.com
.
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
a178235 wrote:> When using gpxelinux.0, pxeboot.com keeps looping, but when I use pxelinux.0, I do not have the same problem. > > Trying to load: pxelinux.cfg/default > > Downloaded WDSNBP... > > WDSNBP started using DHCP Referral. > Contacting Server: 10.1.1.20 (Gateway: 0.0.0.0). > Architecture: x64 > TFTP Download: Boot\x86\wdsnbp.com > . > TFTP Download: boot\x64\pxeboot.com > . > TFTP Download: boot\x64\pxeboot.com > . >As was stated in the announcement, booting another PXE NBP from gpxelinux.0 is not supported at this time, and it looks to me like your initial "WDSNBP" is. -hpa
Sorry it didn?t sink in when I first read the announcement. I?m not sure if wsdnbp.com, pxeboot.com, bootmgr.exe, and boot.sdi would even work over HTTP, so would you consider adding Microsoft SDI file support to SYSLINUX? You can find a patch file at http://remile.free.fr/syslinux/syslinux_sdi_support-0.1.2.patch. This would allow bypassing the above loaders and directly loading a WinPE image. "H. Peter Anvin" <hpa at zytor.com> wrote: a178235 wrote:> When using gpxelinux.0, pxeboot.com keeps looping, but when I use pxelinux.0, I do not have the same problem. > > Trying to load: pxelinux.cfg/default > > Downloaded WDSNBP... > > WDSNBP started using DHCP Referral. > Contacting Server: 10.1.1.20 (Gateway: 0.0.0.0). > Architecture: x64 > TFTP Download: Boot\x86\wdsnbp.com > . > TFTP Download: boot\x64\pxeboot.com > . > TFTP Download: boot\x64\pxeboot.com > . >As was stated in the announcement, booting another PXE NBP from gpxelinux.0 is not supported at this time, and it looks to me like your initial "WDSNBP" is. -hpa _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic. --------------------------------- Special deal for Yahoo! users & friends - No Cost. Get a month of Blockbuster Total Access now
a178235 wrote:> Sorry it didn?t sink in when I first read the announcement. I?m not sure if wsdnbp.com, pxeboot.com, bootmgr.exe, and boot.sdi would even work over HTTP, so would you consider adding Microsoft SDI file support to SYSLINUX? You can find a patch file at http://remile.free.fr/syslinux/syslinux_sdi_support-0.1.2.patch. This would allow bypassing the above loaders and directly loading a WinPE image.I looked over the patch, and it looks sane on the surface of it. It looks like it needs updating for the current source base, but it should be easy to do. Thanks for pointing me to it! -hpa