similar to: Problem with memdisk and DOS on USB

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

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.

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;

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

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

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 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, I''ve some btrfs fs which are encrypted with loopaes. I decrypt them in a script during bootup. Now I want to determine if the decrypted fs is a btrfs fs. If not I missspelled the password and I can handle that error in my script. Thanks for any help! Felix -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message 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

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

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

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

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

> 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

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

Hi, In the man page for vector(): length: A non-negative integer specifying the desired length. Double values will be coerced to integer: supplying an argument of length other than one is an error. Since long vectors are supported, it doesn't seem to be true anymore that "double values will be coerced to integer": > bigraw <-

It seems that the BTRFS_IOC_CLONE ioctl fails when trying to do a cross-subvolume clone of a file. Chris Mason suggested in the past ([1]) that this should be possible. Am I missing something? [1] http://kerneltrap.org/mailarchive/linux-btrfs/2010/6/10/6884911 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

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

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