similar to: SYSLINUX 3.52 released

I just encountered my only bug w/ the ISOLINUX+VESAMENU combination from 3.52-pre5. Updated a *working* CD project w/ the new ISOLINUX+VESAMENU combo just last week. Booting my preferred Linux distro (Slax-6) from my custom CDs work perfectly, however when I updated a CD project that includes BartPE/WinPE, BartPE fails to boot w/ 'CDBoot can not boot CD: error 4" msg. For the

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers <stappers at stappers.nl> wrote: >> Euh, could this be reviewed: >> >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c >> index 8d93a6a..b82e944 100644 >> --- a/core/fs/pxe/dhcp_option.c >> +++

On Sat, Sep 12, 2015 at 08:42:15AM -0400, Gene Cumm via Syslinux wrote: > On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter > >> <teun.docter at brightcomputing.com> wrote: > >>> On

Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com: > Reason: Message body is too big: 1780404 bytes with a limit of 512 KB So previous not on the mailinglist. > Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST) > From: Michael Szerencsits <szerencsits.michael at gmx.at> > To: syslinux at zytor.com > Subject: efi64 boot fail during download from kernel and initrd

On Sun, Sep 13, 2015 at 3:46 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Sep 12, 2015 at 06:56:04PM -0400, Gene Cumm via Syslinux wrote: >> On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm wrote: >> > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers wrote: >> >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c >>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm using the wonderfull vesamenu com32, but I have a little problem I don't known it there is a way or it need to be done, after selecting an entry (e.g. a disk img using memdisk) console mode is not restored so most of msdos apps are not displayed. Bye - -- Gianluigi Tiesi <sherpya at netfarm.it> EDP Project Leader Netfarm S.r.l. -

On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Sat, Sep 12, 2015 at 08:42:15AM -0400, Gene Cumm via Syslinux wrote: >> On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Sat, Sep 12, 2015 at 5:54 AM,

On Sat, Sep 12, 2015 at 06:56:04PM -0400, Gene Cumm via Syslinux wrote: > On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm wrote: > > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers wrote: > >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c > >> index 8d93a6a..b82e944 100644 > >> --- a/core/fs/pxe/dhcp_option.c > >> +++

I am resending this message because I have not recieved any response back. I have found two bugs in the menu.c32 utility, part of the syslinux-3.08-pre5 build, and have a couple of requests. Problem 1: If you use the ^ symbol to define a number as a hotkey, ex. MENU LABEL ^1 Option #1 , the menu will not print the number highlighted. It will use it as a hot key, it just will not highlight it.

On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter > <teun.docter at brightcomputing.com> wrote: >> On 2015-09-12 04:58, Gene Cumm wrote: >>>> >>>> I've captured the following DHCP ACK: >>>> >>>> 10.141.20.1.bootps > 10.141.20.2.bootpc: [udp sum ok]

I have discovered that the JUNOS DHCP server in Juniper J-series routers doesn't support setting the next-server IP address field (I have filed a bug report with Juniper and they are working on it). Instead, it puts the "boot server" in the sname field, which PXELINUX currently ignores. Here's a simple patch (vs. 3.36) that will take an IP string in the field. My assembly is

On Wed, Oct 7, 2015 at 2:33 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Tue, Oct 06, 2015 at 10:27:15PM -0400, Gene Cumm via Syslinux wrote: >> > On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> I have a patch that I think may help your situation of syslinux.efi >> >> being unable to load

Just a reminder that this remains an issue up to and including the latest syslinux 3.53-pre (0x473cfc9c). Additional testing suggests that implicit hostname/IP has never worked, ever since the common prefix suppression feature was added in version 3.00. -------- Original Message -------- Subject: pxelinux doesn't suppress common prefix if nothing precedes double colon Date: Sat, 25 Aug

>On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >... > >> Something like this would be preferable except it's not quite so >> simple. We'd need to not store BOOTP siaddr before parsing. Store a >> pointer to the string during parsing if serverip is unset. After all >> parsing, if the pointer is set, attempt to

I have a project g4l that uses syslinux and have been working on the next version. I installed the 3.74 pre5, and it worked just fine. But I was doing a test, and booted the systems, and usually pick the default kerenel or one of the other kernels on the CD before it times out with 60 seconds. But this time, I didn't do that. It loaded the default kernel with no problem, but then gives

Op 2013-07-13 om 19:58 schreef Michael Szerencsits: > Hi, > > I tested the following config: > > DEFAULT AutoInstall > PROMPT 0 > LABEL AutoInstall > KERNEL http://server/vmlinuz64 > APPEND initrd=http://server/initrd64.img > root=live:http://server/LiveOS/squashfs.img quiet lang=en > keymap=de-latin1 systemd.unit=rescue.target > system.unit=rescue.target

> -----Original Message----- > From: Gene Cumm [mailto:gene.cumm at gmail.com] > Sent: Wednesday, October 07, 2015 4:43 PM > To: For discussion of Syslinux and tftp-hpa; Geert Stappers > Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 > > On Wed, Oct 7, 2015 at 6:27 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Wed, Oct 7, 2015 at 2:33

Gene, All good questions. Thanks for taking time to respond. You've given me great leads to follow up w/ DHCP appliance consultant. >filename being file. I presume it looks like "/path/to/syslinux.efi" >or "/path/to/bootx64.efi" and not a TFTP URL? Correct. >> TFTP Server Name (66) -- a string. I have tried: >> - TFTP Server's IP

Hi, my client pc hangs on pxelinux before starting to fetch the linux kernel. It hangs after printing the ip information row. No traffic is observed at this point on the network. The pxelinux is transferred to the client through a tftp server and with no problems. What options do I have to proceed from this point and try to find out where the problem is? Thanks, Firas. -- Firas Swidan, PhD