Seems curious . . .
Rumors fly all the time, so there's no reason to believe this one over any other. On the other hand, Intel likely knows a LOT more about Hammer than any of us, so they know the potential threat that is Hammer like the back of their hand (the front, or palm, is much more complex . . .). Thus, if Intel was worried, I guess it's not THAT unreasonable to think that they included the CAPABILITY in Prescott, just in case AMD succeeded with Hammer, as they appear to be doing, based on Intel's P4 with HT EE. On the OTHER hand, it seems like a HUGE HUGE HUGE sum of money to spend "just in case". So it's my opinion that:
1.) Intel didn't do it, and it's just a rumor or
2.) Intel DID do it and will enable it regardless, and never intended NOT to enable it, or
3.) Intel was taking a MONUMENTAL risk in developing a 64-bit processor "just in case". Whether or not it was monumentally stupid, or monumentally smart remains to be seen.
I don't think Intel is stupid. God knows they've got at least 50 people sitting around with calculators telling the HPIC (head people in charge) exactly how much EVERY option will cost them, and what the chances are that it will be good or bad. I'm sure they were the ones that had the final say in the P4 with HT EE . . . Intel wouldn't have spent that much money developing a chip unless they thought they were going to need it. And if they DID think they were going to need it, then we can already guess they were afraid of Hammer. And if they were afraid of Hammer enough to make an EE version of the P4, then there's no reason to think that they weren't afraid enough to make a 64-bit Prescott, though I really don't think Intel developed two concurrent Prescott chips, one 32-bit, one 64-bit. I guess they have the resources, but that sounds a little too spendy for any smart company.
On the other hand, I'm just an 18 year old college student, so what the he** do I know about Intel's business practices or development?
Z