In the process of transferring files from one PC to another, I did a Win Explorer copy of about 50GB (19,000 files) from an XP PC to a Win 7 PC.
I then purchased BC3 and ran a folder compare between the XP and Win 7 PCs of those files. (BC3 is running on the Win 7 PC).
The results of the compare were 2 file miscompares.
File miscompare #1 was a photo. I ran a fc /b (binary compare using Windows' fc command) at a command prompt on this file against the original. Windows reported the file identical. With the original BC3 session still open, I selected that one photo file and reran the compare operation. It too then compared identical. What is up with that?
File miscompare #2 was a large VMware workstation file. Did the same procedure as with file #1. Got the exact same results. Windows fc /b reports file identical. BC3 reports file identical the second time.
My first reaction would be a failure somewhere along the transer path (bad RAM, network, storage, etc.) that occurred during the compare but not the original copy or the second compare operation.
Has anyone seen this before? We transfer a lot of data on our network and we tend to run fc /b on large transfers and have never seen an issue. Any suggestions as to what might be going on with BC3?
Thanks.
I then purchased BC3 and ran a folder compare between the XP and Win 7 PCs of those files. (BC3 is running on the Win 7 PC).
The results of the compare were 2 file miscompares.
File miscompare #1 was a photo. I ran a fc /b (binary compare using Windows' fc command) at a command prompt on this file against the original. Windows reported the file identical. With the original BC3 session still open, I selected that one photo file and reran the compare operation. It too then compared identical. What is up with that?
File miscompare #2 was a large VMware workstation file. Did the same procedure as with file #1. Got the exact same results. Windows fc /b reports file identical. BC3 reports file identical the second time.
My first reaction would be a failure somewhere along the transer path (bad RAM, network, storage, etc.) that occurred during the compare but not the original copy or the second compare operation.
Has anyone seen this before? We transfer a lot of data on our network and we tend to run fc /b on large transfers and have never seen an issue. Any suggestions as to what might be going on with BC3?
Thanks.
Comment