similar to: SYSLINUX 2.10-pre7 released

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

I just uploaded SYSLINUX 3.72-pre7. I'm hoping this will be the final 3.72 prerelease. Please test it and holler if something is (still) broken. -hpa

Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick

I have produced a first cut of integrating gPXE with PXELINUX. This builds, in addition to the usual pxelinux.0, an image called gpxelinux.0 which includes the gPXE network stack. The result is that one can now download images via (almost) any network protocol supported by gPXE, including http. This lets one do fun things like using a CGI or PHP script for the configuration file. SAN

Hi all, I have released SYSLINUX 2.09; it is the same as 2.09-pre15 except for the version number. Changes in 2.09: * SYSLINUX: Remove residual setuid crap from syslinux-nomtools. * Handle video pages correctly when using the API functions. * Handle compiling on an x86-64 platform correctly. * Menu system from Murali Krishnan Ganapathy; see the

I have just pushed out Syslinux 3.80-pre7. I am slightly concerned about putting this into the release tree at this point: I was working with some of the shuffler code, and found that the memory map handling was actually severely buggy on some of my test cases. Resolving that problem took rewriting most of syslinux_add_memmap(). However, against better judgement :) I decided to check in the

This version contains a fix to mbr.asm, plus a version of Murali's menu system, but ported to gcc. Although gcc produces much bigger 16-bit code (since it's really 32-bit code with prefixes) I figured it would be much easier for people to deal with since it requires the configuration to be compiled in. That being said, it's a *very* powerful menu system, partially *because*

Look into the original XP cd and see where NTLDR is located, then place it on your cd in the same directory and it 'should' work. I have created some 2000 XP boot cd's with integrated recent service pack's and they still boot. But I do that with cdrecord+original boot sector, not with any isolinux stuff... But I hope this help! -----Original Message----- From: G. Murali

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 have just released SYSLINUX 2.09-pre4 with a few changes: a) SYSLINUX should now correctly handle mode changes from within a COMBOOT program. b) Tweaks to the menu system to avoid the "grey text on black" problem. c) A new color scheme for the menu system (Murali, check it out and see if you think it works for you.) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/

So I realized I really need a better way to collect information from problematic machines, so I spent today rewriting the old memdump tool into a new "sysdump" tool. sysdump can write its output either to a serial port using ymodem[1] or over the network using TFTP *if* it was booted from the network, using PXELINUX. John R.: I would obviously like you to try this on the machine that

3.62 is shaping up to be the "let's get rid of hardcoded limits" release. I got inspired by Bryan Perry's post about people still wanting to be able to use the CLI, so I have implemented putting labels in high memory, therefore avoiding the 64K total limit. This is now released as 3.62-pre7. If you happen to have a use case for this, I would be interested in finding out

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

I'm going to promote SYSLINUX 3.32-pre7 to release candidate unless someone objects, with the intent of releasing 3.32 immediately after Christmas. Please let me know if there are problems that should make me *not* do so, even if you have previously reported them. -hpa

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.

As far as I know the only thing close to that, is to boot DOS from a floppy image (stored on the CD). The floppy image will contain the CD drivers and hence you can use DOS to access the contents of the CD. The floppy image is usually stored in the "boot sector" of the CD, or if you are using utilities like ISOLINUX, then they can be stored on the CD, and ISOLINUX/memdisk can boot

Hello all, I just installed syslinux 2.10 on my usb-stick. It still boots then, but doesn't load initrd.gz (same config file..). Reverting back to syslinux 2.09 works fine, eg: initrd.gz is loaded. Something changed in initrd handling code? greetz, Jaap Crezee NB I am willing to share you more information or hints how to solve the problem. I am using kernel 2.6.7-bk20

>The way the El Torito CD-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a

Hi all, I've decided to move SYSLINUX 3.30-pre7 to release candidate status (the difference from 3.30-pre6 is pretty much that 3.30-pre7 contains a very simple compiled-in graphical background if the user doesn't specify MENU BACKGROUND.) Please test it out and let me know. Thanks, -hpa