search for: newmkfloppyimg

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know if the geometry that MEMDISK >guesses is the one that you actually intended. This will be in the >inform...

..., so require enlarged floppy images. (I prefer floppy images over hard drive images because it seems easier to quickly loop mount and modify a floppy image in Linux, than to loop mount a buried partition from within a hard drive image.) To enlarge existing floppy images, I originally learned of newmkfloppyimg.sh from this mailing list, and had followed the procedure http://www.syslinux.org/wiki/index.php/Large_floppy_images to go from a current 1.44MB FreeDOS fdboot or fdoem to a 10MB version thereof, but trying to boot the result with MEMDISK led to an infinite loop of MEMDISK banners. That's...

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD fdoem_8mb.img APPEND floppy pause LABEL infinite_memdisk_loop LINUX syslinux/memdisk INITRD fdoem_9mb.img APPEND floppy pause With the latter...

...d floppy images. (I prefer floppy images over > hard drive images because it seems easier to quickly loop mount and > modify a floppy image in Linux, than to loop mount a buried partition > from within a hard drive image.) To enlarge existing floppy images, I > originally learned of newmkfloppyimg.sh from this mailing list, and had > followed the procedure > http://www.syslinux.org/wiki/index.php/Large_floppy_images > to go from a current 1.44MB FreeDOS fdboot or fdoem to a 10MB version > thereof, but trying to boot the result with MEMDISK led to an infinite > loop of ME...

...nd 460 bytes (as file system config data is also stored in there), so perhaps that's not enough space for auto-detection code? Perhaps there simply have to be 3 different boot sectors, depending on whether you've got FAT12, FAT16, or FAT32? That would explain what's happening here: newmkfloppyimg called mkdosfs, who made a different file system, yet newmkfloppyimg copied over the old file system's boot sector... Does anyone know whether it is possible to have a "universal" boot sector and "universal" kernel? Then if one starts with a base floppy image containing...

On 07/09/2014 01:54 PM, Alexander Perlis wrote: > > Ah, this might explain things although I don't know what is meant by > "intended". First, to clarify, newmkfloppyimg calls mkdosfs 3.0.12, and > grabs H/S from the output and then computes C. For all the sizes I've > tried, newmkfloppyimg always tells me H=64 S=32 and then C is the > approximately the number of MB. And MEMDISK auto-determines those exact > same numbers. But if I manually call mkdo...

> I'm having trouble getting memdisk 6.03pre18 to boot large floppies and > wondering whether I'm doing something incorrectly. > > 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz > 2) gunzip FDOEM.144.gz > 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img > 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img > 5) Use following pxelinux.cfg: > > LABEL works > LINUX syslinux/memdisk > INITRD fdoem_8mb.img > APPEND floppy pause > > LABEL infinite_memdisk_loop > LINUX syslinux/memdisk > IN...

From: Ady, Tue, 8 Jul 2014 > [...] every document related to newmkfloppyimg.sh > specifically recommends adding: > floppy c=$CYLINDERS s=$SECTORS h=$HEADS > to the MEMDISK arguments. Good advice. As it turns out, according to the memdisk output, it is already correctly determining CHS. Explicitly specifying the values doesn't seem to have an effect. >...