The problem is the admins want to see what has hung, and because of this they are switching to PC Anywhere which does not have the problem. For VNC to be taken seriously by corporate IT this has to be addressed so it works like PC Anywhere where it is the last service to shutdown.
Tony Caduto
Programmer/Analyst
M&I Trust and Investment Management
Michael Ossmann
<michael.ossmann@alttech To:
[EMAIL PROTECTED]
.com> cc:
Sent by: Subject: Re: TightVNC 1.2.3
released
[EMAIL PROTECTED]
ch.att.com
03/25/2002 02:30 PM
Please respond to
vnc-list
There was a good thread on this subject ("shutdown gotcha with Win32
host") about 3 weeks ago. Andrew van der Stock had a good description
of what the problem is and some suggestions for how it might be fixed.
Jake Hoover found this handy workaround:
http://www.winguides.com/registry/display.php/933/
Which allows you to set an automatic timeout for any "end task"
situations. Typically the problem with VNC going down early is that the
connection is lost prior to the system hanging on an "end task" box.
There were also some suggestions for how to force an unconditional
reboot (risking data loss).
--
Mike Ossmann, Tarantella/UNIX Engineer/Instructor
Alternative Technology, Inc. http://www.alttech.com/
---------------------------------------------------------------------
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
---------------------------------------------------------------------
