Deadlock on win7 userlock or screensaver

[klezzz]

Previous changelog i found this:
-deadlock fixed (server hang after desktop switch (logon-default-screensaver, taskmanager needed to kill)

But i have the same problem with 1.8.0.2. Server side application command: winvnc.exe -autoreconnect -connect xxxxxxxx -run
After user lock and resume, it wont connect to listening viewer nor i cant connect manually with viewer.


Another problem is mouse cursor blinking on server screen, when (i found the reason) CaptureAlphaBlending is enabled. Poll settings:
TurboMode=1
PollUnderCursor=0
PollForeground=1
PollFullScreen=0
OnlyPollConsole=0
OnlyPollOnEvent=1
EnableDriver=0
EnableHook=0
EnableVirtual=0
SingleWindow=0
SingleWindowName=

[supercoe]

Install as service and add your -autoreconnect string to service_commandline=

[klezzz]

Ok, i knew this, but i want it to run in application mode. Why vnc stop trying to reconnect after user resume, uac window gone etc..? Seems like it stop my autoreconnect request.

[klezzz]

What is few seconds mean exactly?
Can i config how long to try autoreconnect?

The server attempts to "autoreconnect" for only a few seconds.

-autoreconnect
Is used in conjunction with the -connect switch when having a server "back-connect" to a listening viewer. You can use it in a batch file for your clients that are behind a firewall that is not under your control. The batch file looks something like this:
"c:\program files\ultravnc\winvnc" -autoreconnect -connect 12.34.56.78
On the local computer run the viewer in "listening" mode, and have someone on the server end run the batch file. The -autoreconnect will make the server end attempt to reconnect to the listening viewer if the connection drops or is closed. It will immediately reconnect to the listening viewer if the session is closed. Close the listening viewer altogether in order to stop the server end from "autoreconnecting" to your computer. The server attempts to "autoreconnect" for only a few seconds.
Note that this "autoreconnect" param must be before the "connect" one on the command line!

[klezzz]

Oh and i experienced that deadlock only happen if the vncviewer message box appear with:server closed connection, -the server running as application.
So winvnc try to connect when the server console blocked causing viewer error message and stop future connections.
But if i close viewer before this happen and start again when server resume, everything is fine server connected.