X-no-Archive:yes
In a previous life, I recall benchmarking DOS Copy vs XCopy vs NetWare
NCopy, locally and across the network, for single and multiple files of
various sizes. My conclusion was first and foremost, this is worth doing,
when production processing requires that files are copied. For instance,
COPY is an internal command, so does not need to load, which saves time for
small files. For files larger than COPY can buffer, any command that can use
more memory worked better.

Tracy's immediate work-around was probably the best of all possible worlds.
The Microsoft tools have a local PC or small LAN heritage, and are
ill-suited to much else. And Explorer incurs the unneeded overhead of the
GUI. The NT ResKit has a useful utility (several useful utilities,
actually), called RoboCopy. It's a play on words, for both automated and
robust copy. It tolerates network delays, and can pause and retry by
configurable values, among other useful settings. And, it does not seem to
much care which MS OS it is used from.

But this is clearly a case where your mileage will vary. Learn which tools
you have for copying / transferring files, and learn to use them. Then, when
your processors or network change, run some benchmarks on production
transfers / copies.

Greg Stigers
http://www.cgiusa.com
Free yourselves. Unmap your drives.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *