similar to: MEMDISK ISO Drive 0xE0

'nopassany' is missing in the MEMDISK documentation: http://www.zytor.com/pipermail/syslinux-commits/2010-February/000096.html - Gert Hulselmans commit aeb2406ea701d974c85aa7fdd9af7c53106d7e48 Author: Gert Hulselmans <gerth at zytor.com> Date: Sat Mar 6 22:33:09 2010 +0100 Document 'nopassany' in MEMDISK documentation. diff --git a/doc/memdisk.txt b/doc/memdisk.txt

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

Hi Shao Miller, I found another ISO that doesn't work with MEMDISK-ISO. It is the ISO of the PloP bootmanager. It is a ISO which uses floppy emulation. When I boot it with MEMDISK-ISO (run from Syslinux), my PC instantly reboots. When I extract the floppy image from the ISO and boot this file with MEMDISK, it works fine. Grub4dos iso emulation works fine for this iso. When using Grub4dos

A very special thanks to H. Peter for finding the time to [at least partially, if not wholly] scrutinize and merge the El Torito emulation code for MEMDISK! I'd like to ask that those who've previously used the stale MEMDISK-ISO switch to this latest[1] MEMDISK proper and report any failures. Gert, I believe this version addresses the PloP .ISO trouble you reported. Could you

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive). This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD. For more info: http://www.boot-land.net/forums/index.php?showtopic=8457 This 1 line patch fixes the issue (Thanks to

Hi I would like to start a iso from my USB-Pendrive so I got a Hiren BootCD amd PartedMagic iso + GRUB 2 (1.98~20100115-1) on my USB-Pendrive. My problem it take up to 30sec until the ISO is booted my menu entry: linux16 /memdisk iso initrd16 /boot/iso/pmagic.iso Thanks for any hints M. Simon _________________________________________________________________

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

From 43e0635d7d90f65055d1f49d998974041315f4fc Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Fri, 11 Dec 2009 01:26:59 +0000 Subject: [PATCH] memdisk: Fix "might be used uninitialized" warnings The checksum_buf function was providing an incorrect checksum on at least one build. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca>

Cross-posting to the Syslinux mailing-list. Joakim Schicht wrote: > But part of the question is also about "memdisk raw" vs "memdisk iso". "raw" and "iso" are not mutually exclusive. I think that perhaps you meant "HDD versus El Torito emulation." One can do: LABEL ramwin KERNEL memdisk APPEND raw iso INITRD ramwin.iso > Lets say

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

For anyone wanting to boot an .ISO with MEMDISK: http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=ref s/heads/memdisk-iso NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted from such a MEMDISK will not magically find the MEMDISK image in RAM and use it as a CD without a MEMDISK driver. There are currently 0 MEMDISK drivers in the field, but that might change someday.

Improving chain.c32 help message Impact: Error message is more detailed In case of syntax error, the message is far more detailed and provides the same content as the documentation integrated in the source code. You can get this patch from Erwan's git repo: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=3fc3126d0c7df5701680e043c34f200166f24564 Add 'isolinux=' option to

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

[1} Gert Hulselmans wrote: > > ...Thanks. > > I still think chain.c32 should be able to do a reverse partition > lookup, to determine from which partition it was booted. This would be > useful to boot ntldr, setupldr.bin, bootmgr, grldr, ... when you want > to boot it from the same partition as from which SYSLINUX is booted, > without specifying the partition explicitly

The Windows recovery console doesn't work with chain.c32 3.85 or 3.86-pre1. COM32 chain.c32 APPEND cmldr=/cmldr Initially reported by cdob at: http://www.boot-land.net/forums/index.php?showtopic=10487#entry94001 It did work fine with the: "chain.c32: Handle nonlinear logical partitions" patch. The following patch broke the recovery console hack: chain.c32: add option to set hidden

Some additional fields from the EDD-4 spec. draft for the Device Parameter Table have been added into the structure in setup.c and memdisk.inc. These were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM ThinkPads. --- memdisk/memdisk.inc | 11 +++++++++++ memdisk/setup.c | 10 ++++++++++ 2 files changed, 21 insertions(+), 0 deletions(-) diff --git a/memdisk/memdisk.inc

For the boot floppy at http://superkeen.com/peacecorpsfiles/FUZOMA14.IMG using memdisk from syslinux version 3.72 boots correctly, but for memdisk versions newer than 3.72 (I tested 3.73, 3.75, 3.85, and 3.86) all hang at boot with the following message: Loading boot sector... booting FreeDOS kernel - SVN (build 2039 OEM:0xfd [compiled Oct 2 2009]) Kernel compatibility 6.22 - BORLANDC ... XMGR,