similar to: MENU CLEAR with vesamenu

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

Hello! I've been attempting to add EFI support to a linux live distro (slax), it's built on a syslinux bootloader. I can get EFI to work using menu.c32 on syslinux 6.03; however ideally we'd like the VESA menu as well. When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a blank screen and the machine seems to hang. I've tried adding MENU RESOLUTION based on

Hello. vesamenu.c32 can currently display a PNG image along the menu. But when the kernel is started, the image is lost. LILO supports bmp-retain option, where the bitmap graphic is retained when control is passed to the loaded kernel image; i.e., the screen is not blanked to alphanumeric mode before starting the kernel. Is it possible for vesamenu.c32 (or syslinux in general) to support

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

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

We're currently working for project OpenElec on a syslinux menu. We would like to know if it's possible to move the menu position to the middle/bottom instead of the top... Currently we simply use the Vesamenu as it doesn't require much more functionality. I saw a post regarding the option MENU STARTROW, but that doesn't seem to work (anymore?). Any suggestions are welcome.

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

Hello, I'm reporting a bug, see attached syslinux.cfg I'm using submenu entries to emulate checkbox inputs. The idea is simple, there are submenus generated for all possible cases, and each Enter keypress loads appropriate submenu section. The logic of the menu is correct. Just syslinux has some bug. It doesn't set MENU DEFAULT properly for all submenus. If your first Enter keypress

> On Wed, Dec 3, 2014 at 1:30 PM, Geert Stappers <stappers at stappers.nl> wrote: > > H. Peter Anvin wrote: > > } Thorsten Glaser wrote: > > } } When I have an environment that uses vesamenu, for example on PXE, > > } } how do I configure it so that, for some of the menu entries, it > > } } switches back to the text mode (03h) before handing off to the next

This is a bug report about Syslinux 6.03-pre11 in EFI. To Syslinux EFI developers; the results can be replicated in real hardware. I apologize for the length of the email; I am describing the steps necessary to reproduce the confusing behaviors the best I can. I have been experimenting with VBox and Syslinux EFI32. In EFI, the default screen resolution for [vesa]menu.c32 is not 640 x 480

Op 2013-06-26 om 11:01 schreef syslinux-owner at zytor.com: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: Syslinux at zytor.com > From: ady-sf at hotmail.com > Subject: 6.xx vesamenu and misc issues > Reason: Message body is too big: 1085125 bytes with a limit of 512 KB > > Date:

On Thu, Jun 16, 2016 at 4:53 AM, Jackson, Dan via Syslinux <syslinux at zytor.com> wrote: > Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). > > Thanks, > Dan Jackson (Lead ITServices Technician). > > -----Original Message----- > From: Syslinux

> 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

I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Deployment Services option, it hangs. Thanks, Dan Jackson (Lead ITServices Technician). -----Original

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been using the standard isolinux.cfg file for some time with great success. Have it currently display a file at the beginning with a little .lss graphic file, and some basic info then with the image names and info. Also have 4 of the help files linked to the F1 - F4 keys. But I just had a number of emails back

I'm integrating DBAN (http://dban.sourceforge.net/) into our PXE boot menu system (using vesamenu.c32) but it just hangs when I'm using vesamenu.c32 and confusingly when I revert our menu system to using vesa.c32 it works ok. I've stripped out any extraneous configuration but it still seems to have the same problem. When I use this in pxelinux.cfg it boots into DBAN ok: default

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, vesamenu.c32 from syslinux-3.75.tar.bz2 is broken in my tests with: - qemu 0.9.1 -cdrom iso_image - qemu 0.9.1 -cdrom iso_image -std-vga - virtualbox 2.2.0 (Sun version) It blocks right after showing the copyright notice. I've since compiled the following versions in my machine, running Fedora 10: - syslinux-3.63 - syslinux-3.72 - syslinux-3.73 - syslinux-3.75-143-g080bf56 I did a