similar to: MAJOR memory overwrite bug in the menu system resolved -- 3.52-pre9 (RC) released

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

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

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

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

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

I have released SYSLINUX 1.75 -- this one is identical to 1.75-pre9 except the version number. I have gotten enough testing done that I feel it's time to release... Changes in 1.75: * ALL: NASM 0.98.32 or later is now required to build SYSLINUX from sources. * SYSLINUX: put back in the workaround for the BIOS floppy table. This seems to be a

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

Based on a few reports I've gotten today, I have make a new release candidate, 3.11-pre9, and am pushing out the release target to Friday, September 2. New in this release candidate: - Change to MEMDISK, which hopefully will work right both on machines with and without physical floppies. - Try to enable the 16550A FIFO for serial console. I'm hoping this will help eliminate dropped

I have released SYSLINUX 1.75-pre9... it's just a simple one-line bug fix over -pre8. I expect this will be the final 1.75. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

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

Dear all, I'm using Roxygen for the first time and I'm getting a rather cryptic error message. I must be doing something wrong but I have no clue what is it. Any suggestions? Regards, Thierry roxygenize("AFLP", roxygen.dir = "AFLP", copy.package = FALSE, unlink.target = FALSE) Writing AFLP.outlier to AFLP/man/AFLP.outlier.Rd Writing AFLP.outlier to

Since lot of people want this thing, I will try to take a stab at it. For now, I will hard code the menu in the code, and then somebody else can remove that restriction. May be we can add some kind of keyword to the config file which syslinux ignores and the comboot menu does something with it. I have one question about comboot: If I write a DOS program using C (compiled using watcom -3 -mt -osx

Applies to Syslinux 5.00-pre9. Attached, below, and available at: Repository: git://git.zytor.com/users/sha0/syslinux.git Branch: hexdump - Shao Miller From c9c67dd61ba0b11e46d514601cf0722e1b43017c Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Sun, 4 Nov 2012 00:26:32 -0400 Subject: [PATCH] hexdump.c32: Simple file hex-dumper Usage: %s

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 everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

On the SysLinux page, there is a screenshot of "COMBOOT Menu System for SYSLINUX developed by Murali Krishnan Ganapathy" (Advanced Menu System). I was wondering where I might be able to download this menu system in full to work with? If you dont want to share, I understand, but I am really intrigued by this and want to learn more, and maybe make my own design if I can figure it out.

Fellow syslinux fans, I'm using syslinux on a boot floppy (I'll call this syslinux A) to invoke an etherboot image (zlilo style) which invokes a tagged NBI image from my DHCP/TFTP server. The tagged NBI image is created using mknbi-dos and also uses syslinux (I'll call this syslinux B), a linux kernel and an initrd file. It works perfectly if syslinux A has a basic .CFG, e.g.:

Maybe I missed something here. What I want to happen is PXE boot on a timeout will boot to the hard drive. But, what happens is my comboot menu, which is default, loads right away and the ontimeout only happens when I escape out of the menu. My pxelinux.cfg/default: default menu timeout 100 ontimeout localboot # The Main Menu label menu kernel mainmenu.com append keeppxe #

I am designing an interlaboratory validation study for a presence/absence alternative method test kit vs. a presence/absence reference method test kit. There will be 10 laboratories conducting tests using both methods. In each laboratory, there will be 5 specimens tested, each of the 5 specimens twice by both methods (alternative, standard). The total number of data are 10 x 5 x 4 = 200.