The win7<= use the new "desktop duplication engine" and newer sse sse2 hardware acceleration.It works ( win10) on a i3-i7 intel with a ati/nvidia card and a lot faster then the Xp version.

Difference between versionsXP version: old compiler, use only older acceleration and no "desktop duplication"Vista winvnc.exe, use the newer sse and sse2 sruff, but not the " desktop duplication"win7 winvnc.exe use the newer sse and sse2 sruff, and the "desktop duplication"

Thanks for all you do here with winvnc. I use it daily via reverse connections supporting a wide variety of systems running Win XP through Win 10 32 and 64 bit. My reverse connection tool has been using 32 bit winvnc 1.2.0.5 and has been very reliable for several years. I've updated the tool occasionally to test how it performs with newer versions of winvnc.

RE: 1.2.1.1 test build. For me the 32 bit winvnc 1.2.1.1 compiled for XP (as of 2016/4/20) is the most stable since 1.2.0.5. I've tested this version for the past 24hrs on a wide variety of 32 and 64 bit systems...all windows versions XP through 10 and haven't had any issues ...yet.

Re: Speed: I'm testing only the winvnc 1.2.11 compiled for XP for maximum compatibly with any system that requests my help. My reverse connection viewer is set to -listen -quickoption 3 -scale 8/10 and the speed for typical desktop support has been excellent.

The only connection/speed issues I have experienced so far are requests for support coming from people with known terrible wifi or hotspot mobile connections.... not a winvnc issue.

For my needs the 32 bit winvnc 1.2.11 compiled for XP rocks for all versions of windows XP-10... 32 and 64 bit... so far. One tool for all... makes it easy for me.

I did find a hiccup since posting 24hrs ago although this may not just be 1.2.1.1 I did a quick search for the word "zoom" and didn't find any hits. Maybe someone knows a simple solution for the following and or maybe it can be corrected? Others have likely seen this.

I had a person request support though my reverse connection tool using 32 bit winvnc 1.2.11 compiled for XP (2016/4/20) (which has been working great on all Win OS versions I have tested as previously mentioned. On this particular Win 10 64 bit computer the farther my mouse went from the top left corner of the screen the farther it was out of whack and I could not control his system via mouse. It would not click where I was pointing...my mouse was pointing different to where his mouse was.

I had him reconnect using my reverse connection tool using 32 bit winvnc 1.2.0.5 instead and didn't have any problems. I went into his win10 settings for display and found his zoom set to 200% for his size of text etc.

So if the person sets their text in the windows 10 display settings over 100%... the winvnc 1.2.1.1 (XP) has a mouse alignment issue /scaling whereas winvnc 1.2.0.5 does not.

Anyone with a simple fix? (Without having the person change their display zoom) The goal is to stay with one version of winvnc 32 bit to support all Win OS versions XP and up that request help. I could stay with 1.2.0.5 but it would be nice to update if possible.

Thanks in advanceCPC

**Updated more info. If this helps... My reverse connection program includes vnchooks.dll and the following [poll] section in the ini file. This has worked well for me with 1.2.0.5 and 1.2.11 except for the 1.2.11 mouse scale/zoom issue above.[poll]TurboMode=0PollUnderCursor=0PollForeground=1PollFullScreen=1OnlyPollConsole=0OnlyPollOnEvent=0MaxCpu=40EnableDriver=1EnableHook=1EnableVirtual=0SingleWindow=0SingleWindowName=

Just confirming issue mentioned above and adding symptoms that may be related...but this is on build 1.2.1.0 (Jan 24, 2016)-- On WinXP no issues-- On Win10, using scaling of text size, etc ("Customize your display") :1. Will result in "split pointing" a Arrow will track separate from actual mapped click point b Point will be displayed (elsewhere) as faint but useful "DOT" (you can put this on top of real selection and click) c. Arrow and DOT will be in sync at the extreme upper left corner, getting closer as movement approaches this corner d. Arrow and DOT will be increasingly separated when movement goes to the right of the screen

2. Screen corruption tends to happen at past 150%

In a pinch (to do useful work), one can compensate movement relative to the above comments, and be able to click on things. So, watch for where the darn DOT is...THAT's click-actionable. In ADDITION, one may need to request a "screen refresh" as often as every other command or action.