Rudi De Vos wrote:Chunk is maintained by someone else, you gonna have better luck posting it there.
VNC give this error when winvnc.exe is started and the ultravnc.ini doesn't have a passwd.
If you can preset the ultravnc.ini before running the compiler you don't have the warning.
Rudi De Vos wrote:"Enable Blank Monitor on Viewer Request" only works with OS's that support transparent layers. (xp-win7)
w2k: not supported
win8: not supported
"uvnc_settings.exe"Compiler settings modified to avoid the dependency
valid passwd (sample "aaaaaaaa")
It's not because you have something as passwd string it's a valid password.
The correct way to add a password to the ultravnc.ini is via winvnc or via the setpasswd.exe
this add passwd=DE2A73CE1500270B90
Rudi De Vos wrote:addons are the latest version
updated 18/12/2013 ( version is 22.214.171.124)
Rudi De Vos wrote:plants: The time for the initial drawing isn't longer. Before you just could not see the initial drawing
( used to measure bandwidth), now it show on the screen so at least you know the connection
is in progress. The blank always existed, but wasn't visable. Could not find the reason, it doesn't
always happen, but it could be caused with a auto encoder switch.
Does the viewer stop on connection of the second viewer ?
Some time after both are connected ?
Never tested 2 outgoing connections simultanious, always tested with multiple incoming connection.
But it should not make a difference.
mdrollins83 wrote:I have an issue with 126.96.36.199 not allowing me to use the Start Menu command or clicking the Start button during a remote session with the host computer. Anyone else experiencing this issue? I'm new to UVNC, so I'm not sure if maybe it is just something I'm missing in my configuration. The host machine is running Windows XP. I have another host machine that I have UVNC installed on and it seems to work okay on it, so I'm not sure what the issue really is. Any suggestions?
Users browsing this forum: No registered users and 1 guest