If you ever used svn command line, you know it is not optimal to type in your password every time you do checkout, checkin, info, etc.  In linux world, it is very easy to setup keys to get around this.  Of course in the world of Windows it is not as easy.  Here are the steps you need to follow to get private/public keys working with your SVN under Windows using ssh tunneling.

Assumptions:  you will be connecting as user “root” to svn server located at “10.0.0.1”.  All your files will be saved at c:\ including your svn command line utility

First we will have to generate a key.  We can accomplish this by using a free utility called …

Now since I reinstalled Vista 32bit version and its up and running, lets go through what works what don’t.

1. Daemon Tools (check)
2. Microsoft Office (check)
3. Trillian (check)
4. VMWare Server (CHECK!)
5. Diskeeper 10 (Nope, apparently I have to go download an update for Vista, postponed)

Ok now the fun part starts. How to get everything working the way I want to.

I need to start my Fedora virtual machine so I can get some development/testing done. And a wall I hit. It says that I don’t have permissions to open the file. I am logged in as a user which belongs to Administrators group. So why do I not have permission? Well let me copy it to desktop and see if that works. Voila! it does! Ok.. I will let this one go since I have already wasted my whole weekend getting Vista going.

OK.. so lets change my hosts file so I can point some domain names to …

While looking through my new Vista, I found out that my cpu is 64bit capable! I was like.. OMFG hell yeah! I whipped out the 64bit Vista DVD and nuked all my hard work of setting up software without even giving it a second thought… About 20 mins later, I was back in my new found love, except this time I dove right into installing software. One by one, I get basic stuff installed in following order:

1. daemon tools (went out and got the upgraded vista version) no problems
2. Microsoft Office 2007 ultimate, uh.. thank god no problems there
3. McAfee VirusScan, ofcourse problems.. knew that from 32 bit version but what the hell.. was worth a try
4. Trillian - another no problem
5. VMWare Server………………………………………….PROBLEMS! Sigh.. they don’t support 64bit Vista. Who would’ve known? They support installing 64bit version as virtual machines but then why they don’t …

There I was sitting and working and minding my own business when I heard bunch of noise outside of my office. So I took my headphones off to tune in to the conversation. One of the developers has gone out and bought Windows Vista Ultimate edition and was talking about installing it and trying it out. I have always tried out all of the Windows flavors since 3.1 as soon as they came out and even did beta runs for NT 4, XP, 2000, 2003 and even Vista. But for some reason after installing and running beta 2 of Windows Vista, I wasn’t very impressed. But when they were talking about installing Vista, I myself got curious to find out how good/bad is the released version. So I went and got myself a copy of Vista Ultimate as well.

I didn’t want to destroy my laptop so I decided to install it on my old computer. The specs of that computer are:

Intel Pentium 3.2 with hyperthreading, 2 gig ram, Nvidia GeForce Ultra with Dual DVI

…