GreatMarko

Erm.. UAC doesn't prompt for a username & password though! ..it just offers the user a simple yes/no prompt! ...that's why it's more likely to be Windows prompting for valid login credentials for connecting to another computer!

BitTorrent Sync doesn't use usernames & passwords! Are you trying to access and add a remote folder directly into BitTorrent Sync? If so, you don't need to do this - you should only add local folders to BitTorrent Sync on each device. Trying to add a folder from another computer to BitTorrent Sync is probably why you're seeing a Windows prompt asking you for your Windows login credentials for the other computer you're trying to add a folder from. For example, let's say you have a "music" folder on both Computer A and Computer B that you want to Sync. What I suspect you've been trying to do on on one of these computers is add the local "music" from that computer AND also trying to connect to the other computer (hence why Windows is prompting you for login credentials for that computer) in order to also add the "music" folder from that too - this is not the correct way to sync. The correct way is: On Computer A add the "music" folder from that computer to BitTorrent Sync running on that computer. On Computer B add the "music" folder from that computer to BitTorrent Sync running on that computer.

You only need to remove the folder from BitTorrent Sync itself - you don't have to physically delete the folder from your drive, just remove it from BitTorrent Sync, and then re-add it again with your full-access secret

Are you running a 64-bit build of Windows XP SP3? If so, this will be the reason for this error. BitTorrent Sync is only supported on 32-bit versions of Windows XP, and SP3 is also required.

...yet! If you have a read/search of the wishlist thread, there have already been several requests for proxy support. The developers are aware of these requests

A folder and all its contents will be considered "read-only" after you apply a read only secret to the folder. It should also be noted that once you've applied a read only secret to a folder, you can't then apply a full access secret again, without first removing the folder from Sync and then re-adding it again with the full-access secret

There isn't a public "roadmap" as such at this time. As you probably know, BitTorrent Sync has only been publicly available for a little over a week - and in that time the forum has been literally inundated with hundreds of feature requests from users. The developers do frequent these forums, and are paying attention to all these requests... but there are a LOT of requests to get through, and the team have to prioritize them. We do know they are actively working on a whole host of new features - including mobile device support and an API to name just two! ...but I wouldn't expect any concrete assurances from the developers at this stage that "feature X will be available by date Y", etc. ...erm... the current version is 1.0.116 / 1.0.125... so we've already gone past a "1.0" release!

This could potentially be quite dangerous and result in data loss! ...which is why only single instances of BTSync.exe are permitted to run. I do agree, though, that being able to sync from one location to another on the same computer would be a very useful thing to have (for backup-type scenarios from one drive to another, etc) - but I think, if implemented, this should be done within a single instance of BitTorrent Sync, rather than by just allowing multiple instances to run at once, as this could cause BitTorrent Sync all kinds of confusion and conflicts!

Thanks for the confirmation, Sawyer007, the unofficial FAQ has been updated accordingly!

This means the secret you're using is already being used by another folder you're syncing on that device. You can't have two separate folders on the same device using the same secret.

I think you mean "settings.dat"? Anyhow, in the thread where this original "workaround" to make BitTorrent Sync "portable" on Windows was posted, there have so far not been any responses from anyone confirming as to whether this method actually works (I personally haven't tried it myself yet!) If several people can confirm that this method works for making BitTorrent Sync "portable" on Windows, I will certainly consider updating the unofficial FAQ accordingly.

wontolla, information on "how it works", and how devices find each other, can be found on the main website

You will see this error if the folder you're trying to sync has previously already been added to your BitTorrent Sync. You can't add the same folder to Sync twice!

No, if both devices have the "full access" secret, either one is considered a "master" - updates to either will propagate to the other You could possibly make use of the .SyncIgnore file, however, this is geared more towards excluding files in the directory from sync (rather than specifying which ones to include)

BitTorrent Sync will automatically attempt to find and synchronize all other folders that have that same secret! If these other devices are on the same LAN, BitTorrent Sync will search the LAN. If these other devices are all on different networks/different locations, BitTorrent Sync will use a relay server to establish connections ...either way it's all automated!

Then unfortunately, you won't be able to correctly exclude files from sync'ing at this time.

I've noticed that balloon notifications can persist on the screen until there's mouse movement/key presses, etc. For instance, I have a couple of headless WHS (Windows Home Servers) servers running BitTorrent Sync. When I remote desktop into these I'll quite often see lingering balloon notifications from Sync that a file had finished downloading (even though that action had occurred several hours/days earlier) Well, it may be that your *ithmb files are simply the last files to sync in each directory? So essentially, if a lot of files are changing at the same time, BitTorrent Sync may generate balloon notifications for them all in very quick succession, with the last file that's sync'd being the last balloon notifications, and hence this will persist on your screen for longer?

Agreed! A "Tor-like" platorm in order to "improve anonymity" isn't needed - BitTorrent Sync is already secure, and this would raise suspicions that BitTorrent Sync is being used for unlawful/illegal purposes. Remember, BitTorrent Sync is primarily a file synchronization tool for syncing files you own between your devices.

Are the contents of your .SyncIgnore files identical on ALL devices you're syncing between? If not, they should be! ...but you need to make these changes to the .SyncIgnore files with BitTorrent Sync not running. Only when you've made the changes to all the corresponding .SyncIgnore files on your various devices should BitTorrent Sync then be run. "*.iso" should then exclude all .iso files from syncing. There's a few more examples of how to use .SyncIgnore files in the Unofficial FAQ

Has your read-only computer always had a read-only secret, or did it originally have a full-access secret? If both devices had a full-access secret initially, and then during the initial indexing/sync, one device was changed to read only, this could explain why the remaining full-access device thinks it still has data to transfer? If you restart BitTorrent Sync on both devices, does it still show outstanding data to be transferred?

Yes! Your data is encrypted in transit, therefore BitTorrent Inc have no access to the physical data you're sharing. However, if you're intending on syncing critical/sensitive company files, please do bear in mind that this software is currently only in "alpha"

That's because at this time, there is no solution! - please bear in mind that BitTorrent Sync is currently only an "alpha", and therefore may not have all the functionality you'd personally like at this time. As there is currently no solution, discussion of potential solutions for future versions (given that the developers do read these forums), seemed appropriate!

That is correct

Please see "When a file changes, does BitTorrent transfer the entire file again, or just the part that's changed?" in the Unofficial FAQ

At a guess, I'd say the ".bad" files are created by BitTorrent Sync as a result of failed/incomplete/corrupt transfers?