Re: set 210:string script problem

Good day Daniel,

Don't use Windows Notepad to edit gPXE scripts.  If you do, you should
run dos2unix on the script before embedding it into your gPXE build.
This has been fixed in the latest gPXE, but not very slightly older gPXE
0.9.7+ versions.

gPXE scripts cannot simply be sitting inside the .ISO; you need to
compile ("embed") scripts into gPXE.  To build the gPXE .ISO with an
embedded script, do:

make EMBEDDED_IMAGE=~/myscript.gpxe bin/gpxe.iso

where "myscript.gpxe" is the script saved in your home directory, and
you execute this command from the gpxe/src/ directory.

Also, throw in some 'echo' commands into your script, which will show
you that it's not being executed, because you haven't embedded it.
Something like:

#!gpxe
echo gPXE script for HTTP-booting by Daniel
dhcp net0
set 210:string http://domain.de/boot/
echo PXELINUX prefix is set to ${210:string}
chain ${210:string}pxelinux.0
echo PXELINUX exited, weird!

If you aren't compiling the gPXE .ISO yourself, you can simply put the
script way down at the bottom of
http://rom-o-matic.net/gpxe/gpxe-git/gpxe.git/contrib/rom-o-matic/build.
php and then "Get Image".

- Shao Miller

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf