how can i turn off 32-bit compatibility in win 7 -64

[CommonTater]

Actually it is and does.

If you run a 32bit App in a Windows 64 OS it runs in Wow64 Mode which is emulated.

It is NOT emulated... it's merely using 32 bit DLLs for system calls.

In their infinite wisdom Microsoft decided to artificially create a boundry between 32 and 64 bit apps, that simply doesn't need to be there...

 

[FuturDreamz]

Think of the processor as a road. 64 bit processors are double-wide roads that are made to accommodate bigger vehicles. That does not mean that the smaller 32-bit vehicles have to take a different road, nor does it mean that they have to go at a different speed.

 

[helmutcheese]

Actually it is and does.

If you run a 32bit App in a Windows 64 OS it runs in Wow64 Mode which is emulated.

It is NOT emulated... it's merely using 32 bit DLLs for system calls.

In their infinite wisdom Microsoft decided to artificially create a boundry between 32 and 64 bit apps, that simply doesn't need to be there...

YES it is, I do not agree with any of your posts.

32bit Apps run in Wow 64 and that is an emulator.

Go and read about in on MS site and argue it with them.

http://msdn.microsoft.com/en-us/library/aa384274(VS.85).aspx

(again I back up my claims by hard links).

 

[CommonTater]

Actually it is and does.

If you run a 32bit App in a Windows 64 OS it runs in Wow64 Mode which is emulated.

It is NOT emulated... it's merely using 32 bit DLLs for system calls.

In their infinite wisdom Microsoft decided to artificially create a boundry between 32 and 64 bit apps, that simply doesn't need to be there...

YES it is, I do not agree with any of your posts.

32bit Apps run in Wow 64 and that is an emulator.

Go and read about in on MS site and argue it with them.

WOW64 Implementation Details (Windows)

(again I back up my claims by hard links).

From the very first line of your "I'm proving you wrong" citation...

" It provides an interface between the 32-bit version of Ntdll.dll "

Like I said... it's simply a way of switching out libraries that use 64bit code for those that use only 32bit code. AND... if Microsoft had taken the time to rebuild those libraries rather than simply recompile and rename them... even that would not be necessary.

 

[Scotteq]

*sigh* @ arguments over semantics.

In WoW64, "Emulation" in the strict sense of the word is not required with an x64 processor. i.e. x86 binaries run untouched, untranslated, and natively on the processor. The necessity to do full emulation is only applicable to IA64 environments (and which is being deprecated by Microsoft - as announced yesterday coincidentally).

However, there is some jiggery~pokery going on:

On the OS level, 32bit and 64 bit programs need to remain separate from each other for data/registry/etc integrity. This means most of the (32 bit) DLLs are the same as their standard counterparts. Except for some which (for example) may share memory with 64 bit components, or otherwise need to directly interact with 64 bit system components. These use a custom calling sequence instead of the standard x86 one so that Windows can perform the appropriate redirections.

The other difference is that 64-bit Windows does not support running 16-bit Windows-based applications, whereas 32 bit does. The primary reason is that handles have 32 significant bits on 64-bit Windows. Therefore, handles cannot be truncated and passed to 16-bit applications without loss of data.