similar to: Syslinux-4.06-pre14

Hi, I would like to use INT22h, function 000Dh, but I found that it is disabled in vector table: in core/comboot.inc: int22_table: [...] dw comapi_err ; 000D clean up then bootstrap [...] The code of this function is present in this file (comapi_chainboot). Why this function is disabled? Regards Piotr Romaniuk PS I am using syslinux-4.04.

I just tried to build syslinux-3.71-pre14-5-gfa6a60e and got the following: make[1]: Leaving directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/dos' make[1]: find-mingw.sh: Command not found make[1]: Entering directory `/syslinux/syslinux-3.71-pre14-5-gfa6a60e/win32' gcc -Wp,-MT,syslinux.o,-MMD,.syslinux.o.d -W -Wall -Wno-sign-compare -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I.

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

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 all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

Hi, The menu timeout isn't cancelled but restarted when there's only a single item in the menu and I try to move the selection. The selection flashes but of course does not move. Tested with pxelinux under QEMU: $ qemu -net nic -boot n -net user,tftp=tftpboot,bootfile=/pxelinux.0 pxelinux.cfg/default: UI menu.c32 TIMEOUT 100 LABEL single KERNEL blah Adding another menu item

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

This is missing since "shuffler: comboot interface to the new shuffler". Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> --- core/comboot.inc | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/core/comboot.inc b/core/comboot.inc index d6f670c..ef69c49 100644 --- a/core/comboot.inc +++ b/core/comboot.inc @@ -950,7 +950,7 @@ int22_table: dw

Finally, the 4.06 release is out there. Thanks to everyone who helped by submitting patches and testing! Peter snuck in a change at the last minute that fixes the GCC 4.7 MinGW struct layout incompatibility in a different way. Here are the highlights of this release, Changes in 4.06: * Support for NTFS, by Paulo Alcantara. * EXTLINUX: more robust device detection, allow user to

syslinux.txt: syslinux binary is in "linux" directory menu.txt: menu.c32 and vesamenu.c32 are in com32/menu directory --- doc/menu.txt | 2 +- doc/syslinux.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/menu.txt b/doc/menu.txt index 620527e..8a999cd 100644 --- a/doc/menu.txt +++ b/doc/menu.txt @@ -18,7 +18,7 @@ See menu/README for more

On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: > >> Hi, > >> > >> We have some problems while network booting thin clients. The type is T5540. > >> > >> At this moment we are using pxe linux 6.03. > >> > >> The systems are booting correctly with pxe linux version 6.03-pre14. > >> We have seen the same error

I'm working with a Soekris net45xx SBC and I'm experiencing problems using any syslinux code (syslinux, pxelinux, extlinux) above version 2.20. I'm interfacing with the Soekris via the serial console port, which is the primary bios console. I've tried different configurations with setting serial in the config file, but no change (though I dont even thing it's getting to reading

So it turns out that -pre13 was quite buggy after all. Once I started running the list of tests that I described in my email, a bunch of those bugs came to heed. Now I think I've fixed them, and so have released -pre14. I have also formally decided to call the final release 3.00 when it's ready. Between code base rewrite + EXTLINUX + libcom32 + simple menu, there is plenty of

I have addressed all the issues that I know about (including, hopefully, the isohybrid version dependence...). I would like to release this this week so please let me know as soon as possible if this version is "go". -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Hello, all. I'm just wondering if it'd be possible to include symbol-stripped versions of win32/ntfstest/ntfstest.exe and win64/ntfstest/ntfstest.exe in future Syslinux releases. That way, users could use it while not burdening folks just doing a usual build of Syslinux. If not (scope creep?), no problem. - Shao Miller

I am hoping for some advice regarding another index problem. The code below is intended to assign a value of 'V' if values on certain variables are >= 1, assign a value of 'N' if values on certain variables are >= 1 on other variables and assign a 'O' if values on any variable which have a value <= 0. The outcome of this code is to assign a single

>> Hi, >> >> We have some problems while network booting thin clients. The type is T5540. >> >> At this moment we are using pxe linux 6.03. >> >> The systems are booting correctly with pxe linux version 6.03-pre14. >> We have seen the same error with version 6.03-pre9. >> >> The error message: >> >> Failed to load ldlinux.c32

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

Hi, Thank you for your reply. Below the answers. _ When you update the version of pxelinux.0, are you also updating the version of ldlinux.c32? Yes, I've updated both files. _ The version of all the c32 files in use shall match the version of the boot loader. Yes, I've copied all the files which we are using. The version of all the files is the same. _ When you mention the error

Hello syslinux, Merry Christmas! These patches will make extlinux work with umounted ext2/3/4 filesystem, for example: $ extlinux -i /dev/sdXN or $ extlinux -i file_block Also it can work with something like: $ extlinux /dev/sdXN --reset-adv or $ extlinux file_block --reset-adv We don't use a new option (I planed to use "-d" but it is already in use), it will check whether the