THEY DON'T WORK (unless you're one of very few lucky people in which case you should go grab some lottery tickets).
If you follow the directions, you'll get an error about the new folder not being the original. Umm, isn't that the point of MOVING your folder? By definition, the new one isn't the old one even if it has all the same contents.
The problem and solution both lie in 2 files which you will find in the folder %userprofile%\AppData\Local\Google\Drive (for Windows anyway, not sure about other operating systems though I suspect the file names will match).
Those files are:
- snapshot.db
- sync_config.db
- Stop Google Drive Sync (right-click and Quit)
- Move the entire Google Drive folder (default is in Documents and Settings)
- Open each of the two files and do a find/replace from the old path to the new.
- Start Google Drive
- Be done (NO SYNC REQUIRED)
Related: Recent issue I had, Google wouldn't resolve and I figured out myself. "Google Drive Failure Comes to a Head ... Read More"
UPDATE 2014-04-07: After researching other sync-app solutions, I've discovered one that seems to address the 3 most significant issues I've had with every other sync solution out there.
- Not having to re-download files that are already up-to-date (or at least REALLY close)
- Syncing folders that don't exist in the "Google Drive" folder OR syncing all the folders you want and NOT the ones you don't.
- Moving your "Google Drive" root folder (less significant in light of points #1 and #2) without having to redownload everything.
If you're interested in a premium client that has real flexibility, a good UI, will allow you to seed with existing files, is fast, and efficient at syncing, please comment below. I'm considering a Kickstarter project to help make a final determination of whether I should move forward and how aggressively I should do so. If I move forward, I will be doing a proper beta program (REAL beta meaning I will actively engage to collect feedback, correct issues, update the client, etc..), provide multiple levels of backing which will dictate the level of support beyond beta, featureset, licensing (if I don't go perpetual), etc..
I will also use surveys to get a feel for what is most wanted, needed and what people might be interested in paying for.
Comment below to let me know your thoughts and interest.
UPDATE 2017-04-06: It's been nearly 4 years since my original post, 3 since my last update, and almost 1 since this topic was an issue for me. Somewhere along the way the Drive Sync client was given a registry-controlled feature to help the Sync client recognize existing files rather than ONLY recognizing files synced by the Drive Sync client. In recent history (I'm not sure, but I'd estimate 3 months ago) that feature has been turned on by default so now (in theory), you should just be able to point the client at a folder during setup, and it will merge the contents with Drive, identifying existing files when it's reasonable rather than creating duplicates.
tl;dr: This shouldn't be an issue anymore if you're on a current sync client and Google auto-updates them so you should be.

