similar to: Syslinux 4.02 released

dos/syslinux.elf fails to build on current Ubuntu Natty (binutils 2.21) as follows: ld -m elf_i386 -T dosexe.ld -o syslinux.elf header.o crt0.o ldlinux.o syslinux.o fat.o syslxmod.o syslxopt.o setadv.o getopt_long.o bootsect_bin.o mbr_bin.o cache.o fatchain.o open.o searchdir.o libcom.a /usr/bin/ld.bfd.real: syslinux_ldlinux_size must equal the size of .payload /usr/bin/ld.bfd.real:

Op 20100708 om 14:24 schreef syslinux-bot for H. Peter Anvin: > > Update in preparation of a 4.02 release cycle. > > --- a/NEWS > +++ b/NEWS > @@ -15,6 +15,13 @@ Changes in 4.02: > stage2 of GRUB Legacy (Gert Hulselmans). > * whichsys.c32: execute specific command, based on Syslinux > bootloader variant (Gert Hulselmans). > + * lua.c32: a lot of new

Hello Sir, on Friday, August 20, 2010 11:32 AM Gert Hulselmans wrote > loading the boot file ... > Boting ... > "-" cursor keeps on blincking Are you quite sure that booting the Windows Recovery Console under syslinux can work and that "cursor keeps blinking" is only a problem of your special menu? YES I am 100% sure that booting the Windows Recovery Console

Op 20100709 om 02:05 schreef syslinux-commits-owner at zytor.com: > Message rejected by filter rule match > I don't know why it rejected, this E-mail is to get the NEWS file updated. > From: Geert Stappers <stappers at stappers.nl> > To: syslinux-commits at zytor.com > Subject: Re: [syslinux:master] NEWS: correct credit for new Lua work. > Date: Fri, 9 Jul 2010

Hi Shao, On 2016.02.24 23:43, Shao Miller via Syslinux wrote: > Did you happen to notice anything unusual when compiling with MinGW > under Linux, once 'ok' was removed? I seem to recall warnings about > unused results, but not of unused objects. Maybe that's an incorrect > recollection or maybe it's ancient history, however. I got no warnings with the patch on

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

Hello Sir, Copid cmdcons and cmldr to O:(my usb drive) as follows (1) Microsoft(R) Windows 98 (C)Copyright Microsoft Corp 1981-1999. C:\WINDOWS>format o: /s C:\WINDOWS>format o: /s WARNING, ALL DATA ON DISK DRIVE O: WILL BE LOST! Proceed with Format (Y/N)?y Checking existing disk format. Formatting 967.98M Format complete. System transferred Volume label (11 characters,

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) If I build syslinux on a system without mingw a (successful) build will end with: ls: cannot access win32/syslinux.exe: No such file or directory ls: cannot access win64/syslinux64.exe: No such file or directory [...] make: [all] Error 2 (ignored) Ie, it ends with an ignored error. That's confusing (and a bit

Hi there, I've been trying to boot some new machines via uEFI and it does not work, as you can see below. From my hunting around on the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the

It looks like it is more like the issue in bug #26. In the tcpdump I can see the client attempt to RRQ the kernel but the client itself reports "No file found." I am having similiar issues as reported in both bug reports with getting Syslinux 6.02 to work as in syslinux64.efi gets pulled but then the client gets stuck on ldlinux.e64. Can I use http/nfs instead after syslinux64.efi gets

'nopassany' is missing in the MEMDISK documentation: http://www.zytor.com/pipermail/syslinux-commits/2010-February/000096.html - Gert Hulselmans commit aeb2406ea701d974c85aa7fdd9af7c53106d7e48 Author: Gert Hulselmans <gerth at zytor.com> Date: Sat Mar 6 22:33:09 2010 +0100 Document 'nopassany' in MEMDISK documentation. diff --git a/doc/memdisk.txt b/doc/memdisk.txt

Issue Statement: PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and kernel are on PXE server. Using packet captures I see that the URI request for the remote file on the repo

Comments fix and usage output corrected for chain.c32 - Gert Hulselmans Signed-off-by: Gert Hulselmans <kimmik999999 at yahoo.co.uk> $ diff -u syslinux-3.84/com32/modules/chain.c.old syslinux-3.84/com32/modules/chain.c --- syslinux-3.84/com32/modules/chain.c.old 2009-12-29 01:46:34.058793767 +0100 +++ syslinux-3.84/com32/modules/chain.c 2009-12-29 01:53:41.150794351 +0100 @@ -49,7

Good day Gert Hulselmans, You had reported to me at one point that MEMDISK -> .ISO -> ISOLINUX had failed under certain circumstances. I just noticed with a MEMDISK 3.86 that specifying the "iso" option on the command-line actually resulted in the .ISO getting BIOS drive number 0xFF. I had to specify "iso harddisk=224 pause" to confirm that it resulted in 0xE0 (hd96).

Hello, I wanted to recompile syslinux64.exe (windows 64bit binary) on ubuntu. The default ./find-mingw64.sh script failed to locate mingw64 on ubuntu, even after root at htpc:~# apt-get install gcc-mingw-w64 So I had to patch the script to let it find mingw64 on ubuntu as well. Patch is below, please apply to syslinux sources: --- syslinux-4.05/win64/find-mingw64.sh.orig 2012-08-28

> > In message <BLU0-SMTP4359BC7EA366B1FB76EA9188BBF0 at phx.gbl>, > Ady <ady-sf at hotmail.com> wrote: > > >I am probably misunderstanding something. We seem to go backwards. > > Yes, and ever moreso. > > >"Something" changed. If you now cannot see your USB drive in your > >list (press F12 during POST), there is no point on

> > > Ady, before responding to you further, I'll ask you now to take onje > more (fresh) look at this thread that I started over in the GParted > forums: > > http://gparted-forum.surf4.info/viewtopic.php?pid=31834 > > Please note that I have now followed-up on myself and that I have added > quite a lot of new & additional information. > > It now

> > SYSLINUX 6.03 CHS 6.03-pre1 ... > > Failed to load ldlinux.c32 > Boot failed: please change disks and press a key to continue. > First, let me clarify that all the scripts and procedures in the Clonezilla site are not related to this official Syslinux mailing list or to The Syslinux Project. They are done by the Clonezilla team. Now that I know you are working

On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: > Sorry for the confusion, I am actually using 6.02. It turns out that I was > trying to use the 32-bit efi binary to load 64-bit kernels. I switched to > using "syslinux64.efi" but it hangs during boot, just before loading the > menu. I have not been able to get it to load the menu

On 04.08.2016 00:58, Erik Sandberg via Syslinux wrote: > Does anyone know how to install the gptmbr.bin onto a USB drive with > Windows? I noticed that it would be really easy to modify the source of the > installer to install gptmbr.bin instead of mbr.bin with the -m flag, but > I'd like a solution that doesn't require me to maintain my own custom > syslinux. I'm open