similar to: SYSLINUX 3.10-pre5

Hi all, I have pushed out one more 4.03 prerelease; please help checking or testing it as I'm about to push a 4.03 out really soon. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Sure, I don't mind testing it out on there for you, but, where do I find the pre releases to try then? At least we know it's between 2.13 and 3.00. That narrows it a bit I would think. Mind you, if it jumps up a major revision number, I guess that means a lot of changes went in. On 8/2/05, syslinux-request at zytor.com <syslinux-request at zytor.com> wrote: > Send SYSLINUX

> From: "H. Peter Anvin" <hpa at zytor.com> > To: SYSLINUX at zytor.com > Date: Fri, 05 Aug 2005 10:12:18 -0700 > Subject: [syslinux] Survey: SYSLINUX: 2.13 works, 3.0x don't > Okay, this applies particularly to SYSLINUX, not ISO/PXE/EXTLINUX. > > If you have a system on which 2.13 boots and 3.0x don't, I would like to > get as much information as

Hi! > -----Original Message----- > From: Nazo [mailto:nazosan at gmail.com] > Sent: Tuesday, August 02, 2005 1:37 AM > To: syslinux at zytor.com > Subject: Re: [syslinux] Can't boot Syslinux from HD directly. > Can indirectly? > > > On 8/1/05, H. Peter Anvin <hpa at zytor.com> wrote: > > Nazo wrote: > > > I've installed Syslinux on a

I have released SYSLINUX 3.08-pre5. Sparse files should now work correctly in extlinux. Symlink support still needs to be added, though. -hpa

Goodness, how many prereleases has there been in the last week... have lost count... Anyway, I have implemented the already-promised chainbooting API, and have included a sample program to chainboot floppies (it works for harddisks too, but only for the MBR.) As a bonus, in the process I actually discovered that booting .bs/.bss images under SYSLINUX was actually broken... that has been

This version cleans up the Ethersel (PCI config probing) changes I have been iterating with Alex Heinz. It's not the same code (so please test, especially Alex), but it should work the same. As before, if you have a machine for which 2.13 worked and 3.0x hasn't worked, please test this version too. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

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

Anyone had any chance to try this out? -hpa

Hi all, I have released SYSLINUX 3.30-pre5. This is the first version in which I think we can consider the graphical menu feature-complete. I would really appreciate any and all feedback on this particular test release. Also, if you find a machine on which the graphical menu *doesn't* work, I would appreciate knowing: 1. does it correctly fall back to the text menu? 2. what is

Hello all, With SYSLINUX 3.72-pre5 I think it's time to push SYSLINUX 3.72 into release candidate status. Please let me know if there are any bugs I'm forgetting... -hpa

Well, I'm back and while I was on vacation I hacked up a DNS resolver, so PXELINUX now supports FQDNs (only!) in its alternate server syntax. That is, you should be able to type "server.domain.com::filename" and have it get the IP address; just "server::filename" won't, although I am considering changing that so that it uses the domain received via DHCP option 15

SYSLINUX 3.11-pre5 is hereby a bug fix release candidate. If I don't receive any problem reports, I will release it as-is on Tuesday, August 30. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

HPA, I believe I've found a possible bug with /menu. This against the unmodified -pre5 snapshot. SRC: http://www.survivaldisk.com/menutest.c COMPILED: http://www.survivaldisk.com/menutest.com It's easiest explained if you just compile the .c and experience it for yourself, anyways. If you have two submenus nested within each other and then call a third menu it will bring up the

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 released a new prerelease for SYSLINUX which supports PCI BIOS access for ethersel.c32. If you've had trouble with ethersel.c32, I would appreciate it if you'd test it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Thanks, -hpa

I just pushed out SYSLINUX 3.10-pre19. This version adds symlink support for EXTLINUX. As part of the process of implementing that, I ran into a somewhat embarrassing bug in the menu support, which I fixed, however, if any of you have a chance to test especially menu.c32 on as many derivatives as possible (SYSLINUX, PXELINUX, ISOLINUX, EXTLINUX) I would greatly appreciate it. I've done

I have added the "raw" mode support to MEMDISK, and released it as 2.13-pre1. Please see memdisk.doc. Unfortunately it turns out the command-line parsing in MEMDISK 2.12 is completely buggered, so I'm afraid I'm probably going to have to release a 2.13 in very short order. Therefore, if you can, please try out this prerelease -- especially MEMDISK -- and give me the thumbs

The commit "linux.c32: move handling of mem= and vga= into the library function" also sets DEBUG to 1 in mboot.h. Is this intended? - Sebastian

I just encountered my only bug w/ the ISOLINUX+VESAMENU combination from 3.52-pre5. Updated a *working* CD project w/ the new ISOLINUX+VESAMENU combo just last week. Booting my preferred Linux distro (Slax-6) from my custom CDs work perfectly, however when I updated a CD project that includes BartPE/WinPE, BartPE fails to boot w/ 'CDBoot can not boot CD: error 4" msg. For the