search for: floppi

Create a virtual FAT-formatted floppy disk from a directory of files. For example: nbdkit floppy /path/to/directory The implementation of this is quite different from nbdkit-iso-plugin since we cannot use an external program. Instead this plugin synthesizes the MBR partition and FAT32 structures that are required. To do: Implement bootable virtual floppy using syslinux. This is not

Add nbdkit-floppy-plugin, “inspired” by qemu's VVFAT driver, but without the ability to handle writes. The implementation is pretty complete, supporting FAT32, LFNs, volume labels, timestamps, etc, and it passes both ‘make check’ and ‘make check-valgrind’. Usage is simple; to serve the current directory: $ nbdkit floppy . Then using guestfish (or any NBD client): $ guestfish --ro

These plugins have in common that they store either a list of allocated strings or a list of constant strings. Define either string_vector or const_string_vector as appropriate and use it to store these lists. --- plugins/iso/Makefile.am | 1 + plugins/split/Makefile.am | 1 + plugins/floppy/virtual-floppy.h | 7 +++-- plugins/floppy/directory-lfn.c | 35 +++++++++-------------

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

On 10/28/18 5:13 AM, Richard W.M. Jones wrote: > Create a virtual FAT-formatted floppy disk from a directory of files. > > For example: > > nbdkit floppy /path/to/directory > > The implementation of this is quite different from nbdkit-iso-plugin > since we cannot use an external program. Instead this plugin > synthesizes the MBR partition and FAT32 structures that

Tested floppy boot on two machines (one PII 350, one 486DX4) Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux kernel from floppy on the 2 machines. Tested with 3 different disquettes that were know to work, boot is reached after this very long time. Noise from floppy head make think floppy wait approximatly one minute between each read. No problem with pxe boot with

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS floppies with the dd command or anyt...

On bootup, it seems CentOS automatically mounts the floppy drive to /media/floppy. Is there a way to stop this from happening, short of removing the floppy drive from the system (as I don't use it)? Thanks, Ash Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL:

I found that if I do not have a local floppy installed and enabled on my client, I will get the error 'Non-system disk' when I try to boot DOS floppy images. NT or Syslinux floppy images boot fine. If I enable the floppy in the BIOS, then it boots the DOS floppies just fine. Is this normal? Is there a workaround? There are MS-DOS images, so perhaps this is an MS-DOS limitation. -- Andre Dalle [andre at dalle.ca]

Hello A couple of time a was in situation that I needed memdisk to emulate TWO floppies for me. Let's give an example: Kaspersky Antivirus makes two rescue floppyes, one with ext2 filesystem, one with FAT12 filesystem. Ext2 floppy is bootable and loads fine with memdisk and it search for 2nd floppy to be inserted in floppy drive. This two floppies don't have chance to be com...

Hi - daft one for Friday morning coffee break: I have been trying to mount floppies on a couple of CentOS5 servers - the usual "mount /dev/fd0 /mnt/floppy" (yes, /mnt/floppy exists!). On both servers, the mount command just doesn't come back and I have to hit CTRL-C. I have tried different media and also changed the floppy drive on one server, /dev/fd0 is seen as...

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 =

All: I have recently discovered pxeLinux/memdisk and have been using them without alot of pain in a somewhat unconventional setup.. Win2k DHCP server and tftpd32 on WinXP. Don't throw rocks at me - you use what you've got. Anyways, thanks to HPA for a great tool. I am running into an odd little problem now for which I was wondering if there might be some remedy. On a particular

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy

syslinux 3.11 (from debian's 3.11-3 package) does it job. The machine boots as expected with an 1.44 floppy. Yet the floppy driver's led doesn't turn off. 1) Is this a syslinux issue? 2) Can I safely remove the boot floppy (media) without dameging it? From memory: $ cat syslinux.cfg say linux 2.6.14 (probably with debian modifications) default linux append root=/dev/nfs

The previous code treated floppy disks and CD-ROMs as the same kind of thing, resulting in malformed libvirt XML. You would see the following error when importing a guest into libvirt: error: Failed to define domain from /tmp/v2vlibvirt063486.xml error: internal error: Invalid floppy device name: hdb because we incorrectly generated this bogus libvirt XML fragment: <disk

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

Hello, I am using the pxelinux.0 and memdisk files from distribution syslinux-3.36. I am no longer able to access the real floppy disk drive B: instead I just get a mirrored copy of the emulated floppy disk A: The default config file is as follows label 1 kernel memdisk append initrd=kd202.img I was previously using the sysliunx-3.20 distribution which gave me access to the real floppy