voyager529

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by voyager529

  1. Hey everyone! So, I've got a small group of folks with whom I've been using BT Sync for about a year now. They all have Windows machines of one form or another, but they all sync back to a Nas4Free box running BT Sync as an init script. This has worked wonderfully, everyone's happy, rainbows and unicorns abound. Until last night. One of the users was running a vintage 2007 (i.e. Vista-era) small-form-factor HP, which needed to go. So, I made her a custom build - Biostar mobo, 3.4GHz Core i5, 16GB of RAM, Win7 x64, 240GB PNY SSD, and a 1TB WD Black drive for data. The thing flies like it's got the cops on its tail - from bootstrap to desktop in nine seconds. One point of contention I'm hoping to rectify this year is that she's stuck using wi-fi due to the building layout...but she's using a dual band Hawking Technology USB adapter that's correctly configured for the Asus RT-N56U router it connects to, so she gets 13MBytes/sec real-world throughput, so it's no slouch in that respect. I had the machine built out PERFECTLY, with all her software and data where it should be, all that was left was to get BT Sync set up. Well, I did that...and when it was syncing, there was mouse lag. BOY was there mouse lag. I'm talking 1.5 seconds of cursor lockup, only to appear roughly halfway between "where it should be" and "where I last saw it". A few people who experienced mouse lag like that suggested that it might be the NIC. I didn't happen to have a spare wi-fi adapter with me, and the overlap between "stores that sell wifi adapters" and "stores that are open at 1AM" is rather sparse. I did try reinstalling drivers, using the Hawking utility rather than Windows, going between the USB 3.0 controller and the 2.0 controller, swapping out the mouse for another one, fiddling with the interesting options in the driver control panel, updating Flash Player, etc. Then, I paused Sync. All lag went away completely, no problem. Started Sync again, lag city. Killed the process, no lag. Started process, lag. With BT Sync as the only variable, and a very consistently reproducible problem, I decided to address it in the Sync config panel. If it was an option in Sync, I tried it - increasing buffer size, decreasing buffer size, manually specifying the host, enabling/disabling UPnP, low/high disk priority, encrypt/decrypt LAN traffic...everything that seemed relevant. No love. I ensured that both the NAS and the computer were running the latest build. Still the same situation. No other computer in the network exhibits this issue, including the old one. While I'm willing to replace the Wi-Fi card, I'm hesitant to do so because it would seem a bit strange for the card to be the problem when it's the exact same unit I pulled from the old machine. If it's a setting issue on Sync, I'm certainly willing to change it; I took guesses at everything I was trying to sync. Please let me know if anyone else has experienced this issue, or if I can provide further information to assist in solving the problem. Best regards, Joey
  2. Another +1 for this feature request!! If multiple computers are storing a /music, /documents, /desktop, and /photos folder to a single machine, you end up with multiple 'desktop' folders and get stuck with trial and error. Renaming shares as "Alice - Music", "Bob - Music", and "Carole - Music" would be a huge help!!
  3. Hey everyone! Huge BT Sync fan/user here, it's been a life saver. Presently, I run BT Sync on my NAS. I've got several computers syncing to my NAS in different datasets. Life is good. Generally, I set the NAS up with read-only keys, but read/write keys on the machines. This ensures that accidental deletes don't get replicated to the NAS, which is nice because it allows the NAS to protect against accidental deletions. The challenge is on the flip side. I've been writing down the read/write keys, because if I don't, I can't reconnect the machines to the NAS if I need to reinstall Windows on any of the machines backing up to it. What would be excellent is if I could have read/write keys on the NAS, but have an option where the NAS /behaves/ as if it is in read-only mode. This serves two purposes. First, it enables me to use the NAS as a reference, in the event I need the keys again. Second, it allows me to set the NAS into read/write mode when it's time to restore data to the machines on the flip side of a reload, so that data can flow normally from the existing share. Finally, I can set it back into read-only mode when the process is complete. Thanks! Joey