similar to: MEMDISK without floppy drive

I apologize for the long delay in testing this. I can only reproduce the problem on fancy new laptops, and those do not stay in my hands for very long. As you may recall, certain floppyless laptops have a BIOS bug which prevented them from working with MEMDISK. Around a month ago, Robert Wruck contributed workaround patches, and hpa included a modified version of them in 2.07-pre1. He asked

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

Hi, just tried memdisk - it works, even with token-ring network cards! I've some problems with dos 6.22 on one machine, though. This one doesn't have a floppy controller (e.g. linux reports that it didn't find any controller). The Dos 6.22 boot disk is loaded, then the boot sector is started and tells me that it can't load the system (German message: 'Kein System oder

hi there. I'm trying to boot several OSes floppy images from a cdrom via memdisk. Actually, Linux and FreeBSD boots fine, but, while i'm using the same method, I couldn't get into booting netbsd nor openbsd. The boot process seems to hang up, in those two cases, when the second stage native bootloader try to load the kernel (i'm not absolutely sure about this). The native first

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

memdisk fails to boot HD image, if the system does not have an HD. Has any seen this? Is there a solution? memdisk output: Disk is hard disk, 9216 K, C/H/S = 9/64/32 Total size needed = 2063 bytes, allocating 3K Old dos memory at 0x9dc00 (map says 0x9dc00), loading at 0x9d000 INT 13 08: Failure, assuming this is the only driveold: int13 = f000799a int15 = f000f859 new: int13 = 9d000008 int15

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

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 am trying to acheve pxe booting of a image of barts boot disk (www.nu2.nu). I have managed to get LTSP booting via pxelinux, so I know my dhcp/tftp servers are ok. However when I try to boot memdisk with either a stock suselinux boot image file (taken from SuSE 9.1) or my dos disk (created by dd if=/dev/fd0 of=/imagefile) I get output like MEMDISK 2.08 command line : BOOT_IMAGE=memdisk

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

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

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

Folks: I've used etherboot to create a zrom that successfully brings a image of a bootable floppy into high memory. What I'd like to do is glue memdisk in so that it can hook int13 and serve the transferred image for booting when etherboot hands control back to the BIOS. The trick, and this is where I'd appreciate "gotchas", pointers or "this is an approach I

hi: i try to make some images for pxelinux+memdisk. the version i try is 2.0.6 and 2.0.7pre5 for 2.88M floppy image, first i make a 1.44M boot floopy, then use "winimage" to load the disk and transfer it to 2.88M format, then save the image. it seems a easy way to make a 2.88M boot image. for harddisk image, i use vmware to build a virtual machine with 20M harddisk, make it boot

I have set up a RHEL 5.7 PXE server and trying to get a WinPE ISO to work. Currently PXE seems to handle the image properly but the process stops after Loading boot sector... booting... Full list of what is going on. Ramdisk at 0x72b9c00, length 0x0a680000 command line: iso initrd=../images/windows/winpe_x86.iso BOOT_IMAGE=../memdisk Disk is hard disk 0, 170496 K C/H/S = 340992/1/1 Total size

Hi We have a couple of FSC Computers here which seem to have a very strange bios. I am trying to boot a MS-DOS disk to flash an Scsi Raid controller. Since the computer doesn't have a floppy anymore I tried syslinux from an usb stick. The menu loads fine but I cannot boot disc images with memdisk on this computer. It works fine on others, of course. But now comes the weird part, if I use the

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

Sorry for the cross-post, but I do not know whether this is a bug in Free FDISK, memdisk, or neither. This problem is with Free FDISK 1.2.1 and memdisk 2.04. I am using PXELINUX+memdisk to boot to a virtual hard drive containing MS-DOS 6.22. This works fine; DOS boots and the virtual drive appears as C:. Now I want to use Free FDISK to partition the *physical* drive. But when I run any of the