similar to: version 3.35 boot error

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, 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 was hoping to use wine to run one of those stupid windows binaries that generate a floppy (at least IBM has a clue, and also offers the raw floppy image for dd-ing) In this case, the culprit is seagate's seatools: http://www.seagate.com/support/seatools/ I installed wine under debian unstable (Version: 0.0.20010824-1) and when I run the windows binary under wine, it runs but

I have tested with 3.31 (does not broke /dev/null) and 3.35/3.36 that broke /dev/null I verify that /dev/null exist, then compile one of the target available on top Makefile and /dev/null no more exist. Example root:/usr/src/syslinux-3.36# cat /dev/null root:/usr/src/syslinux-3.36# make .depend Makefile:274: .depend: No such file or directory rm -f .depend for csrc in syslxmod.c gethostip.c ; do

Hi list, I''ve got a system with 3 WD and 3 seagate drives. Today I got an email that zpool status indicated one of the seagate drives as REMOVED. I''ve tried clearing the error but the pool becomes faulted again. Taken out the offending drive and plugged into a windows box with seatools install. Unfortunately seatools finds nothing wrong with the drive. Windows seems to see

I downloaded the 'seatools for DOS' diskette creator on seagate website. it's a windows program that creates the diskette; so a floppy disk must be present in the drive. running the program is ok, but creating the diskette fails, it says "the current diskette format not valid". while the diskette is blank, vfat, mounted and linked to a: in wine; so everything seems to be ok.

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'

In this thread: http://syslinux.zytor.com/archives/2007-February/008014.html I reported that IBM Opteron servers with Broadcom BCM5780 chipsets would freeze randomly in the PXE menus from the SYSLINUX 3.35 tools vesamenu.c32 and menu.c32. There did not seem to be any reason for this nor systematics in when the servers would lock up. The solution is now available: Upgrade your IBM servers to

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

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

Dear All. I have some problem with combined two data frame. .... I have first data frame .. GPAX THAI MATH SCINCE SOCIAL HEALT ART CAREER LANGUAGE 1227 2.99 3.32 2.50 2.64 3.05 3.60 3.72 3.57 2.62 1704 2.81 2.56 2.48 2.86 3.22 3.19 3.55 3.20 2.51 617 2.18 1.90 1.97 2.06 2.38 3.50 3.54 2.33 1.70 876 2.82 3.14 2.73 2.46 2.71 3.11 3.04 3.24 2.90

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

I have used the SYSLINUX 3.35 successfully to boot up vesamenu.c32 as well as menu.c32 on an HP Intel PC (Intel 965 chipset) and a few other types of PCs. But when I use those very same SYSLINUX menus on an AMD Opteron server (IBM x326m), it is capable of loading up vesamenu.c32 and menu.c32 and displaying a list of menu items. But as soon as I select any item whatsoever in the menu list, the

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

After thinking a bit of the multi-file support in 3.31-pre1, and considering a few users' feedback on the subject, I have made a couple of changes: 1. The dummy filename ~ can be used to mean "the main config file". 2. There is a MENU INCLUDE directive now. -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

Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux

I figure I'm probably trying to do something stupid, but here goes. I'm trying to boot a hard disk image (with one 420MB partition, lilo in the MBR) containing debian etch (kernel 2.6.18) using memdisk (onto a dell 2950 with 8G of ram). Lilo (22.6.1) fails on memdisk 3.35, 3.36, 3.50, 3.51, and 3.52-pre, with L 99 99 99 99 et al, but works on 2.x, 3.00 and 3.31. However, the kernel

Hi all, I have released SYSLINUX 3.35-pre5 to the Testing directory; this is a release candidate and I intend to release this as 3.35 early next week unless I hear of any showstopper bugs, so please, pretty please, try it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ kernel.org has been overloaded lately, so it might take a while to show up. Changes in 3.35: *