>I think you miss the point:
Not really I think, but maybe I did not make myself very clear. Let's try again using your table and adding what XP home and XP Pro currently would support:
1 cpu no HT.................1 CPU.....Home & Pro (1 core)
1 cpu with HT...............2 CPU's...Home & Pro (1 core)
1 dual core cpu no HT.......2 CPU's...Only Pro (2 cores)
2 single core cpu no HT.....2 CPU's...Only Pro (2 cores)
1 dual core cpu with HT.....4 CPU's...Only Pro (2 cores)
2 single core CPU's with HT.4 CPU's...Only Pro (2 cores)
Basically HT is "free" from a licencing POV, and dual core for the moment is just considered dual cpu.
Windows XP can differentiate between a (single) hyperthreaded cpu and a dual cpu IOW, XP, unlike 2WK can differentiate a logical core from a physical one, and support for the logical ones is "free". This is unlike windows 2000 however, so if there had been a "single cpu windows 2000 'home' version", it would NOT run on a P4 HT, at least not with HT enabled.
Windows XP however, can not AFAIK differentiate between 2 cpu's (smp) and one dual cored cpu. In fact I'm not sure *any* OS (let alone app) could, as a dual cored cpu simply is two cpu's on a single die. At least not without using tricks like reading the CPUID and making *assumptions* on its packaging (like two chips, or one dual core chip). From an OS point of view, wether a system has 8 physical cores arranged in a 8 chip configuration, 4 dual core chips, or 1 or 2 MCM's with 2 or 4 cores per module is completely transparent: its always 8 physical cores (possibly more logical ones).
It is an interesting point though, since if future intel based offering would require dual cored chips (dothan based) to be competitive with single cored AMD solutions, this will hurt. Maybe not so much for most of us enthousiasts that will run XP PRo on a single cpu system anyway (so we already have a "spare cpu licence"), but definately in the consumer market where XP Home rules, in the workstation market where XP Pro would not support dual chips (4 cores) and even more in the server market where most software is licenced per cpu/core.
Wether or not microsoft will change its licensing policy in this regard is anyone's guess, but my guess is :no. At best they might expand XP Pro to support up to 4 cores on but AFAIK, Oracle, or any other server apps considers dualcored chips simply as two cpu's,and quad core/single MCM systems as a 4 cpu system, and therefore you pay licences accordingly. I don't think MS is going to give dual core opteron or dothan based servers a nice discount by effectively letting customers pay a licence for a system with only half as many cpu's. If they would, rest assured dual cored server chips would sell like hotcakes, and unless you're running opensource/free software, you'd be nuts NOT getting dual cored chips.
Is this more clear now ?
= The views stated herein are my personal views, and not necessarily the views of my wife. =