search for: fat_entry

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

...hing. The whole point of this text is to evaluate the "real" minimal FAT size value. Whether Syslinux should accept smaller values than the "real" one, that's a matter for additional discussion. Values that we know: _ FAT type: 32 (i.e. Cluster allocation of 28 bits_per_FAT_entry, plus 4 unused bits_per_FAT_entry) _ Generic amount of Cluster limits for FAT32: 65'525 to 268'435'444 clusters Please note that these 2 limits are not 100% accurate for every scenario / implementation / OS, but they are the extreme ones that might be found in any case. This...

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

Hi Ady, On 2016.02.25 02:08, Ady via Syslinux wrote: > There is an "extra" sector, in comparison to... what exactly? Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size had an extra sector compared to minfatsize, when of course I meant the opposite (the Large FAT32 has one less sector than the minfatsize computed by the unpatched code, hence the check