Displaying 6 results from an estimated 6 matches for "fdoem".
Did you mean:
does
2010 Mar 24
1
mkisofs help?
...w.linuxinsight.com/how-to-flash-motherboard-bios-from-linux-no-dos-windows-no-floppy-drive.html
to make a bootable CD to flash my bios
I get to mkisofs step, but what I get is not what I think I want.
I dont understand if I unmount /tmp/floppy how the Mkisofs command of: mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144 how I get everything in /tmp/floppy
Here is what I did:
wget http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz
gunzip FDOEM.144.gz
mkdir /tmp/floppy
mount -t vfat -o loop FDOEM.144 /tmp/floppy
Copied the flash files to /tmp/floppy
umount /tmp/floppy
mkisofs -o bootcd.iso -b F...
2014 Jul 08
3
Possible memdisk issue
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 fd...
2014 Jul 08
0
Possible memdisk issue
> 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...
2014 Jul 15
4
Possible memdisk issue
...ount 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 where the discussion started, and turns
out I titled the thread poorly: it really has nothing to do with MEMDISK!
1) newmkfloppyimg.sh calls mkdosfs to create an enlarged...
2014 Jul 16
0
Possible memdisk issue
...> 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 where the discussion started, and turns
> out I titled the thread poorly: it really has nothing to do with MEMDISK!
>
> 1) newmkfloppyimg.sh calls mkdo...
2014 Jul 09
5
Possible memdisk issue
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