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 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, 17 Dec 2019 at 23:19, Gregory Lee Bartholomew < gregory.lee.bartholomew at gmail.com> wrote: > On Tue, 2019-12-17 at 22:46 +0100, David Bala?ic via Syslinux wrote: > > Hi! > > I have bootable (USB flash) disk, that _appears_ to be using syslinux. > > (the word syslinux is in the PBR, in the hexdump). > > How can I chainload it? The payload seems to be a

Hi all, In xen-4.1.2 src/tools/libxl/libxl_dm.c, there is a function called `libxl_build_device_model_args_old`, the func will build qemu-dm cmdline args according to the xl-formated configuration file specified by xl create domid: 2 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Strip off blktap sub-type prefix to /home/malei/c2.delta.img (drv

Hi, I''m using the xen-3.4-unstable version with Debian Lenny. Next to that I use a HVM Guest. The error message from the Xend.log is: 2009-02-26 14:44:15 2325] INFO (XendDomain:1180) Domain ExampleHVMDomain (35) unpaused. [2009-02-26 14:44:15 2325] INFO (XendDomainInfo:1781) Domain has shutdown: name=ExampleHVMDomain id=35 reason=poweroff. [2009-02-26 14:44:15 2325] DEBUG

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

I tried using http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-3.4/xen-qemu-dm-3.4_3.4.2-1_amd64.deb But my hvm instance wouldn't start. I got this in the qemu-dm log domid: 22 qemu: the number of cpus is 2 Watching /local/domain/0/device-model/22/logdirty/next-active Watching /local/domain/0/device-model/22/command char device redirected to /dev/pts/0

Hi. I have problem with installation XCP and XenServer on DomU. Installation just stuck after a while from installation beginning. DomU just stop responding, even reconnect with vncviewer isn''t possible. I''m using iso images to install. Dom0 is kernel 3.6-rc7 with xen 4.2.1-pre. I''m having such log: -videoram option does not work with cirrus vga device model. Videoram

Hello, I have encountered a rather strange issue with memory allocation to the domU. I am trying to run FreeBSD in a HVM, my config file is: [root@xen-srv sandi]# cat /etc/xen/vm/freebsd.cfg builder = "hvm" vcpus = 1 memroy = 2048 disk = [ ''phy:/dev/xen-dom0/freebsd,hda,w'' ] name = "freebsd" #vif = [''bridge=xenbr0,mac=00:16:3e:00:af:d8'']

Hi, Can you tell why my vnic built on top of an aggregation of 2 NICs of 1 Gbit/s doesn''t report a speed of 2 GBit/s ? [root at nazgul /]# dladm show-dev bge0 link: up speed: 1000Mb duplex: full bge1 link: down speed: 0Mb duplex: unknown bge2 link: down speed: 0Mb duplex: unknown bge3 link: down speed: 0Mb

Is anyone here running Smoothwall Appliance as a VM in Xen? We''re running it right now, but it''s running fully virtualized instead of para-virtualized. Anyone know if it can run as a PV? It crashed yesterday with only a 100 user sessions on it. Not much in the log except: [2010-12-06 15:03:31 7341] WARNING (image:559) domain prxy3: device model failure: pid 22922: malfunctioning

How come snoop doesn''t find the vnic0, by default: root at pine:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 vnic0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.9.59.56 netmask ffffffe0 broadcast 10.9.59.63 ether 2:8:20:7f:a9:16 lo0:

Modern distributions are moving toward a common boot scheme called "The Boot Loader Specification". This patch enables syslinux's (vesa)menu.c32 modules to parse the drop-in files that are defined by this new specification. Link to The Boot Loader Specification: https://systemd.io/BOOT_LOADER_SPECIFICATION Link to demonstration bootdisk image (82MB gzipped):

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

Hi, I''m afraid I have some problems understanding how crossbow is supposed to work ;) On my machine (OpenSolaris, snv_111) I''m running VirtualBox with couple of linux / XP installation and additionally a zone with exclusive IP. My network configuration looks like this: [6]elsinore:~>dladm show-link LINK CLASS MTU STATE OVER bge0 phys 1500 up

Hi Kamen, In addition to the signing key, there are a few other issues: 1. The signed 6.0.3 sources from kernel.org<http://kernel.org/> or any other sites/repos directly related to the syslinux project will not cleanly compile 2. As such, Linux distros have had to combine some version of the broken sources with their signed patches to create binary packages 3. Some distros patch the