similar to: interesting problem...

hi, i've seen that there already have been some messages to bios flash via memdisk image. i also had some problem with that. the programmer of "UNIFLASH" told me, that memdisk is using protected mode and this should be a problem, because uniflash only works with real mode. i've found i amiflash that works with protected mode and with this i can flash the bios. [with memdisk]

hi, i've tested with 2 version of awdflash and uniflash: here the results: it only worked with freedos, not with win98 dos; with win98 the images were not bootable; but that does not matter; freedos is ok. awdflash 8.27.45: flash ok awdflash 8.27.41 (uses protected mode): flash ok uniflash 1.40: when starting flashing the program freeze. awdflash 8.27.45 never worked before so i think this

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

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;

Hi, bit of a newbie if I'm honest but was wondering if issue mentioned here: http://syslinux.zytor.com/archives/2006-October/007586.html was ever fixed? basically I have the same issue with the same machine. I have 4 different types of PC's here that i'm trying to boot by USB stick. It works fine on 3 of them, but on the 4th, A HP/Compaq dx2200 MT, memdisk will not boot the .ima

> 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

Dell has an ISO image (Dell version 5061A0, A5061) available here http://support.euro.dell.com/support/downloads/download.aspx?releaseid=R102625&fileid=132637 which contains an ISO with an hard disk image and no-emulation boot. I've estracted the hard disk image (size=2048000) and I'd like to boot it with isolinux. I tried kernel memdisk append initrd=dell5061.img The Dell/Dos os

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,

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

> 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

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

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 all, We are hoping to update our BIOSes remotely with pxelinux and memdisk (it is for a 600 node Beowulf cluster with no floppy access). The DOS floppy loads and starts, however somehow the flash utility 'phlash.exe' or 'phlash16.exe' are both unable to load the provided rom image and just stop doing nothing. It looks like it can't access the rom image somehow, which is

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

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

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

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

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

as everyone deserves to know when things go wrong: i'm trying to flash the bios on my IBM T20 laptop. i've got a floppy image, and am attempting to use memdisk with grub to boot it via the following: title Flash T20 Bios root (hd0,0) kernel /memdisk root=/dev/md0 initrd /T20_flash_floppy.img that much WORKS. the interesting part is that the system becomes unresponsive RIGHT AFTER