similar to: [bug] 5.10: TAB displays only one line of labels

On Thu, 13 Jun, at 06:38:36AM, Gene Cumm wrote: > Confirmed. Tested pxelinux.0 from 5.00 and 5.10. It appears to be an > issue of not having the line wrap in a consistent state. Returning > from a COM32 module does reset it. Hmmm.. returning from a COM32 module should be resetting it. What steps did you take to reproduce this problem? I can reproduce it with Ady's procedure, but

On Thu, Jun 13, 2013 at 5:51 AM, Ady <ady-sf at hotmail.com> wrote: > Hello, > > As the subject of the email says, pressing TAB from the "boot:" > prompt displays only one line of labels. But this only happens under > certain circumstances, not always. > > Obviously, to be able to see this problem you need enough labels. > > If TAB is pressed as the first

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.

The config.c32 module (and the CONFIG directive) is not behaving as expected when using syslinux.exe 5.00pre11 as installer. To replicate: 1_ The content of the device: /dira /cat.c32 /config.c32 /ldlinux.c32 /ldlinux.sys /libcom32.c32 /pwd.c32 /syslinux.cfg /dira/dira.cfg 2_ Content of /syslinux.cfg: DEFAULT pwd1 PROMPT 0 LABEL config1 COM32 config.c32 /dira/dira.cfg APPEND /dira/ LABEL

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 Thu, 13 Jun, at 06:38:36AM, Gene Cumm wrote: > > Confirmed. Tested pxelinux.0 from 5.00 and 5.10. It appears to be an > > issue of not having the line wrap in a consistent state. Returning > > from a COM32 module does reset it. > > Hmmm.. returning from a COM32 module should be resetting it. What steps > did you take to reproduce this problem? I can

> > To be clear, I am not saying there is no bug - there might be. > I performed the following test with several versions of Syslinux: 1_ Execute: 'extlinux --once=non_default_label --install /mnt/sda1' ; 2_ In first reboot, the "non_default_label" should be executed; 3_ In second reboot, the default label should be executed. Results: _ 4.05 to 4.07: OK. _

On Sun, Sep 15, 2013 at 04:31:09PM +0300, Ady wrote: > > > Platform: MS XP > > > > 1. cfg file: > > prompt 1 > > timeout 150 > > display /downloadedPrograms/syslinux/syslinux.cfg > > > > default xp > > label xp > > com32 chain.c32 > > append hd0 1 ntldr=/ntldr > > label de > >

>> Thanks. I've looked through all the links, and it seems everything is >> fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, >> but it didn't help). I'd be glad to provide more details, but the error >> message is the only info I've got by now. It seems nothing else can be >> got from syslinux shell without modifiying the

On Sun, Sep 15, 2013 at 11:14:05PM +0300, Ady wrote: > > > On Sun, Sep 15, 2013 at 04:31:09PM +0300, Ady wrote: > > > > > > > Platform: MS XP > > > > > > > > 1. cfg file: > > > > prompt 1 > > > > timeout 150 > > > > display /downloadedPrograms/syslinux/syslinux.cfg > > > > > > >

On Thu, 13 Jun, at 06:45:03PM, Ady wrote: > There is no contradiction. If you execute, say, ls.c32, you > eventually return back to the "boot:" prompt. Then press TAB once, > and all labels are displayed. Press TAB once more, and only one line > of labels is displayed. I tested this with ISOLINUX only. Could you try 5.11-pre2 and see if this is fixed, please? -- Matt

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

On Tue, Sep 17, 2013 at 09:57:26AM +0300, Ady wrote: > > > On Sun, Sep 15, 2013 at 11:14:05PM +0300, Ady wrote: > > > > > > > On Sun, Sep 15, 2013 at 04:31:09PM +0300, Ady wrote: > > > > > > > > > > > Platform: MS XP > > > > > > > > > > > > 1. cfg file: > > > > > > prompt 1

> On Sun, Mar 26, 2017 at 09:50:17AM +0000, Ady Ady via Syslinux wrote: > > > i wrote: > > > > > I think it still has good reason to exist. > > > > > > Ady wrote: > > > > Would you please clarify what do you mean with "it"? > > > > > > "It" was the code part about > > > > > >

I have some questions about "ALLOWOPTIONS 0". [quote] ALLOWOPTIONS flag_val If flag_val is 0, the user is not allowed to specify any arguments on the kernel command line. The only options recognized are those specified in an APPEND) statement. The default is 1. [/quote] My understanding of the behavior of "ALLOWOPTIONS 0" is that unless I type-in a command that is exactly

Hello Syslinux Team, If I understand correctly (and I should emphasize that condition), the lib*.c32 library modules, when required, are initially searched-for according to the following (fallback) rules: 1_ Search for the relevant lib*.c32 file(s) in the Current Working Directory. 2_ Search for the relevant lib*.c32 file(s) in the directory where ldlinux.c32 is located. Then the lib*.c32

Platform: MS XP 1. cfg file: prompt 1 timeout 150 display /downloadedPrograms/syslinux/syslinux.cfg default xp label xp com32 chain.c32 append hd0 1 ntldr=/ntldr label de com32 chain.c32 append hd0 2 label memtest linux memtest86+.bin label hello com32 hello.c32 2. Installed by >From xp cmd prompt:

> > Hi > I have tried to install syslinux 4.06 on the SD card again, it works > like a charm. > > I am being very carefull with c32 files from the same version > bootloader. No success. > > I am also unmounting /dev/sdb1 before installing syslinux, as mentioned > in the given documentations. > In the pasted syslinux.cfg content--- I have also tried using only

My summary: reviewing ALLOWOPTIONS found reasons for further reviewing 'ALLOWOPTIONS' Op 2014-07-12 om 04:35 schreef Ady: > > > I have some questions about "ALLOWOPTIONS 0". > > > > [quote] > > ALLOWOPTIONS flag_val > > If flag_val is 0, the user is not allowed to specify any arguments on > > the kernel command line. The only

To the Syslinux mailing list administrator(s): There seem to be some issue when searching the Syslinux mailing list archives. To replicate (example): 1_ Open a Google web search page 2_ Search for "site:http://www.syslinux.org/archives/" 3_ Click "Search tools" 4_ Limit the search to "Past month". Result: no match! This has been happening for about 10 months or