Service startup problem for Wireless LAN

[cookie_lu]

I am having problem with the service (version 1.0.6) starting up before the wireless gets connected. It took about 15 seconds to get connected after windows loaded up.
So when the service starting up before the wireless gets connected, I can't connect using the viewer.
However, if I startup manually (after I got connected) I have no problem connecting to the VNC server.
Is there any way to around this problem?

[redge]

change the wireless settings for run with windows not only when user logged.

[YY]

A common workaround is to delay the startup of uvnc service.

You may try to create a dependency setting for the uvnc_service, let it depending on your wireless service, or depending on a service that usually loaded at a relative later stage (e.g. Print Spooler service).

Reference Microsoft's How to delay loading of specific services for more information.

[cookie_lu]

I have found a solution to my problem. Sharing it with those experiencing the same problem.

I tried the Microsoft's "How to delay loading of specific services" but it didn't work for me. I think the service for wireless was not the problem (not delayed) but rather waiting for DHCP, etc to get connected (assigned IP). So I can't create a dependency, unless you care to tell me how.

Anyway, I have found a little utility called Startup Delayer, can be found at
http://startup-delayer.software.informer.com/

With this I can specify to delay UltraVNC startup by 30 seconds until my wireless LAN is connected. Now it is all working.

[redge]

I am having problem with the service (version 1.0.6) starting up before the wireless gets connected.

solution
try uvnc 1.0.9.6 beta

*The interface that update the tray ip address is using DNS...
-Functions replaced by non DNS version
This allow us to call it multiple times without the DNS overhead. This is
the reason the current tray doesn't update the ip change, overhead was
to big. In cases the DNS was set by isp and broken internet connections
this function was extreme slow ( dns timeout)

you need uvnc 1.0.9.x installed before, then replace only the winvnc.exe and uvnc_settings.exe
http://www.uvnc.eu/download/winvnc1096Beta.zip

[Rudi De Vos]

1.0.9.5 running as service already monitor the network.
If network change, winvnc is restarted by the service.

In 1.0.9.6 we added some extra code for non service mode.

[Deehege]

I had the same problem starting up. Thanks for the info re startup delay software, cookie_lu. It works for me. Thanks a million.