I changed the standard drag and drop to always be move and also added renamed old and it works fine except it changes the creation date of the new file to be the same as the older file?
I'm not sure but it might be a quirk of Windows where renaming a file then quickly creating a new file with the same name passes on the attributes to the new file.
Could also be something else, though.
This is how I have it setup:
copy MOVE WHENEXISTS=renameold
Yes this is probably caused by the Windows filesystem "tunneling" feature.
You can read more about it here - that page also contains instructions on how to disable it if desired.
Think I will try this: copy MOVE WHENEXISTS=rename
Looks like the tunnelling feature is off (at least by default) in Vista, FWIW.
(At least, I can't reproduce the timestamp stuff on this Vista machine, and the article was updated in December but says it only applies up to XP.)
I forgot to ask if you can control the add string that gets automatically added when you use the rename feature?
Being able to change file1.exe or file(1).exe or file_1.exe would be a nice feature.
@LEO
I'm using Vista RTM not SP1 so maybe it is turned off in SP1.
I don't think (at the moment) you can change the way the files are auto-renamed in this situation.
Re tunnelling: Interesting. Maybe I just didn't test it right. I'd be surprised if SP1 turned off a feature like that so I suspect my own testing may not have been done right in that case. Or maybe I turned it off a long time ago manually or it's tied to some other thing.