ok but how does SyncBackPro make sure that it reads back the file from the destination HD for hash checking and not just the cashed one in windows standby ram?
I've noticed that SyncBackPro doesn't seem to flush windows standby ram of the cached file after the filecopy process so that/those files are still in memory and windows often chooses to read from memory instead of the HD if the file/files is still there.
I've got 32 GB of memory so alot of files are residing in that before they get overwritten by newer ones.
You can use this program to see what files are residing in the windows standby ram and use the menu to 'empty standby list' which clears all files from memory and forces a read from the HD
http://technet.microsoft.com/en-us/sysi ... 00229.aspx
I've noticed that SyncBackPro doesn't seem to flush windows standby ram of the cached file after the filecopy process so that/those files are still in memory and windows often chooses to read from memory instead of the HD if the file/files is still there.
I've got 32 GB of memory so alot of files are residing in that before they get overwritten by newer ones.
You can use this program to see what files are residing in the windows standby ram and use the menu to 'empty standby list' which clears all files from memory and forces a read from the HD
http://technet.microsoft.com/en-us/sysi ... 00229.aspx