xtraeme Posted April 29, 2015 Report Share Posted April 29, 2015 (edited) A week or so ago I upgraded to Pro to experiment with the new 2.0 features. I have two machines that I am syncing. One is a desktop with literally millions of files from a rather large development project extending Chromium. The other machine is a Surface and only imports subsections of the project over two directories. So imagine my surprise when I upgraded from 1.4.111 on the Surface and all 17 shares were imported on to the Surface from my main desktop after I linked the two devices. The Surface was setup to fully sync; so it started to download the whole project. The BT Sync client immediately locked up. In a panic, since my disk space was quickly filling up, I quickly killed the internet connection. After several crashes and wasting time sitting through the ten minute long load screen I was able to start to disconnect the shares that I didn't need on the Surface. This is incredibly bad behavior. Please in the future ask users what shares they want to import or at the very least start them in a disconnected state. Don't just assume all shares are wanted uniformly across all devices. Even worse I just discovered that apparently deleting a share on one machine will now delete it on the other device. This is just getting ridiculous. I never had half the number of problems with ViceVersa Pro. Edited April 29, 2015 by xtraeme Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.