similar to: Syslinux 5.10pre1 - Failed to load COM32 file .c32

I stumbled across the following patch and wondered if it wouldn't be a good idea to have it included. http://foldingcd.svn.sourceforge.net/viewvc/*checkout*/foldingcd/trunk/folding_cd/patches/syslinux-3.51-64bit.patch?revision=5 It adds a default64 keyword and detection of a 64bit processor. It could be useful for mixed environments. The patch is against 3.51, but looks like it would port

Hi there, ----- Original Message ----- From: koxudaxi at gmail.com To: syslinux at zytor.com Date: 01.04.2013 10:00:27 Subject: Re: [syslinux] Problem with pxelinux 5.0 and memtest > On 04/01/2013 09:28 AM, H. Peter Anvin wrote: >> On 03/31/2013 05:26 PM, Koudai Aono wrote: >>> I ran the test on a x86 emulator is called Oracle VirtualBox. >>> I think it might not be

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

On Wed, Oct 30, 2013 at 09:52:57AM +0200, Ady wrote: > > > The wiki (http://www.syslinux.org/wiki/index.php/PXELINUX) still says: > > > > "copy pxelinux.0 (from the SYSLINUX distribution) and any > > kernel or initrd images that you want to boot" > > > > like I've been doing forever, but how do I know what else I need, and > >

I did confirm earlier that this does work, and combined with a MENU HIDDEN to hide it from the visible menu it is a possible solution. I originally assumed that this was due to that going down a different code path and did not mention it, apologies. The scale of my menu makes doubling/tripling menu entries less ideal, though. Do we consider it intended functionality that modules such as whichsys

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

utils/mkdiskimage.in: With option -s: Avoid zeroizing the partition even if truncate() failed. --- utils/mkdiskimage_patched_01.in 2014-01-30 20:43:02.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:45:09.000000000 +0100 @@ -217,8 +217,11 @@ print OUTPUT "\x55\xaa"; $totalsize = $c*$h*$s; $tracks = $c*$h; -# If -s is given, try to simply use truncate... -unless

--- utils/mkdiskimage.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/mkdiskimage.in b/utils/mkdiskimage.in index 533193a..a95a077 100644 --- a/utils/mkdiskimage.in +++ b/utils/mkdiskimage.in @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given, try to simply use truncate... -unless ($opt{'s'} && truncate(OUTPUT,

ifgpxe.c32 is a com32 module that will run one command if gPXE extensions are available, and a different command if not. At VMware, we use this module to chain-load gpxelinux.0 from pxelinux.0. Both of those binaries use exactly the same configuration file, and this module allows us to differentiate between the two cases and break the infinite chain-loading loop that might result. Typical usage:

Hi! It's funny, but I was unable to find an answer to my question. I am building an embedded system (x86). I want to install syslinux on a fresh system. So, I am booting from a USB LINUX CD (Ubuntu 12.04 in this case). 1) I must have an ext2 partition (This is my application). 2) I understand that I must have a FAT partition (to install syslinux). Correct ? So, basically I understand that

New module which check if the PLoP Boot Loader already has booted a CDROM or USB drive by checking for the presence of the PLoP INT13h hook. The following assembly code (NASM) can detect the PLoP INT13h hook: mov eax,'PoLP' ; Reverse of 'PLoP' mov ebp,'DKHC' ; Reverse of 'CHKD' int 13h cmp eax,' sey' ; Reverse of 'yes ' jz

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello. I'm trying to setup an multiboot USB, mainly to install Debian using netinst images. I've mounted one of iso image and copied to a directory in USB (made with syslinux 6.03) and copied too the kernel and initrd for hd install. I've setup a directory to start the USB and, well it starts, but when I jump (using CONFIG) to the

To remind you once again. ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. This relates specifically to the use of the vesamenu.c32, menu.c32 works without problemos. This "code" is already in 6.03, therefore this is not a fix for it! Revert "SYSAPPEND: Fix space stripping" This reverts commit 3106dcd http://repo.or.cz/w/syslinux.git/commit/3106dcd Fixes

On 01.07.2015 12:10, Gene Cumm wrote: > On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >> >> To remind you once again. >> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >> This relates specifically to the use of the vesamenu.c32, >> menu.c32 works without problemos. > > isolinux-debug.bin is not for

Have been using syslinux for some time for my g4l project, and was just looking at the new 5.00. Normally have just copied the new files, but with version 5.00 it is missing the support files according to ldd, and even putting the missing files in the directory failes to find them. ../../com32/... Script to copy files from new syslinux directory to the projects isolinux directory that is

utils/mkdiskimage.in: New option -S to sync zeroizing after each cylinder and to issue pacifier messages. --- utils/mkdiskimage_patched_03.in 2014-01-30 20:54:27.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:59:19.000000000 +0100 @@ -139,6 +139,7 @@ if ( $file eq '' || $c < 1 || $h < 1 || print STDERR " -4 use partition entry 4 (standard for

On Sun, Jan 18, 2015 at 6:44 AM, Angel <angelv64 at gmail.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hello. > > I'm trying to setup an multiboot USB, mainly to install Debian using > netinst images. > > I've mounted one of iso image and copied to a directory in USB (made > with syslinux 6.03) and copied too the kernel and initrd

On Fri, Nov 30, 2018 at 9:56 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I have a proposal for you here (in the Syslinux mailing list): let's > first find out _what_ exactly is required in order to boot in UEFI > mode, and then you can take the info downstream. Whether "downstream" > means your own personal customized boot.img, or

The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a