Here is the catch: the amount of memory available for the stack is the same in 32-bit and 64-bit Windows, but the stack entries are twice as long on 64-bit Windows. Hence the usable window hierarchy depth is halved. And if you think that you can avoid the problem by using 32-bit edition of the affected application on 64-bit Windows, that is not the case. The problem is in the 64-bit kernel. The worst thing is that Microsoft refuses to consider this a bug and fix it (unless they changed their mind since the last time I checked).I've run into that issue with some of my C# code, and speaking from experience, I can say the following:
that will only ever be an issue with very badly designed code. If you run into this issue, you're doing things wrong - massively wrong.
As for compatibility, I jumped onto the x64 bandwagon relatively early with XP64. At my first attempt, drivers were a problem (blame Creative) and I had to go back to XP32... at my second attempt, I never looked back. Yeah, you can no longer run 16bit apps (neither DOS nor Windows) without an emulator, and some older 32bit apps come with 16bit installers... but generally I've had very little trouble. x64 is slightly faster sometimes (and for some tasks, a lot), it's somewhat more secure, and it lets me use all my memory. It's good.



- carpe noctem











VanDragt.com

I am now.