similar to: Comments sought on the graphical menu infrastructure

I have decided to promote SYSLINUX 3.31-pre4 to release candidate status. If it tests out OK, it will become 3.31 some time next week, probably. -hpa

I have just released SYSLINUX 3.31. It is functionally identical to SYSLINUX 3.31-pre4. Changes in 3.31: * The simple menu system (menu.c32 and vesamenu.c32) now support loading more than one configuration file at a time, using MENU INCLUDE or by specifying multiple filenames. * The MENU COLOR statement can now control the shadowing mode. Changes in

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

Hello all I have installed "syslinux" as follows: Microsoft(R) Windows 98 (C)Copyright Microsoft Corp 1981-1999. C:\WINDOWS>format o: /s C:\WINDOWS>format o: /s WARNING, ALL DATA ON DISK DRIVE O: WILL BE LOST! Proceed with Format (Y/N)?y Checking existing disk format. Formatting 967.98M Format complete. System transferred Volume label (11 characters, ENTER for none)?

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I installed another linux system in other partitions of the same drive (a 64 bit system), updated syslinux.cfg, setup the new system as default, and the new entry appears in the menu. Problem is: it doesn't boot. On timeout, it starts counting down again, and that's it. No error message whatsoever. Selecting the old system

Am 03.07.2013 14:11, schrieb Matt Fleming: > On Wed, 03 Jul, at 12:22:52PM, Andreas Heinlein wrote: >> Hello, >> >> I am currently trying to get the gfxboot archive from Ubuntu 12.04 >> working with gfxboot.c32 under BIOS, using ISOLINUX 6. >> >> AFAIK, the Ubuntu patches have been added in 4.03, and in fact it >> works with the official 4.05 release,

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> > We would need at least: > > A_ the partitions and directory structure in which the following items > are _located_ : /dev/sda1: # tree . . ??? extlinux ? ??? ldlinux.c32 ? ??? ldlinux.sys ? ??? libcom32.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? menu.c32 ? ???

Hello, when I try to boot from my computer extlinux needs about one minute before the boot menu is shown. Here's my system configuration -Two IDE drives on one controller -Second hdd is boot hdd -I'm using Arch Linux (i686) Is there an official bug tracker which I can use? I only found the debian bug tracker and I can't find any information about bugs on the homepage. Here is my

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

Hello, I am currently trying to get the gfxboot archive from Ubuntu 12.04 working with gfxboot.c32 under BIOS, using ISOLINUX 6. AFAIK, the Ubuntu patches have been added in 4.03, and in fact it works with the official 4.05 release, but not with 5.10 or 6.01-pre5. I can tell that the menu is actually working, you just don't see it. If you navigate it "blind", the correct

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 all, In June 2007 Jerry Nelson started a thread on this mailing list about a problem he was seeing. The thread was http://syslinux.zytor.com/archives/2007-June/008673.html After several hours of searching through the list, I am still convinced that his problem was never solved and is very valid. I recently moved from the old syslinux config options model (all labels in 1 default config file)

He Everyone, We found out that till version 3.02 the Yukon nic is supported after it gives code errors, i'm working a lot with ehtherboot via drbl / clonezilla, and together with Steven Shiau we ask you guys if you can arrange that the Yukon can be supported again. Our thanx in advance. Dave & Steven

Dear all, I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem is, I have problem to use it for PXE booting (BIOS mode). It always gives me "Failed to load COM32 file vesamenu.c32". I am sure all the settings are correct because if I switch to the prebuilt syslinux downloaded from

I was able to solve the problem with the following configuration: label custom1 MENU custom1 kernel pxechain.com append ::custom1/pxelinux.0 label custom2 MENU custom2 kernel pxechain.com append ::custom2/pxelinux.0 configdir1/pxelinux.cfg/default configdir2/pxelinux.cfg/default Then I dropped the custom pxelinux.0 files in their respective directories, confgdir1 and configdir2. On Tue, Nov

Hello All, Im using a fresh install of CentOS 4.3 fully updated with the latest Samba packages from SerNet.de http://enterprisesamba.org/index.php?id=64 While I have used Samba/Winbind for quite some time, Im have a peculiar problem with these RPM's. When I try to "net ads join -U

Hi there!! I has been modified the syslinux.cfg file according to the rules to add some boot parameters but since this modification, every time I that I highlight the modified entry in the boot menu and hit the TAB button on my keyboard, the entry's boot parameters is displayed twice and when I try to "backspace" them out, the line again get displayed twice and so on. So my

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