similar to: MEMDISK - floppy=1 Outputs: Disk is hard disk, 1440 K, C/H/S = 80/20/18

Hi, It is becoming a bad habit for big OEM vendors to sell computers & servers without floppy drives. Unfortunatly both Windows and Linux (RedHat) need a floppy drive to load storage drivers etc. during installation. This is what I was thinking: Use ISOLINUX and MEMDISK to load a floppy image of a driver disk into memory as a viritual floppy drive "A:"/"/dev/fda" And then

Hi, I am trying to use the Simple Menu system for SYSLINUX/ISOLINUX, but it fails to work. The menu apper, I can select menu entries, but pressing "ENTER" just takes me back to start. It seem like menu.c32 just reloads. Pressing Space does almost the same, exept the selected item is the one on the bottom instead of the top. By pressing ESC and getting back to command line, I am able

Hi, I am trying to load an disk image as Floppy=1, og B: using ISOLINUX. My Config file reads: ------- Begining Of File ------- KERNEL MEMDISK APPEND raw floppy=1 initrd=CERC6.IMG ------- End Of File ------------ --- MEMDISK Output Snip ------ Ramdisk at 0x03b58000, length 0x00168000 command line: initrd=CERC6.IMG raw floppy=1 BOOT_IMAGE=MEMDISK Disk is hard disk, 1440 K, C/H/S =

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our

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, I am having some problem with LOCALBOOT and menu.c32 This is my isolinux.cfg: ------------------------------------------- default menu.c32 timeout 50 prompt 0 ontimeout local menu title "TITLE" label livecd menu default manu label "LiveCD" kernel gentoo append initrd=initrd.igz root=/dev/ram0 init=/linuxrc looptype=squashfs loop=/ livecd.squashfs

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

Hi, This is off topic for this list, but someone on this list may be able to point me in the right direction. For a couple of years I have been using ISOLINUX + MEMDISK and Smart Boot Manager to chainload a CD-ROM boot after loading a floppy image into RAM with MEMDISK. My problem now is that Smart Boot Manager does not support/detect SATA optical drives used in new hardware. Does anyonw

Franga . wrote: > > Now i moved to my next step of trying to get Simple Menu's working. My > problem occurs after selecting a menu option. The image loads and > gives me this output: > > command line: initrd=images/c201.img BOOT_IMAGE=memdisk Disk is > floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, > allocating 2K Old dos memory at 0x9f000 (map

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 have been using pxelinux for quite a while to automagically build linux boxes with great success. Thanks to everyone involved! Now, I am trying to download a floppy image and get that to boot. My conf file looks like: default sir4 label sir4 kernel ia32/memdisk append initrd=ia32/sir4/floppy.img Everything starts off fine. pxelinux loads I see it get the conf file. gets memdisk

I tried to use memdisk 2.06 to boot a floppy image on my notebook which doesn't have a floppy drive. The boot failed, because the bootstrap code tried to reset the floppy drive (int13, ah=00). Memdisk passes reset calls on to the original int13 handler, which returns failure, because there is no floppy drive to reset (#1). Also i noted that some boot records (notably some created by

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

Hi, I was wondering if 1680K floppy support in memdisk was planned, impossible or undesirable :) I noticed RIP is providing a slightly more stuffed 1680K floppy (but no 2880K floppy) and I had hoped memdisk could support this. Kind regards, -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]

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

I just wanted to chime in and mention that I'm running into the problem with getting a "Non-system disk..." error on a system using a USB floppy when the floppy is not attached when I try to boot the system over the network using memdisk to boot a floppy image. Its actually fairly important to be able to do this, as the architecture of the hardware that I'm working with utilizes

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

Hi all, I have pushed out a SYSLINUX 3.32-pre4. This version attempts to work around the "missing floppy drive" issue. If you have systems on which MEMDISK doesn't work without a floppy drive, I would appreciate it if you would test this out. -hpa

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