similar to: [PATCH] doc: document mBFT and "safe hook"

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]

I tested the memdisk-acpi branch with following results: - Bochs The BIOS provides a RSDT. Available tables are RSDT, FACP, DSDT, FACS, APIC, SSDT. memdisk-acpi is able to hook the SSDT. - VMware The BIOS provides a RSDT and XSDT. Available tables are RSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*) and XSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*). Tables marked with an asterisk (*) are

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. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

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

Let's try that patch again... Here's a better one, instead. I tested with: qemu -kernel memdisk -initrd memdsk.hdd -append pause -hda one.hdd -hdb two.hdd -hdc three.hdd -hdd four.hdd On each HDD image, I had a file (and volume label) to identify the HDD with the DOS 'dir' command. The expected behaviour was met; I wound up with DOS drive letters: C: memdsk.hdd D: one.hdd E:

I have added instructions to memdisk.doc for how to disable MEMDISK. However, it's unlikely that this will work if you're running under DOS, since DOS will be very unhappy about drives changing underneath it. Anyway, until the next (pre)release comes out, here are the instructions: --- memdisk.doc 27 Apr 2004 06:49:36 -0000 1.10 +++ memdisk.doc 6 Jul 2004 01:29:03 -0000 @@ -122,5

Sensei H. Peter Anvin, I have successfully modified/enhanced memdisk so that one can chainload a local operating system after running diskless FreeDOS. I would like your advice regarding the appropriate interface for invoking this functionality. In addition, I would like to know what steps to take so that you feel comfortable considering including this in the standard syslinux distribution.

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

hi everyone. i have a small tftp/pxe server i use to install different OS's without having to burn countless cd's (not all the machines i work on support usb boot). until recently, these were mostly linux/bsd-based systems (plus freedos). recently i've been trying to deploy a network-based windows installation, by booting windows pe (3.1, the one based on win7) with memdisk and from

Hello, I have a compaq machine with compaq smart array raid and with 3com 905C 10/100 TXM network card (supporting PXE). I have setup an dhcp and tftp server for serving pxelinux.0 , memdisk and my dos images along with linux images (vmlinuz, initrd). Booting with vmlinuz and initrd is working fine on any machine but when I'm booting with memdisk along with dos image the result is: 1706:

Hello, I'd be very grateful if someone can help me with the process of creating bootable floppy images to be used with isolinux/memdisk. I usually do the following: label image kernel memdisk append initrd=/bootdisk/image.img floppy (lines in isolinux.cfg file) Sometimes I pass memdisk the c/h/s parameters, depending on the image size. I have learned from this mailing list how to

Syslinux 3.84 has been released. This is a mixed minor new features/minor bug fixes release. Changes in 3.84: * SYSLINUX: make the DOS installer work for MS-DOS 7.x/8.x (Win9x/ME) again. * HDT: updated to version 0.3.6 (numerous changes.) * mboot.c32: now supports video mode setting if requested by the image. * MEMDISK: Fix floppy images of

I'm running into some issues with regard to isolinux and memdisk, and am not sure where to ask/look in the best way possible. These are DOS-related issues. So here goes: * Can MEMDISK map a imagefile (compressed? harddisk?) to more than (and/or beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB available to the user so might as well use the other 4/12GB for MEMDISK. Or max

Syslinux 3.86 is out; it is a bug fix release. Syslinux 4.00, starting with Syslinux 4.00-pre38, is now officially in beta test. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.86: * chain.c32: fix chainloading the MBR of a hard disk (broken in 3.85). * mboot.c32: report the boot loader name in the information structure. *

Hi all, I am new to Syslinux and Memdisk. I setup a PXE boot server that services an image file via memdisk. This works very well. However, I am trying to figure out as to where memdisk the image puts in memory? On the wiki page it says: "MEMDISK simulates a disk by claiming a chunk of high memory for the disk and a (very small - 2K typical) chunk of low (DOS) memory for the driver itself,

syslinux-1.75 We have many legacy boot disks (setup for nics, scsi adapters, ...) and I'm trying to put all of them on 1 CD which would ask the user "which floppy image you want to boot?" I'm using isolinux. I've a problem with the winxp boot floppy made as per: http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q305595 (format a: and then cp ntldr

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

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>