Quote:
There are some differences between fdubcd and the others. For example, when talking about "*.img" images of 1440 or 2880KiB, in most cases they will be assumed to be _floppy_ images - just as memdisk does. But the new fdubcd image is "much" bigger, so the assumption (by some users and/or some programs) might probably be that it is a HDD image - just as the documentation for memdisk states it (although I don't know if the actual behavior of memdisk acts as the documentation describes it).
On the contrary, I think using a different extension will make the user think it is a non-floppy image. Using the same extension will make for consistency.Quote:
So, if the user follows the instructions, why is it that there is _one_ report stating that it can't work from fdubcd? I mean, isn't it possible that the user that reported a problem with this program is just not following those instructions?
You are right! I tested it using the "/ignorexmm" argument and it works fine. Thanks for pointing this out. Will re-add it to FDUBCD in next release.