search for: hiddenkey

Hi, I was hoping you could shed some light in usage of the directive MENU HIDDENKEY in syslinux (extlinux 4.04) The docs say: MENU HIDDENKEY key[,key...] command... So, in my conf I have: MENU HIDDENKEY Esc openelec Where openelec is the label of the boot option I want to run only if Esc is pressed. But pressing Esc on boot has no effect. Default is run. So, do I misunderst...

...or unassigned keys (other than current "reveal menu") *Possible user interface change* MENU HIDDENMENUKEY key[,key] MENU HIDDDENKEY key[,key] [command...] Add ANY as an acceptable value for key Make command optional, defaulting to boot default. *Behaviour* If pressed key is defined by HIDDENKEY, that action is always taken. no HIDDENMENUKEY, no HIDDENKEY ANY: all keys bring the menu (current behaviour) HIDDENMENUKEY ANY: all keys bring the menu (current behaviour) HIDDENMENUKEY Esc, HIDDENKEY ANY (without commands): Esc brings the menu, all keys autoboot HIDDENMENUKEY Esc, no HIDDENKEY AN...

...> > For a workaround for ANY and/or unassigned keys, you could have multiple 'MENU > HIDDEN' directives, each with a list of multiple keys. Based on hide_key[] definitions one would need to list 0x12a entries, some of which likely not having a worldly description to used by MENU HIDDENKEY. >> *Possible user interface change* >> >> MENU HIDDENMENUKEY key[,key] >> MENU HIDDDENKEY key[,key] [command...] >> Add ANY as an acceptable value for key >> Make command optional, defaulting to boot default. >> >> *Behaviour* >> >> I...

...ltiple keys. > *Possible user interface change* > > MENU HIDDENMENUKEY key[,key] > MENU HIDDDENKEY key[,key] [command...] > Add ANY as an acceptable value for key > Make command optional, defaulting to boot default. > > *Behaviour* > > If pressed key is defined by HIDDENKEY, that action is always taken. > no HIDDENMENUKEY, no HIDDENKEY ANY: all keys bring the menu (current > behaviour) > HIDDENMENUKEY ANY: all keys bring the menu (current behaviour) > HIDDENMENUKEY Esc, HIDDENKEY ANY (without commands): Esc brings the menu, all > keys autoboot > HIDD...

On 31-03-14 02:48, Ady wrote: > First, in the 5+ versions of Syslinux, the shift/alt keys are indeed > not working as expected. This is a bug (among several issues related > to keyboard functionality). Thanks for the reply. I assumed the keys not working would be specific to my straight-booting wish, but playing around with the suggestions that you provided, I see it's indeed more

