GreatMarko

Moderators
  • Posts

    3,176
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by GreatMarko

  1. Can you just check your port settings in Sync and also in your router/firewall, to make sure that these haven't changed in your update to 1.4.99 (as blocked ports would explain "No peers")
  2. Have you tried syncing them both to the same internet time server just to be absolutely sure they are identical? As per the help article, "if any of your peers has invalid time (or, which is more often - invalid TimeZone) - the time difference becomes suspiciously significant (1 hour or more) and Sync gives you a warning". There are no other instances under which you'll e seeing an "Excessive Time Difference Between Peers" warning - it will be the time/date/timezone/DST settings on the system clock on one or both of your devices.
  3. 1.4.99 should be backwards compatible with the previous 1.4.x build - so your issue is certainly not a "feature" This isn't practical, as in many cases it's down to the individual NAS vendors who don't update their packages very often/quickly or indeed at the exact same time as each other/BitTorrent Inc!
  4. Please read my previous post: "The fix itself hasn't been included in today's public 1.4.99 build"
  5. Michael, It all depends upon the highest level of folder you've added to Sync. In your instance instance,If you've added the "\TV" folder itself to Sync, you'll be able to move its subfolders around within "\TV" without causing a re-sync. If, however, you've added the 3 folders you list separately to Sync, then in this case, moving them around in/out of each other would cause a re-sync. Sync is presently only able to avoid re-syncing if it detects "moves" within a sync folder tree, rather than between sync folder trees. A few examples to illustrate the current behavior: Example 1: C:\FolderA\ C:\FolderB\ Both folders A and B are separately added to Sync. Moving "FolderB" to become a sub folder of FolderA (i.e C:\FolderA\FolderB) would cause of re-sync (FolderB will be detected as new content within FolderA) Example 2: C:\FolderA\FolderB FolderA is added to Sync. Moving the contents of "FolderB" up a level into FolderA itself will not cause a resync Example 3: C:\FolderA\FolderB FolderA is added to Sync. A new sub folder (FolderC) is then created within FolderA (i.e. C:\FolderA\FolderC) If the contents of "FolderB" (C:\FolderA\FolderB) is then moved into the newly created "FolderC" (C:\FolderA\FolderC) this will not cause a resync So, in summary, the way Sync currently behaves - moves within the "tree" (hierarchy) of an existing folder that's been added to Sync won't cause a resync; moves between "trees" of two separate folders each added to Sync will cause a resync.
  6. @rockhill04, please see my reply to you in this thread.
  7. @afelico / @rockhill04 - there are known issues with AutoCAD which are similar to the issues some users are currently experiencing with Office files (see this thread). A fix for these particular issues is currently in testing and will hopefully become available to all users in the not too distant future. In the meantime, if you're interested in helping test this fix, please PM RomanZ, or express your interest in the thread I've referred to above.
  8. Probably not! There was a specific issue relating to Encrypted nodes that caused them to become "out of sync" - this is the only "out of sync"-related issue that has been addressed in 1.4.99. If you have an "out of sync" issue, that isn't related to Encrypted nodes, making your nodes encrypted is unlikely to magically solve your issue!
  9. Sync 1.4 has supported Windows XP for some time - support was re-introduced in 1.4.82, some 5 releases back!
  10. Are you using Encrypted nodes? - As I say, 1.4.99 fixes "Out of sync" issues with encrypted nodes
  11. Correct Running multiple instances of Sync is not officially supported. Yes, some users have found "workarounds" to achieve this, but perhaps your best solution may be to set sync_trash_ttl to "0" and then have a script/schedule task delete the contents of .sync\archive folders that you don't want to keep "forever" on a recurring interval (i.e. once per day).
  12. @all, if you're unable to PM RomanZ, just express your interest in this thread instead and I'll ensure RomanZ sees it. ...and just to give you an update, it looks like the team have now been able to address this issue! The fix itself hasn't been included in today's public 1.4.99 build however, as it needs further testing to ensure there are no knock-on issues as a result of the fix.
  13. On Windows: 1) Add the C:\users\me\pictures\GoPro folder to Sync 2) In Sync, click the folder's "Share" button (hover over the far right of the row) 3) Click "QR Code", which will display a QR code on screen Then, on your Android: 4) Click the "Add Folder" icon in the top right corner of Sync's main screen 5) Scan the QR Code on your Windows screen, and select the location on your Android device you want to sync with
  14. @all, 1.4.99 contains a fix for Encrypted nodes becoming "out of sync" - please update and report back whether this your issues!
  15. @all, if you're experiencing an "Out of sync" issue with Encrypted peers, then version 1.4.99 contains a fix for this particular issue
  16. Yes - on Android instead of using the "New Backup" menu option, tap the "Add" icon in the top right corner on the main screen instead, then tap "Enter a Key". You can then share a folder using a key rather than having to scan a QR code
  17. As per the article I've directed you to "IgnoreList is located in hidden ".sync" folder" So if you're syncing a folder named "test", you'll find IgnoreList under "test\.sync\IgnoreList" Also, as per the article: "IgnoreList is a UTF-8 encoded .txt file" - you therefore edit it as you would any other .txt file (i.e. in a text editor)
  18. Well, despite your suggestion not to send you to a help topic, you'll find information on where this file is located and step-by-step instructions of how to use it in the following Help Article: Ignoring files in Sync (IgnoreList)
  19. You're seeing this message because you have Internet Explorer 8 installed. You therefore have two options: 1) Update IE so that you can use the "native" HTML Sync UI ...or... 2) Use Firefox/Chrome to access Sync via your browser (http://127.0.0.1:8888)