List Updates/Changes for 2014, please suggest

[Rudi De Vos]

I have some time to prepare an update, a list could be handy as starting point.

List
1) Repeater 2014 + server ( added keepalive messages ) : Both need to be updated, backward compatible not possible as repeater was original made without a version check. (OK)
2) Save passwd/options fix: Current it fail if the logged user is a domain admin. (REQUIRE TEST)
3) Logmein alternative ( test started, waiting feedback)

Please add sugestions..

Current no downloads, download wil be added when more itims are fixed

[Rudi De Vos]

4) mirror driver: wrong colors driver in 16bit mode ( vmware etc..) (OK)

[Rudi De Vos]

Downloads
http://www.uvnc.eu/1200/

free logmein alternative
(see http://forum.ultravnc.net/viewtopic.php?f=69&t=30848 )
http://www.uvnc.eu/download/uvnc2me/uvnc2me11.zip

[Nick_od]

http://www.uvnc.eu/1200/
does not work "winvnc32.exe" program does not start
I have windows XP SP3 32bit

[Rudi De Vos]

Indeed, xp was not working
fixed, bin was made with wrong compiler

[ahussein49]

the colors are messed up when the computer is locked on both 32bit and 64bit.

I am using windows 2003 32bit and windows 2008 R2 64 bit.

[Rudi De Vos]

colors are messed up:
With or without mirror driver ?

[ahussein49]

with the mirror driver.

this problem only happens when the computer is locked. as soon as I unlock it, the colors show up right again.

[Rudi De Vos]

It's a 16bit color + mirror driver issue.
unlock -> driver used
lock -> driver disabled

driver -> BGR
real display -> RGB

In 1.1.9.6, the color was wrong when unlocked, know it seems to be when locked

I don't know if it can be easy fixed...

[Prisma]

1) Repeater 2014 + server ( added keepalive messages ) : Both need to be updated, backward compatible not possible as repeater was original made without a version check. (OK)

Please excuse this stupid question, but which side do you mean to be not backward compatible? Server or repeater side?
If I want to update the repeater now, but I have old 2013 winvnc.exe out there, this will work, won't it? But a new winvnc.exe won't work with old repeater, will it?

This means the 2014 server is not backward compatible to old repeater, right? (I hope so!!)

[Rudi De Vos]

No, the new repeaters keepalive message is only understood by the new servers.
The old server get a unknown message and close connection.

The old server doesn't crash. And if auto reconnect is set it reconnect to the repeater.
But the keepalive message behave like a disconnect message.

-------------old server--------
Server send init, server wait viewer answer.
It's the server that's waiting for the viewer and the viewer answer need in some specific format.
If some other format arrive -> close connection

-------------new server--------
Server send init, server wait viewer answer.
If some other format arrive -> check if keepalive : Yes/ cont listening NO/close connection

It's just impossible to make something that works with old servers

[Prisma]

It's just impossible to make something that works with old servers

But it's also impossible to update 600 customers helpdesk the same time!

This means, we won't be able to update repeater (and viewer?) as long old winvnc.exe are out there.
And if we wait updating our side (repeater and viewer) and we role out the new server and hope that in a few months only new servers exist? As far as I understood this won't be also not possible, because the new server will close the connection with an old repeater/viewer. Is this correct?

[Rudi De Vos]

new server understand keepalive, when not used it just behave like before.

old repeater + new server -> works like 1196 , keepalive is never send by the repeater
new repeater + new server -> repeater send keepalive, it's understood and server doesn't timeout
new repeater + old server -> repeater send keeplaive, server don't understand it and reconnect

For the viewer it doesn't make a difference, the keepalive is only send on the server site.

Old servers will still work with the new repeater.
The only difference is that with the old repeater ( during "waiting for viewer connection") reconnected every x minutes, the new every minute.
We can increase this value to 5-15 minutes, 1 minute is just for testing and isn't needed to keep the line open.
But is still think that the new repeater with a 25 minute keepalive interval behave better then the old repeater, even with an old server.
Yes the server reconnect, but all is proper done and sockets are proper cleaned on both sites.

[Prisma]

OK, we'll have a big update roll out within 4 weeks. So it's recommend to roll out the new server with this update. We'll keep the old repeater as long as technical possible. If we have to renew the repeater one day hopefully only new servers are out there...

