UltraVNC

Patch the function vncEncoding::SetEncoding() use HexT encoder in the case rfbEncodingTigh.
Works with noVNC client.

This is the full log until connection: Mon Sep 12 11:31:46 2016 c:\users\sub-7\downloads\z_sc\winvnc\winvnc\winvnc.cpp : sockets initialised --The operation completed successfully. c:\users\sub-7\downloads\z_sc\winvnc\winvnc\winvnc.cpp : test... 192.168.0.111 5901 --The operation completed ...

I still can not understand how the server in single click mode decides to use ZRLE and where I can patch the code and force, for example, raw enconding

More research:

* All SingleClick patches are under SINGLECLICKULTRA
* Message MENU_ADD_CLIENT_MSG causes adding a new client to the server in single click mode

How the "dummy" chooses the encoding?

Hello, I am trying to run UltraVNC SC_II_RC23 with https://kanaka.github.io/noVNC/ I have to patch the noVNC to allow accept the connections from the VNC server instead of connected by itself. The patches in noVNC are: https://github.com/larytet/websockify/commit ...