similar to: menu.c32 selection bar visibility on serial console

Hello, We have got a bunch of HP Proliant Servers and during power on it's possible to press F9 to reach the System BIOS. Since the servers take very long to power on I miss the stage where I can press F9 to reach the BIOS and so pxelinux gets started. It would be very helpfull if it would be possible to get from the pxelinux menu.c32 to the BIOS. Is this somehow possible ? Regards

Hello, I often see the double dash -- in the append line in isolinux/syslinux configurations I only know this as "disable further option processing" e.g. in bash. What is the function of the -- ? I don't see any difference if I use it don't use it. E.g here : append vga=normal initrd=/install.amd/initrd.gz -- quiet append vga=normal initrd=debian-installer/amd64/initrd.gz

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

> 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

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

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

isoconfig.sys file below - Only change from past is adding stuff after the bz28.7 kernel. DEFAULT vesamenu.c32 Prompt 0 menu color screen 37;40 #80ffffff #00000000 menu color border 30;44 #40000000 #00000000 menu color title 1;33;44 #c0fdd017 #00000000 menu color unsel 37;44 #90ffffff #00000000 menu color hotkey 1;37;44 #ffffffff #00000000 menu color sel 7;37;40

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'

Hi all, I can't suppress TAB menu prompt and I wonder if this feature is working or not. I'm using extlinux and here is a cut from extlinux.conf: UI menu.c32 prompt 0 MENU TITLE MYPC MENU AUTOBOOT Automatic boot in # second{,s}... MENU NOTABMSG timeout 100 TOTALTIMEOUT 1800 label main MENU DEFAULT MENU LABEL Linux Kernel 3.x ... I'm using latest code from the git tagged as

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

hi out there, first of all: samba is pretty cool! question: is there a way to synchronize the clock of my linux box to a win95 box (something like 'smbnet time \\win95 /set /yes')? cheers jodok ;----------------------------------- Jodok Sutterluety Austria, Vienna Tel: ++43 1 4080791 email: js@bonus.unterland.at ;-----------------------------------

Hi all, I would really appreciate feedback on the graphical menu system and its infrastructure. It's not really clear to me that it's what people want; it seems to me that it makes more sense than gfxboot, for example (C rather than pseudo-Forth), but I can understand people would disagree. Anyway, the more feedback I get the easier it will be to pick a direction and a priority for

I have decided to promote SYSLINUX 3.31-pre4 to release candidate status. If it tests out OK, it will become 3.31 some time next week, probably. -hpa

I have just released SYSLINUX 3.31. It is functionally identical to SYSLINUX 3.31-pre4. Changes in 3.31: * The simple menu system (menu.c32 and vesamenu.c32) now support loading more than one configuration file at a time, using MENU INCLUDE or by specifying multiple filenames. * The MENU COLOR statement can now control the shadowing mode. Changes in

On May 31, 2012 5:23 AM, "Arends, R.R." <r.r.arends at hr.nl> wrote: > > Hello Genec, > > Got a question regarding pxechn.c32 in combination with wds (2k8r2). > > We got (i)pxelinux as our main pxe system, and want to chain to wds with a vesamenu option. > > I tried the latest pxechn.c32 from git. But somehow wds still tries to contact the next-server (main

As some have noticed, WDS (Windows Deployment Services) on Windows Server 2008R2 can't normally be chained with pxechain.com. Some have also noticed wdsnbp.com doing something resembling another round of DHCP (discover/ack/request/offer). Working on pxechn.c32 I've found the "issue" and incorporated a workaround into pxechn.c32. wdsnbp.com issues a DHCP discover to the IP

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

On Fri, 19 Jul, at 04:24:52PM, Victor Sudakov wrote: > Gene Cumm wrote: > > > > The big thing I notice is just that since 5.10, the > > > > code in pxelinux.0 does DNS queries for specific calls rather than a > > > > dotted quad conversion first. > > > > > > That *was* relevant. It did not work until I replaced the dotted quad > > >