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
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 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
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
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
