similar to: KRNLINUX? CPIOLINUX?

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

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

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

Hallo, I'm just trying to boot a Clonezilla *.iso (live-20100521-lucid) via PXE; Label clonezilla kernel memdisk append iso raw initrd iso/clonezilla.iso The first step is ok - I see the boot menu of the *.iso. When I choose "Clonezilla live" the system fails with Isolinux: Disk error 02, AX = 4224, drive E0 when I choose "freedos" it fails with

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]

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>

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:

> Which one, just out of curiosity? They are Sony notbooks > What is the "preload install script"? Is the DVD El-Torito-bootable and > it runs something which reports that the system must be EFI _before_ it > boots any OS? > If you are using PXE, then that's along the same lines as BIOS. If they > want EFI, that's a stronger requirement than CD/DVD. If

Hi, Miller, Shao: > I am enjoying this discussion Me not. I feel quite misunderstood. hpa: > Actually, I would prefer if you removed this in its current form. Ok. Will do. If any viable solution emerges, please let me know. Have a nice day :) Thomas

Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at console-pimps.org>: > Which installer? I would hazard a guess that the installer is also bios > specific and is going to need to be tailored for EFI boot anyway. > > -- > Matt Fleming, Intel Open Source Technology Center It's a little be complex. It's a DVD based installer where I try to change this to be

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

> Hi, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

The previous MEMDISK El Torito code merge did not actually work without this. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca> --- memdisk/setup.c | 17 +++++++++-------- 1 files changed, 9 insertions(+), 8 deletions(-) diff --git a/memdisk/setup.c b/memdisk/setup.c index 40f3f8c..5a45f39 100644 --- a/memdisk/setup.c +++ b/memdisk/setup.c @@ -338,6 +338,7 @@ struct geometry

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

I have a USB flash drive that I'd like to image, and then load that image via pxelinux and memdisk. The flash drive was formatted under Windows 98 SE as FAT, and boots just fine on its own. The PXE boot process gets as far as loading the image via memdisk, but then when the boot process switches over to the RAM disk, it fails: [...PXE diagnostic information...] Loading boot

Hi, i'm possibly not the best source of general SYSLINUX knowledge, as my interest in it is only with my xorriso hat on. (As you can see in the SYSLINUX wiki, xorriso can do the isohybridization without the need for the isohybrid program.) Fulalas Caos wrote: > I tried this: > mkisofs -o "$ISONAME" -v -l -J -joliet-long -R -D -A "$CDLABEL" \ > -V

> Hi, > > Pascal wrote: > > mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ > > my iso image is ok with qemu on bios and uefi, > > Astounding. As CD-ROM this is not supposed to work with UEFI unless the > firmware emulates BIOS. What particular UEFI firmware did you use ? > > > and with qemu as hard disk on uefi but not on

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.