similar to: SYSLINUX 3.71-pre15: release candidate

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 just picked up 3.10-pre15 and the "PXELINUX corrupts graphic filename referenced from DISPLAY file" bug is zapped. Yipee! Thanks hpa. And Arwin too, if that 'xor esi,esi' was the crux. However, LOCALBOOT -1 and LOCALBOOT 0 don't work the same as they did for me in 3.07. :-( 3.07: LOCALBOOT -1 apears to work as I have a hard disk listed in bios boot order after the

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

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

I just tried to build syslinux-3.71-pre14-5-gfa6a60e and got the following: make[1]: Leaving directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/dos' make[1]: find-mingw.sh: Command not found make[1]: Entering directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/win32' gcc -Wp,-MT,syslinux.o,-MMD,.syslinux.o.d -W -Wall -Wno-sign-compare -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I.

Okay, I have found a workaround for the build problem that affected -pre13 and -pre14, and as a side bonus I have pulled a couple of fixes, including Sebastian's latest gfxboot updates. -hpa

Hi, I have a problem to report with the 4.10-pre15 branch. The problem is that my KVM guest "just reboots" when booting off the network. The setup is as follows: Host OS: RHEL 6.0/RHEL 6.1 with the default packages (no additional repos or packages) KVM guest configured to network boot. (maybe irrelevant info ...) ?!? DHCP server (using dnsmasq) in the same subnet as the KVM host.

> 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

I just released 2.09-pre15; it has a slightly improved E820 memory parser, which I'm hoping will deal with the "incorrect length" BIOS bug some people reported. If you have a machine with this bug, *PLEASE* test out this release, since I really want to release 2.09 this weekend. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Thanks! -hpa

Hello, I didn't try 6.02-pre15, I will do and I will post the results, my keyboard is a PS/2 model, the "legacy USB storage option" is enabled, I tried also an USB keyboard but there is no change, so it's not a keyboard problem, it probably something in syslinux ( ldlinux.sys ? ) who create a serious bug with my motherboard, I tried also with a USB HDD ( not a flash drive )

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

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"

_ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no config.sys, no autoexec.bat, no TSR's, no memory managers. _ The booting floppy includes syslinux.com 6.02. _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted partition each. Executing syslinux.com -i c: (or "d:") results in the following error: "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083

I intend to release SYSLINUX 3.73-pre7 as SYSLINUX 3.73 as soon as possible. Please let me know if there are any outstanding bugs with 3.73-pre7 that either haven't been reported or I have forgotten about... it's been a while. -hpa

I've tried the pre version, also the today's pre15. Also not working. I've checked it with wireshark, here is the output: No. Time Source Destination Protocol Length Info 1 0.000000 192.168.3.13 192.168.3.1 TFTP 97 Read Request, File: rescue/dev-64/vmlinuz, Transfer type: octet, tsize\000=0\000,

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

I'm going to promote SYSLINUX 3.32-pre7 to release candidate unless someone objects, with the intent of releasing 3.32 immediately after Christmas. Please let me know if there are problems that should make me *not* do so, even if you have previously reported them. -hpa

As promised, here's the DCE patch for pre15. (and this time i didn't forget the attachment ;) It enables ssh to authenticate, set groups and attach network credentials. It's a clean implementation (i left out the credential-move-hack). This one adds the --with-dce option to configure Some notes have rised: The for loop 3->64 closing fd's... is it really needed? Is it

If your email was sent to a distribution list, don't worry, someone else on that list will reply to your query. If your email was sent to me directly, please be aware that I am currenty out of the office with no access to email. All issues should be routed to my manager, John.Farey at oracle.com. Thanks