similar to: working directory in 5.00pre8 and 4.06

Hi Matt, First comments about 5.00-pre10. 1_ When using "ctrl+v" in the boot prompt, there is no space character between the version and the boot mode. Additionally, the main version number is shown twice. For example, "SYSLINUX 5.00 5.00-PRE10CHS" should be: "SYSLINUX 5.00-PRE10 CHS" 2_ Boot to menu.c32, press [ESC] to go to the boot prompt. Pressing [ESC]

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Folks, I've just pushed out another prerelease for the 5.00 branch. The idea behind this -pre was to merge in the final 4.06 release. I'm aiming for a final 5.00 release next week, but as we saw with the 4.06 branch, anything can happen and these deadlines can get pushed backwards. Please, test if you can. One thing that is going to happen next week is a Syslinux-6.00-pre1, which will

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

> 5.01 should be released by the beginning of next week. The following problems (among others) are present in 5.00. I hope they can be solved for 5.01. A_ LABEL directive with trail space characters fails: http://www.syslinux.org/archives/2012-December/019153.html B_ TEXT HELP directive hangs (easier to see when using Windows-like new lines, CR/LF):

Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

> I asked before about config_cwd and after some more digging, it looks > like it could be removed... > > Specifically, the documentation > http://www.syslinux.org/wiki/index.php?title=Config#CONFIG says: > > ---------- > * CONFIG config_file [new_WD] > > Load a new configuration file. The new configuration file is read, the > Working Directory is optionally

On Mon, Mar 06, 2017 at 03:51:07AM +0000, Ady Ady via Syslinux wrote: > > > I asked before about config_cwd and after some more digging, it looks > > like it could be removed... > > > > Specifically, the documentation > > http://www.syslinux.org/wiki/index.php?title=Config#CONFIG says: > > > > ---------- > > * CONFIG config_file [new_WD] >

Hello again, * TFTP and DHCP started using: dnsmasq --port=0 \ --no-daemon \ --enable-tftp \ --tftp-root=/run/archiso/bootmnt \ --dhcp-range=192.168.0.2,192.168.0.254,86400 \ --dhcp-boot=/arch/boot/syslinux/gpxelinux.0 \ --dhcp-option-force=209,boot/syslinux/archiso.cfg \ --dhcp-option-force=210,/arch * and for DHCP+HTTP

On 2016.03.06 23:25, Shao Miller via Syslinux wrote: > Having typed that, perhaps we could discuss your (or Rufus') specific > needs, in parallel? I think that is probably worthwhile, as I wouldn't mind having a second opinion from Syslinux developers on whether my current ISO -> USB conversion process could be improved. > Do I understand correctly that the primary >

The config.c32 module (and the CONFIG directive) is not behaving as expected when using syslinux.exe 5.00pre11 as installer. To replicate: 1_ The content of the device: /dira /cat.c32 /config.c32 /ldlinux.c32 /ldlinux.sys /libcom32.c32 /pwd.c32 /syslinux.cfg /dira/dira.cfg 2_ Content of /syslinux.cfg: DEFAULT pwd1 PROMPT 0 LABEL config1 COM32 config.c32 /dira/dira.cfg APPEND /dira/ LABEL

> Hello Ady & list, > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > >

Hello Ady, On Wed, Aug 27, 2014 at 10:52:25AM +0300, Ady wrote: > > Hello Ady & list, > > > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > > Hello Ady, > > > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 >

Installing with: syslinux --directory otherdir -i my_unmounted_device will install the bootloader in the desired directory ("otherdir") under the root directory of the desired unmounted device ("my_unmounted_device"). All the corresponding syslinux-related files are located in the same installation directory. When booting this device, SYSLINUX fails to find a

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

In message <BLU0-SMTP48EE10402F4B5AE9EC1E078BBB0 at phx.gbl>, Ady wrote: >After dd'ing my test.img to the USB drive, you would have one FAT32 >partition of about 700MB. So: Someone in this thread said something about erasing or eliminating stuff from the USB stick first, so just to be on the safe side, before I dd'd your test.img file to my test stick (i.e. one of my 2GB

Hi folks, Syslinux 5.01 is out, a week later than predicted but that's largely down to the realloc() bug described below. This release is mainly a collection of bug fixes for problems reported after people tested Syslinux 5.00. The NEWS entries are included at the bottom. There was a pretty nasty realloc() bug that took some time to find and fix, which resulted in memory corruption. There

Hello, today I upgraded from Syslinux 4.06 to to Syslinux 5.00. But now the system won't boot anymore and I get the message Failed to load ldlinux.c32 Boot failed: please change disks and press a key to continue What I have done: 1) Installed Syslinux 5.00 2) Reinstalled "mbr.bin" to /dev/sda and /dev/sdb using dd bs=440 count=1 conv=notrunc

Hi On Tue, May 20, 2014 at 9:18 AM, Anatol Pomozov <anatol.pomozov at gmail.com> wrote: > Hi > > On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On May 20, 2014 12:33 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: >>> >>> Hi >>> >>> On Mon, May 19, 2014 at 6:58 PM, Gene Cumm