Total Commander

Intro:
http://www.ghisler.ch/board/viewtopic.php?t=31187&start=0

ghisler(Author) wrote:I haven't added automatic sync because I think that it's too risky. Even if a file is newer, it may have been edited on BOTH sides. Only the user himself can know that and exclude the file from sync.

My situatuion:
I have some work-HDDs and backup one, and sync them weekly.
Often I have a situation with both-sided changes (and there's no sure that newer file is "better", then old one).

Solution is the simple: md5 check, based on a some kind of a database!

Here's the algorythm:
1. first check: TC compares files by content, also writes some "database.md5" (src/sha...) with checksums for all the files checked;
2. (some work done outside, so you get diffrent both-side edited files);
3. second check:
a. TC checks diffrences via files' date attributes (quick check not by content, we already have now);
b. then compares ONLY diffrent files' by content;
c. (if files are still diffrent) TC compares real files' md5/crc/sha with saved one in DB and shows up diffrences - wich file is physically modified, or not.

Profit:
- No need to lose time for shecking already synced before and identical files.
- Only diffrent-dated files are compared by content.
- CRC-check is done only for files, wich have another datestamp.
- Really modified (after crc check) files are highlited.

Reasons for such a suggestion:
Some PC's I use have wrong time/date settings. So, crc check is the only way to find out what I really need to backup.