similar to: SYSLINUX 3.10-pre9

I've begun tinkering with syslinux v3 and have uncovered an anomoly with the DISPLAY file when called by pxelinux.0. If I have: DISPLAY boot.msg With an "^Xsplash.lss\n" in the file boot.msg (exactly: 18 73 70 6C 61 73 68 2E 6C 73 73 0A) file, it will fail to load the rle image. And produce some goofy results in the tftpd log: Jun 5 06:27:06 pxe in.tftpd[24649]: RRQ from

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

Hi, I just replaced the pxelinux.0 of some 2.x version by pxelinux.0 vers. 3.0.7. Some of the PXE Clients refused to boot thereafter (just stopped after reading the config file). I noticed that the APPEND line was too long. Is this intentional? What is the maximum length of the APPEND option line? Thanks, Thomas

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

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

Hi, I'm Florent BERANGER, from Flonix ( http://www.flonix.com ). After several tests, we have found that Syslinux 3.00 pre9 is no longer compatible with USB stick booting. Syslinux 2.13 works fine with this feature. Error infos : Syslinux 3.00 pre9 only displays its version and a new line with a "a" character and then hangs. Tests configuration : Syslinux applied from : Linux

This is the latest version of the gfxboot module. It's supposed to work on all Syslinux derivatives. I am not sure about the copyright notice and would appreciate any input. - Sebastian Index: syslinux-3.74-pre17-2-g2a9ddec/modules/Makefile =================================================================== --- syslinux-3.74-pre17-2-g2a9ddec.orig/modules/Makefile +++

On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: > isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. > Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx

git://git.zytor.com/users/genec/syslinux.git Branch core-diskstart-boot-for-hpa. I found that INT 13h AH 08h in BOCHS used ES, DI, at least when using a partitionless HDD, causing "Boot error" from the magic check as it was loaded to the wrong location. HPA suggested wrapping INT 13h with the push/pop for ES's safety. This then lead to checking over for all int 13h calls in

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

Trivial module to execute an arbitrary command. --- com32/modules/Makefile | 2 +- com32/modules/cmd.c | 42 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+), 1 deletions(-) create mode 100644 com32/modules/cmd.c diff --git a/com32/modules/Makefile b/com32/modules/Makefile index 2739a39..930e89b 100644 --- a/com32/modules/Makefile +++ b/com32/modules/Makefile

Dear all, I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem is, I have problem to use it for PXE booting (BIOS mode). It always gives me "Failed to load COM32 file vesamenu.c32". I am sure all the settings are correct because if I switch to the prebuilt syslinux downloaded from

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

Hi everyone, Kevin Tran of Broadcom just identified a very serious bug in PXELINUX where random parts of the PXE stack would get overwritten by PXELINUX. As a result, I have release SYSLINUX 2.00-pre9 for testing; if you have had problems with PXELINUX **PLEASE** test this version. I will try to make a SYSLINUX 2.00 some time this week if this tests out OK. I will also hunt for similar bugs

Based on a few reports I've gotten today, I have make a new release candidate, 3.11-pre9, and am pushing out the release target to Friday, September 2. New in this release candidate: - Change to MEMDISK, which hopefully will work right both on machines with and without physical floppies. - Try to enable the 16550A FIFO for serial console. I'm hoping this will help eliminate dropped

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

I just picked up 3.10-pre15 and the "PXELINUX corrupts graphic filename referenced from DISPLAY file" bug is zapped. Yipee! Thanks hpa. And Arwin too, if that 'xor esi,esi' was the crux. However, LOCALBOOT -1 and LOCALBOOT 0 don't work the same as they did for me in 3.07. :-( 3.07: LOCALBOOT -1 apears to work as I have a hard disk listed in bios boot order after the

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

Hi, friends It is described at this page: http://superuser.com/questions/195275/usb-boot-no-default-or-ui-configuration-directive-found <http://superuser.com/questions/195275/usb-boot-no-default-or-ui-configuration-directive-found>help, thanks! -- regards chenge

I'm going to promote SYSLINUX 3.32-pre7 to release candidate unless someone objects, with the intent of releasing 3.32 immediately after Christmas. Please let me know if there are problems that should make me *not* do so, even if you have previously reported them. -hpa