Someone posted a fairly detailed description of what exactly is happening some months ago - search the archives for more details. I have not heard anything about changing this, although I think it would be incredibly useful...
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 21, 2002 12:53 PM To: [EMAIL PROTECTED] Subject: Big problem with the VNC service on WIN32 I have noticed that when running as a service VNC is the first thing to shutdown. This can cause problems when doing a reboot if another app or service displays a error message. PC anywhere does not do this. It actually happened to me the other day when I rebooted a server remotely, a error message popuped up and the server never rebooted. I am assuming that the VNC server is responding to the WM_CLOSE message when it actually should not be. This problem is holding VNC back in the corp enviroment. Are there any plans to fix this? Thanks, Tony Caduto Programmer/Analyst M&I Trust and Investment Management --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
