<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Le 20/10/2010 09:44, Rainer Meier a écrit :
<blockquote cite="mid:4CBE9DEE.2090301@wpkg.org" type="cite">
<pre wrap="">Hi,
On 20.10.2010 09:26, Ludovic DUFLOT wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Yes, I installed the 32bit version of wpkg-client ! ;)
And all failed packages are for 64bit programs (Userlock, Paint.Net, 7-Zip, ...).
It's strange that only 32bit packages work and 64bit not !
</pre>
</blockquote>
<pre wrap="">
It's not really strange. This is due to file system and registry virtualization
in Windows x64. 32-bit applications (including 32-bit version of cscript.exe
used by 32-bit WPKG client) will not be able to read 64-bit registry keys so
WPKG cannot read this data and therefore cannot find the keys you're looking for
and reports tha software not being installed.
So either you need to deploy 64-bit WPKG client or use the included wrapper.js
(launch wrapper.js instead of wpkg.js). Read instructions how to use wrapper.js
in the header of wrapper.js. Basically you just need to copy it to the same
directory as wpkg.js and launch it instead of launching wpkg.js directly by WPKG
client.
However I recommend to upgrade to the 64-bit version of WPKG client.
</pre>
</blockquote>
Think's for your explanation.<br>
<blockquote cite="mid:4CBE9DEE.2090301@wpkg.org" type="cite">
<blockquote type="cite">
<pre wrap="">I use 32bit version of wpkg-client because I recompiled it for using wscript
instead of cscript (I don't like the black windows of cscript and I need that
service interact with the desktop sometime). And I did'nt arrive to recompile in
64bit. :(
So, I have a request : for futur release of wpkg-client, it's great to have the
choice between cscript (default) or wscript for running wpkg.js ! ;)
Think's for your help.
Ludo
</pre>
</blockquote>
<pre wrap="">
Not sure what you're doing exactly but if you want to launch wpkg.js using
wscript, then just use "wscript.exe \\path\to\wpkg.js" (works in WPKG client
too). The choice wheter wpkg.js is executed by wcript or cscript is done by
Windows file associations by default (wpkg.js itself does not have any influence
on the choice).
</pre>
</blockquote>
No. The wpkg-client service (WPKGSrv.exe) launch "cscript.exe
\\path\to\wpkg.js", and the "cscript.exe" is hardcoded (line 110 in
WpkgWorker.cpp) !<br>
So, I can't tell it to use wscript.exe instead of, either the
windows file associations doesn't change anything.<br>
<br>
So, it's great if, in the next release, we have the avaibility to
choose which script engine to use in the settings.xml ...<br>
<br>
<div class="moz-signature">-- <br>
<strong>L.DUFLOT</strong><br>
<em>Service Informatique</em><br>
IUT Annecy - Université de Savoie<br>
<pre>============================================
Assistance informatique :
- Web : <a class="moz-txt-link-freetext" href="https://sos.iut-acy.univ-savoie.fr">https://sos.iut-acy.univ-savoie.fr</a>
- Twitter : <a class="moz-txt-link-freetext" href="http://twitter.com/uds_soiut">http://twitter.com/uds_soiut</a>
- Appel interne : 2000
- Appel externe : 04-50-09-22-22 poste 2000
- Bureau : A265
============================================
</pre>
</div>
</body>
</html>