I’m setting up XP on VPC right now, so that I can run Terrarium 2.0 (which doesn’t work on Vista yet).

]]>By: Adam Kahtavahttp://herdingcode.com/episode-8-virtual-machines/comment-page-1/#comment-31
Tue, 15 Jul 2008 12:17:38 +0000http://herdingcode.com/?p=23#comment-31I’m running Hyper-v on a modest 64bit laptop, it’s significantly faster that MS VPC. For example I can run 3 VMs running at native speed, but I do have separate hard drives – my laptop looks like an inverted PC with all the wires and drives hanging out.

For the past year my development has been in VMs, I typically have a Domain Controller, SharePoint Server, and Commerce Server running on separate VMs in an effort to simulate the production environment.

For me, the biggest drawbacks to working on VMs is non standard screen resolutions, I like to remote into my VMs when I can, but when using a VPN I can’t, so I end up working in a VM with a smaller or larger screen size.

On a big screen everything is ok, on a laptop things become painful. I’d like to maximize my screen real estate. Any tips on VPN / VMs and screen resolutions?

Like Dave I’m also running 64bit Vista on my primary dev machine, I did have some issues with video drivers, but once they were updated things have been relatively painless – well… except for weird issue with the keyboard and clipboard. I’m pretty impartial to Vista, I just wanted a 64bit OS, and I think I may install Server 2008 on my desktop for the hyper-v VM performance gains. I’m also toying with the idea of running Linux to make use of KVM.

On both x64 and x86, I have had a few older programs throw up the “This program is known to have problems” dialog. I just ignore it and have had no trouble. Even stuff as old as SQL Server 6.5 Enterprise Manager (don’t laugh) has worked fine. Less Windows friendly apps like SVN and Eclipse have been fine too.

The one program I lost to Vista was CSSVista (ironic). It half way worked on x86, but won’t run on x64 at all. It’s pretty shaky even on XP though, so I have a hard time blaming Vista for that.

Don’t get me wrong. I know you guys don’t have a hidden, anti-Vista agenda or anything. I didn’t mean to make it sound that way.

It just irked me a bit to listen to you guys talk down to Vista, since I was using x64 at the time to listen to the podcast while running a dozen or so development tools and Office products.

]]>By: Dave Wardhttp://herdingcode.com/episode-8-virtual-machines/comment-page-1/#comment-22
Fri, 11 Jul 2008 17:45:45 +0000http://herdingcode.com/?p=23#comment-22It was probably a valid issue at release, but I think you’d be hard pressed to find much recent hardware that doesn’t have signed drivers at this stage. MS won’t sign a vendor’s 32 bit driver without a matching 64 bit driver.

All the drivers for my ~2 year old hardware had signed Vista x64 drivers available about 9 months ago when I installed x86 on this machine.

For that matter, aren’t XP x64 drivers more of a pain to deal with than Vista x64?

]]>By: Jon Gallowayhttp://herdingcode.com/episode-8-virtual-machines/comment-page-1/#comment-21
Fri, 11 Jul 2008 16:55:53 +0000http://herdingcode.com/?p=23#comment-21@Dave – There’s no hidden agenda there. I haven’t used 64-bit Windows since a brief run on Windows XP 64. I found that the driver support was a major problem. I haven’t tried 64 bit Vista, but I have been paying attention to the experience of others who are running it. For instance, Hanselman has more than once reported problems due to running 64 bit Vista: http://www.hanselman.com/blog/Vista64bitBlueScreensWithINTERNALPOWERERRORImmediatelyAfterInstallingVMWarePlayer.aspx

Also, while I understand it can be disabled, the driver signing verification thing seems like a major pain in the neck. I’m constantly reading caveats for things that don’t work with 64-bit due to that or other issues.

Even the current release of Windows Live Writer won’t run on 64 bit – you have to install the Technical Preview of the next version.

]]>By: Barry Kellyhttp://herdingcode.com/episode-8-virtual-machines/comment-page-1/#comment-20
Fri, 11 Jul 2008 16:43:44 +0000http://herdingcode.com/?p=23#comment-20@Dave – probably they’re doing it because it’s true. I have a physical Vista Ultimate x86 box underneath my desk alongside my XP machine, and my most recent laptop came with Vista Business, which I eventually downgraded to XP Pro. There’s no doubt about driver issues – my HP printer doesn’t work right with Vista (spooler crashes), and my trusty scanner (about 2 years old, an old USB Mustek model) doesn’t have drivers for Vista. Also, the Vista UI sucks – it’s the Windows Explorer UI I have the biggest problem with, that along with the way the Control Panel got deoptimized for expert users.
]]>By: Dave Wardhttp://herdingcode.com/episode-8-virtual-machines/comment-page-1/#comment-19
Fri, 11 Jul 2008 16:25:12 +0000http://herdingcode.com/?p=23#comment-19I’ve gotta say that I’m surprised to hear you guys propagate the Vista FUD.

I’m running Vista x64 as my primary development platform, on mostly ~2 year old hardware. I’ve never had any driver issues, even using two video cards.

Granted, having 8gb of RAM probably helps Vista a lot. As cheap as RAM is these days though, I’d expect any serious developer to be headed that direction by now.

I couldn’t imagine going back to x86 at this point, or jumping through convoluted XP+VPC hoops to get back to where I’m already at.

]]>By: Virtual Machines on Herding Code | Lazycoderhttp://herdingcode.com/episode-8-virtual-machines/comment-page-1/#comment-18
Fri, 11 Jul 2008 03:50:54 +0000http://herdingcode.com/?p=23#comment-18[…] posted our 8th episode on Herding Code. We spent some time discussing the pros and cons of using virtual machines in development and for […]
]]>