![]() ![]() After the upgrade, the new full overnight Project only came up with one of the three original different files.Maybe this behavior is normal, but it seems erratic to me? Immediate Parent directories are now green (but higher level remain red), file no longer visible: "Different" File changed from red to green "Identical": Ran a separate project to "Compare As Binary" as you suggested: Changing view parameters oddly changed results back-and-forth from different to identical (when I could see the disappearing file).Īfter last night's run, 2 of the original 3 "different" files are now identical only 1 remains:.It came up clean with NO different files? I the ran a new project, directing the Compare to include only the parent directories of the 3 original troubled files (they are all in the same nested directory).I went back to the view of the original project, and oddly, the offending upper parent directories were still red, the immediate parent directory was now green, but the offending file was nowhere to be found? Did WinMerge hide it because the "Compare As" came up as identical? Why do the upper level directories remain red, while lower level turned green (and display "different")?.I ran your suggested "Compare As Binary" as a separate project- the remaining offending file came up as "identical".Only one different file in a deeply nested directory. ![]() Two of the three offending files shown above were now listed as identical.(I read the Release Notes regarding crashes with large files). It is worth mentioning that it is big- about 3TB total 16 hrs of processing. I then ran the same project overnight (as above).I updated from v2.16.8 (correction to my above mistake) to the current stable v2.16.12 last night.Hello sdottaka - thanks a lot for the reply! Sorry for the length. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |