Please replace "no hit file" with "Source = Destination"
Posted: Tue Feb 05, 2013 5:08 pm
A Linux Boot Glitch trashed 500 GB of NTFS "Used Space" on a secondary HDD into RAW Unallocated, and also changed it from GPT to MBR.
Source and Destination paths are the results of separate attempts at recovering those files with high powered Windows recovery tools,
and I wanted to test how random and variable were the results of those two attempts.
I launched BestSync to compare and was told "(path} <==> {path}-Preview completed, no hit file."
There were no differences shown between the contents of the two paths.
I am not accustomed to seeing ",no hit file" and assumed that this was a warning of a FAILURE to compose a hit file and that this failure prevented normal completion of the preview.
I spent half an hour looking for some strange Access restriction might prevent BestSync from composing or using a "hit file",
and wondering if the Linux Glitch had also damaged Windows.
Eventually I tried adding a file to the contents of the destination path and that was then detected in Preview,
and I no longer saw the negative phrase "no hit file".
"no hit file" is negative and sounds like bad news because something is missing.
"Source = Destination" would be good news and more appropriate in this situation (which I hope never to see again).
Regards
Alan
Source and Destination paths are the results of separate attempts at recovering those files with high powered Windows recovery tools,
and I wanted to test how random and variable were the results of those two attempts.
I launched BestSync to compare and was told "(path} <==> {path}-Preview completed, no hit file."
There were no differences shown between the contents of the two paths.
I am not accustomed to seeing ",no hit file" and assumed that this was a warning of a FAILURE to compose a hit file and that this failure prevented normal completion of the preview.
I spent half an hour looking for some strange Access restriction might prevent BestSync from composing or using a "hit file",
and wondering if the Linux Glitch had also damaged Windows.
Eventually I tried adding a file to the contents of the destination path and that was then detected in Preview,
and I no longer saw the negative phrase "no hit file".
"no hit file" is negative and sounds like bad news because something is missing.
"Source = Destination" would be good news and more appropriate in this situation (which I hope never to see again).
Regards
Alan