I am moving another user from an old PC to a new one, both with Windows 10. The old PC had a lot of files mirrored on Drive for Desktop, so I installed Drive for Desktop on the new PC, set it up so the files were also mirrored and let the files sync on My Drive. After the sync was finished I did a file compare of both computers and found several problems.
(1) Two of the files were mismatched on the two computers. I called the Google help line for this (and what is below), and I also uploaded a screen shot of the output from the file compare program. The person I talked to on the help line said the screen shot was too technical for him and wanted me to send him a video showing why the files were different. That response is beyond me, for what it's worth, but I won't digress about it, at least not now.
(2) Thirty-three files were reported to have different lengths, but most of these were "desktop.ini" files used by Windows, so they don't matter. However, there were nine files that do matter. See below:
(A) One of the files just had a different file length, even though its filename on both computers was the same, so it should have compared with no differences.
(B) The other eight files had similar names, and by similar I mean almost identical. That is, they were named, for example, "File.doc" and "File (1).doc"., and it appears that Drive for Desktop is responsible for their names. Why do I say that? Because on my old PC "File.doc" compares exactly with "File (1).doc" on the new PC, and "File (1).doc" on the old PC compares exactly with "File.doc" on the new PC. In my mind, if the files are mirrored on both computers, then their names should be identical on both computers.
(3) My final problem is that some of the files could not be opened on one computer or the other during the file compare. That might be because Drive for Desktop had the files locked for some reason, so I'll look more into that myself before I ask for an answer. However, if anyone has any insight into that I'd appreciate hearing it.
I have not called the help line back, which is why I am posting this, but for the record, I did submit a bug report a week ago and haven't gotten a response yet.
LinkedIn
Twitter
