search for: fdstd

...indeed, are the other two. What am I doing wrong? My minimalist configuration file reads: kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' device_model = ''/usr/lib64/xen/bin/qemu-dm'' memory = 256 name = "floppy" fda="/scratch/VM/FDSTD.144" sdl=1 boot=''a'' and "xm info | grep xen" release : 2.6.16.33-xen xen_major : 3 xen_minor : 0 xen_extra : .4-1 xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesi...

...SO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as expected. To create my dos image, I did use Murali script and pick the freedos floppy image from http://www.fdos.org/bootdisks/autogen/FDSTD.144.gz I modify cwhosthe script, put FDSTD.144 as the OLDIMAGE I set NEWIMAGE to dexter1.img I set the SIZEMB to 10 The script return the following information Your floppy image is in dexter1.img. When using it in iso/pxelinux, dont forget to add "floppy c=10 s=32 h=64" to the argument...

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

...ains many DOS images, and I use versamenu to select one > of them. If my DOS image is smaller than 8megs, everything is working > fine as expected. > > To create my dos image, I did use Murali > script and pick the freedos floppy image from > http://www.fdos.org/bootdisks/autogen/FDSTD.144.gz > > I modify cwhosthe script, put FDSTD.144 as the OLDIMAGE > I set NEWIMAGE to dexter1.img > I set the SIZEMB to 10 > > The script return the following information > Your floppy image is in dexter1.img. When using it in iso/pxelinux, dont forget to add > "floppy...