> From what you've said, I'm guessing that its actually a Windows > 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. yes that's it. > That all said, the idea of writing a floppy image is the key problem. actually tht's the key problem i didn't think about. > 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. of course! > 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. > probably. > For that it would need to point to the actually floppy device under > /dev, such as /dev/fd0 or /dev/floppy. > yes i set in wincfg a: pointing to the floppy device. so i could access to the floppy device directly by a: through wine. but unfortunately that doesn't work. the error message returned is different. it says "couldn't write to a:" -- Darragh
