My system sometimes flips a bit and the destination files from a simple explorer file copy becomes corrupt.
I don't know what causes it but until I track down the error I want to be sure the files written with Sync Back Pro are 100% non corrupted.
So now my questions/concern:
How does SyncBackPro make sure the destination files in a copy is written correctly and not just read from Windows Standby RAM on the hash check?
I switch the option "Verify that files are copied correctly" on and see that the file is read back right after its written - but doesn't the file get read from Windows Standby RAM instead of the destination hard drive?
Because i've noticed that files are read from Windows Standby RAM if they still reside there when I'm not using SyncBackPro. And only a reboot makes sure that I afterwards read the file from the destination hard disk and not Windows Standby RAM.
I don't know what causes it but until I track down the error I want to be sure the files written with Sync Back Pro are 100% non corrupted.
So now my questions/concern:
How does SyncBackPro make sure the destination files in a copy is written correctly and not just read from Windows Standby RAM on the hash check?
I switch the option "Verify that files are copied correctly" on and see that the file is read back right after its written - but doesn't the file get read from Windows Standby RAM instead of the destination hard drive?
Because i've noticed that files are read from Windows Standby RAM if they still reside there when I'm not using SyncBackPro. And only a reboot makes sure that I afterwards read the file from the destination hard disk and not Windows Standby RAM.