similar to: Customized theme for Syslinux.cfg

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

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

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

>Several points (please read the whole email before doing anything else): > >1_ It is not clear whether you still need/want to "avoid displaying" the menu border (i.e. make it transparent). You mentioned that you >eventually managed to do so, but then you also ask (again) about vesamenu.c regarding the menu border. Or, perhaps... Do you >actually, really, want to

> 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

On Tue, 25 Jun, at 01:09:47PM, H. Peter Anvin wrote: > Not really... let's just document "make bios". There's preliminary documentation in doc/building.txt. -- Matt Fleming, Intel Open Source Technology Center

I am trying to setup a portrait mode screen. I can see that in 3.85, there is an enhancement which allows arbitrary resolutions (http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=commitdiff;h=5d4ade0221c2387345d0a82422866bb8b937cb09). Can I use this new feature to achieve setting the portrait mode. What is the syntax in the config file to set it? Also, is there any other vesa driver

Hi Folks, I'm interested in "headless" installation. If I use GRUB, then I provide arguments to the kernel of things like "headless vnc vncpassword=whoopie ip=dhcp" GRUB passes this on to ISOLinux, which manages the CD and subsequently the installation. Shouldn't I be able to do exactly the same thing with EXTLinux? I ask, because, as you might suspect, I

Hi Folks, When I boot ISOLinux, the locally attached disk is visible but the PATA 40 Gig in a USB attached enclosure is not. The locally attached disk has no bearing on what I am doing and to avoid confusion will not be mentioned again. Everything is happening on the 40 Gig. Let me explain. The goal is: Copy an installation iso to the disk, boot the disk and install it on that disk. I have

Hello, Long story short, example config: ### cut UI vesamenu.c32 MENU TITLE Multiboot USB MENU BACKGROUND #00000000 MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all MENU COLOR unsel 37;44 #50ffffff #a0000000 std MENU COLOR tabmsg 31;40 #30ffffff #00000000 std MENU BEGIN MENU TITLE System Rescue CD 2.4.1 INCLUDE sysrcd-2.4.1.conf MENU END MENU BEGIN MENU TITLE

Hello, I'm extremely new to Linux and am working on creating a PXE server/menu with PXELINUX and Microsoft DHCP/TFTP. I've gotten it to work great with the exception of one box: the IBM SurePOS 532. If I specify a boot image in my DEFAULT file, it works fine. However when I try to use MENU.C32, it gets stuck at "Trying to Load: pxelinux.cfg/default." Based on TFTP logs, it

Hello, I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the VM. The same problem

Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

I thought I've found three bugs on syslinux 6.03: (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and MENU COLOR UNSEL but uncommented MENU COLOR SEL: A black "border" is displayed below the selected line and on its right edge. (2) Uncommenting MENU COLOR UNSEL: This effect appears also on separators and on right edge on every unselected lines. (3)

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

The attached config works, but gives 2 error messages that get covered up by the GUI screen so fast I cannot read them. I think they are probably about having 'LABEL' with nothing after it. I was trying to follow the example in menu.doc but somehow I'm doing it wrong. Please consider helping me figure out how to get the same resulting GUI menu without any error messages. I am using