similar to: 6.xx vesamenu and misc issues

On Wed, Jun 26, 2013 at 8:21 PM, Ady <ady-sf at hotmail.com> wrote: > Vesamenu.c32, v.6.xx: > > qemu: OK > KVM: OK (I have not tested this one) > VBox 4.2.12 / 4.2.14 : incorrect > VMWare Player 5.0.2: incorrect. I presume that the image vesamenu6/vesamenu6.png is what you see in both VirtualBox and VMware Player? I tested with Workstation-9.0.2 (the same code but more

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

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

> 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

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

>From: Ady <ady-sf at hotmail.com> >To: syslinux at zytor.com >Subject: Re: [syslinux] lss broken when upgraded 4.05 to 6.03 >Message-ID: <BLU436-SMTP134329F24C9A85B97FF55BF8B990 at phx.gbl> >Content-Type: text/plain; charset="US-ASCII" > > >> On 11/2/14, Ady <ady-sf at hotmail.com> wrote: >> > >> > FWIW, Utopic uses

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 Thu, 4 Dec 2014, Ady wrote: > > > Perhaps there should be a new MENU-type directive, so to force the > > screen to text mode (as opposed to leaving it in graphics mode for as > > long as it can be)? Perhaps this could also be useful when exiting a > > vesamenu to Syslinux CLI? > > Yes, please. To make this dependent *only* on the configuration of >

Hi, UTF8 is a standard today. Nevertheless it seems to be impossible to display UTF8 characters in vesamenu.c32. Am I wrong? There is nothing about that in the docs. Are there plans to make vesamenu.c32 UTF8 capable or make syslinux capable e.g. for LC_ALL=de_DE.UTF8? Best regards, Uwe Galle

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 list sorry my english is not perfect :( im using pxeboot with vesamenu.c32 in default file i load a backgroundpic (*.jpg) but the vesamenu border overlaps pieces of my background picture ^^ my question is an all coders from syslinux can you make a MENU command like topmargin MENU LABEL xxxx MENU WITH xx MENU MARGIN xx (from left) .... MENU TOPMARGIN xx (from top) <- new to

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

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

Hi guys, i encountered a strange problem or bug, i dont really know ive got a panasonic cf-m34 toughbook here, when i boot up the vesamenu.c32 und select my memtest86 item or try to boot up my dosk boot bisk via memdisk, i get a black screen saying "Loading" and my tftp log tells me " file <memdisk or memtest> error 131 in system call ReadFile..". But when i

Hello I'm using PXELinux with vesamenu.c32 to load a custom knoppix image I made and to allow access to the WDS menu. The problem is that the PXElinux loads the menu automatically (unlike WDS which asks the user to press F12 before loading the menu) and I want it to load only if the user presses F12 in 5 seconds. So I tried using the hidden function of the menu with the timeout option