Hi Riccardo Riccardo Marcon wrote: > i am going to switch to last stable wpkg to handle winxp / winxp x64 > environement: i don't want to use wrapper.js since it runs wpkg thru > cmd.exe and this leaves cmd.exe window exposed to users. so users can > feel free to close cmd.exe window...
There is a 64-bit version of WPKG client available. The problem when invoking wpkg.js with 32-bit WPKG client is that invoking %WINDIR%\System32\cscript.exe will make Windows re-directing the path to %WINDIR%\SysWOW64\cscript.exe which contains the 32-bit binary. The "real" system32 folder which contains the 64-bit binaries (damn, which sick brain invented this re-direction...) is only accessible to 64-bit processes. That's why you need to invoke the 64-bit cscript.exe from a real 64-bit process (I used cmd.exe). Alternatively you can use 64-bit WPKG client which will be able to launch the real 64-bit process from system32\cscript.exe. In this case no wrapper is needed at all and wpkg.js will be able to access all 64-bit paths and registry entries. So wpkg.js fully supports 64-bit systems when cscript.exe is launched either by 64-bit WPKG client or any other 64-bit process. br, Rainer ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
