similar to: ISOLINUX 5.00pre13 INCLUDE directive problem

Conditions to trigger this bug(s): 1_ Boot with ISOLINUX (SYSLINUX seems fine). 2_ Do NOT use the UI directive. 3_ In between TEXT HELP - ENDTEXT directives, use more than one line of text. *** syslinux.cfg start *** DEFAULT vesamenu.c32 PROMPT 0 LABEL pwd1 COM32 pwd.c32 TEXT HELP one line of text two lines of text ENDTEXT *** syslinux.cfg end *** Result: the system ([vesa]menu) hangs.

In 5.00pre13, DISPLAY and F1-F12 files are parsed correctly from vesamenu, but not from the boot prompt. When pressing F1-F12 from the prompt, instead of showing a colored word or sentence, the _code_ for that color is shown. When the same text file is seen from [vesa]menu (by pressing F1-F12), the expected colored words are correctly seen (not the code for the selected color). Also, in

Hello, The following is a comparison of 4.06 and 5.00pre8 behaving differently. I made a floppy image with Syslinux 4.06. I installed ldlinux.sys with: syslinux --directory /boot/syslinux/ --install /dev/fd0 and I added pwd.c32 to the same directory, but I intentionally did not build a syslinux.cfg file. While testing the floppy image in a VM, it correctly boots to the Syslinux boot

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

Hello everyone, Since I have some some adventures in UEFI PXE booting ahead I tried to go with the latest syslinux development snapshot in this case 5.10pre1. But I already fail when booting from CD with Failed to load COM32 file .c32 I am a bit perplex since no name of COM32 files is given. I am trying to trace down the issue as good as I can. COM32 files present are:

Hello, Here are some humble suggestions for 'doc/menu.txt' and 'doc/syslinux.txt'. They might be relevant for other documentation sources too. Unfortunately, I don't know how to prepare adequate patches. For 'menu.txt': _ Line 8: "located in the menu/ subdirectly." Suggestion: "located in the 'com32/cmenu' subdirectory." _ Line 10:

On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote: > On 06/11/2013 01:03 AM, Matt Fleming wrote: > > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > >> Either that or make the path a list rather than a string, using the > >> normal word separators when entered on the command line, a bit like the > >> (t)csh does. That is a bigger change but is probably

> 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, > >> > > >> > As per Ady request (thanks for the reminder), I forgot to send the patches > >> > I

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 Syslinux > >> >> <syslinux at zytor.com> wrote: >

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

> 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

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 documentation (e.g. "PATH rules") left on me the impression that it was

Hello, I am a happy user of syslinux since 3.x. I've been able to load a font to display French accented charecters since then, but it not the case anymore, as problems have started to raise with syslinux 5.x. program : EXTLINUX, ISOLINUX (same behaviour) In extlinux.conf, the culprit is : FONT=lat9w16 This font is taken from 'kbd' package, named lat9w-16.psfu. It contains a

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

Initial comments about 5.00-pre11. 1_ Using ctrl+v at the boot prompt: SYSLINUX 5.00 5.00-pre11CHS Copyright ... Initial copyright notice when booting to Syslinux prompt: SYSLINUX 5.00 CHS 5.00-pre11 Copyright ... Request: make the ctrl+v result to be shown as the initial copyright notice (including order and space characters). 2_ Hello.c32 is still behaving differently than in 4.06.

> To minimize impact and convey the extent of the change, perhaps change to > ';' immediately and make another release, probably 5.20 and this week. > > --Gene I would hope that using ";" as path separator in the PATH directive would not be a problem for ISO9660 fs and ISOLINUX, where the ";" is used in the standard specification to indicate the

Hi Matt, First comments about 5.00-pre10. 1_ When using "ctrl+v" in the boot prompt, there is no space character between the version and the boot mode. Additionally, the main version number is shown twice. For example, "SYSLINUX 5.00 5.00-PRE10CHS" should be: "SYSLINUX 5.00-PRE10 CHS" 2_ Boot to menu.c32, press [ESC] to go to the boot prompt. Pressing [ESC]

> 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

I'm not seeing how to set this path option? Here is what I get using vesamenu.c32 as an example when moved to a directory outside of the build. The current syslinux 4.06 has all the files in the same directory which is at the root of the cd. ldd vesamenu.c32 linux-gate.so.1 => (0xb77c5000) ../../com32/libutil/libutil_com.c32 => not found ../../com32/lib/libcom32.c32 => not found

On Thu, May 12, 2016 at 2:14 PM, Janz, Burt via Syslinux <syslinux at zytor.com> wrote: > Hi Geert, > > I'm building syslinux 6.04 from scratch to prevent any issues with mismatched com32 modules. This gives me a "pure" set of modules as well as "pure" isolinux and syslinux cores. 6.04 hasn't seen a full release, only the pre1 pre-release. >