similar to: SYSLINUX 2.09, 2.10-pre1 released

Working on fixing lower-priority bugs that I didn't want to risk destabilizing the 2.07 release for: Changes in 2.08: * Add "timeoutcmd" to allow timeout to have a different action than just pressing Enter. * Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND now works with COMBOOT/COM32 images.

Hi folks, I've got a problem with COMBoot (16 bit) in SYSLINUX 2.06: while the write string call (ax=2, int 22h) works just fine, the open file call (ax=6, int 22h) does nothing at all. Calling that function doesn't modify any register, and doesn't modify the carry flag. I then modified comapi_open in comboot.inc so it sets ax to some value and recompiled SYSLINUX, reinstalled it

Thanks for the comment. The next pass for a file format ... ------ FILE BEGINS ----- # Comment lines [menu] item="text to display" status="status line text" action= SUBMENU | INACTIVE | whatever submenu= <number> data="arbitrary string" item="text to display" status="status line text" action= SUBMENU | INACTIVE | RUN | EXIT submenu=

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/

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 put out a SYSLINUX 2.09-pre1 release, mostly to support Murali's menu development: 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. As usual,

Hi, I'm successfully using PXELINUX for booting several flavors of Linux using the LABEL/APPEND syntax in the config file. But I don't want to allow the users to append additional kernel command line arguments like "init=/bin/sh". Scanning the docs and the mailing list archive I could not figure out how to do this. Can anyone give me a hint? Thanks, Thomas

Okay, I have finally become convinced that hardware address based config files should be a standard feature in PXELINUX, so I have added it. I am a bit worried that it might not work with all DHCP servers (since I'm trying to do this in a hardware-independent manner), so I'd appreciate feedback. This adds one more name to the list of names queried for the config file, before the IP-based

Hello, Is there any possibility pxelinux could have the ability to pull its kernel/ramdisk/disk images/etc via http instead of tftp? I would really like the ability to pxe boot a machine, have it tftp pxelinux and its config file. Then, all the files listed in the config file are pulled via http. Michael Disclaimer: The content of this message is my personal opinion only and although I

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

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*

I have released what should best be described as "an early prototype" of SYSLINUX 2.00. SYSLINUX 2.00 adds an API for COMBOOT images, plus adds a 32-bit equivalent I call -- amazingly enough -- "COM32". I'm mostly releasing this for comments -- especially on the API design. It has been only trivially tested, so don't blame me if it breaks (send me a bug report

This isn't strictly speaking a SYSLINUX release, it's a change to MEMDISK and mkdiskimage to allow the creation of hard disk images with DOSEMU headers. This should make it easier to create bootable DOS hard disk images under DOSEMU. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

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.

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

Comments inline > -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Posted At: Thursday, November 14, 2002 1:40 AM > Posted To: Syslinux > Conversation: [syslinux] MSDOS not working: problem Solved > Subject: Re: [syslinux] MSDOS not working: problem Solved > > > G. Murali Krishnan wrote: > > > > In short: Is it possible to

Hi, I have a class ''Menu'' with a method ''addItem''. The method (simplified) looks like this: addItem: function(itemId, text) { this.container.innerHTML += ''<div id="''+itemId+''">''+text+''</div>''; Event.observe(itemId, ''mouseover'',

Another SYSLINUX prerelease (I really need to get this out the door...) with additional menu system improvements from Murali. Murali: I made some pretty sizable changes to heap.c. I hope that's ok with you. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ This is definitely a release candidate. Only bug fixes until 2.09 is out. -hpa

Does the COMBOOT stuff with 2.04 work correctly with function calls? or does one need to write it as one huge function? If memory serves me correctly, there was some problem if hello.c was modified to include additional functions, in an earlier version. - Murali

I'm considering the suggestion which was raised before about turning the debugging messages on by default in isolinux, or specifically, not building the non-debugging-messages version in the standard distribution. What do people think (especially distro maintainers?) -hpa