similar to: menu shiftkey directive

Correct the order of the parameters for MENU RESOLUTION. Update references. Rewording. Typos. diff U3 /syslinux-6.03/doc/menu.txt /syslinux-6.03-next/doc/menu.txt --- /syslinux-6.03/doc/menu.txt Mon Oct 06 19:27:44 2014 +++ /syslinux-6.03-next/doc/menu.txt Wed Jun 24 01:28:49 2015 @@ -5,35 +5,38 @@ +++ THE ADVANCED MENU SYSTEM +++ The advanced menu system, written by Murali Krishnan

> 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

> 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

host static anyterm content locally, url parameterize anyterm rows/cols/general param update spec/makefile Ideally I wanted and tried hard to put all this into a seperate ovirt-server--anyterm subpackage, but we cannot 'reopen' the ovirt server virtual host defined in ovirt-server.conf to add the neccessary rewrite rules. it would be nice to figure out a way to do this ---

Testing the following (uncommon) syslinux.cfg with different Syslinux versions allows getting to several observations; some might be of interest to users, and some for the Syslinux developers. syslinux.cfg *** UI menu.c32 DEFAULT help TIMEOUT 30 # ONTIMEOUT help LABEL pwd COM32 pwd.c32 LABEL help MENU HELP help.txt *** 1_ For the TIMEOUT-related directives to behave as expected,

Hello Syslinux Team, The following scenario shows some issues when using DISPLAY files (and the SAY directive). *** help.txt start *** LINE 1 OF help.txt LINE 2 OF help.txt LINE 3 (one before last) OF help.txt USE F1 TO TEST *** help.txt end *** Note: in "help.txt", there are no initial nor ending blank lines. After the last line: " USE

On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > So, my first (still incomplete and still inaccurate) attempt to write > some rules about the PATH directive, and ask about remaining doubts!... > > > The search (for c32 files) is supposed to respect the following rules: > > 1_ The search for c32 files is performed according to the following > rules. The search for

> Im a long time PXE boot fan. I use it for wimbooting windows PE, linux > images via http, and memtest mainly. > > Ive got it nicely customised with my own graphics etc. > > Then UEFI booting came along. Till now ive been content simply setting > bios's to CSM mode and doing my thing.... > > Ive had another go at EFI PXE booting and can now get the menus and

On Sat, Dec 12, 2015 at 8:21 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >> > Gene Cumm wrote: >> >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux >> >> <syslinux at zytor.com> wrote: >> >> > Hi folks, >> >> >

> On Thu, 18 Dec, at 07:47:18PM, Ady wrote: > > I have a question about the PATH directive. In fact, the question is > > not about how it is currently working, but about its intention or goal, > > or how it was supposed to work (or how it was thought about for the > > 5.00 release). > > > > Previous discussions about the PATH directive in the Syslinux

Peter, Paulo reported some problems with his config files under ISOLINUX and PXELINUX - basically TIMEOUT and TOTALTIMEOUT were broken. The patches I've pushed to the elflink branch fix this and also fix parsing of the ALLOWOPTIONS config directive. The following changes since commit d5e02fb16a11bfdbce1e90a39e6cb5f2ad925389: get_key: Valid key values are positive (2012-04-17 11:25:53

On 12.12.2015 17:39, Sebastian Herbszt via Syslinux wrote: > Gene Cumm wrote: >> On Sat, Dec 12, 2015 at 8:21 AM, Ady via Syslinux <syslinux at zytor.com> wrote: >>> >>>> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >>>>> Gene Cumm wrote: >>>>>> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via

> On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > > > So, my first (still incomplete and still inaccurate) attempt to write > > some rules about the PATH directive, and ask about remaining doubts!... > > > > > > The search (for c32 files) is supposed to respect the following rules: > > > > 1_ The search for c32 files is performed according to

The following is a first attempt to list the current change log for Syslinux 6.03. The final stable version, whenever it will be released, might include additional items. I would appreciate feedback regarding: _ Any item that should be added. _ Any item that should be edited in any way. _ Any item that should not be included. _ Any credit that should be added or corrected. _ Any wrong or

> Hi, > > Ady wrote: > > I personally don't like this "hiding" [of CHS], but I understand > > their reasons to do so. > > > > I think that the "USB-Geometry" section in the wiki should try to > > point to the same kind of users. > > But it is in wiki page Hardware_Compatibility. > Check out the neighborhood. > If there

> Using a boot prompt without a menu makes Syslinux 6.03-6 booting the > default label only, ignoring the label that was entered. Auto completion > of the defined labels works, though. Can anyone confirm this? > I compiled binaries from the (hopefully, temporarily) "revert-9acbffd" branch from GeneC. The building environment is using old dependencies (i.e. not recent

Indeed; I agree it is not an implementation detail as potentially valid SPIR could be almost untranslatable to valid code running on a target without dedicated workgroup-local memory. Micah: the problem can be distilled down to: __local variables in SPIR are represented as Constants (GlobalVariable : public Constant), but they are not in fact constant, for a device with no workgroup-local memory.

> Hi, > I am trying to boot syslinux with an SD-Card on COMe-mBTi10 board, it works > perfect with syslinux 4-06(as BIOS supports booting from SD-CARD), but > hangs with syslinux-6.03 during 'Loading vmlinuz ... '. > I tried various ways in which I could debug but no hints, just one time I > got the error below the loading screen. > > 'Loading vmlinuz0 ... CHS:

Processing commands for control at bugs.debian.org: > forcemerge 644125 466683 Bug #644125 [xenstore-utils] xenstore-utils has completely inadequate description Bug #466683 [xenstore-utils] xenstore-utils: The package description doesn't say what the utilities contained in the package are for. Severity set to 'normal' from 'minor' Marked as found in versions xen/4.0.1-2.

On Thu, 18 Dec, at 07:47:18PM, Ady wrote: > I have a question about the PATH directive. In fact, the question is > not about how it is currently working, but about its intention or goal, > or how it was supposed to work (or how it was thought about for the > 5.00 release). > > Previous discussions about the PATH directive in the Syslinux Mailing > List, and its