similar to: SYSLINUX 2.08-pre5 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.

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

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.

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

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

Hi. I want to use PXELinux to build a dynamic boot menu for a computer lab. Sometimes, the machines need to be in Linux mode/Windows mode/allow the option of Linux/Windows. I configured this all fine with PXELinux. My problem is really one of security. Someone can plug in a laptop with a DHCP server, and tftp server and fake a lab machine to boot into any mode they desire, or even

It seems that quite a bit of stuff built up very quickly after the 2.07 release: Changes from 2.07 to 2.08-pre6: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is

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

I mentioned in a private email recently that it would be useful if syslinux had a malloc implementation. I have one now if anyone's interested. -- Hebe 2004-02-08 14:26:08.183 UTC (JD 2453044.101484) X = -1.159504592, Y = 2.015990327, Z = 0.638260245 X' = -0.010415779, Y' = -0.003652077, Z' = 0.001024628

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

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

It works! Now, is there a way to use this handler multiple times so different submenus can have different position values. -Aaron On Fri, 2 Apr 2004, ganapathy murali krishnan wrote: > You write your own menupos_handler (like in complex.c) and register the > handler. > > So all you need to do is to copy the code for the menupos_handler from > complex.c and modify it to suit

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 a small problem with my COM32 image. It is more related to how the COM32 images get their arguments. Here are the relavent parts of my isolinux.cfg ----- # default image = defimg default defimg # Boot automatically after 5 seconds timeout 50 # By default auto select image. If no autoselect list # found, then boot into prep label defimg kernel readker.c32 append prep

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

This version has the following changes: - It adds a MEMDISK installation check API (as Murali asked for) - It renames TIMEOUTCMD to ONTIMEOUT. I decided "ontimeout" was the best alternative, especially since I'm going to try to implement Murali's suggested "onerror", and it seemed to work well in combination. As usual,

Is there a method to reboot a memdisk (floppy) image? I'm working on a DOS-based installation floppy that needs to repartition the hard disk prior to proceeding. DOS will only recognize the updated partition table after a reboot, but I'd like to be able to save information to the currently loaded memdisk floppy disk and simply reboot the image. Possible? I haven't had any luck with

Is it possible to have a isolinux based boot CD, where one of the options is to boot off the network. This would mean, 1. The kernel that one boots into is on the network and not on the CD. So easy to make changes. 2. One does not need a 'PXE enabled' network card. - Murali