similar to: Syslinux 4.04-pre15

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

I am hoping for some advice regarding another index problem. The code below is intended to assign a value of 'V' if values on certain variables are >= 1, assign a value of 'N' if values on certain variables are >= 1 on other variables and assign a 'O' if values on any variable which have a value <= 0. The outcome of this code is to assign a single

> Message: 3 > Date: Fri, 06 Jun 2014 08:13:36 -0700 > From: "H. Peter Anvin" <hpa at zytor.com> > To: Andrew Rae <A.M.Rae at leeds.ac.uk>, "'syslinux at zytor.com'" > <syslinux at zytor.com> > Subject: Re: [syslinux] EFI booting over network - can't then load > anything > Message-ID: <5391DAA0.2050207 at

On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled

> Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. > > below are results of me testing - i did each a few times to make sure they are valid results. > > hope it helps identify something that's gone awry ? > so far, 6.03

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

I was hoping for some advice regarding indexing, From a dataframe there are 27 variables of interest, with the prefix of "pre". [7] "Decision" "MHCDate" "pre01" "pre01111" "pre012" "pre013" [13] "pre02" "pre02111" "pre02114" "pre0211" "pre0212"

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

On Wed, Dec 17, 2014 at 5:54 AM, Willem Bargeman <willem at bargeman.eu> wrote: > On Wed, Dec 17, 2014 at 2:55 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Tue, Dec 16, 2014 at 4:22 PM, Geert Stappers <stappers at stappers.nl> wrote: >>> On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: >>>> >> Hi, >>>>

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

>> Hi, >> >> We have some problems while network booting thin clients. The type is T5540. >> >> At this moment we are using pxe linux 6.03. >> >> The systems are booting correctly with pxe linux version 6.03-pre14. >> We have seen the same error with version 6.03-pre9. >> >> The error message: >> >> Failed to load ldlinux.c32

Hi all, I just pushed out SYSLINUX 3.71-pre15. This version officially begins the release candidate stage of SYSLINUX 3.71. To be honest, I'm a bit baffled that the numbers got that high for what has always been intended as a maintenance/bugfix release, but those 15 prereleases only correspond to 55 commits total, so I guess it's really not that much. -hpa

On Jul 22, 2013 5:27 PM, "Gene Cumm" <gene.cumm at gmail.com> wrote: > > On Mon, Jul 22, 2013 at 11:36 AM, Matt Fleming <matt at console-pimps.org> wrote: > > On Sat, 20 Jul, at 09:48:38AM, Victor Sudakov wrote: > >> Negative. > >> > >> I have changed the stanza into > >> > >> label WDS > >> menu LABEL ^4.

(SNIP) > > 6.03-pre11 EFI64: fails - gets stuck in a loop downloading files - > > differs each boot > > 6.03-pre12 EFI64: fails - downloads /pxelinux.e64 & /ldlinux.e64 - > > then continually retries to download ldlinux.e64 > > 6.03-pre13 EFI64: boots OK TFTP & HTTP > > 6.03-pre14 EFI64: fails - downloads /pxelinux.e64 & /ldlinux.e64 - > > then

I was able to solve the problem with the following configuration: label custom1 MENU custom1 kernel pxechain.com append ::custom1/pxelinux.0 label custom2 MENU custom2 kernel pxechain.com append ::custom2/pxelinux.0 configdir1/pxelinux.cfg/default configdir2/pxelinux.cfg/default Then I dropped the custom pxelinux.0 files in their respective directories, confgdir1 and configdir2. On Tue, Nov

System: Dell OptiPlex GX620 (Both BIOS A10 and A11 affected) Medium: Physical CD-RW Observed: ISOLINUX 5.11 0x51D1AE48 ETCD_ is the only line displayed on-screen. A flashing cursor trails at the end of the line. Escape key does not return boot: prompt. Line1 of syslinux.cfg: DEFAULT vesamenu.c32 Note: Reverting to syslinux-4.06 allows for successful booting on the same system. Patrick On Tue,

Hi, first of all I would like to voice my deep gratitude to all syslinux developers for this really important software. I am using it in all my automation projects and could not manage without. Unfortunately now I stumbled upon a problem where I am out of my wits and need some help. The core problem is that HTTP transfers by gpxelinux.0 are very slow. Sadly this problem seems to be somehow

From: Jorge D Cisneros <jorge.cisneros at hp.com> Problem: The actual code only check for entries with kernel or linux, so this example will not work, this patch is to add support to gfxboot to detect the entry COM32 and use any module, in this case the module is chain.c32 Version: Syslinux 4.04 Example: UI gfxboot.c32 LABEL boot_hd0 MENU LABEL Boot from first hard drive COM32 chain.c32

Hello all, I have a boot server (running Debian Lenny x64) with a number of bootable options already configured (freedos, memtest, sysresccd etc). What I am struggling to do now is add Ubuntu and Debian netinst images so that I can boot from the network and have all the boot options available as if I was using a CD-ROM. The problem is that (as far as I can tell) the Ubuntu and Debian

Just reporting some iperf results. In each case, Dom0 is iperf server, DomU is iperf client: (1) Dom0: Intel Core2 3.16 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 1.17 Gbits/sec (2) Dom0: Intel Core2 2.33 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 725 Mbits/sec (3) Dom0: Intel Core2 2.33 GHz,