similar to: SYSLINUX 1.75 released

http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Here is the list of changes in 1.75 so far: 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 requirement for "extended" floppy formats to work

Please try this version out if you are using floppies to boot, and *especially* if you have observed either of the following two problems: a) "booting with syslinux without -s takes forever" b) "booting with syslinux without -s doesn't work, -s works" Changes in 1.75: * ALL: NASM 0.98.32 or later is now required to build NASM from sources. *

On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because >> > there is no convenient way in new_linux_kernel() to control the boot >> > flags value. >> >> This is the part that has me questioning things and trying to recall >> if any other

My reason for patching circa line 225 is that I think it is clearer. The reason for patching circa line 575 is http://bugs.debian.org/647603. They concluded that a .0 file is recognized not only by PXELINUX. And what is NBP? --- a/doc/syslinux.txt 2011-12-07 04:53:29.201556663 +0200 +++ b/doc/syslinux.txt 2011-12-07 04:50:11.000000000 +0200 @@ -221,7 +221,6 @@ LABEL label The following

> - PXELINUX: Support changing the default server and boot file prefix? > - Support loading a new configuration file. What are the time frames/progress on these? Would it be possible for pxelinux.0 to accept command line arguments, like: KERNEL pxelinux.0 APPEND keeppxe conf=<new config file> I also need a way to change the boot server ip that is left in the pxe stack, i.e. I want

On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: >> > >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because >> >> > there is no convenient way in new_linux_kernel() to control the boot >>

On Thu, Dec 4, 2014 at 11:27 AM, Thorsten Glaser <t.glaser at tarent.de> wrote: > On Thu, 4 Dec 2014, Gene Cumm wrote: > >> Ady has an excellent point. Try the following instead: >> >> LABEL test >> MENU LABEL test >> COM32 pxechn.c32 >> APPEND pxebsd.0 > > Thanks, that works! How do I use that in the generic case? > The

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

Hello syslinux mailing list users, I've initially filed a bug about my problem [1], but people from irc channel suggested to ask for help here. I have a PXE server based on syslinux 4.05 that distributes ReactOS to client machines over network. It has a pretty simple pxelinux.cfg/default, with the following contents (that were suggested by ReactOS wiki [2]): DEFAULT chain.c32 APPEND

> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> > there is no convenient way in new_linux_kernel() to control the boot > >> > flags value. > >> > >> This is the part that has me questioning things and trying

On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > > Thanks, that works! How do I use that in the generic case? > > The ?pxebsd.0? file can be called as? > > > > ? PXE loader > > ? COMBOOT (16-bit) > > ? DOS .COM > > ? Multiboot (although it switches back to 16-bit mode immediately) > > ? from its own bootsector, if installed on disc (blocklist)

> On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> > > >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> >> > there is no convenient way in new_linux_kernel() to

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

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 would suggest putting this syslinux web page info near the top of the man page. I was using debian, which has all the linux images being linux.bin. So, to make my own boot disk, I thought I would just copy bzImage to the floppy as linux.bin. Big mistake, if one does that it will not work, and one gets output like: - 0400 AX:0208 BX:0200 CX:0002 DX:0000 etc. Just renaming

On Thu, Dec 4, 2014 at 11:40 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > >> > Thanks, that works! How do I use that in the generic case? >> > The ?pxebsd.0? file can be called as? >> > >> > ? PXE loader >> > ? COMBOOT (16-bit) >> > ? DOS .COM >> > ? Multiboot

> Marcel Ritter wrote: > > > > The good thing about it: The PXE code removal seems to work now ... > > > > But I'm not quite sure about the syntax - is the following right? > > > > label undi > > kernel memdisk keeppxe > > append initrd=UNDITest/dosundi.1 > > > > The documentation only says: > > > > ... option

Thanks to Dell for sending me a specimen system, and of course, rPath, my employer, for letting me spend the several days it took to chase this one down. There is a memory-overwrite bug where part of the BIOS data area gets overwritten by certain comboot calls, including some used by the simple menu system. Anyone who has had problems where booting from the prompt works but the menu system

> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > > there is no convenient way in new_linux_kernel() to control the boot > > flags value. > > This is the part that has me questioning things and trying to recall > if any other KERNEL-like directives ever utilize keeppxe. > @Gene, Not being a developer myself, I don't understand this

Hi all, I have released SYSLINUX 1.75-pre4, which is a release candidate for 1.75. Please pretty please test it out: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ I'm working on some new stuff, basically COMBOOT+an API+32-bit support, which should make doing things like menus and other UI features very easy as separate modules. When that gets finished I'll probably