[syslinux] Issues with syslinux_run_command(str) and parameters

[Ian Bannerman]

I did confirm earlier that this does work, and combined with a MENU HIDDEN to hide it from the visible menu it is a possible solution. I originally assumed that this was due to that going down a different code path and did not mention it, apologies. The scale of my menu makes doubling/tripling menu entries less ideal, though. 

Do we consider it intended functionality that modules such as whichsys will not work under ALLOWOPTIONS 0? A strict reading of the wiki would allow for this, as the subsequently loaded module does not have parameters in an append label: http://www.syslinux.org/wiki/index.php/SYSLINUX#ALLOWOPTIONS_flag_val

Naturally given my situation here, I think it would be ideal if we could separate disabling user edits & commands from blocking modules loading other modules, etc. :)
--Ian

> From: ady-sf at hotmail.com
> To: syslinux at zytor.com
> Date: Wed, 30 Apr 2014 03:36:35 +0300
> Subject: Re: [syslinux] Issues with syslinux_run_command(str) and parameters
> 
> Try the following and let us know. If it doesn't work, we'll try 
> other alternatives.
> 
>  ***
>  
>  DEFAULT vesamenu.c32
>  ALLOWOPTIONS 0
>  
>  LABEL test
>  COM32 whichsys.c32
>  APPEND -iso- iso -sys- sys
>  
>  LABEL iso
>  LINUX memdisk
>  APPEND initrd=fdboot.img
>  
>  LABEL sys
>  LINUX memdisk
>  APPEND initrd=fdboot.img
>  
>  ***
> 
> Regards,
> Ady.
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux