[syslinux] Syslinux-5.00-pre9

[Ady]

> 
> Date sent:      	Wed, 31 Oct 2012 15:06:33 +0000
> Subject:        	[syslinux] Syslinux-5.00-pre9
> 
> > I've just pushed out another prerelease for the 5.00 branch. The idea
> > behind this -pre was to merge in the final 4.06 release.
> > 
> > I'm aiming for a final 5.00 release next week, but as we saw with the
> > 4.06 branch, anything can happen and these deadlines can get pushed
> > backwards. Please, test if you can.
> > 
> 
> Hi Matt,
> 
> Some 5.00pre9 comments:
> 
> 1_ The "--directory" option is not working in the Win32-based 
> SYSLINUX installer. The same installer works if "--directory" is not 
> used. The nomtools Linux-based installer works correctly with 
> "--directory".
> 
> 2_ When running an installer with "--version", could the result 
> include the "complete" version ("5.00-pre9"), instead of "5.00" only?
> 
> 3_ Special combination of keys in the boot prompt are not working. 
> For example, "ctrl+v" used to give the version in the boot prompt in 
> 4.06.
> 
> 4_ In the boot prompt, when pressing arrow keys some characters 
> (letters) are inserted. This was not happening in 5.00pre8.
> 
> 5_ When running the (Windows-based) installer with "--directory" and 
> the directory path doesn't exist in the destination device, there is 
> no (error) message. I don't expect the path to be created, but since 
> ldlinux was not installed (in any path), it shouldn't just end as if 
> the installation was successful. Either some general "error" message 
> or some "no such directory [exists]" or alike could be helpful.
> 
> 6_ From 5.00 NEWS: 
>   ... "Split non-core functionality into ldlinux.c32"...
> I wonder; will the INITIAL CWD definition still be the location of 
> ldlinux.sys (as example for SYSLINUX)? Is there a possible case where 
> ldlinux.sys will be located in one directory, and ldlinux.c32 in 
> another? Or they must always be located in the same directory?
> 
> 7_ From 5.00 NEWS: 
>   ... "reducing both disk space and runtime memory consumption."
> Interestingly, the installers are several times bigger than in 4.xx.
> 
> TIA,
> Ady.
> 
 
 
_ Part of the problems described in my previous report were resolved 
by adding *lib*.c32 files to the same location where ldlinux.c32 and 
menu.c32 were already located. This means that ALL the new 
dependencies need to be documented for the final user.


_ When no UI nor DEFAULT directives are found, there is no message.

_ Even though I changed to a different CWD, it still runs the 
commands without the need to type the path. Strange. It may be useful 
in some cases, and problematic in others.

_ The first argument for config.c32 works correctly, but the second 
(the soon-to-be new CWD) doesn't. The CONFIG directive from a menu 
seems to work (at least at first impression).

_ In some situations (from menu.c32 for example), pwd.c32 seems to 
clear the screen first and then it presents the resulting CWD. I 
don't think this is what was happening in 4.xx, unless instructed 
with the relevant MENU CLEAR directive.

Testing in a VBox VM:

_ hdt.c32:
Undef symbol FAIL: cpu_flags_strings

_ hello.c32:
Hello, world, from 0x00229200! malloc return 0x0022ac60


Best Regards,
Ady.