When will we have a stable 1.2? Can we help testing? What are the neuralgic functions to test?

[Nick_od]

hi
I started Repeater "Changes for 2014" Windows 2003 server

I have connected 100 (id) server
discovered the problem:
sometimes come ID
when I want to connect to the ID
Repeater shows that there is no such ID
but after restarting Repetar this ID is presented, and can connect to this ID.

it has already been tested with the latest version (winvnc64.exe Changes for 2014)
but I expect that there is not the problem server UltraVNС this problem in the Repeater

[Kirck]

It's a 16bit color + mirror driver issue.
unlock -> driver used
lock -> driver disabled

driver -> BGR
real display -> RGB

In 1.1.9.6, the color was wrong when unlocked, know it seems to be when locked

I don't know if it can be easy fixed...

Same issue, thanks for your effort.

[Rudi De Vos]

It's a 16bit color + mirror driver issue fixed in src for next update.
seems some previous patch was the actual cause

[danielnice]

On the client side, I would like a "rate limit mouse cursor messages" to avoid flooding the server with so many packets.
This option has always been present on RealVNC. Can this be added back to UltraVNC ?

[Rudi De Vos]

I was just implementing it, but found that is was already done a while ago..

rate limit mouse cursor messages: This is implemented
Check viewer option "mouse event throttle" you can set your ms ( default=0)

[Prisma]

OK, I needed 2 explanations. But after the second one I thought I understood. But obviously I didn't:

If I run a test winvnc 2014 (service mode) against distributor/repeater 2013, which as far as I understood should work, winvnc-service tries 8 times to connect with winvnc+service_commandline and stops trying.

Can anybody confirm that winvnc 2014 is able to connect to repeater 2013?

[CommanderLake]

I need the mirror driver to be plug and play so no restart is required, also writing the frame buffer to the C: drive is an extremely bad idea it will wear out SSD's quickly.

[Rudi De Vos]

The driver use a memory mapped file as shared memory.
See MapViewOfFile()
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
The file is create on start, but data is written direct into the system memory...else the driver would be slow as hell

[Prisma]

Please excuse my insisting.

Rudi wrote:

old repeater + new server -> works like 1196 , keepalive is never send by the repeater

Can anybody confirm that winvnc 2014 is actually able to connect to repeater 2013? I already reported this, but I'll do it again:

Prisma wrote:

If I run a test winvnc 2014 (service mode) against distributor/repeater 2013, which as far as I understood should work, winvnc-service tries 8 times to connect with winvnc+service_commandline and stops trying.

This is an essential question.

[Rudi De Vos]

That should work.
SERVER
pre 2014
if message is RFB cont
else close error
2014
if message is RFB cont
else if message is KEEPALIVE keep waiting
else close on error

This doesn't change any behaviour if KEEPALIVE is never sended.

[Prisma]

OK, THX for info. Possibly a local problem. But I can't imagine which one... Continuing testing...

[Prisma]

Rudi, for a full test we need a WIN2000 build of 1.2.0.0 Would you please be so kind and include it in upload? Or is WIN2000 support depreciated or ended?

[Rudi De Vos]

added
winvnc_1200_xp.zip

[dgoiko]

-A "restart service" button under the "stop service"
-An option in the repeater to kick people. Would be nice if combined with previous option.
-A multi-tab client, so I could connect to 3 servers in the same window, with a tab layour like modern browsers.
-WoL client built in the repeater. We already have the last IP (and MAC if you decided to keep it). Its not a big deal to configure a persistent DB in the repeater to remember the last IP/MAC from each ID


More advanced things:
-A way to send a file to a server and force it to execute it/store it somewhere, without even sending any image to the client. It would be usefull for massive deplyments. You could add a login feature if needed.
-An easy way (or an API) for external applications to communicate with the repeater. My idea is to make a frontend which asks the repeater for info about stablished connections, waiting servers etc.
-Some way for an application to ask a running server about the current state of his connecion. My idea it to build a service to watch over the UVNC service and avoid connection losses.

[Rudi De Vos]

I see what's possible...not simple requests.

[CommanderLake]

Am I the only one wanting plug'n'play?