search for: optmenus

...dd option-key submenus to menu.c32 and vesamenu.c32 for doing things like changing the video mode. This was inspired the the patch that SuSE applies to the syslinux family and Grub, without the ugly pseudo-PostScript spaghetti. The patch may be found at http://www.valleyhold.org/~gordons/syslinux-optmenus.diff (it's over 30K, so posting it here didn't seem appropriate). Let me know what you think - I hope this can make it as mainline code! It's almost certainly not fully debugged yet - I'm sure you can break it if you try - but it should be a good (functional) start. Here's a...

...ctly what you're after. It's not quite as "pretty" on the screen as SuSE's stuff, but it's much "prettier" code and HUGELY easier to use. (I wasted several hours trying to make SuSE's stuff work on my live-CD...) http://www.valleyhold.org/~gordons/syslinux-optmenus.diff The message I sent about it should be hitting the list archive soon, and the patch also updates README.menu with the new keywords. HTH, let me know if this works for you!

Hi all, I have a question regarding the syslinux menu as used on the Ubuntu, Sabayon, ... live CD's. According to the syslinux documentation the function keys can be used to display a help file, but in the menu of these live distros the function keys are used to pick the resolution, language and keyboard. I would like to bind a submenu to these function keys. Is this possible and how can

...ou're editing the command line - but it's fairly usable. The documentation for the new keywords is added into README.menu by the patch. Please let me know what you think! (I'm not posting the patch itself here, since it's nearly 35K.) http://www.valleyhold.org/~gordons/syslinux-optmenus.diff

...positive I wrote it against the most current thing available then. (I wrote it over a weekend trying hard to get a project out, and was not always paying as good attention as I should have been...) > Furthermore, I'd rather not introduce new core keywords if at all > possible (OPTMENU, OPTMENUS). Any sane syntax to use them with the MENU > leading keyword? If not, can we stick to a single keyword (perhaps > OPTMENU ENABLE F1...?) If it doesn't make sense, then oh well, but... > Let me ponder that for a little bit; I suspect there's something reasonable, yes. >...