As of this post, I am on version:
After battling the many slowness issues I seem to have run into due to the numerous CloudDrives I have coupled with my dirt slow internet, I have been very happy with CloudDrive. I have a macro script that goes through and allows the drives to run until they are flushed of "to upload" files allowing them to run one at a time. This gives me pretty good performance as well!
As I discovered early on, and on purpose, if you reboot before the drive's cache is 100% flushed out, you have to restart the upload of all the data in the cache. Fair enough.
As I was able to make the drives perform properly through my crazy macro programming skillz, I recently was able to get the drive all flushed out to the internet. So, I decided to reboot the PC. I wanted to test my macro, backup software, etc. loading up upon reboot to try to try to make things automated. Think upside down house of cards. Everything has to be JUST RIGHT for this to work...but it is only used as a backup dumpsite..so ... I'm ok with that.
I was surprised that upon reboot:
- EVERY drive needed to be unlocked, then re-authenticated. They were ALL configured for automatic unlock upon creation. Even if I made a mistake, I did not do that on EVERY drive
- every drive LOST my upload configuration.
I understand for #2 you would automatically assume upload being enabled. However, there was a reason I disabled prefetching as well as changed the upload threshold to [Off] instead of 1MB. I also had a few drives that had Upload verification reenabled. That might have been my fault for missing that on those drives, however I am mentioning it to ensure it is captured before that information leaves my brain.
Any idea what is going on? As it takes SO long to unlock and re-authenticate that many drives, as well as reconfigure the settings on that many drives...I'm hopeful there is something I can do about this?