similar to: SYSLINUX 3.30-pre1 with pxelinux ?

-----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 all, I have pushed out a SYSLINUX 3.30-pre1. The main difference versus earlier versions is that this version contains a *preview* of a VESA graphical menu system (vesamenu.c32); it's used the same way as menu.c32, with the addition of a few more commands (which can also be used in menu.c32 in this new version): MENU BACKGROUND file.png ... loads a background image in PNG format.

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

> 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

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, I am trying the simple menu passswd in syslinux 3.11, and it seems that if I set the timeout option, the menu passwd is ignored. For example: ----------- default menu.c32 timeout 70 prompt 0 noescape 1 MENU MARGIN 5 MENU MASTER PASSWD $4$x$03NXHMe7QS0Ukxlkyh684LkWdqY$ label local MENU DEFAULT # MENU HIDE MENU LABEL Local operating system (if available) MENU PASSWD localboot 0 label

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 [mailto:syslinux-bounces at zytor.com] On Behalf Of Jackson, Dan via Syslinux Sent: 16 June 2016 09:27 To: 'syslinux at zytor.com'

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

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

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)

Hi All, We seem to have a strange problem with our NEC ML4 pcs. When using pxelinux to network boot, we are getting our menu (using menu.c32) when we choose a option the machine just locks up. If the option requires a password it shows the password box , I put in the password and then it locks up. But strangely the machine will boot from local disk which is an option on the boot menu. Our

I don't think that's it, but fair enough, try this sample config: ************************************************# Test File: isolinux.cfg default vesamenu.c32 ALLOWOPTIONS 0 LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img MENU END************************************************ I am using binaries from 6.03-pre11 from kernel.org. I used

Apologies for how that formatted. Also on pastebin: http://pastebin.com/EXSq75yX --Ian > From: ian at internals.io > To: ady-sf at hotmail.com; syslinux at zytor.com > Date: Tue, 29 Apr 2014 19:09:09 -0500 > Subject: Re: [syslinux] Issues with syslinux_run_command(str) and parameters > > I don't think that's it, but fair enough, try this sample config: >

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

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

Hi, there now i am booting pxelinux menu32 with 2 boot images 1. DOS boot image 2. Thinstaion pxelinux and my directory structure is like this (Pxelinux with menu32) /tftpdroot/pxelinux.0 /tftpdroot/pxelinux.cfg/default /tftpdroot/dos.imz (DOS bootimage) /tftpdroot/memdisk (memdisk package) (Thinstation Pxelinux) /tftpdrooot/pxe/pxelinux.0 /tftpdroot/pxe/initrd

Hello While testing PXE booting, I decided to change IPAPPEND to the new SYSAPPEND and does not work: nothing is appended to command line. I tested using menu.c32 and vesamenu.c32, same issue. --------------------------------------------------------------------- SERIAL 0 38400 UI boot/syslinux/vesamenu.c32 LABEL arch64_nbd MENU LABEL Boot Arch Linux (x86_64) (NBD) LINUX boot/x86_64/vmlinuz

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

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.

On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > Hello > > While testing PXE booting, I decided to change IPAPPEND to the new > SYSAPPEND and does not work: nothing is appended to command line. > > I tested using menu.c32 and vesamenu.c32, same issue. > > ---------------------------------------------------------------------