*serversite scaling and multiple viewers, framebuffer size get overwritten-confirmed-source fix: OK(Scale is now lock when multiple viewers are connected to avoid a framebuffer change, first connected viewer set scale. Site effect is that the viewer report the unused, incorrect scale, but at least it doesn't crash anymore)-published: OK

*-connect ip, passed to winvnc running as service is not remembered forautoreconnect.-confirmed-source fix: OK-published: OK

*-stopreconnectstop the autoreconnect function of the server.-source fix: OK-published: OK

SERVER-autoreconnect was indeed invers, corrected again-All Messagebox() replaced by a function that put it on the visable desktop ( done for all messageboxes)-Auth Message dll not found, name corrected and refuse access.-if all groups are empty check also admin.-if OS_SHUTDOWN initiated ingore all lock functions.

bins uploaded

Last edited by Rudi De Vos on 2011-04-28 21:08, edited 22 times in total.

>>>> -All Messagebox() replaced by a function that put it on the visable desktop "done for all messageboxes" ( bug YY)For those Error/Warning message box that I have reported, they are now visible and properly displayed.

javaviewer While waiting for the new Javaviewer i did a little trick.... add 2 javaviewers One with and one without mslogon, if the server use mslogon browser download javaviewer(mslogon)Live swicthing between mslogon and vncpasswd is not supported, files are loaded on vnc startup.

Signed java using an official certificat ( same cert as for winvnc.exe seems to work for java)

lock keyboard/mouseviewer icon now proper indicate if keyboard is locked this is not to screen blanking state....If not running as service, system security settings often give permission denied when you try to lock the keyboard,now the icon displayed on the viewer use this permission info to show lock icon or not.Permission to lock keyboard and blank screen seems to be independed...icon only indocate keyboard locking.

Blank monitorworks but is limited in usage.win7 with aero, only monitor power functions can be used (limited, permission)win7 without aero support the background image ( prefered method)The lock icon give the keyboard state, not the blank monitor state. If you use the "non aero" alpha blending method, youalso can check if the top cover window is running.

You use the same port for java download an rfb.On connection, winvnc need to detect if it's a webbrowser requesting for data or a vncviewer that only want rfb data.

When i'm correct the problem was.The detection has trouble with non webbrowser or rfb packets that arrive on port 80, sometimes you need to connectmultiple times before the connection engine get back in sync.

We also use a new encryption engine, don't know if a special version with single http port still can be used for normal connection and encryption.

please wait test of YY about vncviewer so we don't have "stupid" bugs come back

Viewer x64 1.0.9.6.1 (Built May 2) shows Win32 in the Connection and About dialogs.

YY wrote:>>>> -All Messagebox() replaced by a function that put it on the visable desktop "done for all messageboxes" ( bug YY)For those Error/Warning message box that I have reported, they are now visible and properly displayed.

Add the DS_CENTER property to the About and Connection Options dialogs and let Windows take care of centering of this dialogs in the active display.

yes, too latethere others known issue with java and single portuntil prompt authentication OKafter vnc authentication, network error, NOK i think is old java problem and not rfb.other known issueFT if vncviewer running from protected folder %programfiles%\UltraVNCunlucky for fix FT, i will list soon all known limit of uvnc 1.0.9.6.1

I've noticed that the latest winvnc.exe 1.0.9.6.1 doesn't allow me anymore to have 8greycolors mode, wich is really needed for performance issues. it always shows a mode that seems to be the 256 colors.

jellysandwich, I've seen people mention this issue before. The big question is whether these connections are inbound or outbound.

If they're inbound, then the natural interpretation is that your router is forwarding the port properly, and that random drive-by scanning malware is probing your open VNC connection (and, luckily for you, failing to authenticate). Simple solution: pick an obscure non-standard listening port other than the default 5900. Also make sure you have a solid password.

If they're outbound connections, then your PC is trying to initiate connections, and we'd have to question (a) whether you got a clean copy of UVNC, and from where, and (b) if your machine is infected with some kind of trojan. No simple solution!