I started developing all kinds of weird aches when using it in the Apple store, and I guess I just didn't get it. I just use a Logitech MX on my main system, and a Razer Orochi with Flip 3D bound to a side button.

@Kirtay

Nice link! The Engadget site is MUCH nicer now. Thanks.

@sevenbates

Agreed. Dig the site, hate the font.

I have a Dell Studio XPS 1340, and with BIOS A11 it works great under Windows 7. Been sitting through a remote class on WebSphere for the last couple of days with no scratching or popping, even with the crappy TANDBERG client. I listen to music with Etymotic hf5 canalphones, and it's fantastic. So I imagine they'll probably trip over the issue with a BIOS/driver update.

I'm a huge Windows fan, but I don't see how they're alike or how one is much more stable than the other. I prefer the greater flexibility and control of Windows, but I can see why people run OS X (I've used it off and on for 4 years, with SL in a VM right now). If you have good hardware and drivers, both OS are fine. I've also trashed both with crappy hardware and poor drivers. I've been annoyed by both with their respective admin prompts while at the same time appreciating the security aspect. Different, but the same.

I love that line. :-)

Windows 7/Ubuntu/RHEL user.

Cool, as I like Warhawk and my daughter loves Katamari.

I "downranked" you because you're a moron. Semper Fi.

So when George Lucas needs more money and releases another Star Wars, will these be in the bar scene? :-)

Yes and no on HDS being on the hook for backups. I use HP XP12000 arrays (same as the HDS Tagmastor) and we routinely contract with HP for a variety of work done on the arrays. It all depends on the contract terms, but most vendors (such as HP) with push to make sure there's a recoverable backup on site before touching anything, along with doing a site survey of all the systems, adapters, and firmware levels of everything connected. Yes, it's incredibly complicated but migrating between arrays can be a fairly simple and routine task. My guess, having lived through a variety of things like this, is that the data owner didn't have a reliable, recoverable backup and the SAN vendor couldn't help. It could be that they have the data, but no way to recover and migrate it. This is something we may never know fully about.