[syslinux] 5.01 pre4 CONFIG directive

[Matt Fleming]

On Wed, 2013-01-23 at 20:06 +0200, Ady wrote:
> > On Wed, 2013-01-16 at 22:30 +0200, Ady wrote:
> > > > > 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 
> > > > > directive) is not located in the soon-to-be new CWD. One potential 
> > > > > example could be the ML email thread that _ends_ at 
> > > > > http://www.syslinux.org/archives/2012-December/019062.html.
> > > > 
> > > > This should be fixed in git but please ensure that -pre3 works for your
> > > > testcases.
> > > 
> > > Hi Matt,
> > > 
> > > Unfortunately, it fails with 5.01-pre3.
> > 
> > Hi,
> > 
> > Could you please try with Syslinux-5.01-pre4? Thanks
> > 
> 
> Hi Matt,
> 
> Sadly, pre4 also fails, in several ways. For example, using the same 
> image as in my previous report about this, but updated to 5.01pre4 
> (including the new names for some lib*.c32 files)
> 
> 1_ Boot.
> 2_ Select LABEL "mainmenu".
> Now it hangs (and crashes VBox)

OK, this is just weird. How much RAM have you assigned to your VBox
instance?

> Moreover, if I also add an additional PATH directive in the first 
> syslinux.cfg file, I can hang it by:
> 1_ Boot.
> 2_ Select LABEL "pwd1". See the result.
> 3_ Select LABEL "mainmenu". This time it does not hang.
> 4_ Select LABEL "pwd2".
> 5_ At the "boot:" prompt, press [ENTER] so to go back to the menu.
> 6_ Keep repeating steps #4 and #5, until it hangs.

Exactly what PATH did you add to syslinux.cfg?

> Then I also tested 5.01pre4 without the CONFIG directive, booting 
> some ISO image as optical media booting a VBox VM. After the usual 
> "initrd.img... OK" message (booting a distro), it just stays there 
> (while the original ISO image with Syslinux 4.06 successfully loads).
> 
> I also found that DISPLAY files that contain the relevant ASCII 
> character to clean / clear the screen (ASCII 12) before they show 
> their content, are not doing so. The content is shown, but the ASCII 
> 12 character is not clearing the screen. The same DISPLAY file works 
> as expected with Syslinux 4.06.

Has this ever worked for 5.x? Please provide an example config.

-- 
Matt Fleming, Intel Open Source Technology Center