similar to: Updating BIOS with pxe syslinux memdisk & DOS problems

Hello all, We are trying to make our own NFSroot via PXELINUX without the e1000 ethernet module compiled into the kernel. All works fine, we have a ramdisk that can setup networking from information provided by $ip, however I would like to download the specific e1000.o via tftp before inserting it into to the kernel. Since ramdisks are static I rather not have the situation where we have to

I have just pushed out SYSLINUX 3.10-pre21; this fixes ISOLINUX, and adds a fix for MEMDISK -- it so happens that running ISOLINUX under Bochs triggers a bug with similar behaviour as I've seen reported on here, so I'm *hoping* this might fix the "doesn't work without harddisk" problem and perhaps the IBM/USB problem some people have been reporting. Again, I really want

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: ...

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.

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 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

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

HI: i just trying memdisk that comes with syslinux 3.35. i try to load a dos image, which contains ghost verison 8.3 and ghost version 11. both version of ghost hangs when start-up. memdisk that comes with 3.40 pre is ok. and many earlier versions is ok too. i try some parameter like "safeint","raw". but none work. i use memdisk with pxelinux, below is part of my

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,

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

Hello, I would like to access Memdisk (as a RAM disk) from my application in pure protected mode. "Pure" means that I don't' want to have any switches to real mode even if these switches are automatically handled by Memdisk interrupt stubs. The reason is that my application is running on top of Virtual Machine Monitor (VMM). This virtualization layer is quite simple and

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

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

Hi Guys, I'm currently using pxelinux 4.03 and memdisk to boot a DOS based floppy we use this software for training purposes to run a basic hardware check. It does not seem to like systems which have more than 1GB of RAM, which is some of the machines our company are now starting to see. Is there a way I can ask memdisk or PXE linux to use only xxx MB of RAM, e.g. 256MB...?

Hi, I am currently working with Memdisk. I setup a floppy disk that boots DOS and performs a VLM login into a NetWare Server.

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.

Hi all, I think I have asked about this before but I do not know whats happening. I have problems booting syslinux in my GPT disk which I have asked in a separate topic "Boot Error GPT partition" . I loaded https://github.com/skodabenz/Tianocore_DUET_memdisk_compiled (append options - floppy ro nopass) . Using syslinux when it was booting properly, did not lead to loss of RAM.

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

Hello list, I had to boot a Dell Diagnostic Disk today, and tried doing this via memdisk - which was when I noticed memdisk isn't working for me at all, neither from pxelinux nor syslinux. After trying around with 'raw', 'bigraw' and the like I noticed it doesn't even do anything when just using: LABEL diag KERNEL memdisk .. when I try that: boot: diag nothing

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