Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
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
Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
thanks Rainer, Rainer Meier wrote: 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). i didn't know about folder redirection... 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. i don't use wpkg client, i am activating wpkg.js thru GPO: anyway your suggestion is truly the easyest viable alternative, i will follow it. it will be not so practical setting the layout of cmds to a minimum size or to switch exec with run in wrapper.js. i will be exploring for something like rundll* hack. thanks again riccardo -- riccardo marcon dipartimento di scienze economiche universita' di padova via del santo 33 - 35123 padova tel +39 049 827 4272 (4212) fax +39 049 827 4211 e-mail: riccardo.mar...@unipd.it - 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
Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
i don't use wpkg client, i am activating wpkg.js thru GPO: anyway your suggestion is truly the easyest viable alternative, i will follow it. it will be not so practical setting the layout of cmds to a minimum size or to switch exec with run in wrapper.js. i will be exploring for something like rundll* hack. thanks again riccardo Then there is nothing to take care of, no tweaks needed at all. The startup and logon scripts are always run in native mode, none of them is run in 32-bit mode on a 64-bit machine. --- Stefan - 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
[wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
hi all, 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... in a test environement i solved this by invoking explicitly proper cscript.exe (32/64 bits) straight from wpkg-start.bat, as in the following line: %WINDIR%\System32\cscript.exe %WPKGROOT%\wpkg.js /synchronize /quiet /nonotify so far all the tries i performed succeed... is it enough ? any hint would be appreciated. thanks riccardo -- riccardo marcon dipartimento di scienze economiche universita' di padova via del santo 33 - 35123 padova tel +39 049 827 4272 (4212) fax +39 049 827 4211 e-mail: riccardo.mar...@unipd.it - 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
Re: [wpkg-users] x64 - x86 mixed evironment-how to get rid of wrapper.js
hi all, 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... in a test environement i solved this by invoking explicitly proper cscript.exe (32/64 bits) straight from wpkg-start.bat, as in the following line: %WINDIR%\System32\cscript.exe %WPKGROOT%\wpkg.js /synchronize /quiet /nonotify so far all the tries i performed succeed... is it enough ? any hint would be appreciated. thanks riccardo There is no need to specify which cscript.exe to use. On x86 the 32-bit version and on AMD64 the 64-bit version will be used. --- Stefan - 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
