So i just got my first x64 computer up and running. The specs of the machine are awesome. 16 GB RAM, Quad Core Xeon processor, Windows X64 with upgrade disk to Vista 64. The best thing is I still have 4 Ram slots free and a spot for another quad core processor if this configuration doesn't quite have the horsepower I need. I also have a 250 GB SATA HDD installed with room for 3 more, but storage isn't my priomary concern here, so they will likey remain unfilled.

This machine is mainly going to be used remotely, by multiple users concurrently, so I wanted something that could handle that kind of abuse. Its kind of an experiment, but if I can make it work the rewards should be a pretty sweet solution to a problem that has been plaguing me for a while.

Now for the shock. Its not as natively fast as I expected. However I haven't yet installed the software to see how it performs. Windows logon is sooo slow. Though once it finally logs in it performs as expected. I'm tempted to try Vista 64 to see how it compares, but for now I'll stick to x64.

The most shocking thing I've found is some pisspoor naming of stuff by Microsoft Programmers. The OS is a bit schizofrinic in that it has 64 bit OS folders as well as 32bit OS folders. They do this, so you can still run 32 bit apps in the 64bit environment. What's stupid is the 32bit folder is called SysWOW64 and the 64bit is called System32. From what I've read online the reason is it amounts to laziness of the Microsoft Programmers not wanting to rename the system32 folder because they would then have to go and rewrite all their code to read the new name. I can understand a bit of lazinees here, but seriously they have made something that is so backwardly named that I am on longer shocked but in awe of their sloth.

Anyway, back to installing Windows updates.

-Steve G.