Thank you to everyone for all your advise. I was going to write back today
at work, but W2K rebooted on me when I tried to VNC in! The good thing I
know is the reboot happened at the exact moment that I attempted to VNC in.
Therefore it is definitely a problem/conflict due to that. I suppose I am
going to procede by uninstalling/reinstallind VNC and seeing if that fixes
it. Michael, I have already patched ZA to fix the SP1 problems. James, the
reboot problem is the one that popped up with SP1. The other problem has
been there since day 1. ZA apparantly doesn't like the fact that VNC is
running as a server before it boots up. Andy, thanks for the advice. I
will also try to set WinVNC to come up after ZoneAlarm. This reboot problem
has me stumped, Anyone know how to analyze NTMiniDumps?
-----Original Message-----
From: owner-vnc-list@uk.research.att.com
[mailto:owner-vnc-list@uk.research.att.com]On Behalf Of Andy Mason
Sent: Thursday, August 31, 2000 9:11 AM
To: 'vnc-list@uk.research.att.com'
Subject: RE: Win 2000, Zone Alarm, Random Reboots and other goodies
Unfortunately it doesn't work that way on NT. You should be able to add a
Key to each service called DependsOnService as a REG_MULTI_SZ (they're in
HKLM\SYSTEM\CurrentControlSet\Services\)
Then add the name of the service to wait for as the value.
In your case, you would add the key to WinVNC and tell it to wait for ZA.
Have a look at IISADMIN for an example.
You have to use Regedt32 instead of Regedit to be able to add a REG_MULTI_SZ
Andy.
PS - here's some more info, somewhat related:
http://support.microsoft.com/support/kb/articles/q179/3/65.asp
-----Original Message-----
From: Jonathan Morton [mailto:j.d.morton@lancaster.ac.uk]
Sent: Thursday, August 31, 2000 5:16 AM
To: vnc-list@uk.research.att.com
Subject: Re: Win 2000, Zone Alarm, Random Reboots and other goodies
> timestamped. Anyway, the main question that I would pose is how should I
> start up WinVNC after a reboot AFTER ZA to get me past the problem of
having
> to stop/restart the service? If it ran as it should then I should simply
be
> able to login if a reboot did occur.
A common method to change startup sequence is to change the filenames of the
affected files, so that they alphabetically come in the desired order. This
method is used on UNIX and Macintosh systems, so I see no reason why it
shouldn't work on Windows in some form.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
main e-mail: <chromi@cyberspace.org>
attachments over 100K: <j.d.morton@lancaster.ac.uk>
The key to knowledge is not to rely on people to teach you it.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo@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@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@uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
-----------------------------------------
TridiaVNC - http://www.tridiavnc.com/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 18:48:57 EDT