If VNC was written in Pascal I would fix it myself, but alas I am no C/C++
guru.
I think it would just require tweaking the service code in the win32 VNC
server, but I don't know for sure.
Win32 services respond to a shutdown message and this can be ignored and
the service can ignore it until it is the last service running, then accept
the shutdown message.
Any C/C++ developers can kick in here :-)
Tony Caduto
Programmer/Analyst
M&I Trust and Investment Management
"Alex K. Angelopoulos"
<alex "at" bittnet.com> To: <vnc-list "at" uk.research.att.com>
Sent by: cc:
owner-vnc-list "at" uk.resear Subject: Re: Forced Shutdown of Windows NT/2K Systems
ch.att.com
03/26/2002 11:45 AM
Please respond to
vnc-list
This is exactly the reasoning behind the argument that VNC should include
certain extra functionality on Windows platforms.
The issue is not a problem with VNC; it's a problem with the underlying OS
if I understand it correctly. For corporate use, however, the point is not
"who is at fault?" but "how do we fix it quickly?" and that comes down to
switching to a product such as pcAnywhere all too often.
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------