1.2.1.1 ( test builds)

[Rudi De Vos]

Same as 1.2.10 but
-some resource leaks, possible crashes, locks should be fixed.
-added protection mutex around delete cahebuffer ( this crashed onces)
-update jpeg lib to latest version

I just can't repeat in my test environment some reported issue's, so please test this version if you has some issue's with the
1.2.10.
winvnc for win7>=
http://www.uvnc.eu/download/1211/winvnc32.zip
http://www.uvnc.eu/download/1211/winvnc64.zip
winvnc for XP>=
http://www.uvnc.eu/download/1211/winvncXP32.zip
http://www.uvnc.eu/download/1211/winvncXP64.zip

[Rudi De Vos]

vnchooks.dll

There was an error in the hook that can cause a crash so we reverted back to the old version, but looking
at the vnchook size not all installers contain the correct version.

Update version number and recompiled hook.

hook updated and version updated from 1.1.0.0 to 1.1.0.1

Updated 10/3
http://www.uvnc.eu/download/1211/vnchooks_1101_32.zip
http://www.uvnc.eu/download/1211/vnchooks_1102_32.zip
http://www.uvnc.eu/download/1211/vnchooks_1101_64.zip
http://www.uvnc.eu/download/1211/vnchooks_1102_64.zip

[Skyfighter]

hook updated and version updated from 1.1.0.0 to 1.1.0.1
http://www.uvnc.eu/download/1211/vnchooks32.zip
http://www.uvnc.eu/download/1211/vnchooks64.zip

The x64 file still has v1.1.0.0 (not that really matters )

(Installed updated winvnc.exe and vnchooks.dll -> will report any findings...)

Thanks for your efforts, Rudi!

[Rudi De Vos]

gonna update the hook number, i want to be 100% sure test are done with the correct file.

Some other solution to fix the crash was also provided by a company, also gonna compile that hook code
and call it 1.1.0.2

http://www.uvnc.eu/download/1211/vnchooks_1101_32.zip
http://www.uvnc.eu/download/1211/vnchooks_1102_32.zip
http://www.uvnc.eu/download/1211/vnchooks_1101_64.zip
http://www.uvnc.eu/download/1211/vnchooks_1102_64.zip

[Prisma]

Kind of disastrous. Can't understand it... Within shortest time we had return to 1.2.0.9. Reverse connection still unstable (disappears from repeater after some viewer connect/disconnect) from a Vista32 low end test system with rdpmode disabled (!). rdpmode enabled behaves pre-alpha style the more. 1.2.0.9 still rock stable.

I wish I could analyse it more detailed and could say more than "*not working*", you know me. I'm a IT professional and I know what info a programmer needs to find a bug. But I have absolute no time at the moment, really sorry.

[Skyfighter]

With v1.2.1.0 & v1.2.1.1 I've seen the following problems (these might exist in older versions too - haven't checked that):

1) no remote cursor = tiny dot cursor; only when encoder Ultra or u2 is used - all other encoders have a proper cursor
- 100% reproducible in this constellation: viewer @ win8.1 -> server @ win7 with mirror driver & dual monitor
- does not happen: viewer @ win7 -> server @ win8.1

2) UVNC_Launch: saved password of last opened connection/session is used for the following connection/session IF the following connection has no saved password. => If the following connection needs another password you get "Authorization failed." (or something like that) and you can see the password of the previous connection has been passed to the viewer (command line of the viewer). Workaround: restart UVNC_Launch

3) Viewer: remote screen "freezes" - no more screen updates. Happens only occasionally. When it happens: even the Viewer Status window (speed, traffic bytes sent/received) doesn't indicate any changes any more; after minimizing viewer screen refresh works again.

[OSXFeatureRequest]

Viewer: remote screen "freezes" - no more screen updates. Happens only occasionally. When it happens: even the Viewer Status window (speed, traffic bytes sent/received) doesn't indicate any changes any more; after minimizing viewer screen refresh works again.

Ah, it's not just me then.

The host still receives input from the client while the view is frozen, like mouse cursor motion etc.

[Skyfighter]

The host still receives input from the client while the view is frozen, like mouse cursor motion etc.

Jep, mouse-clicks in the "freezed" viewer window are still processed/executed at the host/server. (Forgot to mention that)

[Rudi De Vos]

after minimizing viewer screen refresh works again

