James Kendrick says Spybot Search and Destroy eats Tablet PCs.
If you have a Tablet PC, better look at this one.
James Kendrick says Spybot Search and Destroy eats Tablet PCs.
If you have a Tablet PC, better look at this one.
When I saw this picture of the Fanatec heäd$h0t mouse/mousepad combo, I first thought it was a parody.

I couldn’t figure out whether this description from Crunchgear was inspired satire or straight-up rave-up:
[T]his mouse is designed for gamers with OCD and is comprised of the mouse, the mousing surface (mousepad), and an arch to hold your mouse cable. The base itself is a two-port powered USB hub, which means it needs an AC adapter.
[,,,]
All in all the mousing action is really smooth thanks to the mouse + mousepad combination, and is a great deal for $100. If not for the fact that we already have a few Logitech gaming mice sitting around here, we’d pick up one of these in a heartbeat. But if you don’t like making your desk look like the Joel Schumacher Lego Batman Starter Set, this may be a bit garish for you.
And then I looked at the folks who run Crunchgear (be sure to scroll down). Ah. Now I understand.
I’m researching a story about digital media and am interested in any stories you want to share about how you use digital media in the living room.
Do you have a TiVo? A Media Center, with or without extender or Xbox 360? A cable or satellite company DVR? Have you connected an iPod or other music player to your home stereo? Do you use a third-party program like Sage TV or BeyondTV?
If you don’t currently have any of this hardware, why not?
A handy Microsoft page explains the ins and outs of Multicore Processor Licensing. Short version: Windows is licensed on a per-processor basis, not a per-core basis. So, despite the fact that the operating system treats individual cores as if they were separate virtual CPUs, the license agreement does not:
The customer will incur the cost for one software license per processor, not per core. So if a customer replaces the single-core processor on their system with a multicore processor, they will need to have only one license per processor.
[…]
Microsoft Windows XP Professional and Microsoft Windows XP Home are … licensed per installation and not per processor. Windows XP Professional can support up to two processors regardless of the number of cores on the processor. Microsoft Windows XP Home supports one processor.
This also means that quad-core processors (due to hit shelves in November) will not cause any licensing problems. Nor, in fact, should the 80-core processors Intel says it will have within five years.
(Via Raymond Chen)
… And I almost forgot this article on Windows Vista’s support for 64-bit and dual-core CPUs.
Thanks to everyone who played along in yesterday’s troubleshooting quiz.
The consensus answer was correct: My video card had come loose and needed reseating in its slot.
Clue number 1 was the complete absence of display on the screen. That could have meant that the monitor(s) had become unplugged, but the power lights were still on, so that clearly wasn’t it. Any kind of software failure or a corrupted hard disk would have allowed the Power-On Self Test routine to appear on screen before failing.
It had been a warm day, so I considered the possibility that the machine had overheated. But if that were the case I would have known it, because the fans would have been working overtime right before the failure. And the fact that it didn’t restart even after a proper cooling-down period ruled that out.
Memory errors? Those usually result in visible failures – random crashes and misleading error messages. I wouldn’t expect bad RAM to shut down the whole video subsystem.
That left two options: Motherboard failure (bad) or problem with video card (not so bad). I strongly suspected the video card because of the three beep tones. This is an Intel board, as I pointed out obliquely in the description of the problem. I turned to a handy list of error messages associated with each beep code on this machine. (If you have a different BIOS, visit that page and follow the links in the sidebar.) Three beeps – one long, two short – means a video adapter problem.
I unplugged both monitors, removed the PCI-e video card, visually inspected it to make sure nothing was obviously wrong, and reseated it in its slot. When I turned the computer back on, I had a signal to both displays again. If this step hadn’t worked, the next option would have been to try another video card.
So, how does a card come loose in the first place? Well, this machine has been jostled around a fair amount in the past few months as I’ve swapped out various components (network cards, hard drives, TV tuners) while testing Windows Vista. In all that moving, I never fiddled with the video card. But it obviously had come loose enough (a micron here, a micron there, pretty soon you’re up to half a millimeter) that one slight motion did it in.
Props to Carl, who was first to suggest this solution.
No prizes this time, but next time I’ll give away a book or two and make the challenge a little tougher.
Ah, the joys of hardware!
Last night, as I was reaching the end of the first shift (5:00PM, which is followed by a dinner break and then the second shift – ah, the joys of writing books about beta software), my computer screen suddenly went black. A second earlier, I had a half-dozen apps open, and then … nothing.
After trying in vain to make something reappear on the screen, I pressed the power switch, held it down for five seconds, and waited as the computer restarted. This time I heard, from inside the case, three faint beeps. Nothing appeared on the screen, however. And I mean nothing. No BIOS messages, no Intel logo, no prompts from a storage adapter … nothing.
I took the cover off the computer, powered it on again, and checked inside. Everything looked normal. All fans were working, I could hear chattering noises from each hard drive at startup, and nothing was emitting smoke.
Eventually, I solved the problem. What troubleshooting did I have to do, and what was the solution?
All the information you need is in the post above.
Update: I have two monitors attached to this system. Both went black at precisely the same time, and the power light remained on for each one. So no, the solution wasn’t as simple as plugging in the monitor.
There have been some good comments so far. The correct answer might even be in there already. I’m going to leave comments open for the rest of the day to give working folks (especially those who can’t check this site during the workday) a chance to take a crack at it.
Update #2: This is not the same computer that experienced memory problems a few weeks ago. That was a Dell server. This is a desktop machine that was built by Mwave in August 2005.
OK, here’s the answer.
Thomas Hawk understands the power of the Reality Distortion Field:
Now I know what some of the Appleheadish types will say. C’mon it’s Steve Jobs. He’s a marketing genius. If anyone can do it Apple can do it. Apple is so damn cool it makes me want to melt down in a puddle of tears as I weep translucently at how amazingly magical their ultra hip marketing department can name things. How nobody cares about HDTV and how people will accept inferior sound quality over at iTunes, so why not with movies.
As we like to say in the reality-based community, read the whole thing. And chuckle.
… Oh, OK. I can’t resist quoting the punch line: “Yes, idiots overpay for things. Yes, there are a lot of idiots out there and yes Steve Jobs may be able to use the Obi Wan Kenobi trick voice with some, but I predict this thing [the iTV] will flop hard.”
Who knew that Macs have their own Blue Screen of Death?
Update 24-Jan-2010: The Customer Advocate e-mail address mentioned later in this post has been discontinued. However, Dell still accepts comments from customers and will act on them in timely fashion. If you’ve been through the regular support channels and things aren’t working, go to the Outstanding Issues page and fill in the form. This is not a first-line support alias. You’ll need a case or reference number.
It looks like Dell has officially launched its Cluefulness 2.0 program. I got wind of the pilot program last April when I received an unsolicited phone call from a Dell support executive over a horrible support experience I had had. My issue had eventually been resolved, but it had left a bad taste in my mouth.
In the past few days, I’ve seen more signs that Dell is figuring out how to find unhappy customers and try to make things right. This November 2004 post, Memo to Dell CEO Kevin Rollins, turns up at #1 on the Google search results if you look for Kevin Rollins email address. As a result, the comments section has grown into an impressive collection of complaints about Dell service and support. Last week, a Dell employee named Richard added this comment to the thread:
Ed, we are reading comments like this. In fact, we have a specialized team that reaches out to fix individual customer issues, and then goes back to look at where we made mistakes internally. We arent where we want to be yet, but we will get there. Just in last few quarters we have committed over $150 million to improving customer service, recognizing publicly that we had let issues like these get away from us. We have hired more staff, opened new support sites, retrained staff and are very focused on regaining our leadership by solving the custtomer issues the first time they call.
They’ve even gotten some grudging praise from Jeff Jarvis (here and here), whose foray into Dell Hell has been well documented.
And today I got a personal e-mail message from the same executive who contacted me last April:
I want you to let us know if there are any customers in need on your blog. Our outreach team will be glad to help them as quickly as possible. They are some of our very best people and are ready to help. Their email address is Customer_Advocate@dell.com.
I would be glad if you shared this email on your blog for any in need.
Consider it done. I’m nearly ready to purchase a new PC, and Dell has made it back onto the short list.
Thomas Hawk is trying a tech support experiment, in which he posts problems with his PC and then requests help. Instead of posting in his comments, I’m going to cover one of his problems here:
Problem number 1. My computer seems to be inexplicably freezing up (yes it’s a Windows machine, I know, I know, get a Mac) periodically. These are really bad freeze ups. Control-alt-delete does not return my PC. I can’t alt tab. Total freeze up. The only way to get my computer back is to restart. The last time it happened I had Pandora on in the background (but this is probably just coincidence) the music even stops and stutters as the freeze happens. The most recent thing I’ve installed is Windows new Live One Care. My next step is going to be to uninstall Live One Care and see if that helps me out at all.
By a curious coincidence, the same thing has happened to me within the past two weeks. Based on the symptoms, Thomas’s problem has nothing to do with software and everything to do with hardware. Here’s my story, and how I resolved it.
I have a Dell PowerEdge 600SC server running Windows Server 2003. It’s about 3-1/2 years old, and it has been running nonstop with virtually no problems for all that time. Over the years, I’ve added some big hard drives, and about a year and a half ago I replaced the original 2GB of RAM with 4GB so I could run multiple virtual machines on this box.
For the past month or so, this system has been responding slowly on some activities, especially file copies over the network. Then, about two weeks ago, the server froze up one day. Simply stopped responding. The power was still on, but the screen was black and the system didn’t respond to mouse input. I pressed the power button to restart, and when it came back on, I checked the System log in Event Viewer to see if there were any events captured there that might shed light on the error. Nope. Every recorded system event up until the crash was perfectly normal.
(Note to Thomas: Be sure to check Event Viewer. From Control Panel’s Classic view, double-click Administrative Tools, then double-click Event Viewer.)
The fact that there were no events listed is actually a crucial troubleshooting piece of information. It means that whatever happened was a complete surprise to the Windows code that’s running in kernel mode and supervising the whole system. Essentially, it means Windows was mugged.
A few days later, it happened again. This time, when I restarted, I booted into Dell’s Diagnostic Utilities partition and ran its comprehensive series of diagnostics. They showed no hardware problems. I also ran a quick memory test that showed no problems. Baffled, I restarted the system. Maybe it’s a failing motherboard, I thought, or a system that’s overheating.
When it happened again the next day, I decided to run a more comprehensive memory test. And sure enough, when I ran the full suite of memory tests included with Dell’s diagnostic suite, I found that the error correcting code (ECC) in one of the server’s memory modules was causing unrecoverable errors. Now, an unrecoverable memory error is bad news and would completely explain why (1) the system was locking up and (2) the lockups had no apparent relation to any software running.
Using another diagnostic tool, I ran a different suite of tests, which showed that the fault was in the memory module in DIMM slot A. This particular system has four slots, each with a 1GB stick of RAM in it. The RAM is installed in pairs. I wasn’t sure which slot was DIMM slot A, so I took out the modules on either end and then reseated the other two DIMMs in the remaining slots.
I restarted and ran another memory diagnostic. This time the system passed with flying colors. I now a highly confident that one of the two modules I removed is defective. They’re still under warranty, so I should be able to return them for replacement.
Lessons learned:
Most system and application failures are fairly easy to identify. Random failures often indicate hardware problems.
Bad RAM, overheating, and defective hard disks, in order, are the most common hardware failures in my experience.
Hardware can fail over time. Most people assume that the problem is software because they haven’t changed any hardware lately
Hope that helps, Thomas!