Dear group:

I recently upgraded my WinVNC to version 4.0 Built Jun 15, 2004 on a Windows Me 
machine.

I was somewhat concerned about the upgrade since I had problems with 4.0beta hanging
the machine after a period of time, i.e. the screen freezes, the keyboard freezes and 
I have
to reboot the machine (no blue screen of death).

I checked the documentation regarding VNC 4.0 Known Bugs and Features and noticed
that item dated 13 Jul 2004 (5)  might be the issue in my case so I increased the 
disconnect idle clients after (seconds) parameter
to 2000000 as indicated in the workaround.  Unfortuantely
the problem continues to persist.  MS System Configuration Utility displays the 
startup command
(upon boot) as "c:\program files\realvnc\vnc4\winvnc4.exe" -noconsole -service which I 
assume
to mean that VNC begins as a service.  The registry item "Idle Timeout" is set to 
2000000.  The "When last client disconnects" is
set to "Do nothing".

I'm running vncviewer on a Linux box which accesses that Windows Me machine.
I'm running vnc-4.0-1.beta4.11 on Fedora Core 2.

Ideas would be appreciated.

Thank you
Lou
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to