and the files were in:
C:\...
Correct.
And that is a definite bug!
---
In your case, it looks like you are using the same source & 'move to' directories.
---
On a local drive, what happens is that the files simply end up being renamed.
- Code: Select all
05/06/2021 06:43:47 PM - Renamed "C:\TMP\BRU\PICS\SSD_icon.ico" to "C:\TMP\BRU\PICS\PICS-------SSD_icon.ico"
05/06/2021 06:43:47 PM - Renamed "C:\TMP\BRU\PICS\SSD_install_icon.ico" to "C:\TMP\BRU\PICS\PICS-------SSD_install_icon.ico"
On a network drive (UNC path), what happens is that the files end up on C:.
What it says (below) is NOT what happened.
(Well, actually it is. It's just that the
intended action did not occur [do to the bug].)
- Code: Select all
05/06/2021 06:37:14 PM - Renamed "\\Nas\pub\PICS\SSD_icon.ico" to "\NAS\PUB\PICS\PICS-------SSD_icon.ico"
05/06/2021 06:37:14 PM - Renamed "\\Nas\pub\PICS\SSD_install_icon.ico" to "\NAS\PUB\PICS\PICS-------SSD_install_icon.ico"
(Note the single slash \ in the
to path name.
[In the screenshot, from above, you can also see the single slash in the 'Copy/Move to Location'.]
Single slash would denote the root directory of the (current) drive.
A double slash \\ would point to a UNC path.)
- Code: Select all
C:.
\---PUB
\---PICS
PICS-------SSD_icon.ico
PICS-------SSD_install_icon.ico