Related to T75: Improve progress indication
Received support request about newer Replicator running slower than old Replicator and it was the 1-update-per-second thing. Every 1 second the utility needs to boast about how quickly it is scanning files, or at least a Files Scanned counter.
Peter wrote to support:
I'd like to email the Replicator results. I have mailsend.exe
Should have option to send results of job (summary, list of errors, etc)
Leonard B just reported a test where "Move deleted Items to Recycle Bin" simply deletes the file, no error, and it's counted in the Files Recycled count.
This is no longer a problem. Was resolved by T36: Folder timestamps in destination should match source
Nope, I've misunderstood Jim's issue. Editing this task to reflect the real issue. Or is there another task? My head is spinning... I'll just copy ticket text here:
This is because some people may want to copy if the Last Modification time is different -- it could be earlier than the copy in the Destination Folder. I don't personally have a use case for this, but some users might be using Replicator to restore previous file system states, I guess.
Going to wait for C# .NET version which will work right out of the box.
Fixed the free space problem by stripping off the \\?\ from the beginning of a drive name.
Is this specific to "desktop.ini?"
The job order function of the Settings form is already in sorted order when it comes up. So, if you're going to add a specific sort order field to the job then I guess that's still a thing.
I've not been able to verify how this could actually happen. I double checked the code again today and I've never experiences the problem.
It's not at all perfect, but I've added an index column.
Also added checkbox setting on Other Settings page.
Removed from the milestone for release v3.7.4 which was more of a hassle than one might think: Had to unlock it so I could edit the task (being Admin isn't enough), then I set up a custom policy so Sam could edit it again (needed custom policy because if Administrators wasn't in the policy then I couldn't save it). Also made public so people could see it. I've changed the default visibility of the Default space to be publicly visible.
[I]f there is an opportunity to implement a limit to the size of the log file Karen's Replicator creates, that would be appreciated.
Say around 500KB to 1MB. Oldest logs to be deleted. Perhaps a user's choice as to whether to limit the log file's size or not.
For those that backup many folders, the log file size mushrooms fairly quickly, especially for those that backup daily.
Large log files are a chore to read and, on older systems, may not load into the "notepad" like window due to its very large size.
I have run into some users that did not realize there was a log file to peruse! Their log file sizes were gargantuan!
5/27/2019 6:44:00 AM: Error: Copy of K:\_VISTA_\D\VB6\Replicator\BigFiles\bigbase.iso to E:\Karen's Tests\BigFiles\bigbase.iso Failed (Error 112 - There is not enough space on the disk.): 5/27/2019 6:44:00 AM: Error: Copy of K:\_VISTA_\D\VB6\Replicator\BigFiles\bigfile.dat to E:\Karen's Tests\BigFiles\bigfile.dat Failed (Error 112 - There is not enough space on the disk.): 5/27/2019 6:44:00 AM: Error: Copy of K:\_VISTA_\D\VB6\Replicator\BigFiles\bigfile.dat.27b4.part to E:\Karen's Tests\BigFiles\bigfile.dat.27b4.part Failed (Error 112 - There is not enough space on the disk.): 5/27/2019 6:44:42 AM: Finished Job: BigFiles to E