Originally posted by: bsobel
Unfortunately things are slower with the 64bit version with 4gb of ram than they were with the 32bit version with 3.2GB of ram.
You'll have to be more explicit than that, hard to fix 'slower' without parameters. I'm really surpised to hear that however, can you try to quantify it a bit so perhaps we can figure it out?
When I first got Win95 almost everything was still being released in 16bit. It took companies forever to start making 32bit versions of their software. Sure the 16bit applications worked fine but does that mean that we should have stuck with 16bit? Of course not. I also want 64bit applications because I want to see if the slow down is being caused by running 32bit applications in a 64bit environment or if it's immature drivers that are causing the slow downs. I'm thinking about just living with less ram and using the 32bit version since it's faster.
Irrelevant comparison. 16bit code running on Win95 had to go thru expensive transitions from the 32 bit environment. These cost a lot of cpu cycles and is why 16bit code on 32bit machines where so much slower. The model is much different in the 32bit to 64bit transition we are going thru now.
32bit on 64bit is completely different and for all practical matters runs at full speed.
The ONLY difference a 32bit v 64bit app is going to give you in in available memory to the application. So worry about those apps which need more than the amount of user memory available to a 32bit app (which is 2-3gig on 32bit windows and 2-4gig on 64bit windows).
The other apps will get there over time, but unlike 16bit your not actually getting a penalty for them still being 32bit apps so the need to move is driven more by the apps that can perform better in the 64bit environment than just a port for ports sake.