NT Service handling (was: bad review)

Michael nshbyjan "at" gte.net
Wed, 19 Sep 2001 12:05:42 +0000


I have installed the latest client on a number of Win2k machines.

On about half it works and on the other half it does not work. They are all
same regarding instll, etc. They all have basic Win2k not service packs.
Trying to use IE version 5.5+.

Any help appreciated.

Michael



----- Original Message -----
From: "Andrew van der Stock" <ajv "at" greebo.net>
To: <vnc-list "at" uk.research.att.com>
Sent: Tuesday, September 18, 2001 11:59 PM
Subject: NT Service handling (was: bad review)


> This is because VNC does not use NT service dependancies and uses a
> simplistic SCM handler, and thus is started last and terminated first.
> Changing things so that VNC relies on some of the other services will
> allow it to start a little quicker as well.
>
> For a long surviving shutdown, the best bet is to change the service
> control handler in WinVNC. When the SCM issues a SERVICE_ACCEPT_SHUTDOWN
> message, you clean up resources that can be damaged across a reboot (ie
> flush and close any open files and registry handles), and then issue a
> message called "SERVICE_CONTROL_PENDING" with 30 seconds set aside in
> dwWaitHint and return control to the SCM.
>
> During the shutdown, SCM ignores the pending status and WinVNC will get
> terminated as the box goes down just before reboot. However, if you get
> asked again (during a long shutdown, typical of Exchange servers, etc),
> just set another 30 seconds in dwWaitHint and reset the pending hint.
>
> WinVNC after doing this should *not* try to use any of the previously
> open files or registry keys; if the user is able to stop the shutdown
> and tries to change VNC settings or re-authenticate, VNC should display
> a dialog stating along the lines of "a shutdown did not occur properly,
> and should it restart VNC?".
>
> Andrew
>
> -----Original Message-----
> From: owner-vnc-list "at" uk.research.att.com
> [mailto:owner-vnc-list "at" uk.research.att.com] On Behalf Of Tony Caduto
> Sent: Wednesday, 19 September 2001 04:14
> To: vnc-list "at" uk.research.att.com
> Subject: Re: Bad Review of VNC at CNET
>
>
> Another big problem that needs to be addressed is the fact that VNC when
> run as a service shuts down before everything, so if something hangs
> after VNC shuts down, you can never restart the server.... unless you
> physically go the machine.
>
> Tony Caduto
>
> ----- Original Message -----
> From: "David Brodbeck" <DavidB "at" mail.interclean.com>
> To: <vnc-list "at" uk.research.att.com>
> Sent: Tuesday, September 18, 2001 7:42 AM
> Subject: RE: Bad Review of VNC at CNET
>
>
> > I'll second this...would it really be that much extra work to add
> > dialog
> box
> > controls for some of those registry keys?  Or maybe just a stand-alone
>
> > configuration utility?  Even editing a flat configuration file would
> > be easier than having to dive into Microsoft's hellish registry
> > structure. ;)
> >
> > -----Original Message-----
> > From: Andrew van der Stock [mailto:ajv "at" greebo.net]
> > Sent: Monday, September 17, 2001 10:18 PM
> > To: vnc-list "at" uk.research.att.com
> > Subject: RE: Bad Review of VNC at CNET
> >
> >
> > Documentation could be improved, particularly for first time users.
> > Dialog boxes could be better from a purist HCI point of view Security
> > can be made easier (particularly the hidden AuthHost stuff)
> > Localization could be done properly
> > ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list to
> > majordomo "at" uk.research.att.com See also:
> > http://www.uk.research.att.com/vnc/intouch.html
> > ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list to
> majordomo "at" uk.research.att.com See also:
> http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to majordomo "at" uk.research.att.com
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------