GREAT advice - I have done my development this way for 3 1/2 years now and my experience is also with VMWare workstation. Until very recently, it was the only way to go. VirtualBox is good for 32 bit Windows VMs as long as you don't need external hardware to connect to it. Also, one other tip I would give on the hardware is this: Add up all the memory of all of the virtual machines you MIGHT run at the same time, then double it to get the amount of memory for the host machine. Any less than that, I have found does too much swapping and memory switching - i.e. performance suffers too much. So for example, say you want to run 3 512 MB vm's at the same time. This becomes 1.5GB. The host should then have 3GB MINIMUM. Also, unless you are using small memory footprint VMs, I would highly recommend a 64 bit OS on the host so that you can have as much memory as possible and you don't have to swap out the host OS when you want to upgrade its memory later. For the host, I have used all of Microsoft's 64 bit OSes, XP x64, Server 2003 x64, Vista x64, and Server 2008 x64. One thing I have used it for extensively is for installation testing on a clean machine. Snapshot the clean machine, do your installation testing, and revert it back to the snapshot after each test. Awesome for that - I used to have to do this through ghosting the machine and then bringing back down the image. A lot of waiting there - now, it is just a click of a button to do the same thing. David