Another vote for x86 (32-bit) after finding out a few production applications (including my choice for security) are not compatible with x64.
Shakes, I am sure they were problems I could have overcome, but I decided to go with 32-bit for the time being. I plan on going back to 64-bit within six months.Really? We've been hacking away, got most of our shiz running now.... not going to move to it for another year, but it's testing well (VPN, AV, Remote Toolz we use...)
Let me know what you are having trouble with... the Cisco VPN took a bit of tinkering...
It's just ironic that MS calls this the 'gaming' OS, then.How soon we all forget: 75% of the games didn't work under XP when it first came out. Why do many of you fail to realize it is no different?
good point, you're probably right, but don't those games exist for xp?That's a bit of a huge overstatement there. I can guarantee that a lot of the up-and-coming games will NOT be 64-bit simply by the fact that 64-bit drivers are a pain in the arse and most 'gaming' hardware tend to release the latest drivers on the 32-bit platform, not the 64-bit. 64-bit gaming is usually an afterthought, once the company has released their game out for a few months.
Prime examples: Half-life 2, Far Cry
Also, Vista (DX10) games are not that far away. We'll start seeing them within the next 6 months. We won't start seeing a huge adoption of 64-bit within that same time.