similar to: Just one machine could not boot into PXE

Hi, all Can I call mboot.c32 from a DOS menu, since if I do not use menu.c32, it can use the default label to bring up a default DOS menu, and if I can setup the time out for default of DOS menu to boot into local drive then I solved the problem. I just need to boot into the local drive after 10 seconds without other choices and this machine has problem with menu.c32 Or any other ideas?

I researched on Archive, but the instruction says to copy startrom.com to startrom.0, so I changed boot program to startrom.0 instead of pxelinux.0, it gives me a TFTP error saying file not found. then I keep startrom.0, change boot program back to pxelinux.0, then I do not see F12 key and boot directly to PXE. then I change the boot program to startrom.com it asked me to press F12, but can

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, >

On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > First, I'm confused. In the prior "whole" setup (the one you generated > after my 15 steps, plus one workaround), was/is the basic boot menu at > least "working" when you used the workaround for the buggy PATH > directive when booting in UEFI mode? I mean: > >

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:

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'

works with legacy, hangs with efi. where works is: No DEFAULT or UI configuration directive found! but enter and ^v make things happen hangs is: nothing happens, no response from keyboard, have to reboot. note: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > works with legacy, hangs with efi. > > > > where works is: > > No DEFAULT or UI configuration directive found! > > but enter and ^v make things happen > > > > hangs is: nothing happens, no response from keyboard, have to reboot. > > > > note:

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

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

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

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > After some discussion/debugging behind the scenes, we are back on > track, with updated Debian packages. > > > 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted > in "target" (or "$target", or some similar notation), and the version

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 Wed, Dec 12, 2018 at 4:00 PM Carl Karsten <carl at personnelware.com> wrote: > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > > > > > > > You should be able to see the effects of the DISPLAY directive when > > > > testing the floppy image I sent you, because it starts with the

On 05-08-15 04:17, Ady via Syslinux wrote: >> Now... why is vesamenu.c32 crashing like it does now? Why is the version >> I tried without Gene's latest patches crashing before even beginning to >> load the first stage: ldlinux.e64? > I think you were "hinted" about this before. About what? Did I miss something obvious? I now know why it did not load

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

syslinux.txt: syslinux binary is in "linux" directory menu.txt: menu.c32 and vesamenu.c32 are in com32/menu directory --- doc/menu.txt | 2 +- doc/syslinux.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/menu.txt b/doc/menu.txt index 620527e..8a999cd 100644 --- a/doc/menu.txt +++ b/doc/menu.txt @@ -18,7 +18,7 @@ See menu/README for more

I'm not seeing how to set this path option? Here is what I get using vesamenu.c32 as an example when moved to a directory outside of the build. The current syslinux 4.06 has all the files in the same directory which is at the root of the cd. ldd vesamenu.c32 linux-gate.so.1 => (0xb77c5000) ../../com32/libutil/libutil_com.c32 => not found ../../com32/lib/libcom32.c32 => not found

On Thu, Jun 6, 2013 at 4:01 PM, H. Peter Anvin <hpa at zytor.com> wrote: > Very odd! > > This shows a TFTP connection being correctly established and then > disconnected, with all the negotiation involved. I'm wondering if it is > iPXE that is playing games with us here... > > -hpa > > Some odd things I observed just now. 1. Since yesterday, I have