That's something i can work with.
minimize-> restore: The viewer send a message to the server...(send_next_update)
It looks like the server loose this message and keeps waiting for the viewer to ask for an update, while the viewer waits for an update from the server.

Added:
If server detect that it take to long before the viewer ask for an update, just inject one.
The drawback is that when you minimize the screen, there will still be some background updates.

[Rudi De Vos]

anti freeze test

win7>=
http://www.uvnc.eu/download/1211/winvnc_32.zip
http://www.uvnc.eu/download/1211/winvnc_64.zip
win7<
http://www.uvnc.eu/download/1211/winvnc_xp_32.zip
http://www.uvnc.eu/download/1211/winvnc_xp_64.zip

[Rudi De Vos]

Clean password after use

http://www.uvnc.eu/download/1211/UVNC_Launch_64.zip
http://www.uvnc.eu/download/1211/UVNC_Launch_32.zip

[OSXFeatureRequest]

That's something i can work with.
minimize-> restore: The viewer send a message to the server...(send_next_update)
It looks like the server lose this message and keeps waiting for the viewer to ask for an update, while the viewer waits for an update from the server.

Added:
If server detect that it take to long before the viewer ask for an update, just inject one.
The drawback is that when you minimize the screen, there will still be some background updates.

I just observed this in action, and it recovered.

[Skyfighter]

Clean password after use

http://www.uvnc.eu/download/1211/UVNC_Launch_64.zip
http://www.uvnc.eu/download/1211/UVNC_Launch_32.zip

Thanks Rudi - that works perfectly!

@OSXFeatureRequest
Any idea how to reproduce the freezing viewer? I can't reliably reproduce it and it happened only 3-4 times in the last weeks, so I'm not sure how to test Rudis fix...

[Rudi De Vos]

The auto recover is done with a counter, current 300 loops are required before the auto recover activate.
Does it need to be set higher, lower or is 300 ok

[Rudi De Vos]

Re-enabled cursor for ultra encoders, is was disabled with a switch, but don't know the reason why i disabled it before.
test version
win7>=
http://www.uvnc.eu/download/1211/winvnc_cursor32.zip
http://www.uvnc.eu/download/1211/winvnc_cursor64.zip

[Skyfighter]

Re-enabled cursor for ultra encoders, is was disabled with a switch, but don't know the reason why i disabled it before.
test version
win7>=
http://www.uvnc.eu/download/1211/winvnc_cursor32.zip
http://www.uvnc.eu/download/1211/winvnc_cursor64.zip

Thank you very much - cursor is fixed!

But there seems to be a side effect: After starting the uvnc-service with this fixed winvnc.exe one of the first three connection attempts brings up the viewer without a remote screen (= viewer shows only a grey area where the remote screen should be). If I close that viewer and try to connect once more it is working but the remote winvnc.exe has a stalled connection (My Client IP is listed twice unter "List all clients"; the stalled connection can't be killed - nothing happens!).
This problem is already known, but the cause is unknown. This is the first time I could reproduce this problem multiple times in a row! Please let us investigate it further: are there any viewer logging options which would produce something usable for you?

3) Viewer: remote screen "freezes" - no more screen updates. Happens only occasionally. When it happens: even the Viewer Status window (speed, traffic bytes sent/received) doesn't indicate any changes any more; after minimizing viewer screen refresh works again.

