UltraVNC 1.2.2.1 - Download links

[Tintifax_x]

1. When connecting with a 1.2.2.1 client (and older clients) to a 1.2.2.1 server, there is an initial delay of 5-10 seconds on the 'password accepted' message. This delay did not happen with the previous 1.2.2.0 beta you provided (or earlier server releases).

I've updated some 30+ Win10 x64 machines to 1.2.2.1 and can fully confirm the initial delay issue which cyberstream has brought up. Gonna go back to an earlier version until this is fixed. Rudi, can you please confirm that this is on your radar?
Also, I wanted to thank you for all of the work you're putting into UltraVNC!

[Thomas Levering]

I have found the problem with Filetransfer over Repeater

If the Send Buffer is > 20Sec Full, the Server close the connection

200Sec was not enough, I set it to 600Sec
max 16MB TCP Window / 600Sec = 213kbit

} while (count == 0&& !fShutdownOrdered && aa<600);
if (aa>=600) return 0;

Code: Select all

vsocket.cpp

sendall(SOCKET RemoteSocket,char *buff,unsigned int bufflen,int dummy)
{
int val =0;
	unsigned int totsend=0;
	while (totsend <bufflen)
	  {
		struct fd_set write_fds;
		struct timeval tm;
		tm.tv_sec = 1;
		tm.tv_usec = 0;

		int count;
		int aa=0;
		do {
			FD_ZERO(&write_fds);
			FD_SET(RemoteSocket, &write_fds);			
			count = select(RemoteSocket+ 1, NULL, &write_fds, NULL, &tm);
			aa++;
		} while (count == 0&& !fShutdownOrdered && aa<20);
		if (aa>=20) return 0;
		if (fShutdownOrdered) return 0;

....

[Rudi De Vos]

Still on holliday, back in a few days.
Can't check or test anything now.

[Rudi De Vos]

Thanks Thomas, that's something that can take long to find

[Rudi De Vos]

msi X64

Indeed, forgot to update the number… files are the 1221, but installer has a incorrect number

[Rudi De Vos]

initial delay :
before or after password accept message ?

[Skyfighter]

intial delay: for me there is a noticeable delay after password has been accepted. (password query comes up instantly and after input + closing the password window the viewer stays in "password accepted" for a few seconds.) I am not sure if this is specific to the new version but I am confident that this delay happens no matter if encoding is set to auto or explicitly set to tight/u2/...

[moe]

same initial delay for me... when connecting from win10 to win8/10 clients!
when connecting to a win7 client, the delay doesnt happen.
when connecting to win8/10, it delays after saying "password accepted", tried changing the options, like with/without the new desktop duplication etc,
nothing helps

[Rudi De Vos]

Do you mean you have a gray screen for a few seconds or no screen at all while waiting ?

I have trouble repeating it... what's your cpu i3 i5 i7 ?

[Rudi De Vos]

mirror driver button.

The button is below the checkbox, you only can see it but not click it.
When you click you actual click the checkbox.

This is a pure graphical issue, i enlarged the size of the checkbox, over the button
It has nothing todo with the working of the mirror driver it just make the check button unusable.

Repositoned the button for next update

[Mr Wolf]

mirror driver button.

The button is below the checkbox, you only can see it but not click it.
When you click you actual click the checkbox.

This is a pure graphical issue, i enlarged the size of the checkbox, over the button
It has nothing todo with the working of the mirror driver it just make the check button unusable.

Repositoned the button for next update

Thank you!

[moe]

Do you mean you have a gray screen for a few seconds or no screen at all while waiting ?

I have trouble repeating it... what's your cpu i3 i5 i7 ?

Okay, I just uploaded three files:
screenshot of the delay screen [edit: this screen lasts about 8-10 seconds]
.vnc file used to connect to the remote client (called serverf52)
ultravnc.ini used on the remote client (serverf52)

my pc is win10 with i7-6700, serverf52 is win8 with i5-4590.
same thing happens when I use a Win7 PC to connect to the serverf52..
also, same thing happens when connecting to a win10 client instead of serverf52.

url: https://drive.google.com/drive/folders/ ... sp=sharing

[Skyfighter]

initial delay: there is no "gray screen" while waiting, only the small "viewer status"-window is visible (see moe's screenshot). And moe might be correct: the delay definitely happens when I connect to Win10 or Win8.1 Machines, but I can't reproduce it connecting to Win7 Machines (winvnc server running as service; Win10/8: ddengine; Win7: mirrordriver with older winvnc version). I see two possibilies: winvnc server version* or mirrordriver capture engine vs ddengine capture engine?
(* If I remember correctly: I got used to this delay because I regularly have it connecting from Win7 to Win8.1 Machines; these Win8.1 Machines run older WinVNC as a service, not sure which versions exactly.)

mirror driver button.

The button is below the checkbox, you only can see it but not click it.
When you click you actual click the checkbox.

This is a pure graphical issue, i enlarged the size of the checkbox, over the button
It has nothing todo with the working of the mirror driver it just make the check button unusable.

Repositoned the button for next update

Ok, but more important: did you find out why the mirror driver isn't used although it is enabled (EnableDriver=1 in INI)?

[Rudi De Vos]

Skyfighter
The mirror driver wasn't working for any version.
Some debug code was still active and prevented to start/stop the mirror driver.

Found and fixed for next update

[Skyfighter]

Good news, Rudi! Thank you very much!

Will there be a new pre-release binaries-zip-download on occasion? Or do you still hunt other bugs?

[Rudi De Vos]

I still want to fix the slow start...

Then i can put the FT, mirror driver and start issue in the same update. 1.2.22

Some pre-test exe can always be uploaded.

[Skyfighter]

Is there anything we could do to assist you regarding the slow start/intial delay bugfix?

A pre-test exe with the existing bug fixes (mirror driver initialization, mirror driver button graphical issue) in x64 would be great!

[Rudi De Vos]

x64 server
mirror driver

https://www.uvnc.eu/download/1222/winvnc.zip

[Chaka]

Thank you Rudi. Mirror Driver works again...nice.

[Rudi De Vos]

There still seems to be some issue's with the initial screen gray/black/partial update

I'm getting different behaviours for ddengoine/mirror/plain with or without fixed encoder.
Sometimes a manual refresh is needed...stil searching for that part.

[Chaka]

I've tested a little v1.2.2.2 at different machines (Win7/10) using different methods (ddengine, vnchook, schook, mirror driver). WinVNC always running in service mode. Conclusion: Windows 8/10 initial delay whether or not using desktop duplication. Windows 7 initial black screen with little artifacts using schook, using mirror driver everything is fine.

Details:
1.) Windows 7
Using Mirror driver everything works like a charm, great.
Disable mirror driver using schook64.dll leads to inital black screen with 1-3 screen artifacts. I have to push the "refresh screen" button to see anything.

2.) Windows 10
Initial delay of 5 seconds after the "password accepted" message.
With desktop duplication there is no initial gray/black/partial screen. It's just waiting for the whole remote window to come up. After that I can control the remote machine without issues.
Without desktop duplication using schook:
First connection just after switching to schook: Remote window appears instantly but with a initial black screen. Black screen remains until I toogled manually "refresh screen" button. Looked like Win7 using schook.
But subsequent remote sessions: Initial delay of 5 seconds but no black screen or artifacts. It's like using ddengine, strange.
When switching between vnchook and schook and vice versa first connections are fast while subsequent connections have the inital delay. For testing purposes I renamed dll files (schook64,vnchooks) forcing winvnc to use the one or the other method. Hope it helps to narrow down the problem?

Question is why has Windows 8/10 problems with initial delay while Windows 7 shows initial black screen/artifacts? So it seems it has nothing to do with special ddengine feature?!?!

[Chrispy]

Hi,

I am running 1.2.2.1 in Oracle VirtualBox with Win 10, using ddegine64.dll.

All I get at the Client is a black Screen, mouse movements and clicking work without Problems. Switching Screens from Client also works with correct sizes, but also only with black Screens.

I have the source code compiled for x64 and debug, if that helps, but even the precompiled 1.2.2.1 installer exe has the same effect. Source code is r1127.

I tried this on my other non-vm and the ddengine works on one and black Screens on the other with multiple Screens.

Willing to try anything.

Regards,
Chris

[Proger]

Thanks for Win7_x64 fix of mirror driver!
But same issue with mirror driver in Windows server 2003...
back to 1.2.1.7

[ReD]

I use the following on remote computers to initiate the connection and it doesn't work anymore on this version.

Code: Select all

"C:\Program Files\uvnc bvba\UltraVNC\winvnc.exe" -connect myhostname.mydomain.com

Using the "add new client" function from the menus instead, works as usual.

[Rudi De Vos]

There is one exe from XP - win10.

If driver is fix for win7 x64 it's also fixed for windows server 2003 ( x64)
We shall also put a 32bit version online for testing...

[Chaka]

@Proger: Can't confirm, UltraVNC v1.2.2.2 with mirror driver running Windows Server 2008 R2 Standard x64 works as expected.
@Chrispy: And after you click "refresh screen" it works? Or do you have permanently a black screen? I'm running Windows 10 pro 64-Bit by myself in virtualbox only with initial black screen.

[Rudi De Vos]

Next test...
(svn: 1130 Test_initial_black require refresh fix)
Updates src so i can keep track with the results, just in case we need to revert.
For test i gonna use the src numbers, so this is test svn1130

The problem was that we first need to capture the screen before sending it.
Sending and capturing is done in seperated threads but seems to be out of sync.
On faster systems you catured/send, but on slower the update was send before we had time to capture the display.
Vnc server sended a black screen... as initial update.

I don't know if it also fix the initial delay, i just can't repeat it on any system.

https://www.uvnc.eu/download/1222/winvnc_svn1130.zip
( winvnc.exe and winvnc64.exe)

[Chaka]

Hello Rudi,

thanks for your try, but the initial delay is still there with svn1130.
Tested on nativ Windows 10 pro 64-Bit and i think my UltraVNC-Server isn't running at the slowest system (Intel i3-7100 3.9GHz). I'm wondering you can't repeat it on any system, strange.
Btw after the delay the window appears with a blue screen. 500ms later the real remote content appears. I don't no if this is related und will helping you?!

[Rudi De Vos]

winvnc running as service/application ?
please pm the ultravnc.ini ( just remove the passwd string)

It can't be the cpu an i3 is OK.
The normal buildin video card is an HD 630 intel when i'm correct, that's also ok any external card is even faster.

As viewer i retested with a dualcore 1.3 Ghz, almost any viewer system is faster.
Are you sing a wifi or fixed network ?

Do you have the issue with and without ddengine selected ?
If you select a fix encoder ( hextile/u2) does it make a difference ?

I wish i could as easy repeat it as you... a i3 is a standard cpu so taht can't be it.

[Rudi De Vos]

blue instead of black/
When you select an encoder with 256 colors instead of full colol, the initial screen is blue instead of black.

In automode this indicate a network < 1mbs...