pdxrlk

Thanks for the reply, yes the machine blue-screened several times before I noticed this. I ended up re-linking the device. In order to correctly link up the directories across multiple disks I first disconnected each folder (Deleting the placeholder files in the process). I then connected and specified the correct directories, and sync'd. All is good now.

My main workstation ("A") has btsync 2.0 installed for many moons now. There are multiple other nodes including a Raspberry Pi which has all of my sync'd folders and they are working fine. btsync on machine A seems to have lost its marbles. Today I brought up the btsync window on A and instead of the usual list of directories, I received the initial "Link Devices" windows (which is used initially to tie the btsync instance to a device already running Sync 2.0). I'm stumped - how do I debug this? Is my only recourse to re-link this device? That's a bit of a pain as I have directories spread out over multiple disks and Sync 2.0 doesn't handle that as smoothly as 1.4 did and there are about 20 synced directories.

I disagree. In 1.4 I could create a folder ("folderName") on machine A, copy the key and then use that key to set up a sync folder on machine B. On machine B I could use that key to link to a folder with any arbitrary name ("folderName-from-machineA"). In 2.0 there doesn't seem to be a way to do this - it's called "folderName" everywhere (and what's worse, it insists on placing it in the default BitTorrent sync directory, so that I can't spread folders across drives).

In 1.4 I set up syncs so that each of my windows "Desktop" folder was available on all devices. Each folder would be available as a sync folder called "machineNam-desktop" (which is different than the actual folder name on the initiating device, which was called, of course, "Desktop"). In 2.0, however, sync names are the same as the folder names, and there doesn't seem to be any way to change that. So, for example, if I sync "Desktop" on machineA, then all linked devices will see this as "Desktop". If I want to make machineB's desktop folder available on other machines, I'm screwed. Is there any way to implement this in 2.0? I realize it's simpler to keep sync names and folder names the same, but it's also limiting.