similar to: SYSLINUX 3.11-pre9 -- release candidate; release delayed

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

Okay, the serial port feature in 3.11-pre9 was of course completely broken (I seem to have bad luck with -pre9's :)... a 3.11-pre10 is now available, and it does seem to have a more reliable handling of arrow keys ... *but not perfect*. There simply is no way to reliably detect both [Esc] and arrow keys on existing serial consoles. -hpa

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

Hello everyone, I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX, which would get confused by directories with deleted file entries. Special thanks to Stas Kysel of rPath, Inc. for spotting this problem and giving me an excellent test case; and of course to rPath, Inc. in general for being my employer and being extremely supportive of my SYSLINUX work! I have also

Hi, I'm Florent BERANGER, from Flonix ( http://www.flonix.com ). After several tests, we have found that Syslinux 3.00 pre9 is no longer compatible with USB stick booting. Syslinux 2.13 works fine with this feature. Error infos : Syslinux 3.00 pre9 only displays its version and a new line with a "a" character and then hangs. Tests configuration : Syslinux applied from : Linux

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

Dear all, I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem is, I have problem to use it for PXE booting (BIOS mode). It always gives me "Failed to load COM32 file vesamenu.c32". I am sure all the settings are correct because if I switch to the prebuilt syslinux downloaded from

I have just pushed out SYSLINUX 3.10-pre9. Please test it out, especially everyone who has been working with me on various systems trying to get them to work, or have had recent breakage. -hpa

Hi everyone, Kevin Tran of Broadcom just identified a very serious bug in PXELINUX where random parts of the PXE stack would get overwritten by PXELINUX. As a result, I have release SYSLINUX 2.00-pre9 for testing; if you have had problems with PXELINUX **PLEASE** test this version. I will try to make a SYSLINUX 2.00 some time this week if this tests out OK. I will also hunt for similar bugs

Hi all, We are hoping to update our BIOSes remotely with pxelinux and memdisk (it is for a 600 node Beowulf cluster with no floppy access). The DOS floppy loads and starts, however somehow the flash utility 'phlash.exe' or 'phlash16.exe' are both unable to load the provided rom image and just stop doing nothing. It looks like it can't access the rom image somehow, which is

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

Changes in 3.11: * MEMDISK: Fix bug by which accessing the real floppy disk as B: in MS-DOS was broken. * Simple menu system: allow tweaking of the screen layout. * Simple menu system: better command-line editing, correctly handle command lines above 256 characters. * PXELINUX: revert memory allocation change that caused problems

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

Hello A couple of time a was in situation that I needed memdisk to emulate TWO floppies for me. Let's give an example: Kaspersky Antivirus makes two rescue floppyes, one with ext2 filesystem, one with FAT12 filesystem. Ext2 floppy is bootable and loads fine with memdisk and it search for 2nd floppy to be inserted in floppy drive. This two floppies don't have chance to be combined in one

Hi all, I have released SYSLINUX 3.35-pre5 to the Testing directory; this is a release candidate and I intend to release this as 3.35 early next week unless I hear of any showstopper bugs, so please, pretty please, try it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ kernel.org has been overloaded lately, so it might take a while to show up. Changes in 3.35: *

Sensei H. Peter Anvin, I have successfully modified/enhanced memdisk so that one can chainload a local operating system after running diskless FreeDOS. I would like your advice regarding the appropriate interface for invoking this functionality. In addition, I would like to know what steps to take so that you feel comfortable considering including this in the standard syslinux distribution.

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a