Connecting to Nexus 7 device for debugging on Windows 8.1

While the instructions Using Hardware Devices and OEM USB Drivers are adequate, here's my experience setting up my 2nd generation Nexus 7 on Windows 8.1 Pro.

When connecting the device to my computer's USB port, Windows does recognize it and installs drivers, but treats the device as a Music Player:

At this point, adb does not recognize the device for development purposes:

However, after following the instructions for the Google USB Driver, I get the following: 

and from adb, I do see the device listed when doing the command "adb devices".

PostgreSQL server starts up but then stops immediately

On Windows, starting through the Services window will indicate the above with a message similar to "The PostgreSQL Server 8.4 service on Local Computer started and then stopped.  Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service".


Check the Event Viewer (shortcut:  Type "eventvwr" in Start > Run). In my situation, the data directory I specified at installation time appeared to not exist as indicated by the error message "FATAL:  data directory "XXXXXXXXXXXX" does not exist".  However it appears to be a permission problem, as the directory indeed existed. 
 
The easiest solution is to uninstall and reinstall and specify a directory that you know the postgres user ID will have no issues accessing (e.g. the default data directory suggested by the installer)

Subversion over SSH on Windows: Folder '' does not exist remotely

Setting up SpringSource Tool Suite on Windows 7, when attempting to connect using Subclipse to SVN server with a URL of the form svn+ssh://, get the error "Folder '' does not exist remotely". 

Some people have had luck with HowTo: Configure SVN+SSH with Subclipse on Windows but I kept being prompted for username/password with each folder navigation in the SVN repository (unworkable!).  One of the comments in the blog referred me to Subversion Access from Eclipse Using Subclipse which worked for me although I continue to use username/password (saved) rather than public/private key as the latter method didn't work.  I probably have the key saved improperly on the client and/or server side. 

Other problems that I had as I accessed our SVN server over a VPN:

• hostname wasn't resolving so I had to find out the IP address of the SVN server and use that in the URL
• Attempted to use TortoiseSVN as it supposedly handles svn+ssh:// out of the box but after installation and rebooting Windows, still couldn't find the TortoiseSVN menu in the context menu in Windows Explorer