paulo_v
Sat Jul 02 12:39:56 CDT 2005
On Sat, 2 Jul 2005 18:04:02 +0100, "Mike M" <No_Spam@Corned_Beef.Only>
wrote:
>Unfortunately the applications launched via the various registry run keys
>are launched synchronously rather than sequentially. I would suggest that
>you perhaps consider moving the launch point for your Clock Synchroniser
>to perhaps the Programs | Startup folder.as this is I think the last of
>the various startup locations accessed in the startup process.
>
>You may want to have a look at KB 179365 - "INFO: Run, RunOnce,
>RunServices, RunServicesOnce and Startup"
>(
http://support.microsoft.com/?kbid=179365).
Thanks Mike, but it's NOT the Clocker that worries me. It's the fact
that if the Clocker can get in before the firewall becomes operative
then so too could some other "rogue" task that installs itself
unanounced in the start-up lists. :-(
I've tested this supposition by removing the Clocker's permission for
accessing the Internet then restarting. The Clocker managed to
synchronize thru NTP BEFORE the firewall became operative :-(
I was just trying to see if I could close what appears, to me, to be a
loophole.
Such is life! :-((((