GreatMarko

Moderators
  • Posts

    3,174
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by GreatMarko

  1. The latest version is 1.1.15 and may be manually obtained here (it's not yet be pushed out via auto-update) If your boss downloaded the latest version today (June 14), he/she will be running either 1.1.12 or 1.1.15 (1.1.15 was released today) - these 1.1.x versions are not compatible with 1.0.x versions, such as your 1.0.134. Updating to 1.1.15 will likely resolve your issue.
  2. That's because you can now simply double-click the entry to open the corresponding path directly!
  3. If you've signed up for the private alpha of BitTorrent Sync Mobile, you should have (or will shortly receive) an email informing you that "You're on the list!" and which goes on to say "Over the course of the next couple weeks, we’ll be sending out invitations to people on this list; first come, first serve. The iOS app will be ready for the first alpha testers a few weeks before the Android app."
  4. Have you looked this up in the Supported NAS thread? (Hint)
  5. Does the old name still appear after you restart BitTorrent Sync on your other devices?
  6. Guys, please! How many more identical topics do we need on this!!!? This topic has been discussed to death in this thread, this thread, this thread and this thread
  7. No, they're there in the Windows GUI and in the WebUI on Linux
  8. .!Sync files are temporary files which are used to store incoming data. For example, let's say on one device you have a "file.zip", and this is to be sync'd to a second device. When the transfer begins, a temporary "file.zip.!Sync" file is created in the destination folder on the second device. Chunks of data are then added to this file as and when they are received from the first device. Once all the data has transferred, the ".!Sync" extension is removed (i.e. the file is renamed), resulting in a "file.zip" file on the second device which is an identical copy of the "file.zip" file on the first device.
  9. Why not?! It doesn't cause BitTorrent Sync an issue, as .!Sync files are ignored!! It only becomes an issue if you have other applications interacting with files in that folder that can't filter/ignore .!Sync files.. but what's the alternative? Store .!Sync files in a "central pool" elsewhere? Where?! ...and how would they be named?! You couldn't have a single central folder "pool" containing all the .!Sync files, as what happens if you're separately syncing two sets of folder, but each contain a file with the same name?! How should their respective .!Sync files be named/stored? ...you'd have to replicate the entire directory structure in the "pool" to avoid conflicts with files of the same name! ..plus there would potentially be more hard disk activity i.e. instead of simply renaming .!Sync files once they've finished transferring, which is what happens at present, instead they'd have to be "moved" from this "central .!sync storage location" back to the original location upon completion - potentially leading to more disk activity/fragmentation! To be honest the current method of storing in-progress transfers in their original folders as .!Sync files isn't that unusual! I mean, it's no different to the way, say, Windows Live Mesh worked - this used the similar method of creating temporary ".wlx" files in their original folders whilst transfers were in progress.
  10. Well, Kos just needs to enable the "Add the 'Edit by' line in this post?" option the next time he edits his post... but for reference, the builds currently listed in the first post of this thread have the following dates: 1.1.12 - June 11 1.0.134 - May 15 1.0.132 - May 8 1.0.130 - May 7
  11. They will no-longer sync between devices running 1.0.x and devices running 1.1.x
  12. Well, yours is quite a specific case... with the issue being a problem relating to a specific 3rd party application, rather than a problem to BitTorrent Itself. Therefore, unless anyone else is running the same 3rd party application you reference, this will unlikely be an issue for general users.
  13. The problem is that you're trying to sync files that are currently open/locked by another application/process. Therefore, BitTorrent Sync won't begin to sync them until they are closed/unlocked by whichever application/process is currently working on them. If you don't wish these files to sync, or they are always open/locked by some process, you should consider adding them to your .SyncIgnore, otherwise BitTorrent Sync will continue to attempt to access/index these files
  14. From the Unofficial FAQ: "Memory usage increases by around 300-400 bytes per file being monitored by BitTorrent Sync. Therefore, if you're monitoring/syncing 1 million files, you will need around 300-400 MB of free memory..."
  15. Yes, yes, and yes(!) - please see this post
  16. On Windows, click the "Preferences" tab, and then the "Advanced" button
  17. Remember you need to add ".tmp" to the .SyncIgnore file on EVERY device for the folder you're syncing, and then restart BitTorrent Sync on your devices for changes to .SyncIgnore to take affect. This won't prevent whatever other application/service is creating these temporary files from doing so, but it then should prevent them from syncing between your devices.
  18. Assuming you're only sharing one folder across devices, you can simply count up the number of entries in the "Devices" list to find out the number of devices connected at any given time. Obviously if you've got hundreds/thousands of devices connecting, this isn't very practical, but that's really the only to determine the number of devices connected
  19. Well, Google Chrome OS is a linux-based operating system... so have you tried experimenting with the available linux builds?
  20. Good question! ...do try it and let us know your findings!?
  21. No, the predefined hosts function is implemented - could the issue perhaps be that you're trying to use the same port number for two different devices on the same router?
  22. If you're quick, each time you start BitTorrent Sync on Windows, the "Devices" tab will list connected devices as IP:Port numbers, before their actual names are resolved. This only lasts a couple of seconds, so you need to be quick!! I do agree with you though, it would be very useful for a device's IP address to be shown (perhaps on a tooltip when "hovering" over a device name in the Devices tab?), primarily because at present, there's nothing preventing you from naming all your BitTorrent Sync devices the same - making them then indistinguishable in the Device list!!
  23. Well you could use the "Limit download/upload rate" settings (on Windows, you can find these on the "Preferences" tab of BitTorrent Sync). Other ways you can potentially reduce the amount of network traffic is by disabling tracker, relay, and DHT options (however this may affect your ability to sync to remote devices on other networks) BitTorrent Sync monitors your files in real-time. However, in addition, it also rescans for any changes every 10 minutes. As of version 1.1.12, you can change this 10 minute rescan interval by adjusting the advanced "folder_rescan_interval" setting
  24. What version of BitTorrent Sync are you running? If it's not the latest build (1.1.12), then please update to this build, which has some fixes which may well resolve your sleep issue!
  25. Please see the Unofficial FAQ entry: "Can I control how frequently syncing occurs?"