Displaying 20 results from an estimated 20000 matches similar to: "Backward compatibility"
2010 Jul 01
2
[PATCH] ifplop.c32: Detect if PLoP USB/CD INT13h hook is enabled/disabled
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
2010 Jun 13
0
[PATCH]: ifplop.c32: COM32 module for detection of PLoP USB boot-loader
I wrote a COM32 module which detects if the PLoP bootmanager was used to
boot a CDROM drive or USB drive, by checking for the presence of the PLoP
INT13h hook.
The PLoP INT13h hook check works like this (NASM syntax):
mov eax,'PoLP' ; Reverse of 'PLoP'
mov ebp,'DKHC' ; Reverse of 'CHKD'
int 13h
cmp eax,' sey' ; Reverse of 'yes '
2013 Jun 29
3
Plop Boot Manager quit working with 5.10
> On 06/28/2013 05:32 PM, Patrick Verner wrote:
> > I have updated syslinux in Parted Magic's test version to the 5.10 release.
> > With 4.06 I booted plop like this:
> >
> > LINUX /boot/plpbt/plpbt.bin
> >
> > Now it says /boot/plpbt/plpbt.bin... ok
> > Booting kernel failed: Invalid argument
> >
> > Other "extras" like
2013 Jun 30
1
Plop Boot Manager quit working with 5.10
> On Sat, Jun 29, 2013 at 3:04 PM, Ady <ady-sf at hotmail.com> wrote:
>
> > If with "ancient kernel" you are referring to the memtest(86|86+)
> > issue, I don't see the same *exact* problem / behavior.
>
> My cuent understanding is as follows: HPA is using the label "ancient
> kernel" for any kernel that has a hard-coded load address and
2012 Nov 01
1
Syslinux 4.06 and 5.00-pre9 Binary Sizes
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
2013 Jun 29
0
Plop Boot Manager quit working with 5.10
> I have updated syslinux in Parted Magic's test version to the 5.10 release.
> With 4.06 I booted plop like this:
>
> LINUX /boot/plpbt/plpbt.bin
>
> Now it says /boot/plpbt/plpbt.bin... ok
> Booting kernel failed: Invalid argument
>
> Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc...
> all work with 5.10. Revert to 4.06 and
2013 Jun 29
7
Plop Boot Manager quit working with 5.10
I have updated syslinux in Parted Magic's test version to the 5.10 release.
With 4.06 I booted plop like this:
LINUX /boot/plpbt/plpbt.bin
Now it says /boot/plpbt/plpbt.bin... ok
Booting kernel failed: Invalid argument
Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc...
all work with 5.10. Revert to 4.06 and plop works again.
Is this a problem with syslinux
2010 Jul 02
1
Syslinux 4.01 released
Syslinux 4.01 is a bug fix release for 4.00, but also includes the new
experimental lua interpreter, as well as the ifplop module.
Changes in 4.01:
* ISOLINUX: fix initialization on systems which don't zero
low memory.
* SYSLINUX/EXTLINUX: fix handing of disk read retries in
EDD mode.
* ISOLINUX: change the initialization sequence to avoid
2014 Aug 24
1
Library_modules (list of & wiki write permissions)
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
2010 Sep 05
1
Loading plpbt.bin from Syslinux 4.02 causes reboot
Hi,
I'm trying to setup a flash drive with Syslinux 4.0.2, ifplop.c32, and
plpbt.bin (5.0.10) as shown in the thread here:
http://forum.plop.at/index.php/topic,165.0.html
Unfortunately, the system reboots as soon as I load plpbt.bin from Syslinux.
I don't think it's a problem with plpbt.bin because it works if I boot
Grub4DOS and load it. : (
It will also work if I boot
2015 Mar 16
2
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
On Mon, Mar 16, 2015 at 1:41 PM, Ady via Syslinux <syslinux at zytor.com>
wrote:
> Hmm... AFAIK, efibootmgr currently accepts slash and automatically
> converts it into backslash. So for a current version of efibootmgr, a
> path like:
> /EFI/syslinux/syslinux.efi
> (including the initial slash) should be OK as command-line argument.
>
?Right?. I just used the
2012 Dec 16
1
Upgraded to Syslinux 5.00 - Failed to load ldlinux.c32
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
2014 May 20
0
"EDD Load error" on btrfs, how to debug?
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
2014 Apr 23
0
*.c32 for efi64 and efi32?
>
>
> On 2014/4/23 12:54, Ady wrote:
> > Is this about not liking the need for (sub)directories (depending on
> > firmware)? Or is it about functionality?
> >
> > If I understood correctly the prior email threads, the (real) problem
> > was in trying to maintain the searching for:
> >
> > pxelinux.cfg/01-88-99-aa-bb-cc-dd
> >
2015 Sep 20
1
[syslinux:master] com32/modules: Split build by architecture. Add dir.c32
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
2013 Feb 06
1
Weird ldlinux loading trouble
Hi,
I'm currently on elflink branch with commit 52443dc7dc5a203d053b70e870e6b83986ebb530
I did a make spotless before the following problem.
If I do a make inside com32/ my hdt.c32 is working properly.
If I do a make inside com32/hdt/ my hdt.c32 is not working and fails with
Failed to load ldlinux.c32
To to my tests, I use the following command
qemu-kvm -net nic -net user -boot n -tftp
2015 Dec 12
0
Some patches from mageia
On Sat, Dec 12, 2015 at 8:21 AM, Ady via Syslinux <syslinux at zytor.com> wrote:
>
>> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote:
>> > Gene Cumm wrote:
>> >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux
>> >> <syslinux at zytor.com> wrote:
>> >> > Hi folks,
>> >> >
2012 Nov 04
1
hexdump.c32 for Syslinux 5.00-pre9
Applies to Syslinux 5.00-pre9. Attached, below, and available at:
Repository: git://git.zytor.com/users/sha0/syslinux.git
Branch: hexdump
- Shao Miller
From c9c67dd61ba0b11e46d514601cf0722e1b43017c Mon Sep 17 00:00:00 2001
From: Shao Miller <sha0.miller at gmail.com>
Date: Sun, 4 Nov 2012 00:26:32 -0400
Subject: [PATCH] hexdump.c32: Simple file hex-dumper
Usage: %s
2009 Oct 03
3
PATCH: Build floppy image which contains HDT
This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux.
When you compile Syslinux, this floppy image isn't build automatically.
To build it, runthe following from the extracted Syslinux source:
$ cd ./com32/hdt
$ make hdt.img
As suggested by Pierre-Alexandre Meyer, all extra files required for building
the floppy
2016 Mar 26
2
Follow up to adding EFI boot?
Have been trying some things, but something isn't working at least with using
Virtual Box with EFI option. With it off, the cd boots as normal, and works, but
with EFI on, it has an error that flashes on screen, and then it drops to a shell
prompt. I'm hoping it is just a dumb mistake I am making, and can be
resolved. Perhaps I've named the directories incorrectly, or there is a