similar to: MEMDISK and Doc Memory

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

> > Message: 5 > Date: Sat, 28 Apr 2007 11:37:51 -0700 > From: "J.H." <warthog19 at eaglescrag.net> > Subject: Re: [syslinux] USB stick meets ISO system > To: Geert Stappers <stappers at stappers.nl> > Cc: syslinux at zytor.com > Message-ID: <1177785471.25140.29.camel at localhost.localdomain> > Content-Type: text/plain > > On Sat,

Has anyone had a problem with afud408 (Award flash program) freezing the system when ran from memdisk? The freeze occurs when just running afud408 (not attempting to update bios, although it freezes then as well.) I was using pxelinux/memdisk 3.36, I upgrade to 3.51, and also fell back to 2.11 all have the same issue. I have tried all the switches for memdisk that I saw posted on the memdisk

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

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

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,

H. Peter Anvin, The following problem came to my attention with memdisk. I cannot claim the credit, but wanted to be sure the information made it back into the program for the benefit of all users... In file memdisk.asm, in respect of the operation of the raw and bigraw options, the order of pop instructions does not correspond to the order registers are pushed;

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

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

hpa, Seeing your post about 3.71, I wanted to get a message out even though I don't have the stats right now. I am having a problem with memdisk with a lot of shuttle computers, but also affects a variety of other hardware (low though, 5%? less?). The image that I can most reliably test against is the Hitachi Drive fitness Test.

Hi, I'm trying to boot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000

Hi I'm new to this list and hope this is the right way to contact you. I'm trying to create a boot disk using generic pxe stuff (not got there yet but still reading the manuals). Problem: Documentaion in memdisk.doc [memdisk.doc,v 1.18 2005/08/23 21:11:36 hpa Exp] points to http://www.intel.com/support/network/adapter/1000/software.htm this should be changed to

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

> 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

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

Hi list! I'm trying to make a hd image with can boot from memdisk over PXE. So this is what i did: - Created a new VM [VMware] -Installed DOS on a 100MB HD from a floppy -bootet Linux over PXE [DamnSmallLinux] -in terminal: dd if=/dev/hda of=dos.img This image [dos.img] isn't working! Memdisk loads the Image and boots the HD! The error message is something like this: I/O Device

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

Hi guys, I'm trying boot a floppy basead netbootdisk solution ( http://www.netbootdisk.com/) using grub and memdisk. This is a Floppy 1.44 Mb with TCP/IP and Ethernet Drivers for DOS. This image doesn't has a command.com. This file is unzipped on boot. Using a floppy, the machine boots, but when I trying to use a image from floppy which memdisk, the boots hangs. The image can found at

> It would be possible -- in fact, fairly easy -- to hack the > "raw" mode of MEMDISK to drop the system into big real mode > after finishing instead of real mode; such a "bigraw" mode > might solve the problem with this particular program. > > The PC hardware... gotta love it. ok, i don't understand a lot of this; but sounds nice ;) could you please

Hello all. I am pretty new to this list but I have looked through the archives and did not see any reference to this problem. I have an MS-DOS boot floppy image that I am trying to load using MEMDISK. The disk is simply a boot floppy made using XPSP2. I have tried it on 4 different machines, all Dells. PowerEdge 2650 Server, Latitude D610 Notebook, Optiplex GX280 Desktop and Optiplex GX520