similar to: Accessing Memdisk from Protected Mode

Hello, I was browsing the code for memdisk (I want to adjust it to my hardware) and noticed a couple of things that I am struggling to understand. I would appreciate if someone could clarify the following mysteries to me: 1) _binary_memdisk_bin_start[], _binary_memdisk_bin_end[] and _binary_memdisk_bin_size[]; These variables are declared (as extern const chat in 'setup.c')

Greetings, As a Google Summer of Code student for the SYSLINUX project, I had the chance to learn many interesting things from hpa regarding the internals of SYSLINUX. So besides my main task of implementing ELF modules loading & linking, I decided to put down in the wiki all the information I found concerning SYSLINUX development. In this regard, I have created a special category on the

> No. Big real mode is not real mode, and in particular > MEMDISK doesn't have the control over what mode transitions > the world outside MEMDISK performs. i understand. if only dos will be used (without himem, emm386 or something like that) that the cpu will be leaved in real mode, is that correct? and e.g. bios update would work... mfg johannes

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 I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

Hi guys, This may be a stupid question... I was trying to get a machine to boot with PXE. Everything supportive is setup, the DNS/DHCP works fine, TFTP is also handing over pxelinux.0 and config files correctly. The problem happens at: label xxx kernel memdisk initrd blabla My machine would report "cannot find kernel: memdisk". When doing a tcpdump, I found the machine actually

I've been trying to use memdisk with grub2 to boot some iso images -( I've done this without any problem with pxe ) There is a memdisk.mod in /boot/grub/ and I've seen some material talking about this, but no example of a menu. After trying countless permutations - Right now I have : menuentry "Memtest-Plus 4.2" { echo `hello` insmod lvm

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

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.

Hello ALL, I've got a diskless server working (under Gentoo), booting on it works. (a linux session start with no problem.) My Big problem, is to get Memdisk to boot with PXE. In fact memdisk is loaded, but it cannot find the img file. I've tried a lot of thing, but nothing works... tftp use : /diskless the config file for PXE in then in : /diskless/pxelinux.cfg/ the root for the

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

Hi, I looked at the web http://clic.mandrakesoft.com/documentation/pxe/ch06.html, and create a floppy boot image by : dd if=/dev/fd0 of=boot.img. I copied the boot.img to /tftpboot, and my /tftpboot/pxelinux.cfg/default is : default freedos display boot.msg label freedos KERNEL memdisk APPEND initrd=/boot.img When I boot up my client, it shows : could not find kernel image: memdisk What

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>

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

Memdisk 2.08 cannot boot an XP boot floppy image (XP appears to use WinME boot files for its bootable floppy). For example: http://members.iinet.net.au/~bdriver/bootdisk/download.htm This disk will not boot with Memdisk (Memdisk starts to load the image and then hangs). I'm using Bart's tools to build a boot CD: http://www.nu2.nu/corpmodboot/ Which uses Isolinux and Memdisk.

has anyone got memdisk to work directly? i mean such as: add_item("W98 Boot","Windows 98 Boot",OPT_RUN, "memdisk initrd=98se.ima",0); I have tried various methods, and I get the same results: Loading memdisk....Ready. MEMDISK 3.11 2005-09-02 Copyright 2001-2005 H. Peter Anvin MEMDISK: No ramdisk image specified! I know I can setup (in my case)

We are working on a prototype for an installation system, and it would be very useful if we could load two memdisk images, having one pretend to be normal A: drive, and another as B: drive. I have read through the docs as well as done some google searches, and haven't seen such a thing described. We have one person who has asm programming experience, and we were wondering if we could get

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,

Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem

Hi, I saw the Nov. 2006 message on Memdisk having a problem with ThinkPads. I also saw the comment in the memdisk code enabling and disabling A20. I've got a ThinkPad x61t that memdisk is not loading disk images on. The symptom is that it gets as far as saying "Loading boot sector... booting..." Then image partially runs - FreeDOS prints out its kernel message and it's