Re: autoexec.nt elusive
I have done that, a few days ago, and again today. That method doesn't
correct my computer clock.
There is something wacko going on, beyond even the reported nuances of the
Windows time service application. I have read that if the local computer
clock is FAST, invocation of the service will slow the clock gradually to
bring it into compliance with atomic time. If the local computer clock is
SLOW (i.e, behind atomic time), then the correction will be immediate.
Excerpt from
http://www.microsoft.com/technet/prodtechnol/windows2000pro/maintain/w2kmngd/16_2kwts.mspx
..
If the local clock time of the client is behind the current time received
from the server, the Windows Time service will change the local clock time
immediately.
..
If the local clock time of the client is more than three minutes ahead of
the time on the server, the service will change the local clock time
immediately.
..
If the local clock time of the client is less than three minutes ahead of
the time on the server, the service will quarter or halve the clock
frequency for long enough to synchronize the clocks.
..
If the client is less than 15 seconds ahead, it will halve the frequency;
otherwise, it will quarter the frequency. The amount of time the clock
spends running at an unusual frequency depends on the size of the offset
that is being corrected.
I have just observed this to be the case, through experiment, by moving my
computer clock AHEAD one minute, then attempting correction, and BEHIND one
minute, then attempting correction.
I'm digressing from the context of the original thread here...but for
reason. I want to demonstrate that I have attempted to personally solve
this issue, and more importantly, to share my dilemma.
Dilemma? Yes. There's a larger problem. And I suspect its essence lies in
the nuances of the time service, rather than the primary topic in our
thread.
Yes, I can automatically start the Windows Time Service in the manner you
recommended. But (dilemma), it doesn't correct my local computer clock, if
I do that. I have to "restart" the service. It's as if I'm premature in
starting the Windows Time Service, if I do it automatically. Perhaps it
starts so early that the computer isn't ready to poll the internet yet, to
get the correct atomic time.
So if you've got the answer, now that I've digressed, I'd appreciate your
sharing it with me.
Regards,
John B
--
Sent via OE by John, from MERCURY
"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:E9BA0E90-C7BE-4137-9ED4-C58FCC1B80C1@microsoft.com...
> You only need to set the time source once. No need for the logon batch. No
> need to start the Windows Time service from batch. Set it's startup type
to
> 'Automatic'
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "John B" wrote:
> > I'm doing that, quite exactly. But as I have put "net time /querysntp"
as
> > a
> > line entry in autoexec.nt, that line is replied to with "Bad command or
> > file
> > name" upon my invocation of "start, run, command [enter]"
> >
> > Once I open a command window, then "net time /querysntp [enter]" will
> > indeed
> > function as expected.
> >
> > I don't know why ALL my line entries are "so flunked" when invoked
within
> > autoexec.nt from "start, run, command [enter]"
> >
> > Your comments would be greatly appreciated.
> >
> > Thanks.
> >
> > The sloop John B.
>
kRqi.489$cV6.424@newsfe04.lga...