This is not just another Move command it features more: Recursive directory
movements (including creation of destination dir), pattern support, and
command line flags like those known from e.g. C:Rename
PUBLIC DOMAIN, includes source...
Fixed since Version 37.11 (Yep, even a small program may have bugs ;)
- Same Volume detection method, didn`t always work, so
Move didn`t try to Rename() all the time. Furthermore
fixes concerning last release didn`t work (Move pic? pics)
- Technically un-pured Move, while using global LibBase to DOS
(fixed for this release. Move is really PURE, again)
Fixed since Version 1.10 (Yep, even a small program may have bugs ;)
- Changed version numbering to official scheme
- One couldn`t move the entire contents of a directory
to a dir within that directory (eg. Move #? Dummy)
- One couldn`t move directories, if the destination dirs
already existed (eg. Move Dummy1 Dummy2 t:; if Dummy1
and Dummy2 both existed in t:)
- OldWindow and HitMask vars weren`t preset to 0
(Reported by : Christian Buchner)
- When one issued something like this "Move #? dummy/",
Move stopped when trying to move dummy to itself ;) Fixed
Fixed since Version 1.9 (Yep, even a small program may have bugs ;)
- Move didn`t end up some operations with a "moved" string,
thus leading to corrupted display
(Reported by : Albert-Jan Brouwer)
- One still couldn`t rename a directory
(Reported by : Albert-Jan Brouwer)
Fixed since Version 1.8 (Yep, even a small program may have bugs ;)
- On recursive moves, Move will indent the output according to
recursion depth. This is for better readability
- Move will refuse to move a dir to itself now.
- One couldn`t move a dir to another dir on the same device
Fixed since Version 1.7 (Yep, even a small program may have bugs ;)
- Added PURE information to Doc, since Move really is pure
(Suggested by : Albert-Jan Brouver)
- Due to the move-renaming bug one couldn`t rename a dir
an Assign was put on.
(Reported by : Albert-Jan Brouver)
- Fixed move-renaming of directories.
(Reported by : Albert-Jan Brouver)
- Move had some severe problems recursively moving
the contents of a directory
Fixed since Version 1.6 (Yep, even a small program may have bugs ;)
- Error while moving to a "device full" disk
(Reported by : Chris Conger)
- FileName length-bug fixed
(Reported by : Juergen Lang)
- Recompiled using SAS 6.50
- Stack usage reduced
Fixed since Version 1.5 (Yep, even a small program may have bugs ;)
- Move got screwed up, when attempting to move a
zero size file
- Added Buffer Keyword to specify the maximum buffer
size for an inter device move. Normally Move would have used
the max amount of available free memory in order to
accomplish the move, or the size needed by the file...
(Suggested by : Christof Damian)
- One couldn`t rename a file using move, because the
"destination" file was removed before doing the rename,
ie. the source file was deleted.
(Reported by : Chris Conger)
Fixed since Version 1.4 (Yep, even a small program may have bugs ;)
- Freed the FileInfoBlock _BEFORE_ setting the Bits, Comment
etc. This lead to MungWall hits (of course it did)
(Reported by Nico Francois)
- Exidentially called one ExAll() without ED_SIZE
This lead to some calls to DoTheMove without the Size set ;)
(Reported by Karsten Weiss)
Fixed since Version 1.3 (Yep, even a small program may have bugs ;)
- Now uses Rename() when source and dest are on the same
device. This is faster ;) Why haven`t I thought of that
earlier ??? ;)
Fixed since Version 1.2 (Yep, even a small program may have bugs ;)
- UnLock Problem solved when doing recursive Dir-Moves
This bug lead to "Object in use" error messages
Fixed since Version 1.1 (Yep, even a small program may have bugs ;)
- Added CTRL-C checking
- Added FORCE Flag in order to move read/deleteprotected or
to overwrite a delete/writeprotected files
Fixed since Version 1.0 (Yep, even a small program may have bugs ;)
- Added well known CLONE, DATES, COM, NOPRO,
QUIET and NOREQ options also used by e.g. Rename
|
aminet net>