http://bugzilla.wpkg.org/show_bug.cgi?id=224 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Rainer Meier <r.meier at wpkg.org> --- Just commited a (slightly modified) update: NEW: Added support for IA64 Itanium architecture. Basically this adds the possibility to use os="ia64" in extended host attribute matching. So the current list of supported architectures is: x86: 32-bit Windows operating system running on x86 instruction set x64: 64-bit Windows operating system running on x86-64 instruction set ia64: 64-bit Windows operating system running on IA64 instruction set Fixes bug 224. Thanks to Stefan Pendl for requesting. Actually WPKG internally uses the "is64Bit()" method to detect the folders it has to check as well as registry paths. For example the WoW64 folders. I am not sure if these folders are the same for IA64 machines. So there are a few questions to be clarified. Until then WPKG might behave wrongly on IA64 systems: - Is there a native IA64 WSH binary (cscript.exe)? - Does it provide access to 32-bit reg keys via "HKLM\SOFTWARE\Wow6432Node"? If there is no HKLM\SOFTWARE\Wow6432Node then WPKG might try to open the wrong path to get uninstall information from. Of course it would be ideal if somebody could provide access to such a system. Or at least verify the conditions listed above. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |