| 1. |
Solve : comctl32.ocx win7? |
|
Answer» there was not a copy of it in SysWOW64 but yes it works thank you very much sir top marks for this forum now i can get BACK to it.Just to explain for future readers, on x64 systems there are two SYSTEM folders. C:\Windows\System32 is where 64-bit components are stored, and C:\Windows\SysWOW64\ is where 32-bit components are stored. 32-bit Applications, however, will get MAGICALLY redirected to C:\Windows\SysWow64 if they access C:\Windows\System32. This causes a lot of confusion. 32-bit Applications, however, will get magically redirected to C:\Windows\SysWow64 if they access C:\Windows\System32. This causes a lot of confusion.HUH Quote from: Geek-9pm on June 18, 2013, 07:17:26 PM HUHPrecisely. I wrote about this behaviour some time ago. Basically, 32-bit applications are often written to access components in C:\Windows\System32. This is why MS couldn't just make a new System64 folder for 64-bit components. In order to be as compatible as possible, Applications running under WoW64 (32-bit apps on 64-bit windows, that is) can still access C:\Windows\System32, but those requests are redirected to C:\Windows\SysWOW64. 32-bit applications that are aware of the redirection can access the actual System32 folder contents by accessing C:\Windows\sysnative. This can be tested without having to write applications (or something) by using something like Command Prompt. C:\Windows\System32\cmd.exe is the Command Prompt, as we all know; on 64-bit systems, this is a 64-bit executable. However on 64-bit systems the 32-bit version is still available in C:\Windows\SysWOW64. |
|