similar to: menu.c32 and old syslinux options

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 everyone I'm new to using menu.c32 and vesamenu.c32. I have used the original method of using pxelinux menus. I've read the wiki page and it speaks of being able to create submenus by making one of my menu options reference to (vesa)menu.c32 as the kernel and append the config file. I'm not sure I'm doing it correctly it was a little over simplified. Any help would be

On 8/5/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Since you are using only 2 menu entries, would you consider the > possibility of using the msg file(s) and the boot prompt, while > avoiding the use of (vesa)menu.c32 for this particular project? If you > do, there is room for improvements. > > Thanks for the info. Yes, I previously did not have a menu, for

I'm currently building a tree-like boot menu for my network, using pxelinux and vesamenu.c32. I jump from one page to another with "kernel vesamenu.c32" and "append newmenu". However, at some points I'd like to use the classic interface, for example with a distribution install image (in order to have the exact same interface as on the CD). I tried loading pxelinux.0

Hi, I've recently did some extensive testing with PXELinux and I must say it's great! I've tested it with several pc's and VMware vm's at home, this works flawlessly. However at my work, we only use MS Virtual PC 2007 and so on. I've started today to testimplement pxelinux into wds/ris, this seems to work but when I want to display a menu eg: default menu.c32, then

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

On 8/4/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Note, I am using syslinux from Ubuntu 16.04.2, presume that is 6.03. >> >> Regards, >> Barry > > Before investing time in replying to each different (unexpected) > behavior, I would suggest testing with *pre-built* binaries from > 6.04-pre1 downloaded from kernel.org (considering the

Hello, I'm trying to boot a HP Proliant DL320 G5 with a HP Smart Array E200i RAID card (latest BIOS and latest RAID card firmware). With menu.c32 or vesamenu.c32 from syslinux 3.50 the system hangs Booting from local disk... PXE-M0F Exiting With the latest dev version (3.52-pre) it hangs with : vesamenu.c32: attempted DOS system call The issue has already been reported but

Hi, I have been using syslinux on my portable disk with success on many types of machines (both bios boot and EFI boot) I however hit a small issue recently If I use menu.c32, on some UEFI systems (HP) the menu does not appear after the vendor splash screen. The system however goes ahead and after the timeout configured in the menu system syslinux boots the kernel. I can then (after kernel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu have different background color than that in 3.20. 1. use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu is: http://lfod.nchc.org.tw/stick/syslinux/syslinux_menu_3.30_pre1.jpg 2. use the menu.c32 from SYSLINUX 3.20, the simple menu is:

Hi, Maybe I am just not looking in the right spot but I can't figure out how to set a default menu in my isolinux.cfg. This is what it looks like: PROMPT 0 TIMEOUT 40 DEFAULT /boot/vesamenu.c32 LABEL cubez MENU LABEL Graphics mode (Compiz) - Experimental KERNEL /boot/vmlinuz APPEND vga=0x317 initrd=/boot/initrd.gz ramdisk_size=9999 root=/dev/ram0 rw chexpand=256 load=cubez

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:

Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp

Hi All, I have used menu.c32 to offer several booting options to our users via pxelinux... the icing on the cake would be if there was some mechanism whereby the pxelinux boot could be restarted, with the usual search for pxelinux.cfg/... files... all without a reboot and going through POST. Does anyone know if this is possible or if a comboot module exists for such a thing ? Cheers, Doug

Thanks very much for syslinux and pxelinux,they bring me many conveniences.I have problem in some computers.My english is very poor,so i submit in chinese and poor english.First I say sorry! ????pxelinux???sis900??????????? ????????default???????menu.c32??vesamenu.c32????? ???default???????DEFAULT memdisk c=638 h=2 s=18 floppy append initrd=netboot.zip???????????????????????? ???3com?boot image

On Fri, Jul 8, 2016 at 11:46 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hi, >> >> I have been using syslinux on my portable disk with success on many >> types of machines (both bios boot and EFI boot) >> >> I however hit a small issue recently >> >> If I use menu.c32, on some UEFI systems (HP) the menu does not appear

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)

Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to

I was having a display problem with memtest86 and dos via a memdisk image not displaying properly when launched using vesamenu.c32 and using a PNG background image. Instead of proper text output the display mode is not changed and the existing menu image is corrupted by the outputted text. This seems to be similar or identical to a problem describe in a previous mailing:

On 31-03-14 02:48, Ady wrote: > First, in the 5+ versions of Syslinux, the shift/alt keys are indeed > not working as expected. This is a bug (among several issues related > to keyboard functionality). Thanks for the reply. I assumed the keys not working would be specific to my straight-booting wish, but playing around with the suggestions that you provided, I see it's indeed more