Re: gpxe and memdisk could not boot winpe diskimage
"Miller, Shao" <[email protected]> Mon, 28 Sep 2009 01:10:57 -0400
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
It sort-of looks like my e-mail was wrecked somewhere along the line. I've attached the sample script to this e-mail. - Shao -----Original Message----- From: Miller, Shao Sent: Monday, September 28, 2009 00:39 To: ShenQiyu Cc: [email protected] Subject: RE: [Etherboot-discuss] gpxe and memdisk could not boot winpe diskimage Good day Paul, In regards to your gPXE -> MEMDISK setup failing, versus gPXE -> PXELINUX -> MEMDISK succeeding: As an interim solution, you could very well use gPXE supported protocols (such as HTTP) from PXELINUX. Simply use a gPXE script to set DHCP option 210 for PXELINUX to use. Something like: #!gpxe # Assuming this is an embedded script, leave the next line uncommented # otherwise, perhaps you chain this script in which case you do not # need to perform a DHCP transaction again dhcp net0 set 210:string http://webserver/ chain ${210:string}pxelinux.0 and then your PXELINUX config-file will reference MEMDISK and the Windows PE image. They will be fetched with the DHCP option 210 prefix. The gPXE community will have to investigate this MEMDISK incompatibility at some point, surely. - 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 _______________________________________________ Etherboot-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
paul.gpxe
(application/octet-stream, 261 B) - not displayed