![]() ![]() WIA launches the wiawow64.exe extension host that UI extensions will be loaded into. This is similar to what happens when you run a 32-bit application on 32-bit versions of the Windows operating system.ģ2-bit application. The 64-bit WIA minidriver UI extension is loaded directly into the process space of the application. The WIA service will determine where UI extensions get physically loaded, depending on whether the application is 64-bit or 32-bit:Ħ4-bit application. ![]() ![]() The wiawow64.exe extension host will be available in Windows Server 2003 64-Bit Edition for Extended Processors, Windows XP 64-Bit Edition for Extended Processors, Windows Vista, and later operating system versions. This host ensures transparent interoperability between 32-bit applications and 64-bit WIA UI extensions. To mitigate the 32-bit to 64-bit problem, Microsoft provides a 64-bit extension host, wiawow64.exe. A Microsoft Win32 application's unmodified 32-bit process that runs on an 圆4-based machine would not be able to load the 64-bit UI extension. However, WIA minidriver UI extensions are loaded in the application's process space. On 64-bit editions of the Windows operating system, the 64-bit WIA minidriver is loaded in the WIA service's 64-bit process. ![]() On systems that run Windows 64-Bit Edition for Extended Processors, all WIA components are 64-bit so the WIA infrastructure was changed to allow interoperability between these 64-bit drivers and existing 32-bit applications. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |