similar to: Bug-report: Memdisk regression for XMGR DOS memory manager

I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa

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

With the same configuration an ISOLINUX CD which boots a FreeDOS Floppy image via MEMDISK Syslinux-3.73 crashes in VMWare and also on several newer boxes just after the kernel loading with "invalid OPCODE ...". Same CD with Syslinux-3.72 is working fine. Build environment for 3.72 was gcc-4.3.2 for 3.73 gcc-4.3.3 - any idea what can cause the troubles? --

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

I'm new to memdisk and I wanted to have multiple floppy boot images on my USB key, I installed GRUB2 as the boot loader and have memdisk in /syslinux and my images in /image, I first tried booting normal images, memtest86+ works, my linux kernel work and they boot perfectly. Now using memdisk, I tried booting Spinrite which uses FreeDOS, it booted fine with no argument them frozen at querying

Hi, I got "Floating point exception" when running linux/syslinux using syslinux 3.72. How to reproduce: 1. On debian Etch, kernel 2.6.24-etchnhalf.1-686 2. wget http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-3.72.tar.bz2 3. tar xvjf syslinux-3.72.tar.bz2 4. syslinux-3.72/linux/syslinux --help 5. An error message "Floating point exception" was shown. Same problem

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

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

Dear All. I have some problem with combined two data frame. .... I have first data frame .. GPAX THAI MATH SCINCE SOCIAL HEALT ART CAREER LANGUAGE 1227 2.99 3.32 2.50 2.64 3.05 3.60 3.72 3.57 2.62 1704 2.81 2.56 2.48 2.86 3.22 3.19 3.55 3.20 2.51 617 2.18 1.90 1.97 2.06 2.38 3.50 3.54 2.33 1.70 876 2.82 3.14 2.73 2.46 2.71 3.11 3.04 3.24 2.90

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.

I recently downloaded the latest syslinux zip file from kernel.org and didn't know to create a directory for it and unzip it in its own directory. Oie what a mess.

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

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, I need to use syslinux with partedmagic to create a bootable USB version of partedmagic. I installed syslinux using apt-get, the version installed is 3.31-4 (which is quite old).? This version seems to be lacking -d option to specify a directory for syslinux configuration file. What debian repository can the latest version of syslinux be found on ? So I downloaded the latest source 3.72,

Hello, I am new to this list. We are trying to move away from our WDS server with PXElinux mods and are testing using iPXE on a linux box only. We mainly use HP but also have Dells, Panasonic, and Lenovo. On almost a dozen models tested now, everything works great. These were mostly laptops but a Dell Optiplex 360 and 380 booted fine. So far we have just had a problem with the HP 6005 Pro SFF

Changes in 3.73: * Upgrade gPXE to release version 0.9.5. * Fix a number of build errors on various platforms. * Handle systems with E820 "extended attributes" per ACPI 3. Someone "cleverly" decided to change the E820 spec in a backwards-incompatible manner! * MEMDISK: default to "safeint". * Adopt the moniker "The Syslinux Project", standard

Dear all: I am trying to compile syslinux on my machine. It's a Linux From Scratch build, pure 64 x86_64 with uClibc, using kernel 2.6.26.5, gcc 4.3.2 and binutils 2.18.0. The compile fails at the following command: make[1]: Entering directory `/home/lfs/src/pkgs/syslinux/syslinux-3.72/gpxe' make -C src EMBEDDED_IMAGE=../../core/pxelinux.0 bin/undionly.kpxe make[2]: Entering directory

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