🚀 go-pugleaf

newsham@wiliki.eng.hawaii.edu (Timothy Newsham) writes:
>Sometimes the most easiest and quickest solutions elude us.
>A simple batch file can make a great mv command.  Just create a batch file
>with the following lines:
[etc]

This thread has gone on a while, hasn't it?  A few weeks ago I was telling
someone else exactly why this is NOT what we're looking for.

1) If the copy fails, you delete the original, no saving throw.
2) If the destination is on the same drive, you have to:
   a) wait for the copy to finish, fragmenting your drivespace
   b) hope that you have enough room for both copies during the copy

I could also point out what happens if you do a 'copy *.* e:\dir' and
e:\dir doesn't exist.  You get all the current directory's files appended
together into a file called e:\dir.  If you then delete the source files,
you're royally hosed.

What we want is a small, fast, compatible, and reliable program to handle
the various cases intelligently.  If the drives are different, copy if
there's enough space, then delete if succeeded.  If on same drive, rewrite
directories to just change the entries, not move any data.  Other nice
features could include an option to move subdirectories (prune & graft),
and an intelligent ability to "cache" directory modifications so things
would go faster in case you weren't using a disk cache.

I use something called 'REDirect' which someone renamed to 'mv.com'
somewhere along the line.  It works fine, but won't copy/delete when it has
to.  It also won't rename along the way.  It also doesn't cache dir writes
or allow prune & graft.

I'd write one, but I don't have access to enough versions of DOS and such
to be sure of the compatibility.  Who wants to run a 'mv' command which
might turn your FAT into oatmeal?

-- 
Kevin Martin
sigma@ipl.rpi.edu
"Can I kiss one of the bridesmaids instead?"