JerryWithaJ

Members
  • Content Count

    7
  • Joined

  • Last visited

About JerryWithaJ

  • Rank
    New User
  1. SInce I'd used enough pixels about problems some users experience when moving from 1.4 to 2.0, it seemed only fair to report that my transition from 1.4 to 2.2 went without a hitch. In a previous thread, I was told, "Technically, Sync 2.x was designed to do upgrade from 1.4. Just shut down your 1.x Sync and start 2.x. All folders will stay as "classic" or "standard" (depending on minor version of 2.x Sync) folders. Identity will stay unchanged. Indeed, community members reported issues during upgrade. There are bugs in Sync 1.x which sometimes cause changes in the database, representing the folder - which stay after upgrade and can behave differently in 2.0. We've fixed all that we've managed to identify, although I can't claim that we've fixed all the 100% of issues." In a separate email, I was warned, "to remove your old local storage of the app before upgrading to 2.2 version from 1.4 version. In this case you will need to re-add and re-index all necessary folders which you want to synchronize." The thing I most wanted to avoid in updating was having to "re-add and re-index all necessary folders which you want to synchronize." Since everything was working fine in 1.4, I decide to take a chance and update without removing old local storage." I took a chance here. I don't recommend that anyone else do it. But it seems to have worked. The only small hiccup involved the Android update. At first, it looked like the the folder information (but not the folders) was lost during the upgrade. However, it reappeared while I was in the process of reentering it. I don't know what triggered it, whether it was just a matter of time, or whether the keystrokes completed some process. In any case, it's all good, so far.
  2. Thanks! I sent my concerns to Support. I understand that not every thread can be monitored. However, when the information is not readily available on the website, all that is needed is a link if there is one, and there are responses to queries posted after one's own, it isn't totally unreasonable to think that there is nothing to be said. I'd been using BTSync since the early days. Yes, I didn't like the annual fee or the 10 folder limit on free, but it was the issues that users seemed to have when trying to upgrade that had me hold back. Now, I;m so deeply entrenched in 1.4 (1 desktop, 4 laptops, 1 smartphone, a half dozen tablets), that it would be nice to hear that I can upgrade without having to jump through hoops to keep my devices talking with each other.
  3. @patoka: I asked something similar on September 17. I'm squeaking along on 1.4, but would upgrade to support the project IF I could be shown how to do it--step by step upgrade instructions, say--without all of the grief reported by 2.0 adopters. The ONLY response I received was from another user who said, "If [1.4] working fine, I would stick with it." What distresses me is that it was the only response. I could have easily dismissed it if the Admin had responded with an appropriate link. But, no one did despite having responded to a query posted after mine. I find that silence deafening.
  4. When Sync announced its previous business model, I decided to stay with 1.4, which continues to serve me well, thank you. It wasn't just the cost that had me stay with 1.4. It was the change in the way Sync worked, with many users saying the conversion was giving them fits. I'm happy to buy a personal license, but it should be for a product I'll use. Is there a document along the lines of "Moving from 1.4 to 2.2"? How many hoops will I have to jump through. Ideally moving from 1.4 to 2.2 should be transparent to me. I've gotten the sense (wrongly?) that it's anything but! Thanks!
  5. 1.4 seems to work with Win 10 for me, but it's 32 bit Win 10.
  6. Thanks! I'm almost tempted to ask what the fuss is all about. We were told 1.x would never lose its functioinality and it hasn't. One can stick with it rather than move to 2.x. In my case, I'm staying with 1.4.111 not because of the absence of a floder limit but because it's so much easier (for me) to use!
  7. The title says it all: "What is the last version of 1.x that will continue to work with no folder limit?" Will any version? Thanks!