...uld be: MENU <some_appropriate_name> 'key_stroke_or_combination' 'behavior' The 'behavior' could be, for example, 'ENTER', or a 'LABEL' (which in turn could be, for example, a 'MENU GOTO' directive). This syntax is similar to the 'MENU HIDDENKEY' directive. BTW, the 'MENU HIDDENKEY' directive is another way to define actions when pressing specific keys (or combination of keys). Add the 'MENU IMMEDIATE' directive too. Personally, I would very much like to see the known bugs and regressions (which are still keeping m...

On Thu, Sep 11, 2014 at 4:09 PM, Ady <ady-sf at hotmail.com> wrote: >> Since keystrokes were brought up, this seems like a reasonable time to >> make the following seemingly simple-to-implement feature request: >> >> Navigating a multi-level menu structure seems to require use of >> UP/DOWN/ENTER/ESC. It would be easier to quickly search/navigate if it >>

...z-3.16.2 ??? lost+found ??? slackware ??? vmlinuz-huge-4.4.14 4 directories, 15 files # cat syslinux.cfg #UI menu.c32 DEFAULT menu.c32 #UI vesamenu.c32 #DEFAULT gentoo #DEFAULT slack64 PROMPT 0 MENU TITLE Boot Menu #MENU BACKGROUND default_blue.png MENU RESOLUTION 1024 768 #MENU HIDDEN #MENU HIDDENKEY Space # hwinfo --framebuffer (to find which resolutions are acceptable) TIMEOUT 50 MENU WIDTH 78 MENU MARGIN 4 MENU ROWS 5 MENU VSHIFT 10 MENU TIMEOUTROW 13 MENU TABMSGROW 11 MENU CMDLINEROW 11 MENU HELPMSGROW 16 MENU HELPMSGENDROW 29 MENU COLOR border 30;44 #40ffffff #a0000000 std MENU...

...First, in the 5+ versions of Syslinux, the shift/alt keys are indeed not working as expected. This is a bug (among several issues related to keyboard functionality). Now, regarding your goal, you should be able to achieve it by using the following directives: _ MENU CLEAR _ MENU HIDDEN _ MENU HIDDENKEY _ UI [vesa]menu.c32 _ PROMPT _ DEFAULT _ TIMEOUT _ ONTIMEOUT Some of the above directives might be optional for your goal/needs (e.g. using a simple menu or a boot prompt when pressing some key), and there are some other directives that could be added so to achieve better/different looks. Rega...

Good day, I was expecting this to be a FAQ but haven't been able to find an answer... how would I arrange to, normally, not be presented with either prompt or menu when booting, yet be still able to call up prompt/menu when needed? If the right answer is "set PROMPT 0, provide a DEFAULT entry and no UI entry" then that doesn't work currently, in the sense that it is then

...; 4 directories, 15 files > > # cat syslinux.cfg > #UI menu.c32 > DEFAULT menu.c32 > #UI vesamenu.c32 > #DEFAULT gentoo > #DEFAULT slack64 > PROMPT 0 > MENU TITLE Boot Menu > #MENU BACKGROUND default_blue.png > MENU RESOLUTION 1024 768 > #MENU HIDDEN > #MENU HIDDENKEY Space > # hwinfo --framebuffer (to find which resolutions are acceptable) > TIMEOUT 50 > > MENU WIDTH 78 > MENU MARGIN 4 > MENU ROWS 5 > MENU VSHIFT 10 > MENU TIMEOUTROW 13 > MENU TABMSGROW 11 > MENU CMDLINEROW 11 > MENU HELPMSGROW 16 > MENU HELPMSGENDROW 29 &g...

..._word(&p); + } else if ((ep = looking_at(p, "hideifnot"))){ + if (ld.label) { + refstr_put(ld.visiblesource); + ld.visiblesource = refstrdup(skipspace(p + 9)); + } } else if ((ep = looking_at(p, "hidden"))) { hiddenmenu = 1; } else if (looking_at(p, "hiddenkey")) { As always , I'm sorry for my english :) !! hope this can help. Bruno Levert Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that (a) The contribution was created in whole or in part by me and I have the right to submit it under the op...

...d be appreciated. * Include a set of diagnostics by Gene Cumm. * Fixes for gcc 4.6 and binutils 2.21.51. * chain.c32: Allow "uuid" as a synonym to "guid". * Handle directory names starting with .. for vfat and iso9660. * New MENU HIDDENKEY command to provide a one-keystroke way to activate a boot option from a hidden menu intro screen. Begin3 Title: syslinux Version: 4.04 Entered-date: 2011-04-18 Description: SYSLINUX is a collection of boot loaders for the Linux operating system which...

...it is case insensitive: +with the keywords MENU or TEXT. As the rest of the Syslinux +configuration file language, it is case-insensitive. + +The remaining of this document is a reference of the directives that +are relevant in the Simple Menu System. MENU TITLE title @@ -50,7 +53,7 @@ MENU HIDDENKEY key[,key...] command... - If they key used to interrupt MENU HIDDEN is <key>, then + If the key used to interrupt MENU HIDDEN is <key>, then execute the specified command instead of displaying the menu. Currently, the following key names are recognized: @@ -60,9 +63,9 @@ ......

I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I installed another linux system in other partitions of the same drive (a 64 bit system), updated syslinux.cfg, setup the new system as default, and the new entry appears in the menu. Problem is: it doesn't boot. On timeout, it starts counting down again, and that's it. No error message whatsoever. Selecting the old system