UltraVNC

We are just going to stick with 1.2.0.9.

thanks

Are you using the same viewer settings ?
Yes, the same VNC/INI shortcut file is used to start the viewer for each test. You can see those settings in the notepad window below each VNC/INI shortcut file. All other settings are default - except the password.


1209 viewer on a 1212 server ? same ...

re-size the viewer window by dragging the window's edges: That part didn't changed.
[v] scale the window is possible the missing option.

uvnc 1.2.0.9 on both VMs:
https://www.youtube.com/watch?v=Sanbr1TKeq4

uvnc 1.2.1.1 on both VMs:
https://www.youtube.com/watch?v=z6FHmt82Huc

The installations ...

The video below shows two virtual machines. Both VMs are running 1.2.0.9 (build Nov. 2 2015 20:50:06).

The VM on the right is the "remote" computer. Look in the lower right part of the screen where the clock is on that "remote" computer. Just above the clock is a tool tip displaying the seconds ...

We will probably go back to version 1.2.0.9 :-(
...where this idle timer reset does not happen :-)

I don't want to wake up more than a dozen monitors just to glance at the status of things running on remote computers.

Also, version 1.2.0.9 has the ability to re-size the viewer window by dragging ...

Are you using the same ultravnc.ini settings for both versions ?

uvnc was completely uninstalled and any left over folders were deleted between version tests. The ultravnc.ini contains whatever the default install creates. The only thing changed was the password (test). [Password privacy is not a ...

Sorry that I was not clear: I'm not talking about a balloon that is created by the VNC app. I'm talking about a balloon that is created by some other app on the remote computer. As soon as I create a view only VNC session to the remote computer, the balloon goes away (if the balloon had been ...

Today, several remote computers had a tray tip (balloon? notification?) message down by the clock. Creating a View Only VNC session to those computers made the tray tip go away before I could read it. These tray tips usually stay around if the computer is not disturbed (e.g. no mouse movements or ...

Both the client and server are using pre-release 1.2.1.2 64bit on W7 pro 64bit OS.

https://www.youtube.com/watch?v=bfWNbMfxn4I

The reason for right clicking on the VNC shortcut file is:
I wanted to show that I only started two VNC sessions...
...no issue with the mouse left clicking too many times ...

Did you see orphaned Status windows when you ran your script?

If not, then maybe something is different when starting VNC by rapidly running several VNC [INI] shortcut files like the one that I posted.

You are correct, there is probably no real life use for a batch file that connects one VNC ...

Difference between cancel close button
1) The status screen always open [cancel], before connection.
[Close] is while connected

[cancel]: disconnect the viewer -> This should indicate that a connection fail, you try to connect to a pc that doesn't have
vnc running or can't connect, the network ...

I did see one permanent* grey screen today. Refresh did not help. I confirmed that the new server version was in use.

*sometimes (if VNC sessions already exists) subsequent VNC sessions will be all grey for a second or two. This is not a problem.

For what it is worth: the permanent grey screen ...

That's good news...let's hope it also fix the grey issue for other people........ It seems to have fixed it for me too. I tested the version in your zipped file on more that 30 live/real computers and on two Virtual computers (a mixture of W7 64bit, W7 32bit and XP 32bit).

Thanks for your time on ...

I guess it depends on what you mean by a static screen.

https://www.youtube.com/watch?v=IyJxt6FI-vk

The video shows two W7 pro 64bit Virtual Machines side by side. The "remote" VM is playing a video full screen.

I sent you a PM with the log file.

I stopped the service on the remote computer shortly after the grey screen happened. That should have ended the log collection near the grey screen event.

That did not seem to help

https://www.youtube.com/watch?v=VI0gQliaj7k

> Does the grey screen show all buttons ?
All of the buttons eventually appear, but the screen is still grey.

https://www.youtube.com/watch?v=iVoM0Z2-X3k

In that video, the grey screen has control, but the user cannot see where he is clicking.

The video also shows the build info on the server ...

Thanks for looking into the issue.

The setup for the video used two VirtualBox VMs (both running XP) and VirtualBox's Nat Network.

Maybe others that see this issue will be able to suggest a way for you to replicate it.

This grey screen issue happens on Windows 7 (32bit and 64bit).

It also happens on XP. Please see the video below:

https://www.youtube.com/watch?v=746FVbqiBh8

See the info here:
http://www.uvnc.com/docs/uvnc-viewer/52-UltraVNC-viewer-commandline-parameters.html

-autoscaling
"C:\Program Files\uvnc bvba\UltraVNC\vncviewer.exe" -autoscaling hostname:5900

-scale
"C:\Program Files\uvnc bvba\UltraVNC\vncviewer.exe" -scale 1/5 hostname:5900
where hostname ...

I try to repeat it without luck.

Server and viewer are both 1.2.11 ?
This look simular to a bug we had in the previous version and was reported fixed in 1211.
But has the cause was some initiating timing issue's...

Yes, both server and viewer are 1.2.1.1.

Most of the time we get a grey screen ...

Our current work around is to open more connections until one of them works. For us, it often takes more than a dozen new connections to get a working one

I have seen threads talking about grey screens. I've been getting those even with older versions of uVNC and I'm still seeing the grey screen issue with version 1.2.1.1.

I use a VNC [INI] file (with password hash saved) to make a view only connection to computer A:
[Connection]
host=10.0.2.5 ...