btsync: How To Download Older Versions

I’m not sure how long these will work, but here are sample links.  Its based on released versions.

I’m going to give the new v2.0 a try, but since they are now trying to monetize that version… And with a yearly license too!!!!  🙁    I’m afraid it will limit my options.

P.S.  I would even consider paying for btsync, if it was a one-time deal… But not yearly.

Issue: Chrome 37 Update Looks Bigger

Normally I’m a big fan of Chrome.  And its automatic updates are also normally pretty harmless.

Then there was Chrome 37 and it made me think I was crazy.  It just looked wrong.  I thought my computer’s resolution somehow got messed up, but I checked and it was good.

And then I did a little googling and came across the answer!

“XXXXXXXX\chrome.exe” /high-dpi-support=1 /force-device-scale-factor=1

After making the updated to my Chrome shortcut and re-ping it to my taskbar in Win7, everything went back to normal, which is all that matters in the end.

Hopefully this is not a permanent change from Google.

Synology, Raspbian, NFS and Nobody…

It took me a couple of weeks (or months) to… Not fix a problem… Even discover that I had a problem.

Once I discovered that I even had a problem… And I have a feeling this issue has been causing me a number of permission annoyances… I was able to use some “Google-fu” and resolve it in less than an hour.

With the actual fix taking < 5 mins.


From one of my Raspberry Pi’s running Raspbian I was seeing files with weird ownership info… Specifically files were owned by “nobody”.  I suppose I originally considered this a quirk of NFS… But then I noticed that this same thing was not happening on my other Pi.

The problem presented itself via many annoying “access denied” or “operation not permitted” failure messages when working in NFS mounted directories.

The final straw was when I could not run dos2unix successfully on a text file.  Such a simple operation… Very interesting, especially when I stopped watching TV and paid more attention to the error message.

dos2unix: Failed to change the owner and group of temporary output file ./d2utmpte0dzV: Operation not permitted


The fix is very simple… Force my clients to connect via NFSv3 instead of v4.

In /etc/fstab I added the option “nfsvers=3” to all my mounts. /public nfs nfsvers=3,rsize=8192,wsize=8192,timeo=14,intr 0 0

Once added and re-mounted… Either manually or via a quick and easy reboot… Things started working as expected.

Additional Thoughts

This issue was the result of new behavior.  I recently updated my Synology DSM from v4.2 to v4.3.  I have a feeling that this enabled NFSv4 on my Synology NAS.  This could explain why I was seeing things differently between my Pi’s… I’ve been working on and rebooting one often lately, but the other has been up for many weeks and once the NFS mount is established I’m pretty sure the version does not change.

I believe I saw results for bugs and issues related to NFSv4 along this same vein that were not Synology related… So this issue may not be specific to Synology’s NFS support / implementation.

During my troubleshooting I had a need to confirm that the NFS version could be the issue… So I obviously needed to confirm what version of the NFS protocol was being used.  The quick and easy command to determine that is “nfsstat”.

Multiple Windows 7 Crashes (Possibly Resolved)

My laptop has crashed 3 times in the last 24 hours on my Asus G73J with Win7.

  • I usually put it into hibernate over night, but left it awake and in a power saving mode to allow it to finish syncing with a server.  The next morning it was off.
  • Put it to sleep while not in use.  Came back and it was off.
  • Don’t recall the 3rd incident… Probably similar to the 2nd.

So now I’m trying to determine what’s happening and have come across some interesting tools and links.

NirSoft BlueScreenView

  • Got this to analyze the “.dmp” files being produced.  Gives me some info, but after just a few minutes of using it (and obviously becoming a quick expert), it does not appear to provide a root cause of my problem.
  • Looks like it can call a “DumpChk” utility.  Vaguely familiar with this.  I believe its part of a Windows SDK package

Windows SDK Package

  • Found the listed pages to help go further than BlueScreenView
  • Installed the Windows SDK via the instructions on the 2nd link
    • I did get an error for my first install and it is resolved with this page:
    • I had to 2010 versions installed.  I only uninstalled the one that was greater and it worked.
    • Not sure I need to reinstall yet though… Also, after a quick look I could not find it on MS’s website.
  • Now to keep following the first link’s instructions.
    • Instructions from the links about could have been better.  Looked like he was running a linux command, but he was really in the WinDbg program already.
    • Found this link as helpful:

Windows Autoruns

  • In my searching, I found this utility from MS.  Looks like it may be useful… Maybe not for this issue, but still useful.  It analyzes all “startup” programs.  One potential and interesting use is that it supposedly can tell you what programs are being autoran but not longer exist or cannot be found or any other reason why the configured path does not work…

 Possible Resolution

  • So my analysis basically circled back to a driver that I already knew about… I guess I learned some new stuff, so that’s good.
  • Everything pointed to my crashes being caused by:  NETw5s64.sys
    • Googling suggests this is an Intel Wireless driver and said to make sure its updated and suggested using this Intel page:
  • Now time will tell if this resolved my issue… I’m done with troubleshooting for the day. 🙂

WHS 2011 Share Permissions

Issue:  Share permissions are not working as I would like.  I set HomeGroup permissions to “Read” and created a user on the server with the same username as my client and gave this user “Read/Write” permissions.  But I’m only getting “Write” permissions when I increase HomeGroup permissions.

Why is my client not logging in with the username?

Hopefully Google will be kind to me…

Solution: Well, apparently HomeGroup permissions override individual user permissions.  I just tested this by giving myself no access, but leaving HomeGroup as RW and was still able to access my files.  Then when I removed HomeGroup access, I was denied access.  Not how I would like permissions to work, but oh well…

WHS 2011 Network Responsiveness

While the install of WHS 2011 went very well, getting everything setup has taken some extra time and was further complicated by network access being quite slow and unresponsive at times.

However, I may have resolved the issue very quickly.  Or it was just a coincidence and the server likes me right now.

(Possible) Solution:  On the WHS 2011 server, disable IPv6 support for the NIC.  It was that simple and quick.

Assuming this was the issue, I’m now wondering how this was affecting the install of the client software, which took FOREVER.  Could this have made that go faster?

WHS 2011 Install

The install of WHS 2011 went pretty smoothly.

Biggest issue was a little static electricity that froze the system during the install.  Had to start over, but was not far in, so not a big loss. No hardware lost either (silver lining!).

The install automatically partitions the main drive, with no option to change.  Other than the feeling of losing control, I can understand this decision.

The install DOES require a network connection to perform.  Not sure why during… Afterwards when needing to do all the updates (and there are a good number) sure… But during?

I was worried that the Shuttle BIOS would not like the lack of a monitor / keyboard / mouse connected post-install, but it did not complain a bit.  Win!

I did disable “Shadow Copies” on my drives.  Primarily to reduce space usage since I cannot just add more drives to increase space (and got the biggest 2.5″ drives I could find).  We’ve never had a need for this feature, so its not a big loss.

The client connector installs were very time consuming.  The wizard says it could take 30 mins or more… Try well over 1 hour with little feedback that things are even working.  At least this time, patience worked.

One Issue / Resolution: I did hit a small snag when installing the client connector software.  I believe it may have been a conflict with the old client connector software, which I had already removed as a first step.  However, it kept saying that it could not install because of another software install was happening (or something like that).  So I restarted and that solved the problem. I guess there was something still hanging around from the uninstall.