[wpkg-users] [Bug 106] WPKG holds log on operation and does nothing

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=106





--- Comment #12 from Rainer Meier <r.meier at wpkg.org>  2008-04-09 21:08:54 ---
Hey Tomasz,

It looks like I was much too fast when committing comment #10. All findings
were done using invalid assumptions. I forgot that for testing reasons I set
the WPKG service to "manual" execution. Therefore it was never automatically
executing.
As a result I found out that the logon delay is completely independent from the
service. It just waits for the service to start I think. Unfortunately if the
service is set to manual execution, it will never start ;-)

As a result the logon delay waits for timeout.

Now I set it to "automatic" again and logon delay is working too.

Even when enabling the offline mode. It immediately closes the logon delay
window if I disable the VMWare network controller at boot. So this seems to
work for me here.

However I could imagine that there is a "timing" problem between the logon
delay and WPKG service. Recent versions of WPKG client introduced a new
feature: "Stop the service when all actions are done".

Question: How is the logon delay checking if WPKG terminated its execution?
Probably on some machines the service already terminates before the logon delay
window is invoked and then it waits forever for the WPKG service to start
(since it already terminated).

Probably somebody who has this problem could try disabling the "Stop the
service when all actions are done" feature within the configuration of WPKG
client.

Some seem not to have the problem when WPKG is actually installing package
(which actually delays the process and keeps it alive for some time). As a
work-around invoking wrapper.js instead of wpkg.js slightly delays the
invokation of wpkg.js. If this is not enough someone could try inserting
something like "WScript.sleep(20000)" within the startup procedure of wpkg.js
to force a delay of 20 seconds.

Well, just some wild guesses and suggestions...


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.