OK gang I have done a little testing. I created images of a 1.44MB
3.5 inch floppy disk (an old MaxBlast diskette, presumably bootable)
using RawWrite for Windows 0.7; Floppy Image 1.52; and Floppy Image
Creator 1.41.
RawWriteWin
http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm
FloppyImage 1.52
http://www.321download.com/LastFreeware/page3.html#Floppy Image
Floppy Disk Creator 1.41
http://www.geocities.com/johnno_ann/
RawWriteWin wrote an image that was 1474560 (1440 x 1024), and I was
able to load it into Virtual Floppy Drive (VFD) 2.1, as Drive O:
(arbitrary choice by me). I was able to display a directory of drive
O:, load TXT files into notepad, and run an EXE.
The files created by FloppyImage 1.52 and Floppy Disk Creator 1.41
were slightly larger, and could not be loaded by VFD. Then I ran
FloppyImage again, had it make a compatible IMG file without the
description. I didn't see any way of disabling the description in
Floppy Disk Creator 1.41.
Then I decided to try to compare the two files made by RawWrite and
Floppy Image 1.52. (I used Tiny Hexer, which is anything but Tiny)
The files were different! I think that I changed the contents of the
RawWrite image file by writing to a file contained in the image, when
loaded into VFD. So, if you want to make sure that your archived
floppy is not altered, make sure you use the Write Protect option, or
use the VFD option to load the floppy image into RAM, not directly
from the FILE.
VFD supports WinImage IMZ compressed disk images. Floppy Image
registers IMZ files to itself, but I didn't see a way to write one.
Since I couldn't figure out how to write a compressed disk image, I
didn't test trying to load one into VFD.
I am unclear on whether VFD supports self-executable EXE floppy disk
images; I thought I saw somewhere that it does, but I can't find it
now.
Bottom line, I'd go with RawWriteWin or Floppy Image 1.52, write
compatible uncompressed disk image files without a description added.