similar to: Customized theme for Syslinux.cfg

> Thanks Gregory, my mistake, your explanation was half right and your code was > fully right, I meant to say the key is setting the first two digits in the > foreground and background to "00" (which means transparent) this will delete the > color of the border, and then making the shadowing variable equal to "none" this > will delete the shadowing black line

Thank you Gregory your code worked to remove the border in syslinux! It wasn?t the Alpha (that changes the opacity of the border color), but it was the ?shadowing? that had to be changed, so ?none? in the shadowing column worked(you notice the border come back if you change ?none? to ?std?) reference this link for terms: https://wiki.syslinux.org/wiki/index.php?title=Menu#MENU_COLOR ! I am also

Thank you Gregory your code worked to remove the border in syslinux! It wasn?t the Alpha (that changes the opacity of the border color), but it was the ?shadowing? that had to be changed, so ?none? in the shadowing column worked(you notice the border come back if you change ?none? to ?std?) reference this link for terms: https://wiki.syslinux.org/wiki/index.php?title=Menu#MENU_COLOR ! I am also

Thanks Gregory, my mistake, your explanation was half right and your code was fully right, I meant to say the key is setting the first two digits in the foreground and background to "00" (which means transparent) this will delete the color of the border, and then making the shadowing variable equal to "none" this will delete the shadowing black line that appears by default. See

> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory is relevant, specially for relative

The following are some comments about Syslinux documentation as present in version 4.06 - 5.00pre9. 1_ In "./NEWS", the changelog for version 4.04 includes "GCC 4.5 fixes". Maybe the changelog for Syslinux 4.06 should include "GCC 4.7 fixes" (or 4.7.x ?). 2_ In "./NEWS", the changelog for version 4.05 includes "ISOLINUX: remove the .img file

> > SYSLINUX 6.03 CHS 6.03-pre1 ... > > Failed to load ldlinux.c32 > Boot failed: please change disks and press a key to continue. > First, let me clarify that all the scripts and procedures in the Clonezilla site are not related to this official Syslinux mailing list or to The Syslinux Project. They are done by the Clonezilla team. Now that I know you are working

> I'm starting this thread to discuss what git repository should be > designated as primary and which repositories should be designated as > secondary. > > For years, git.kernel.org has been the primary repo, updated at least > with every full and pre- release. git.zytor.com has been the > secondary and development repo. > > Additionally, I've maintained my

On Sun, Jun 14, 2015 at 4:33 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: >> >> > I'm starting this thread to discuss what git repository should be >> > designated as primary and which repositories should be designated as >> > secondary. >> > >> >

> If I understand the syntax correct, it is: > (hdX,Y)/path/to/file", where X is disk number and Y is partition number. > As far as I understand X and Y are zero based. > > I've tested it with qemu and 2 disks: > - the first with bootloader > - the second with kernel+rootfs > > I've used the following configuration file label: > > label MULTIFS >

> Both sticks show very unusual factors for heads and sectors > which are hardly intentional. If BIOS gets confused like fdisk, > then the failure to find files is quite plausible. > > ------------------------------------------------------------- > > Could you please exercise what is described for Linux in > http://www.syslinux.org/doc/usbkey.txt > and check whether

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

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

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

>> 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

Greetings Syslinux forum, I used this link; https://askubuntu.com/questions/1090891/grub-menu-colors and I followed it's tutorial for implementing the grub theme and was able to delete the menu border by creating a customized grub theme for UEFI boot (grub.cfg)! Do you know if the "syslinux.cfg"(legacy boot grub) can have it's border removed, like do you know if

On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: > > > I'm starting this thread to discuss what git repository should be > > designated as primary and which repositories should be designated as > > secondary. > > > > For years, git.kernel.org has been the primary repo, updated at least > > with every full and pre- release.

After some discussion/debugging behind the scenes, we are back on track, with updated Debian packages. 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted in "target" (or "$target", or some similar notation), and the version of Syslinux-related packages in the OS should be "6.04~git20171011.af7e95c3+dfsg1-6" or newer. At the moment

> I proposed -h 252 -s 63 because it yields the largest > possible cylinder size which is divisible by 4 (i.e. > the byte count is divisible by 512*4 = 2048). > -h 240 -s 63 would fulfill this constraint, too. > Size limits are 252*63*1024*512 = 8,323,596,288 > resp. 240*63*1024*512 = 7,927,234,560 bytes. > > > The workaround cannot be temporal, because the

Testing the following (uncommon) syslinux.cfg with different Syslinux versions allows getting to several observations; some might be of interest to users, and some for the Syslinux developers. syslinux.cfg *** UI menu.c32 DEFAULT help TIMEOUT 30 # ONTIMEOUT help LABEL pwd COM32 pwd.c32 LABEL help MENU HELP help.txt *** 1_ For the TIMEOUT-related directives to behave as expected,