DISK2IMG is a simple diskette imaging utility for DOS.  It has the ability to
query the diskette to determine geometry and rename the file's extension
accordingly, has a slow error-tolerant mode and a fast track mode, and displays
ETA and a sector dump display while it is running.  Partial source code is
included if you want to see how disk2img operates.

I currently use DISK2IMG to image DOS-formatted floppies in bulk with the
following options:

disk2img b: image.raw /q /f /e

This determines what kind of disk it is, dumps it as quickly as possible, and
then renames the ".raw" part to something that makes sense (ie. .360, .720,
etc.)

DISK2IMG revision history:

Version 0.9, 20130627:

  + Added traditional command-line usage:  "DISK2IMG X: FILENAME.EXT".
  Old way of /da or /db still works if you don't want to rewrite batch files.

  + Added "/e" for "rename the file extension based on disk image size".
  So if your image is that of a 320K disk, whatever extension you
  originally specified will be changed to .320, etc.  Use this with /q
  so that actual disk geometry is determined.  Filenames without
  extensions remain untouched, so use a dummy extension like .img or
  .raw if you want to use this feature.

  + Full support for MDA/monochrome.

  + Faster screen writing routines (although this modification was to
  bring the code size down, not bring screen writing speed up)

Version 0.8, 20110925:

  + Added dumping by track instead of by sector.  Massive speed-up, but
  no error checking whatsoever.  Only use on disks you trust, like disks
  you just cracked the shrinkwrap on.  Use /F to enable.

  - Fixed all of the goofy errors caused by a braindead command-line
  argument parser.  You can now put options anywhere on the
  command-line and name the file any 8.3 filename you want.

  * Removed snow checking from all screen writes since it slowed down
  sector-by-sector dumping by a few seconds.  Which is just dumb.

Many prior versions were released but their details are lost.  Older
versions than this one are unacceptably buggy so you shouldn't be using
them anyway.
