ZCOPY32 (C)Copyright 1997 William H. Decorie

This program will do an exact cluster for cluster copy of one logical drive
to another.  This ensures that long filename information is not only copied,
but also maintains the correct 8.3 to LFN relationship.

What I mean by that last statement is this:  there is no way to 'force' a
LFN to a specific number at the end of the shortened 8.3 filename; the 8.3
name simply gets the next available number, always starting from '1'.  So,
if you were to copy two files (or worse, directories) from the same directory
that translate to the same 8.3 filename, you have no guarantee that they
would have the same number at the end of the 8.3 name on the destination.

An example is in order.  Say you have the Norton Utilities 3.0 installed.
This package creates three directories in your Program Files directory:
"Norton Web Services", "Norton Utilities" and "Norton Crashguard".  The
shortened 8.3 names are simply NORTON~1, NORTON~2 and NORTON~3.  If you were
to copy all 3 at once however, their new names would be NORTON~3, NORTON~2
and NORTON~1.  So, any entry in the registry that referred to NORTON~3 would
now be looking in "Norton Web Services" instead of "Norton Crashguard".

This ZCOPY32 program, as stated above, does not have this problem and is
therefore ideal for copying one drive to another.  The only drawback is that
both drives must have the same cluster size.  However, since all FAT32 drives
under 8GB use 4K clusters, you can use this program to easily upgrade to a
larger drive if you are already running FAT32.

FAT12, FAT16 and FAT32 are all supported, EVEN FROM MS-DOS.  If you have any
FAT32 volumes, however, the drive letters this program uses will not agree
with your MS-DOS letters because the FAT32 volumes aren't 'seen' by DOS.

This program requires an extended memory manager (e.g. HIMEM.SYS), and as
much conventional memory as it can get.  It will not work with a compressed
drive.

