similar to: syslinux configuration file -- CONFIG directive with parameter

> > I am trying to find out whether vesamenu.c32 was crashing or the code > that was loading/starting vesamenu.c32. I haven't found that out yet. For testing this case with vesamenu.c32 I would suggest a very simple cfg with 2 or 3 entries (not just one entry, as the behavior would be slightly different) as first step. For example: *** syslinux.cfg start *** # Note that

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

With 6.03, I'm trying the "common directory distinct config" approach from http://www.syslinux.org/wiki/index.php?title=PXELINUX-Multi-Arch which essentially sets a different PATH (for BIOS vs EFI64). It seems PATH is correctly used to load .c32 modules, but not to load 'memdisk': PATH syslinux/bios UI vesamenu.c32 <-- WORKS (tries /vesamenu.c32, 404 error,

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

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 05-08-15 04:17, Ady via Syslinux wrote: > >> Now... why is vesamenu.c32 crashing like it does now? Why is the version > >> I tried without Gene's latest patches crashing before even beginning to > >> load the first stage: ldlinux.e64? > > I think you were "hinted" about this before. > > About what? Did I miss something obvious? If I

> On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > First, I'm confused. In the prior "whole" setup (the one you generated > > after my 15 steps, plus one workaround), was/is the basic boot menu at > > least "working" when you used the workaround for the buggy PATH > > directive when booting in

Den 21. april 2016 kl. 14.21.04 +02.00 skrev Geert Stappers <stappers at stappers.nl>: > On Thu, Apr 21, 2016 at 06:39:44AM -0400, Gene Cumm via Syslinux wrote: > > > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <<atle at team-holm.net>> wrote: > > > > > Under EFI/BOOT are the following files: > > > BOOTIA32.EFI (from efi32/efi/syslinux.efi)

I am attempting to setup a test gpxe(linux.0) http site, to test among other things the recent dynamic option 252 solution. In the process of investigation I stumbled across http://www.etherboot.org/wiki/appnotes/authmenus which indicates the gpxe can launch vesamenu.c32 directly. Various other pages on etherboot's site indicate menu.c32/vesamenu.c32 can be used independently as well.

First, I'm confused. In the prior "whole" setup (the one you generated after my 15 steps, plus one workaround), was/is the basic boot menu at least "working" when you used the workaround for the buggy PATH directive when booting in UEFI mode? I mean: "PATH EFI/BOOT/SYSLINUX/EFI64/" in "target/EFI/BOOT/SYSLX64.CFG". It is not perfect, but at

Den 21. april 2016 kl. 22.04.37 +02.00 skrev Gene Cumm <gene.cumm at gmail.com>: > On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <<gene.cumm at gmail.com>> wrote: > > > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <<atle at team-holm.net>> wrote: > > > > > Under EFI/BOOT are the following files: > > > BOOTIA32.EFI (from

I played with `mkdiskimage' some last night, here is what i came up with: mkdiskimage -z -F binary.img 1000 i="$(losetup -f --show binary.img)" j="$(kpartx -savu "${i}" | awk '{print "/dev/mapper/"$3 }')" mount "${j}" /mnt cp /usr/lib/syslinux/vesamenu.c32 /mnt cat > /mnt/syslinux.cfg <<EOF UI vesamenu.c32 DEFAULT linux LABEL

> Hallo, Matt, > > Du meintest am 25.06.13: > > >> Not really... let's just document "make bios". > > > There's preliminary documentation in doc/building.txt. > > (sent to you and to the mailing list; some robot blocks the list ...) > > Additionally: > > Compiling (with "make bios") worked. > > Running

On Tue, Aug 4, 2015 at 2:42 PM, Oscar Roozen via Syslinux <syslinux at zytor.com> wrote: > On 04-08-15 17:38, Oscar Roozen wrote: >> Any suggestions while I keep on debugging? > Got some result! > > I was using 'vesamenu.c32' to display a menu. Changing this to 'menu.c32' > resulted in a booting system! Okay, the menu is not that beautiful, but the

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, >

On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > 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:

Hello everyone, Since I have some some adventures in UEFI PXE booting ahead I tried to go with the latest syslinux development snapshot in this case 5.10pre1. But I already fail when booting from CD with Failed to load COM32 file .c32 I am a bit perplex since no name of COM32 files is given. I am trying to trace down the issue as good as I can. COM32 files present are:

On Fri, Dec 7, 2018 at 7:47 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > First, I'm confused. In the prior "whole" setup (the one you generated > > > after my 15 steps, plus one workaround), was/is the basic boot menu at

Hi Guys, I have done a tutorial in spanish to create an Installation Windows Pendrive using syslinux. It works well but it is in spanish, sorry. You are free to translate a upload to any place. *Crear USB Autoarrancable con syslinux * 1. Descargar la ?ltima versi?n de syslinux del enlace siguiente http://www.syslinux.org/wiki/index.php/Download *NOTA:* actualmente es la 6.03 2.

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)