similar to: Comboot Menu

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

Hi I am using PXELinux to boot BartPE and some other application and it works fine. There are some other Boot application which I am using 3COM MBAUTIL PXE.mnu and floppy images. I have problem chaining from pxelinux.0 to 3com pxe.0 (pxe.mnu). Consider: BIOS->(DHCP-TFTP)->pxelinux.0 works fine. BIOS->(DHCP-TFTP)->3COM pxe.mnu works fine, the menu appears and I can choose a floppy

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*

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.

Hi all, I'm looking for some menu examples for Murali's menu system. Specifically, a headstart on creating a Kickstart menu which covers the most common options with the intention of creating this: label ks.menu kernel vmlinuz.ks.$DIST append ksdevice=eth0 ks=http://kickstartserver/$DIST/Custom/ks.cfg.$DIST initrd=initrd.ks.$DIST lang= devfs=nomount ramdisk_size=8192 Hmm...looking

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=

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've now been able to test the simple.com in dosemu, worked fine. We provide a CD that has multiple kickstart configurations on it and users are prompted as to what type of server they want to build based upon the isolinux.cfg selections. My goal is to use Murlai's menuing system instead because the large number of configs is taking too much screen real estate. Looking at simple.c

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

I was using the simple menu with this configuration: DEFAULT MyMenu PROMPT 1 TIMEOUT 10 ONTIMEOUT LocalBoot ALLOWOPTIONS 0 IMPLICIT 0 NOESCAPE 1 MENU MAST PASSWD <password_omitted> MENU TITLE Bootable Options: LABEL MyMenu MENU HIDE KERNEL pxelinux.cfg/menu.c32 label Remote Instalation Server kernel memdisk/memdisk append initrd=RisMenus/RisDisk.IMg Now I'm

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

has anyone got memdisk to work directly? i mean such as: add_item("W98 Boot","Windows 98 Boot",OPT_RUN, "memdisk initrd=98se.ima",0); I have tried various methods, and I get the same results: Loading memdisk....Ready. MEMDISK 3.11 2005-09-02 Copyright 2001-2005 H. Peter Anvin MEMDISK: No ramdisk image specified! I know I can setup (in my case)

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/

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

Hi, I need to add an additional feature to Murali's menu system: sending and receiving UDP datagrams. I have no experiences with writing programs at such a low level. Therefore, I need some help. 1) How to transfer IP address and other options from PXElinux to comboot? 2) I got PXE specification, ver. 2.1 (sept. 1999); can I follow it safely? 3) Is there an easy interface to use PXE stack

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