Crashes when trying to copy long file path So to summarize this transfer, both tools have strong pros and cons: Once everything was copied, I had to redo all the permissions-heritage on the destination folder, as all NTFS permissions were taken 1:1 from the source (this might be good in some scenarios, but that wasn't what I needed). But again, one file at a time, which made it much slower. I was forced to use Robocopy again, which had no problems whatsoever with long file names or file paths and everything was copied.
I retried the same copy process and Richcopy crashed again. The lucky moments were short: After a few subfolders (with so many subfolders that the UNC path is too long) Richcopy started to have problems and crashed. That's exactly what I needed in this file transfer scenario. Another nice improvement is the fact, that now the copied folders and files take heritage of the destination folder.
That's a big improvement over Robocopy! With this multi-threaded copy, it didn't only seem faster to my eye, but was in fact much faster. As soon as I started the copy process, Richcopy accessed several files at the same time (see screenshot above).
0 kommentar(er)
