similar to: comments about 5.00pre10

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

Testing the following (uncommon) syslinux.cfg with different Syslinux versions allows getting to several observations; some might be of interest to users, and some for the Syslinux developers. syslinux.cfg *** UI menu.c32 DEFAULT help TIMEOUT 30 # ONTIMEOUT help LABEL pwd COM32 pwd.c32 LABEL help MENU HELP help.txt *** 1_ For the TIMEOUT-related directives to behave as expected,

I just tested 6.02-pre10 version. ? On physsical machine it is booting ok now,?but chain.c32 result is the same errors :? ERR: Primary partition (in MBR) with invalid offset and/or length. ? ERR: Cant't find myself on the drive I booted from Adding 'relax' option to chain.c32 invocation resolves the problem. ? In qemu the boot and chaining works ok (without 'relax' option).

Initial comments about 5.00-pre11. 1_ Using ctrl+v at the boot prompt: SYSLINUX 5.00 5.00-pre11CHS Copyright ... Initial copyright notice when booting to Syslinux prompt: SYSLINUX 5.00 CHS 5.00-pre11 Copyright ... Request: make the ctrl+v result to be shown as the initial copyright notice (including order and space characters). 2_ Hello.c32 is still behaving differently than in 4.06.

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

Okay, the serial port feature in 3.11-pre9 was of course completely broken (I seem to have bad luck with -pre9's :)... a 3.11-pre10 is now available, and it does seem to have a more reliable handling of arrow keys ... *but not perfect*. There simply is no way to reliably detect both [Esc] and arrow keys on existing serial consoles. -hpa

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 Erwan, First off, many thanks for your wonderful addition to syslinux: dmitest.c32 and another thankyou to hpa for it's inclusion. I need to ask if you are missing a couple of definitions in dmi_processor.h, specifically, the "long mode" flag. I need to use this flag to determine whether a machine is 64-bit capable or not. There is a great web page explaining the "long

Hello, Here's a small enhancement feature for menu.c32. Looking for feedback before starting any coding (not sure when I'll have time for implementation) Regards, Dany St-Amant *Problem statement* When MENU HIDDEN is used on an headless server, any noise on the serial console can interrupt the boot; it would be preferable if there only specific keys were allowed to interrupt, reducing

> Hallo, Matt, > > Du meintest am 25.06.13: > > >> Not really... let's just document "make bios". > > > There's preliminary documentation in doc/building.txt. > > (sent to you and to the mailing list; some robot blocks the list ...) > > Additionally: > > Compiling (with "make bios") worked. > > Running

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

Just a few bug-reports, before I forget: - A Windows installer bug for 4.06 and presumably 5.00-pre9 whereby the ADV contains backslashes. Reproduced with: syslinux.exe --directory \two\dirs e: - An open() (?) bug for 4.06 and presumably 5.00-pre9 whereby the filename /ubcd/custom/syslinux-5.00-pre9/com32/gplinclude/acpi/facs.h fails to open() after 134 iterations in a loop where it's

Am 03.07.2013 14:11, schrieb Matt Fleming: > On Wed, 03 Jul, at 12:22:52PM, Andreas Heinlein wrote: >> Hello, >> >> I am currently trying to get the gfxboot archive from Ubuntu 12.04 >> working with gfxboot.c32 under BIOS, using ISOLINUX 6. >> >> AFAIK, the Ubuntu patches have been added in 4.03, and in fact it >> works with the official 4.05 release,

Hello, I am currently trying to get the gfxboot archive from Ubuntu 12.04 working with gfxboot.c32 under BIOS, using ISOLINUX 6. AFAIK, the Ubuntu patches have been added in 4.03, and in fact it works with the official 4.05 release, but not with 5.10 or 6.01-pre5. I can tell that the menu is actually working, you just don't see it. If you navigate it "blind", the correct

As the first step, I want to thank everybody involved for making a majorly useful application! Second, here are the problems I see: Bug 1: if DEFAULT is not a tag, but a kernel name, menu.c32 fails loading. Bug 2: When menu.c32 returns to syslinux (on pressing Esc), the splash screen is not shown; Bug 3 or a missing feature: When grub.exe tries to return control to syslinux, it

Yes. Prior versions (all to 6.01 inclusive) are working very well. ?And yes it fail before invoking chain.c32 (as I said in qemu there is no errors). ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Tuesday, July 23, 2013 5:16 PM

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

Hello, The following is a comparison of 4.06 and 5.00pre8 behaving differently. I made a floppy image with Syslinux 4.06. I installed ldlinux.sys with: syslinux --directory /boot/syslinux/ --install /dev/fd0 and I added pwd.c32 to the same directory, but I intentionally did not build a syslinux.cfg file. While testing the floppy image in a VM, it correctly boots to the Syslinux boot

In Syslinux-5.00, is the goal that the core and .c32 modules alike will use the same heap? There is a bug I am thinking about: - QEmu with 1024 MiB RAM - Syslinux 4.06 - .c32 can realloc() up to 1013 MiB - QEmu with 1024 MiB RAM - Syslinux 5.00-pre9 - .c32 can realloc() up to 45 MiB I am wondering if there's a maximum-allocation-size being hit, or if it's actually a bug I should look

Hi folks, There are enough changes on the 'firmware' branch to warrant another prerelease. Things that jump out are the changes to update the current working directory when executing syslinux.efi (previously .c32 failed to load if installed to a non-standard directory such as /boot/syslinux, because the current working directory wasn't correct), the realloc() fix from Shao and a new