similar to: [PATCH]: ifplop.c32: COM32 module for detection of PLoP USB boot-loader

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

> 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

> 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

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

From: Mark Jarvis <mark.jarvis at pvmail.maricopa.edu> > HUH? FAT32 problem??? No, it's a geometry issue on legacy BIOS/DOS Disk Labels (Partition Table Format) aka "Basic Disc" in NT5+ (2000+) when both NT and Linux share the disk for booting. Microsoft never standardized how geometry should be handled after NT4.0 Service Pack 4 (SP4) other than using legacy LBA32 --

> 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

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

Hello Syslinux Team, Syslinux 5.xx / 6.xx are currently showing some backward compatibility issues. Between the ML and the IRC, there have been some comments / reports regarding memtest, older kernels, plop boot manager, ifplop.c32, hdt.c32... In some cases, the problems were seen when booting with some specific variant of Syslinux 5.xx / 6.xx (say, ISOLINUX only, or PXELINUX only); or with

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

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 IPXE, HDT, memtest86+, chntpw, Super Grub Disk,

On Fri, 28 Jun, at 07:32:30PM, 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 IPXE, HDT, memtest86+, chntpw, Super Grub

On Mon, 01 Jul, at 11:49:45AM, Patrick Verner wrote: > You're right, I tried pre4 last. My brain hasn't fully recovered from the > weekend yet... plop works with pre5 just like it did with 4.06. I guess > this is fixed in pre5 then. Thanks! Excellent, thanks for testing. -- Matt Fleming, Intel Open Source Technology Center

Hello, I have a problem with a comboot 16 bits program for syslinux, I use the API openFile, ReadFile and CloseFile for read my own config file. It's ok. I use the int13h to write a floppy disk (syslinux runs on a USB stick), after the first call to int13h, all the call to openFile return an error. Do you know what's the problem? Is it possible to use int13h when we use syslinux API?

git://git.zytor.com/users/genec/syslinux.git Branch memdiskdbg-for-sha0 This starts with adding another check in two of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe

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

The following changes since commit 4fc3fd1e14f4c1b9208ef262e5b6aef853e9fce4: graphics: make use of syslinux_force_text_mode() (2012-05-19 02:05:38 -0300) are available in the git repository at: git://github.com/aericson/syslinux.git elflink for you to fetch changes up to 2779b713bdd8644ee2b52962ece6daa209b4ba6b: com32: remove duplicate modules (2012-05-22 20:59:51 -0300)

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our

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 that linux.c32 and all 5.xx+

On 06/30/2013 09:45 AM, Gene Cumm wrote: > > My cuent understanding is as follows: HPA is using the label "ancient > kernel" for any kernel that has a hard-coded load address and that > linux.c32 and all 5.xx+ (they're actually the same code) are less > likely to be able to succeed in loading these kernels due to how the > core/linux.c32 responds to the memory map

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command] [-pxe- command] [-sys- command] Examples: whichsys.c32 -iso-