similar to: Comboot menu crashes when it goes off screen

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=

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.

But the win wks on the other subnet is configured to use my SAMBASERVER as its WINS SERVER, and it is configured using the IP Adress of the SAMBASERVER and not the name. Shouldn't this do the trick? win wks is on a wireless subnet and hence runs at 11 MBPS, while the SAMBASERVER is on a wired subnet. I read somewhere that windows does some kind of "optimization" with slow networks.

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

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

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

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, On Tue, May 22, 2012 at 6:18 PM, Balachandran Sivakumar <benignbala at gmail.com> wrote: > Hi, > >      Thanks, I had done an svn up on one of the sub directories and > hence it had been out of sync. But had completely missed that point. > Just did an svn up and started off the build again. Thanks > The clang build went on fine. But subsequently, when I build

On Thu, Feb 17, 2005 at 16:09:50 -0800, Mikey Sklar wrote > > I use 8MB DOS images with pxelinux to load firmware. Which platform > would you like them for (I have many). I just saw your post and I would definitely be interested in an 8 MB DOS images to work with pxelinux. I have tried the method described in http://people.cs.uchicago.edu/~gmurali/gui/downloads.html but I keep getting

Hi, I just thought of trying vmkit and checked out the source from the svn repo a few minutes back. The build is failing with the following error. llvm[4]: Compiling CGCleanup.cpp for Release+Asserts build CGCleanup.cpp:507:36: error: no member named 'getCaseSuccessor' in 'llvm::SwitchInst'; did you mean 'getSuccessor'?

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

Here is the script I put together now. I hope I haven't overlooked anything. You might need to modify the first section of variables to suit your setup. Ofcourse you need to run this as root. May be some version of this should be included with syslinux? Basically given an existing floppy image, it creates a larger image and copies its contents over and sets up the bootsector of 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*

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

Hi All, I hope to find some time to work on the Advanced menu system. I personally no longer have a need for it (changed jobs). Since I dont want to spend time doing stuff which will not be useful, I would to know what features you would like. What I have in my list are * Eliminate the need to compile each menu into its own .c32 file * Eliminate #define constants in menu.h which impose various

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

Hello all, First off, thanks for the great work. I have recently added "more submenus" to a functioning advanced menu that only had one "submenu off of the main menu before" The addition of the new submenus has caused the main menu to not function correctly and I have been pouring over the code for several weeks and I just cannot see the error that I have introduced. This

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

I'm using ipappend and getargs.com with a dos boot image to get the environment variables for the IP and MAC. The format of the %ip% environment variable is ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> Is there a way to tell ipappend to assign these to individual arguments. Or does anyone know a good way to parse each of these to individual variables in dos. What

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/