similar to: Syslinux 5.00 LABEL directive with trail space fails

Initial comments about 5.00-pre11. 1_ Using ctrl+v at the boot prompt: SYSLINUX 5.00 5.00-pre11CHS Copyright ... Initial copyright notice when booting to Syslinux prompt: SYSLINUX 5.00 CHS 5.00-pre11 Copyright ... Request: make the ctrl+v result to be shown as the initial copyright notice (including order and space characters). 2_ Hello.c32 is still behaving differently than in 4.06.

Hi guys, Here's another 5.00 prerelease. This one includes fixes for most of the bugs reported in the last round of feedback. The XFS filesystem code from Paulo also got merged this time and there were a bunch of fixes from a Coverity report. This won't be the last prerelease, but we are nearing the end of the 5.00 release cycle, so please do test. Shortlog append below. --- Chen

Folks, I've just pushed out another prerelease for the 5.00 branch. The idea behind this -pre was to merge in the final 4.06 release. I'm aiming for a final 5.00 release next week, but as we saw with the 4.06 branch, anything can happen and these deadlines can get pushed backwards. Please, test if you can. One thing that is going to happen next week is a Syslinux-6.00-pre1, which will

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

I know everyone is itching to test out another prerelease, and there's been quite a lot of activity since the last one. The shortlog is appended below. The feedback from testing the previous prereleases has been really constructive, so thanks to everyone for that. That feedback has been addressed in some of the commits listed below, but it's not all bug fixes, we've also got some new

> 5.01 should be released by the beginning of next week. The following problems (among others) are present in 5.00. I hope they can be solved for 5.01. A_ LABEL directive with trail space characters fails: http://www.syslinux.org/archives/2012-December/019153.html B_ TEXT HELP directive hangs (easier to see when using Windows-like new lines, CR/LF):

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Hello, today I upgraded from Syslinux 4.06 to to Syslinux 5.00. But now the system won't boot anymore and I get the message Failed to load ldlinux.c32 Boot failed: please change disks and press a key to continue What I have done: 1) Installed Syslinux 5.00 2) Reinstalled "mbr.bin" to /dev/sda and /dev/sdb using dd bs=440 count=1 conv=notrunc

Just a few bug-reports, before I forget: - A Windows installer bug for 4.06 and presumably 5.00-pre9 whereby the ADV contains backslashes. Reproduced with: syslinux.exe --directory \two\dirs e: - An open() (?) bug for 4.06 and presumably 5.00-pre9 whereby the filename /ubcd/custom/syslinux-5.00-pre9/com32/gplinclude/acpi/facs.h fails to open() after 134 iterations in a loop where it's

Conditions to trigger this bug(s): 1_ Boot with ISOLINUX (SYSLINUX seems fine). 2_ Do NOT use the UI directive. 3_ In between TEXT HELP - ENDTEXT directives, use more than one line of text. *** syslinux.cfg start *** DEFAULT vesamenu.c32 PROMPT 0 LABEL pwd1 COM32 pwd.c32 TEXT HELP one line of text two lines of text ENDTEXT *** syslinux.cfg end *** Result: the system ([vesa]menu) hangs.

I am trying to build an RPM starting from the TAR archive. The relevant error is: make[1]: Entering directory `/tmp1/Software/rpmbuild/BUILD/syslinux-5.00/libinstaller' perl bin2c.pl syslinux_bootsect < ../core/ldlinux.bss > bootsect_bin.c perl bin2c.pl syslinux_ldlinux 512 < ../core/ldlinux.sys > ldlinux_bin.c perl bin2c.pl syslinux_mbr < ../mbr/mbr.bin > mbr_bin.c perl

Hi folks, There are enough changes on the 'firmware' branch to warrant another prerelease. Things that jump out are the changes to update the current working directory when executing syslinux.efi (previously .c32 failed to load if installed to a non-standard directory such as /boot/syslinux, because the current working directory wasn't correct), the realloc() fix from Shao and a new

Hi, I encounter a problem with Syslinux 5.00 I cannot really describe. So I created two small videos: Booting with Syslinux 5.00 (1.3 MB): <https://www.dropbox.com/s/b6g8cdf2t9v48c6/boot-syslinux5-fail.mp4> How I fixed the problem by downgrading to Syslinux 4.06 and how booting should look like (6.5 MB): <https://www.dropbox.com/s/lt7cpgfm0qvqtba/boot-syslinux5-how-i-fixed-it.mp4>

Another prerelease for the 5.00 (elflink) branch should be making its way to the mirrors now. The shortlog for -pre7 to -pre8 is listed below. Just like the 4.06 branch I was really hoping to drop a final release this week. Once 4.06 is out I'll merge that into 5.00. If you can, please test it out and let know any of any bugs you find. Because so much of the core infrastructure is rewritten

Hello, The following is a comparison of 4.06 and 5.00pre8 behaving differently. I made a floppy image with Syslinux 4.06. I installed ldlinux.sys with: syslinux --directory /boot/syslinux/ --install /dev/fd0 and I added pwd.c32 to the same directory, but I intentionally did not build a syslinux.cfg file. While testing the floppy image in a VM, it correctly boots to the Syslinux boot

I'm not seeing how to set this path option? Here is what I get using vesamenu.c32 as an example when moved to a directory outside of the build. The current syslinux 4.06 has all the files in the same directory which is at the root of the cd. ldd vesamenu.c32 linux-gate.so.1 => (0xb77c5000) ../../com32/libutil/libutil_com.c32 => not found ../../com32/lib/libcom32.c32 => not found

Have been using syslinux for some time for my g4l project, and was just looking at the new 5.00. Normally have just copied the new files, but with version 5.00 it is missing the support files according to ldd, and even putting the missing files in the directory failes to find them. ../../com32/... Script to copy files from new syslinux directory to the projects isolinux directory that is

Hello I just tested my pxelinux installation with 5.00-pre6. For the installation I did first the same steps as I did with 4.05. I copied the following files out of the archive into my /tftpboot folder: syslinux-5.00-pre6/core/pxelinux.0 syslinux-5.00-pre6/com32/menu/menu.c32 syslinux-5.00-pre6/memdisk/memdisk With only this files, it was not working and I also had to copy this two

> > > On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > Would someone please be so kind to explain / describe the PXERETRY > > > directive? > > > > $ git grep -ni pxeretry > > com32/elflink/ldlinux/readconfig.c:1305: else if (looking_at(p, "pxeretry")) > >

On Wed, Apr 27, 2016 at 7:55 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: >> > Would someone please be so kind to explain / describe the PXERETRY >> > directive? >> >> $ git grep -ni pxeretry >> com32/elflink/ldlinux/readconfig.c:1305: else if