similar to: SYSLINUX 3.11 released

Changes in 3.10: * gcc 4.0.1 compilation fixes. * Add support for querying the PCI BIOS in libcom32 (used by ethersel et al.) * Fix PCI handing (ethersel etc) on several old chipsets (and VMWare.) * Try to deal with systems with broken EBIOS. * New API call to do "localboot". * New API call to query features.

It was actually released yesterday, but due to some technical difficulties I didn't get a chance to announce it properly: Syslinux 4.03 is primarily a bug fix release. Changes in 4.03: * Don't hang if no configuration file is found. * Better support for booting from MBRs which don't pass handover information. * EXTLINUX: Try to be smarter about

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

Tying up lose ends, and adding the ethersel module for the Etherboot folks. -hpa Changes in 3.02: * SYSLINUX: The "unix" installer now sets the MS-DOS attributes (hidden, system, readonly.) * COM32 library: build the .lnx (test modules for running under Linux) as architecture native modules, in case i386 devel libraries aren't

Hello Erwan, You will find below a pull request for the bug reported by Robert Jordan in the disk library. The first patch is the one he tested (see http://syslinux.zytor.com/archives/2010-September/015341.html) and the second one is a sanity check for the number of sectors written by call ( see http://syslinux.zytor.com/archives/2010-September/015342.html). Thanks, The following changes

Okay, let's hope *fourth* time is a charm... Changes in 3.06: * Fix typo that caused the ramdisk to load in the wrong place. Changes in 3.05: * New API function "shuffle and boot"; allows COM32 modules to load or construct (almost) arbitrarily complex objects, e.g. a kernel and its initrd/initramfs in pieces, and have the API core

Let's try it again... *fifth* time is a charm? Changes in 3.07: * Fix chainloading (chain.c32). * Fix zlib build problem. Changes in 3.06: * Fix typo that caused the ramdisk to load in the wrong place. Changes in 3.05: * New API function "shuffle and boot"; allows COM32 modules to load or construct (almost) arbitrarily complex

I decided the FAT directory-parsing bug was about as serious as it gets, so I decided to push out a new release. However, I decided I feel comfortable enough with the new features (or at least, that they wouldn't break anything else, knock on wood) that I did the patch off the 3.10 development tree and called it 3.05. Changes in 3.05: * New API function "shuffle and

Hi all, I have officially released SYSLINUX 3.20: Changes in 3.20: * EXTLINUX: New options --install (-i) and --update (-U), to make it clear if a boot loader should be installed or updated. For now, defaults to --install for compatibility; a future version will require one of these options. * New library functions to load and place files in

Nice to see the venerable syslinux updated to version 3.35. I did happen to encounter an issue with the latest release though. I performed 'syslinux -f' on a 32MB USB drive and all seemed well...until I tried to boot from it. Error message and drive details below: - - - /error message: SYSLINUX 3.35 2007-01-28 EBIOS Loading Invalid or corrupt kernel image. boot: /bootable USB drive

I am having difficulty trying to figure out how to get a computer to boot from it's local disk automatically after the pxe menu times out. I installed syslinux-3.11-4 with yum onto CentOS 5.5 It boots to the local disk if I select Local from the menu and press enter but it never times out and boots localy. The AUTOBOOT message doesn't appear either. Which instructions in the PXELINUX

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

It's basically the same as 2.13-pre1 but with some makefile and specfile cleanups. For the RPM package, there is now a separate RPM with the com32 build environment. 2.13: Bug fixes for the 2.12 release. 2.12: Add a C runtime library for writing COM32 applications; minor improvements. Changes in 2.13: * MEMDISK: Fix command-line parsing "brown paper bag" class

2.12: Add a C runtime library for writing COM32 applications; minor improvements. Changes in 2.12: * Simple C library, based on klibc, for writing COM32 programs. * Fix the handling of file length in loading of COM32 programs. * MEMDISK: Work around a linker bug by rearranging the code to not use the linker for the 16-bit code.

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

Hey all, I got a unique requirement of having AD groups map over to unix gid and existing perms of Unix only groups being granted. Reading through the man pages it seems this can be accomplished via idmap_nss. So my config looks like: [global] workgroup = SKUNKTEST realm = SKUNKTEST.LOCAL security = ads preferred master = no encrypt passwords = yes log level = 5 log file =

Hello everyone, I have pushed out SYSLINUX 3.08. It's identical in all but version number to 3.08-pre11. Sorry for everything that probably should have been done that didn't make it, but I simply haven't had time :( :( :( However, given several bugs fixed in 3.08, this seemed important... Changes in 3.08: * SYSLINUX: Fix performance regression (-s mode always

I didn't see any further communication here; would anyone be against my submitting/proposing a patch for this? I can see two possible approaches. One approach would be to isolate the restriction on user commands away from syslinux_run_command / load_kernel. Another would perhaps be to add support for a 'NOTAB' or 'NOTABTOEDIT' option. There already exists a NOESCAPE

Some people have reported portability problems with SYSLINUX 3.00, mostly due to the use of HDIO_GETGEO_BIG, which is deprecated; additionally, the advanced menu system wouldn't build for everyone due to a spurious reference to %ebp. This release fixes these things, plus makes the extlinux installer default to zipdisk geometry (64 heads, 32 sectors) if it can't guess anything else.

Yes, MENU HIDE would work as well, but still requires additional entries for each case (possible entries for pxe, syslinux, isolinux, cpu architectures, PCI devices, lua scripting scenarios, etc.) By blocking modules, I meant that as long as I disable user editing of menu commands via ALLOWOPTIONS 0, I cannot use any of the following com32 modules without creating duplicate LABEL entries for each