similar to: SYSLINUX 3.70 released

I have produced a first cut of integrating gPXE with PXELINUX. This builds, in addition to the usual pxelinux.0, an image called gpxelinux.0 which includes the gPXE network stack. The result is that one can now download images via (almost) any network protocol supported by gPXE, including http. This lets one do fun things like using a CGI or PHP script for the configuration file. SAN

Hello everyone, I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX, which would get confused by directories with deleted file entries. Special thanks to Stas Kysel of rPath, Inc. for spotting this problem and giving me an excellent test case; and of course to rPath, Inc. in general for being my employer and being extremely supportive of my SYSLINUX work! I have also

Hello everyone I am experiencing problems with PXELinux/gPXE when netbooting using HTTP. The problems I encounter: - When the intel bootROM is sending out a DHCPDISCOVER it might not recieve an IP address, but the server did send out a OFFER. Capturing packets reveals the packets have been sent, and the client _should_ have recieved it. But when it passes that stage: - When the gPXE bootROM is

>Velu Erwan wrote: >>>The real reason is it dropped off my mental list, since I don't have any >>>way to test this stuff. >>> >>>Either way, I would actually prefer to see this done as a COM32 module, >>>similar to mboot, rather in the syslinux core if at all possible. >> >> I don't have the skill to do it but I can give my

Have a look at the 911cd forums. I wrote the initial thread on RAM booting WinPE. To answer to question... memdisk won't work with Windows. Windows uses 32bit access (direct HW access) and memdisk relies on the BIOS. Any programs that don't use the BIOS disk interfaces will not work. The other problem is the allocation of memory. Windows doesn't respect the memdisk allocation.

Hi all, I have pushed out a prerelease of one of the development branches (I currently have three development branches open), 3.70-pre1. This release revamps a whole lot of internal APIs to support reading files without knowing their length ahead of time. This is necessary in order to support network protocols which do not advertise the transfer size. The immediate user-visible change is

The following patch for chain.c32 adds support to boot the Recovery Console of Windows NT/2K/XP. Normally when you want to boot the recovery console, you need to patch "cmdcons\0" into the bootsectorof the partition (8 bytes starting at 0x3 (4th byte)). We can do this patching in memory: strcpy((char *) 0x7c03, "cmdcons"); To boot the recovery console with chain.c32:

I have just pushed out SYSLINUX 3.70-pre8. The two main differences is that I have updated the gPXE source base, and added a sanboot module (sanboot.c32). sanboot.c32 *should* be capable of initiating an iSCSI or AoE boot, but I haven't actually tested it. The other main difference is that gPXE now advertises HTTP/1.0 instead of HTTP/1.1, since the code was not actually HTTP/1.1

Comments fix and usage output corrected for chain.c32 - Gert Hulselmans Signed-off-by: Gert Hulselmans <kimmik999999 at yahoo.co.uk> $ diff -u syslinux-3.84/com32/modules/chain.c.old syslinux-3.84/com32/modules/chain.c --- syslinux-3.84/com32/modules/chain.c.old 2009-12-29 01:46:34.058793767 +0100 +++ syslinux-3.84/com32/modules/chain.c 2009-12-29 01:53:41.150794351 +0100 @@ -49,7

Good day, Pasi. Perhaps you'd be interested in joining the Syslinux mailing-list, if you haven't done so already. Is part of the problem description that the 'LOCALBOOT 0' directive does not behave as expected? If I'm not mistaken, I believe that 'LOCALBOOT 0' will return control to the computer's PXE boot ROM code. The PXE boot ROM code is then supposed to

Unable to boot using qemu-kvm and gPXE from virt-preview repository https://bugzilla.redhat.com/show_bug.cgi?id=512358 Signed-off-by: Alan Pevec <apevec at redhat.com> --- common-blacklist.ks | 9 +++++++++ common-pkgs.ks | 3 +++ 2 files changed, 12 insertions(+), 0 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index 7c19aa4..2f8842f 100644 ---

Hi All, I've been enjoying playing with gpxe and gpxelinux, however I have a few questions that I'd love to get some answers for... 1) Will gpxelinux support chain loading of other NBPs without hanging or is this already resolved ? 2) Why does gpxelinux take much longer than pxelinux to enumerate the UUID, MAC address, then hex IP address chop ? 3) Can gpxelinux load gpxe scripts at all

Hi, As requested on IRC, here are the step-by-step instructions to reproduce the failure I see: On http://rom-o-matic.net/gpxe/gpxe-1.0.1/contrib/rom-o-matic/build.php: output format: .dsk NIC type: e1000_82540 x CONSOLE_PCBIOS x CONSOLE_SERIAL BANNER_TIMEOUT: 20 COMCONSOLE: 0x3F8 _ COMPRESERVE COMSPEED: 57600 COMDATA: 8 COMPARITY: 0 COMSTOP: 1 x DOWNLOAD_PROTO_TFTP x DOWNLOAD_PROTO_HTTP _

First let me say I'm really excited about the possibility of dynamic menu creation over http using php. When this is stable it will make maintinging some of our pxelinux infrastructure much easier. Id like to thank all involved; I'm really looking forward to the gpxe intigration. After hpa's announment for 3.70pre7 I begain testing. I dropped the new gpxelinux.0 and new c32 modules

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

Dear, "InetBoot for x86&x86_64 LiveCD (Fedora/Ubuntu/KNOPPIX/VMKnoppix)" is released. HP: http://openlab.jp/oscircular/inetboot/ Guide-PDF: http://openlab.jp/oscircular/inetboot/InetBoot080731E.pdf We prepared the InetBoot scripts for "gPXE" and "syslinux". Please boot them from the shell-mode of gPXE and syslinux. Example: gPXE> dhcp net0 gPXE>

So I've been playing with this for hours and still unable to get everything working properly. In short I'm trying to boot an ISO image created by BartPE over pxelinux. When I attempt to do this it goes directly to a blank screen that just has a blinking cursor. Here's what my setup looks like: pebuilder.iso - the ISO file created from BartPE using WinXP SP2 CD as source but with

Hello all, I was reading http://www.etherboot.org/wiki/appnotes/autobootchainurl, and figured that as long as I was going to be modifying the code I might as well try a cleaner solution. ?Attached to this message is a patch that makes the following changes: 1) Allow the "dhcp" command to accept a list of interfaces and to try them in order until it succeeds, e.g.: ?gPXE> dhcp net0

I have been looking at the etherboot site and at the syslinux/pxelinx sites trying to figure out how to use gpxe, and I am a bit confused. :) In a nutshell, I simply want to use http to grab the config and messages files. (I need those files to be dynamic.) I tried just replacing pxelinux.o with gpxelinux.0. But, gpxe complains (A LOT) about unrecognized commands. I can't find a simple

I am attempting to setup a test gpxe(linux.0) http site, to test among other things the recent dynamic option 252 solution. In the process of investigation I stumbled across http://www.etherboot.org/wiki/appnotes/authmenus which indicates the gpxe can launch vesamenu.c32 directly. Various other pages on etherboot's site indicate menu.c32/vesamenu.c32 can be used independently as well.