<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Would it be worthwhile changing the wpkg service to a script that tries
to access the share or port 139 on the server every 5 seconds before
launching wpkg. You could even put in place detection of dialup and
abort wpkg at this point.<br>
<pre class="moz-signature" cols="72">--
User Support Officer - Information Technology
Great Barrier Reef Marine Park Authority
PO Box 1379
TOWNSVILLE, QLD 4810
Ph 07 47500874 Fax 07 4772 6093
<a class="moz-txt-link-abbreviated" href="mailto:email@example.com">firstname.lastname@example.org</a>
If you have received this transmission in error please notify us immediately
by return email and delete all copies. Any unauthorised use, disclosure or
distribution of this email is prohibited.
Tomasz Chmielewski wrote, On 23/05/2007 06:07:
<blockquote cite="mid46534D95.email@example.com" type="cite">
<pre wrap="">Dave Ewart schrieb:
<pre wrap="">On Monday, 21.05.2007 at 19:03 +0100, Dave Ewart wrote:
<pre wrap="">On Monday, 21.05.2007 at 12:02 -0500, Adam Williams wrote:
<pre wrap="">Is the erroring PC using a wireless NIC? I've found that wireless
NICs don't start their software and connect to the wireless
connection until a few seconds after the login screen comes up (or
after the start menu loads if not in a domain), however in both
cases, WPKG service has already ran and errored out since there
wasn't a network connection yet.
<pre wrap="">No, all the PCs I mention use wired NICs. In fact, the PC hardware is
all pretty similar, really; different, but very similar.
<pre wrap="">Working on this basis, though, I was wondering if there was any way to
make WPKG launch later in the boot process. I even tried hacking the
registry to make "WPKG Service" dependent on some other services such as
TCP/IP and NetBIOS, to see if that made a difference, but no luck.
I am assuming that the problem I'm seeing is essentially a race
condition at boot-up and WPKG sometimes loses :-(
I could add it to the TODO list (delay startup of WPKG service) - but:
how should we handle the so called "delayed logon" in that case (user
not allowed to logon when WPKG client operate, for 10 or 15 minutes or so)?
Somehow I feel, these two exclude each other?