similar to: Syslinux-5.00-pre8

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

> > To be clear, I am not saying there is no bug - there might be. > I performed the following test with several versions of Syslinux: 1_ Execute: 'extlinux --once=non_default_label --install /mnt/sda1' ; 2_ In first reboot, the "non_default_label" should be executed; 3_ In second reboot, the default label should be executed. Results: _ 4.05 to 4.07: OK. _

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I wanted to let everyone know that going forward, Matt Fleming will be doing at least some of the releases and prereleases for Syslinux. Other than who pushes the button, there should be little or no change in how the builds are done, where they are kept and so on. Thanks Matt! -hpa -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12

Hi, I've just pushed out a last -pre release before 4.06 final. The purpose of this prerelease was to make sure that all the build infrastructure is configured correctly and to ensure that the win installer problem is now gone (I've done the build on an F16 machine which should have a working mingw toolchain). Barring any major problems I'll do the final release this week. -- Matt

Tested floppy boot on two machines (one PII 350, one 486DX4) Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux kernel from floppy on the 2 machines. Tested with 3 different disquettes that were know to work, boot is reached after this very long time. Noise from floppy head make think floppy wait approximatly one minute between each read. No problem with pxe boot with

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

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, > Do you see the same error with 5.11-pre8? Yes, I do :( -- Regards, Igor

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

> 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):

On Jun 05 2014, Ady wrote: > > I'm working on a system derived from ARCH linux, running what they > > call version 6.02-4 of the syslinux package (which would be your > > version 6.02 plus their/our patches). I've got a syslinux.cfg > > ArchLinux currently is already using 6.03-pre12 or newer, so I would > suggest for you to update. I want to keep the

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

On 07/11/2013 01:38 PM, Igor Sverkos wrote: > Hi, > > OK, I solved the problem. Before calling "make installer", I first > have to call "make spotless" and "make". Then I can call "make > installer". > > Is that documented, somewhere? > That would be a bug. The documented sequence is "make clean", "make

Hi, > What steps are you using to recompile the releases? Are you working from > git? No, not git. See http://www.syslinux.org/archives/2013-July/020543.html and the f'up from Ady and my response regarding re-compiling. So actual I think I don't re-compile everything. I think I am using the pre-build modules from your provided archives (if 'make installer && make

Hi Matt, First comments about 5.00-pre10. 1_ When using "ctrl+v" in the boot prompt, there is no space character between the version and the boot mode. Additionally, the main version number is shown twice. For example, "SYSLINUX 5.00 5.00-PRE10CHS" should be: "SYSLINUX 5.00-PRE10 CHS" 2_ Boot to menu.c32, press [ESC] to go to the boot prompt. Pressing [ESC]

Sorry for the delay, we were too busy drinking and playing with explosives yesterday. :) Here are some tests. We did one on a similar machine and it worked. We deleted the configuration file, obviously. # Dell OptiPlex GX620 ISOLINUX 5.11 5.11-pre7 isolinux: Starting up, DL = 82 isolinux: Loaded spec packet OK, drive = 82 isolinux: Main image LBA = 00000115 isolinux: Image checksum error,

I have updated syslinux in Parted Magic's test version to the 5.10 release. With 4.06 I booted plop like this: LINUX /boot/plpbt/plpbt.bin Now it says /boot/plpbt/plpbt.bin... ok Booting kernel failed: Invalid argument Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... all work with 5.10. Revert to 4.06 and plop works again. Is this a problem with syslinux

-------- Original Message -------- From: Alexander Perlis <aperlis at math.lsu.edu> Sent: Mon Jan 28 18:21:18 PST 2013 To: hpa at zytor.com Subject: Minor syslinux menu system bug report Sorry for the intrusion, I know authors dislike receiving direct e-mail, but I couldn't see bug report submission info at the syslinux website. This bug report is for syslinux 4.05 and affects both

Date sent: Tue, 9 Oct 2012 21:09:22 +0200 From: Geert Stappers <stappers at stappers.nl> To: syslinux at zytor.com Subject: Re: [syslinux] Final line of menu selectable even if it is disabled > On Tue, Oct 09, 2012 at 01:10:31PM +0100, Matt Fleming wrote: ... > > Message from Matt Septhon > > Sorry I'm not in a position to

While testing the syslinux-4.06-pre11, I encountered a failure booting Windows Vista using syslinux. Looking at the details of the failing machine, I discovered that the main difference between this machine and the working ones is taht, on this machine, the MFT is fragmented in multiple fragments, and ldlinux.sys is indexed in one of the extended fragments. Does the syslinux NTFS implementation