executable that gets downloaded and when run it will write an image to
the floppy disk. You then reboot from that disk and run the tool from
the FreeDOS environment that comes up.
That all said, the idea of writing a floppy image is the key problem.
Having a: symlinked to /media/floppy or wherever else your floppy is
mounted doesn't allow for a raw disk image to be written to the floppy.
Which is exactly what I suspect this program is attempting to do. It
probably has a binary blob that it expects to be able to write directly
to the floppy.
For that it would need to point to the actually floppy device under
/dev, such as /dev/fd0 or /dev/floppy.
The problem is that writing to the mount point, only writes on to the
filesystem on the floppy, where as the most likely senario here is
that it has a floppy image containing a filesystem and files with which
it wants to overwrite the current filesystem and contents on the floppy.
--
Darragh
"Nothing is foolproof to a sufficiently talented fool."
