Actually, I'd like to interject at this point. (Well, I'd have prefered to have done it sooner, but I only just got around to reading through this thread.) As a software engineer and occasional PC maintanance and hardware tester for a company that sometimes works with some pretty weird $#!7, I've run into problems like this before.
Believe it or not there <i>are</i> drivers out there that will totally crash when run on any sort of a multi-processor Windows. So any dualie system running NT or better, or now with HT-enabled CPUs any modern single-CPU system running NT or better (though it's usually just done on XP because it's the only M$ non-server OS that supports HT correctly) will cause these drivers much grief.
Now, you might think that's stupid. It should never happen, right? Well, you're right. It never <i>should</i> happen. However, sometimes computer programmers are lazy sots. In the cases of drivers like these, the drivers are written under the assumption that they can access the CPU directly without having to first ask the OS <i>which</i> CPU is running their code. Should the driver code end up being processed under an assignment that wasn't hard-coded into the poorly-written drivers, <b>CRASH!</b>
So basically there <i>are</i> some drivers out there that just can't be run under <i>any</i> dualie or HT systems because the drivers themselves are hard-coded to access the processor directly. It's bad coding. These are drivers written by either lazy sots or unskilled monkeys. Take your pick. Either way, it's pretty sorry for a software engineer to have made such assumptions, and it's even worse that the manufacturer of the product which uses these poorly-written drivers doesn't at some point re-write the drivers to run in a multi-processor configuration.
It happens. It's pretty rare, and it's incredibly sad, but it does happen. It is in no way Intel's fault. It does not prove that HT is faulty. It is in no way Micro$oft's fault. It does not prove that M$ can't write a stable OS.
<i>It is <b>entirely</b> the fault of the <b>idiot</b> who hard-coded the driver to only access the first CPU when they wrote the driver.</i> And it is <i>entirely</i> the fault of the hardware manufacturer for <i>not</i> making sure that the drivers were written right in the first place, for <i>not</i> testing the drivers thoroughly, and for <i>not</i> taking the time to fix their drivers when the problem is discovered. So blame the manufacturer of the hardware that has the faulty drivers because it is completely, totally, and irrevocably <i>their</i> fault and their fault <i>alone</i>.
Frankly, it's an issue that pisses me off greatly because the company that I work for has had to deal with a hardware manufacturer that refuses to fix this flaw, and thanks to a certain mutual-exclusivity contract that gives us and them both certain benefits we can't just go with another manufacturer instead.
"<i>Yeah, if you treat them like equals, it'll only encourage them to think they <b>ARE</b> your equals.</i>" - Thief from <A HREF="http://www.nuklearpower.com/daily.php?date=030603" target="_new">8-Bit Theater</A>