Additional note: "Refresh"-Button in the Viewer Toolbar fixes the broken screen refresh, too. (anti freeze test wasn't applied yet in that case!)

Now the anti freeze test is installed...but I'm still not sure how to reproduce the freeze / verify if the workaround works as expected...

The auto recover is done with a counter, current 300 loops are required before the auto recover activate.
Does it need to be set higher, lower or is 300 ok

hmm...300 loops of what? how much time are 300 loops approximately?

[Rudi De Vos]

Latest viewer changes
Just some fixes
*a crash
*mem leak fix

Compiled with VS2013 with XP compat mode on.
exe should work on all OS's.
Dual signed with sha1 and sha2

http://www.uvnc.eu/download/1211/vncviewer_1211.zip
http://www.uvnc.eu/download/1211/vncviewer_1211_x64.zip

[Skyfighter]

Still trying to identify the problem "viewer shows nothing = grey area / ghost connection @ server":
With the winvnc_cursor64.zip applied at my Win7x64 PC (server) the problem is 100% reproducible: the second incoming viewer connection (after starting the winvnc service) fails (stuck client connection @ win7 server side; viewer at win81 client shows only grey area). The stuck viewer connection on the server side is shown under "List All Clients" until stop service + kill all winvnc.exe processes (until I do that aero stays disabled).
(On the other hand: I don't see / can't repeat the problem using winvnc_cursor64.zip @ Win8.1x64.)

I've tried to catch the problem after enable of debug log to file (level = all)...while logging the following happened:

Code: Select all

LogLine   timestamp - description
         15:32:15 - winvnc service stop + kill all winvnc.exe processes, delete winvnc.log, start winvnc service
120      15:33:30 - 1. viewer connection      -> OK
491      15:34:15 - viewer closed
566      15:35:00 - 2. viewer connection      -> FAIL: grey viewer / no remote screen
         15:35:30 - viewer closed
735      15:36:30 - 3. viewer connection      -> OK, but server lists duplicate of viewer connection!
1099      15:37:30 - viewer closed
1280      15:38:30 - 4. viewer connection      -> authentication rejected (remote station not locked -> query window shown at server...ran into timeout)
         15:40:15 - winvnc service stop, kill all winvnc.exe processes, copy winvnc.log, start winvnc service


The log can be found here: http://pastebin.com/L91GptbQ
If this log catched anything useful I would guess it should be between line 566 and 735. Perhaps lines 633-635 and 643 are suspicious?

[JSmith]

Latest viewer changes
Just some fixes
*a crash
*mem leak fix

Compiled with VS2013 with XP compat mode on.
exe should work on all OS's.
Dual signed with sha1 and sha2

http://www.uvnc.eu/download/1211/vncviewer_1211.zip
http://www.uvnc.eu/download/1211/vncviewer_1211_x64.zip

It does seem to help a bit with stability. I do still get some lockups when a device reboots and it tries to reconnect. Viewer is not trying to reconnect and just hanging instead of cycling through the retry loop when connecting to old server (1.0.9.5) but 1.2.1.0 server seems improved on some devices. (not on my windows 10 tablets though, yet)

[Rudi De Vos]

Seems i can repeat the lock ( using the cursor version).
Now trying to find the cause...

[Skyfighter]

Sounds good! Let me know if I can test anything...

[Rudi De Vos]

WIN7>= 32 and 64 bit

http://www.uvnc.eu/download/1211/uvnc_1 ... _test1.zip

[Skyfighter]

Jep, that fixed it!

Thank you very much!

[Rudi De Vos]

On slow VPN it was still locking, fixed with extra change.

WIN7>= 32 and 64 bit

http://www.uvnc.eu/download/1211/uvnc_1 ... _test2.zip

[Skyfighter]

Thanks Rudi! With both test versions I can't reproduce the lock anymore.

After a lot of connect/disconnects for testing purposes I've only observed one thing with both test versions (not sure if it is even worth mentioning it - doesn't really bother me): On viewer connect sometimes I only see a small square/little part (*1*) of the remote screen...hitting "Refresh Screen" button of the viewer full remote screen is shown immediately (if I don't hit the refresh button it stays the same way for a long time showing only this little part of the remote screen...gave up waiting for magically auto-reload of the remote screen after a few minutes). This seems to happen frequently using u2 encoding (viewer config: QuickOption=8 + preferred_encoding=10 + autoDetect=0) but not (at all?) with tight enconding. Like previous locking problem I can only reproduce this running winvnc server @win7x64.

(*1*) it is always the little part of the remote screen where the cursor is blinking (I've configured winvnc.exe to lock the workstation after viewer disconnect: so on viewer connect theres the windows login screen showing the currently logged in windows user with the cursor sitting in the password field...)

[Rudi De Vos]

I hope this also solve some other strange connections issue's posted.
Gonna wait a week before releasing an updated version.

[JSmith]

I tried it hoping it would help out with my disconnects on Win10 tablets. no luck here!

[Rudi De Vos]

Can you try some exe build with older compilers ( like w2k or xp builds)

http://www.uvnc.eu/download/1211/Uvnc_1211_bin.zip

[JSmith]

Yep, trying that next!

[JSmith]

Confirmed! Windows 10 doesn't seem to entirely like the new compiler versions. XP version seems to work great where the Win7>= version was having issues!