I have no interest in 32 bit Windows emulated on current MS OS offerings. ... Why add an emulator as another layer? Personally I wish MS would have spent the effort maturing their 64 bit OS rather than wasting the energy on emulating ...
WoW64 is
not an emulator, John. It is a subsystem, in fact, a sub-OS in its own right that uses the CPU and its cores natively through the sets of 32-bit instructions that the CPU supports alongside its 64-bit armory by design. Using WoW64 is basically the same as using a 32-bit XP on an x64 CPU, e.g. on an Intel Core2 Duo, which is exactly what I've been doing in the recent 5 years or so, without any abstraction layers in between. The CPU's hardware virtualization options are
not engaged by, nor necessary for, the WoW64 subsystem.
The system and program modules including WoW64's kernel32.dll are all genuine MS software compatible, and in many cases even interchangeable, with XP's original modules.
Have you ever tried to run your 32- and 64-bit Windows 7 samples in the OS' Aero modes? The Windows 7 desktop's DirectX 9-based compositing window manager (DWM) is much more intricate than that of XP and it often seems much better optimized for Aero than for Classic and Basic (that's what you're using judging by your snapshots) DWM modes.
Next, the lag that you're getting with your samples may be due to improper implementations of linuxoid SDL/IUP/whatever modules on MS Windows platforms. Linux devs are usually not that bright in almost everything that relates to graphics and UI's, and this is true whatever you say in favor of your preferred OS, server-wise.
And finally, you cannot find open-source 64-bit code simply because the general x64 program base is still rather scarce against myriads of 32-bit applications available on the net. There are only a few thousand applications known to the entire Linux world and maybe tens of thousands 64-bit applications altogether, but there are virtually millions of them still available in the 32-bit flavor.
"The patient is rather more alive than dead", John.
