Danew wrote:...there was a problem while trying to load V6.3.13.0 with its default settings. V6 on install finds my profiles and configures itself. I renamed V3 in Program Files but that did not stop V6 from locating my profiles and setting itself up as custom
Changing the program folder name won't stop V6 finding V3 profiles, as they are stored in the registry (except de-selection databases, which are stored in the V3 program folder - your rename may have crippled finding those...)
Danew wrote:With the filters and file/folder lists disabled V6 took 5 minutes to scan to the differences profile window with a simulated run. I noticed that V6 still refers to source and destination. I next ticked the do not use selections box in the file and folder window. I have tried these things more than once and have rebooted in between tests. The time to scan now increased from 5 minutes to 42 minutes. Repeating the test took 60 minutes, perhaps I forgot to reboot.
Sorry, this is not making sense. With "the file/folder lists disabled", you ran some tests then ticked 'Do not use selections'. Isn't that what you say you already did before the test? (With "the file/folder lists disabled")? Plus, I can see no note of your having added any de/selections at some point (which is what I suggested as 'stage-2')
Now that we know you are scanning over a million files, it's possible you are encountering memory issues. The Pro version switches to a disk-based database to avoid this at ~175,00 files, for comparison. Try splitting your file-scope into multiple profiles?
Danew wrote:Sometimes the source scan time is long with a short destination time?
Sorry, I'm lost as to which side is Source and which Destination (and when, and how each side is reached (internal v. network)). But it suggests system issues (affecting throughput), maybe.