Daniel Dehennin schrieb:
> Hello,
>
>> I'm using WPKG client on workstations with run on shutdown to avoid user
>> annoyance.
>>
> [...]
>
> I plan to create a shutdown task, late at night, but I need to permit
> users to cancel the shutdown if they are using the computer.
>
> I found "shut
Tomasz Chmielewski schrieb:
> Can you try:
>
> http://wpkg.org/files/client/beta/1.3.11/
>
> (the previous one started the installation as SYSTEM, and not a running user,
> so it could be that it was not able to access settings.xml).
Hello,
1.3.11 installs and works fine on XP here.
The old Win20
p did not finish as
expected. Contact your support personnel or package vendor. Action
_A9459942_EE79_497A_9080_F39DDA8A7B80, location:
C:\Programme\wpkg\wpkginst.exe, command: --SETTINGSFILE= "
Greetings,
Gerd Ott
Yes, it works without a "execute before script" !
(Even if there is an eventlog "error" saying "Starting WPKG on shutdown")
I had as well a script running "execute before", which was just
updating the wpkg-settings. ("%PROGRAMFILES%\WPKG\wpkginst.exe"
--SETTINGSFILE=\\server\share\settings.xml)
A
Hallo,
Scheduling the execution on system shutdown works fine on a XP-System
here. Thanks for your investment!
On a win2000 testbox (SP4, all windows-updates, installer 3.1)
execution does not start on shutdown, no errors in eventlog. Perhaps
it's even not possible with this OS-version?
Greetings,
Hi,
Your report.pl is not ugly, it's pretty pretty!
Works fine for me after adjusting the locations, even if perl -W
(v5.8.8) is saying: "Using a hash as a reference is deprecated".
BTW. If I copy the statusfiles to a share using a wpkg-package like
http://wpkg.org/Viewing_software_installed_on_w
Hi all,
I also was confused, because variables defined in wpkg-client are not
expanded, if you test your installation from the command line manually
with "/debug" flag.
So I think for testing/debugging packages with variables defined in
the client one has to use the wpkg-client and set "Show" in "
