Hi All,
I'm using RealTime sync on a google drive and it is (apparently) not detecting the google drive.
The message I get is
"waiting until directory is avaiIable "C:\Program Files\FreeFileSync\Gdrive:\etc\etc..."
I can open the same script in FFS and it runs fine.
What am I doing wrong.
Thanks
Dave
RealTimeSync and Google Drive
- Posts: 4
- Joined: 19 Jan 2019
-
- Site Admin
- Posts: 7285
- Joined: 9 Dec 2007
This should have failed with an error message, and in the next version it will:
viewtopic.php?t=4302
Solution: Remove the "gdrive" path from the RealTimeSync folder list.
viewtopic.php?t=4302
Solution: Remove the "gdrive" path from the RealTimeSync folder list.
- Posts: 4
- Joined: 19 Jan 2019
Thanks Zenju,
Just clarifying.
- remove the testing of the entire folder effectively making it a one way compare.
or
- remove the Gdrive: bit of the folder spec.
Thanks
Dave
Just clarifying.
- remove the testing of the entire folder effectively making it a one way compare.
or
- remove the Gdrive: bit of the folder spec.
Thanks
Dave
DELETED
- Posts: 4
- Joined: 19 Jan 2019
Hi, The Fallender,
Actually I have the opposite problem here. Google's B&S has failed and I can't sort it out because of a corrupt .msi (can't uninstall old so can't install new).
I have spent a bit of time playing and thinking about implications and have the following thoughts.
The issue is that there is no mechanism for remote systems to be notified of changes in google drive - they have to directly examine and decide.
Therefore, short of spending considerable CPU and internet time FFS can't decide to initiate a sync. So inappropriate for background task.
On the plus side- FFS can still be notified of changes on the local machine, which will initiate a full sync, this will bring changes from GD to local machine.
BUT care must be exercised with this. If GD has an updated version of (something.doc) and you edit (something.doc) locally then FFS may lose one lot of edits for the file. If this happens you may be able to recover some info using GD's versions information. It is possible you may not even notice that there was a conflict.
Solution is to save the sync job to desktop, do manual sync before your edit to ensure local file is up to date and resync after editing. This will solve all except concurrent file editing but several people.
Hope this clarifies.
Actually I have the opposite problem here. Google's B&S has failed and I can't sort it out because of a corrupt .msi (can't uninstall old so can't install new).
I have spent a bit of time playing and thinking about implications and have the following thoughts.
The issue is that there is no mechanism for remote systems to be notified of changes in google drive - they have to directly examine and decide.
Therefore, short of spending considerable CPU and internet time FFS can't decide to initiate a sync. So inappropriate for background task.
On the plus side- FFS can still be notified of changes on the local machine, which will initiate a full sync, this will bring changes from GD to local machine.
BUT care must be exercised with this. If GD has an updated version of (something.doc) and you edit (something.doc) locally then FFS may lose one lot of edits for the file. If this happens you may be able to recover some info using GD's versions information. It is possible you may not even notice that there was a conflict.
Solution is to save the sync job to desktop, do manual sync before your edit to ensure local file is up to date and resync after editing. This will solve all except concurrent file editing but several people.
Hope this clarifies.
DELETED
- Posts: 4
- Joined: 19 Jan 2019
By Golly Fallender,
I had tried a 3rd party uninstaller but it failed. I ran IObit and B&S is gone, Fresh install of new version OK. Thanks for the pointer.
Dave
I had tried a 3rd party uninstaller but it failed. I ran IObit and B&S is gone, Fresh install of new version OK. Thanks for the pointer.
Dave
DELETED
