similar to: MENU HIDDENKEY help?

Hello, Here's a small enhancement feature for menu.c32. Looking for feedback before starting any coding (not sure when I'll have time for implementation) Regards, Dany St-Amant *Problem statement* When MENU HIDDEN is used on an headless server, any noise on the serial console can interrupt the boot; it would be preferable if there only specific keys were allowed to interrupt, reducing

> Le 11 avr. 2019 ? 14:48, Ady Ady via Syslinux <syslinux at syslinux.org> a ?crit : > > >> Hello, >> >> Here's a small enhancement feature for menu.c32. Looking for feedback before >> starting any coding (not sure when I'll have time for implementation) >> >> Regards, >> Dany St-Amant >> >> >> *Problem

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

> 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

I have successfully created bootable USB flash drives containing the following bootable products: 1) Clonezilla (recent version) 2) Ultimate Boot CD (recent version) 3) OpenELEC (recent version) All of these apparently use SYSLINUX as part of the boot process. All three boot up just fine and with no problems at all on virtually all of the various systems that I have here at my

> Hello, > > Here's a small enhancement feature for menu.c32. Looking for feedback before > starting any coding (not sure when I'll have time for implementation) > > Regards, > Dany St-Amant > > > *Problem statement* > > When MENU HIDDEN is used on an headless server, any noise on the serial > console can interrupt the boot; it would be

I have a menu conf as follows: LABEL enabled, use as item LABEL disabled, use as description SEPARATOR LABEL enabled, use as item LABEL disabled, use as description In this situation, I expect the cursors to be able to select from only the two enabled lines. However, the final disabled line is also selectable. Even if I put a final separator and/or disabled label the final line of the menu

We're currently working for project OpenElec on a syslinux menu. We would like to know if it's possible to move the menu position to the middle/bottom instead of the top... Currently we simply use the Vesamenu as it doesn't require much more functionality. I saw a post regarding the option MENU STARTROW, but that doesn't seem to work (anymore?). Any suggestions are welcome.

> > In message <BLU0-SMTP1383C5798F6C577E5FFF368BA40 at phx.gbl>, > Ady <ady-sf at hotmail.com> wrote: > > >> With respect to all of the actually important stuff however, I may have > >> missed it all, but I don't recall having read or seen an explanation of > >> what Ady & everybody else finally figured out about all this... > >

In message <BLU0-SMTP218A5F5400BB0FCA0312DC28BA70 at phx.gbl>, Ady wrote: >By adding technical details, it makes it harder for a non-technical >user to follow, and such user will probably go away looking for a >simpler answer. Yes. >If a user doesn't know what "create a new DOS partition table" means, >there are many ways to find out, including a web

In message <52D97530.5040706 at zytor.com>, "H. Peter Anvin" <hpa at zytor.com> wrote: >On 01/09/2014 03:35 PM, Ronald F. Guilmette wrote: >> >> SYSLINUX 5.10 2013-06-04 ... >> >> Failed to load ldlinux.c32 >> Boot failed: please change disks and press a key to continue. >> >> In the case of the Ultimate Boot CD, the

In message <BLU0-SMTP557B92590B4CC34F8318088BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Since in all cases you get to see at least the Syslinux copyright >message, the problem doesn't seem to be related to whether your BIOS >can identify the USB disk and boot from it. I can only agree. >Some GA motherboards might identify some USB drives as

-------- Original Message -------- From: Alexander Perlis <aperlis at math.lsu.edu> Sent: Mon Jan 28 18:21:18 PST 2013 To: hpa at zytor.com Subject: Minor syslinux menu system bug report Sorry for the intrusion, I know authors dislike receiving direct e-mail, but I couldn't see bug report submission info at the syslinux website. This bug report is for syslinux 4.05 and affects both

Hello, According to http://tinc-vpn.org/documentation/tinc_4.html: ,---- | Name = <name> [required] | | This is a symbolic name for this connection. The name should consist | only of alfanumeric and underscore characters (a-z, A-Z, 0-9 and _). `---- However, if I set an arbitrary name, I get # tincd -D -n hbt -d tincd 1.0.11 (Nov 18 2009 03:31:26) starting, debug level 1 Cannot

Unix.gettimeofday returns a finer resolution than seconds, which is what we need since deciseconds of timestamps are printed. --- mllib/common_utils.ml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mllib/common_utils.ml b/mllib/common_utils.ml index 32e908d..516cff3 100644 --- a/mllib/common_utils.ml +++ b/mllib/common_utils.ml @@ -282,11 +282,11 @@ let verbose () =

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> > We would need at least: > > A_ the partitions and directory structure in which the following items > are _located_ : /dev/sda1: # tree . . ??? extlinux ? ??? ldlinux.c32 ? ??? ldlinux.sys ? ??? libcom32.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? menu.c32 ? ???

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that

> > I have successfully created bootable USB flash drives containing the > following bootable products: > > 1) Clonezilla (recent version) > 2) Ultimate Boot CD (recent version) > 3) OpenELEC (recent version) > > All of these apparently use SYSLINUX as part of the boot process. > > All three boot up just fine and with no problems at all on

In message <BLU0-SMTP46982596DE9C2639CEB6B078BA40 at phx.gbl>, Ady wrote: >I am going to repeat what Genec requested at some point. Please post >the result of (replace 'sdX' with the adequate device): > > 'fdisk -l -c=dos -u=cylinders/dev/sdX' >and > 'fdisk -l -u=sectors /dev/sdX' > >where 'sdX' is (are) the problematic device. I

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