palpable

Synkron is entirely innocent in this, it never actually got to run and in any case was only intended to perform a scheduled copy of *.txt once an hour. Whatever happened was beteween me and BTSync, and tbh I'm a bit baffled about what transpired. I've done my best to explain what I did, but I'm at a loss to see how thousands of nested directories could be created and replicated. I'm sure I could set up an individual sync for each of the 20 or so subdirectories of \Hardware, but that's hardly a convenient way of working. I thought I had done "investigate using .SyncIgnore", before embarking on this- I read both the offical and unofficial FAQs and looked through these froums. I didn't find anything detailing the exact syntax I should use, nor any discussion of how to achieve what I was trying to do. If you know where that info is, please point it out.

Hello, here's a cautionary tale.. I have a directory \Hardware which contains subdirectories for each of my toys. I set up a BTSync task so the whole of \Hardware syncs between my main W7 PC and a new W8 netbook. However I also want to sync \Hardware\Phone with my phone but when I set up a new task I got the error message "This folder cannot be added to BitTorrent Sync as it is part of a folder that is already syncing.". So I made a new directory "\Hardware\Phone\_BTSync to Phone" and set up a little utility called Synkron to copy relevant files into it. Then, after deleting the PC sync task, I excluded the new directory using \Hardware\.SyncIgnore. Or at least, I thought I did, although the syntax isn't entirely spelt out in the faq it looked obvious enough, just add a line D:\Hardware\Phone\_BTSync to phone Then I recreated the PC sync task and er, and then I had a nested directory \Hardware\Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone\_BTSync to Phone recurring forever. Happily this was replicated on both PCs Then ensued a long scouring of the web for how to delete folders whose names are too long for Windows to cope and many, many fruitless attempts, including downloading dodgy utilities <avoid http://longpathtool dot com/ it's a scam>, following MS Technet threads, making batchfiles I barely understood, using Robocopy and Total Commander and even booting into Linux and using rm -fr * In every case the names were too long or the directory tree was in use, or both. On the main machine I've eventually had to admit defeat, make sure the backups were all up to date and reformat the drive, which has worked. And, praise be to Acronis, the restore worked. Easy with a data drive, not so convenient when the system & data are both on the same drive. I may have to factory reset the other machine, which is only a few days old so there's nothing significant to lose, except my time. So don't do this at home kids, it's not hugely enjoyable For the time being I've disabled BTSync until all is back to square 1. I don't think what I was trying to achieve was unduly ambitious, so if anyone has any (obviously idiot proof) ideas as to the best way I'd be most grateful.