autoexec.nt elusive

[John B]

I am running under Windows 2000 Pro + sp4. I have gone into a CMD window
and typed "autoexec.nt" + [enter]. A file executes OTHER than the one and
only autoexec.nt file that I can find in my computer... The one I find is
at %systemroot%\system32\autoexec.nt.

How can this be?
Can anyone refresh my memory? It seems there were various "autoexec" files
under Windows 95...a long time ago. I have used "attrib" to scan the
system32 directory, which should ferret out hidden files, but I only see
autoexec.nt...the same one I can edit.

TIA
John

 

[Pegasus \(MVP\)]

"John B" <jb@nospam.com> wrote in message
news:_xqqi.17$U_5.3@newsfe05.lga...
>I am running under Windows 2000 Pro + sp4. I have gone into a CMD window
> and typed "autoexec.nt" + [enter]. A file executes OTHER than the one and
> only autoexec.nt file that I can find in my computer... The one I find is
> at %systemroot%\system32\autoexec.nt.
>
> How can this be?
> Can anyone refresh my memory? It seems there were various "autoexec"
> files
> under Windows 95...a long time ago. I have used "attrib" to scan the
> system32 directory, which should ferret out hidden files, but I only see
> autoexec.nt...the same one I can edit.
>
> TIA
> John
>

There is only one autoexec.nt. It's the one you found in the System32
folder. Why do you want to execute it? It's a legacy file meant for
legacy applications! If you want a certain command to run at logon
time, place its shortcut into your Startup folder! If you want a certain
command to run at boot time, use the Task Scheduler!

 

[John B]

Thanks for the astute suggestions. Yes, those two methods are quite
appropriate. I want to invoke a clock synchronization scheme to NIST, and
since I turn my computer off and on quite frequently, I thought I could just
invoke "net start w32time" upon start up... Of course this didn't work,
when I installed that command line in autoexec.nt. That's why I posted.

(Given that I have set my computer to appeal to time server
time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to start
that service, w32time, to synchronize my clock to atomic time.) So I
suppose I could use Task Scheduler for this.

Better still, NIST provided me with a convenient executable for the purpose
of periodic synchronization: nistime-32bit.exe.

That being said, I am still curious about autoexec.nt. When, quite
specifically, is it executed, may I ask? It doesn't seem to happen for me.

Thanks for the replies.



--
Sent via OE by John, from MERCURY
"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:ep7zq5J0HHA.2312@TK2MSFTNGP05.phx.gbl...
>
> "John B" <jb@nospam.com> wrote in message
> news:_xqqi.17$U_5.3@newsfe05.lga...
> >I am running under Windows 2000 Pro + sp4. I have gone into a CMD window
> > and typed "autoexec.nt" + [enter]. A file executes OTHER than the one
and
> > only autoexec.nt file that I can find in my computer... The one I find
is
> > at %systemroot%\system32\autoexec.nt.
> >
> > How can this be?
> > Can anyone refresh my memory? It seems there were various "autoexec"
> > files
> > under Windows 95...a long time ago. I have used "attrib" to scan the
> > system32 directory, which should ferret out hidden files, but I only see
> > autoexec.nt...the same one I can edit.
> >
> > TIA
> > John
> >
>
> There is only one autoexec.nt. It's the one you found in the System32
> folder. Why do you want to execute it? It's a legacy file meant for
> legacy applications! If you want a certain command to run at logon
> time, place its shortcut into your Startup folder! If you want a certain
> command to run at boot time, use the Task Scheduler!
>
>

 

[Pegasus \(MVP\)]

It happens for you too. Open up autoexec.nt, add this
line as a second line, then save the file:

echo We come on the sloop John B

Now click Start / Run / command{OK]

and watch the screen, then remember that command.com
is a legacy 16-bit command processor that should not be
used under Win2000.


"John B" <jb@nospam.com> wrote in message news:KEHqi.8$991.4@newsfe06.lga...
> Thanks for the astute suggestions. Yes, those two methods are quite
> appropriate. I want to invoke a clock synchronization scheme to NIST, and
> since I turn my computer off and on quite frequently, I thought I could
> just
> invoke "net start w32time" upon start up... Of course this didn't work,
> when I installed that command line in autoexec.nt. That's why I posted.
>
> (Given that I have set my computer to appeal to time server
> time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to start
> that service, w32time, to synchronize my clock to atomic time.) So I
> suppose I could use Task Scheduler for this.
>
> Better still, NIST provided me with a convenient executable for the
> purpose
> of periodic synchronization: nistime-32bit.exe.
>
> That being said, I am still curious about autoexec.nt. When, quite
> specifically, is it executed, may I ask? It doesn't seem to happen for
> me.
>
> Thanks for the replies.
>
>
>
> --
> Sent via OE by John, from MERCURY
> "Pegasus (MVP)" <I.can@fly.com> wrote in message
> news:ep7zq5J0HHA.2312@TK2MSFTNGP05.phx.gbl...
>>
>> "John B" <jb@nospam.com> wrote in message
>> news:_xqqi.17$U_5.3@newsfe05.lga...
>> >I am running under Windows 2000 Pro + sp4. I have gone into a CMD
>> >window
>> > and typed "autoexec.nt" + [enter]. A file executes OTHER than the one
> and
>> > only autoexec.nt file that I can find in my computer... The one I find
> is
>> > at %systemroot%\system32\autoexec.nt.
>> >
>> > How can this be?
>> > Can anyone refresh my memory? It seems there were various "autoexec"
>> > files
>> > under Windows 95...a long time ago. I have used "attrib" to scan the
>> > system32 directory, which should ferret out hidden files, but I only
>> > see
>> > autoexec.nt...the same one I can edit.
>> >
>> > TIA
>> > John
>> >
>>
>> There is only one autoexec.nt. It's the one you found in the System32
>> folder. Why do you want to execute it? It's a legacy file meant for
>> legacy applications! If you want a certain command to run at logon
>> time, place its shortcut into your Startup folder! If you want a certain
>> command to run at boot time, use the Task Scheduler!
>>
>>
>
>
>

 

[Dave Patrick]

Why not use the Windows Time service?

net time /querysntp

net time /setsntp:132.163.4.101


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"John B" wrote:
> Thanks for the astute suggestions. Yes, those two methods are quite
> appropriate. I want to invoke a clock synchronization scheme to NIST, and
> since I turn my computer off and on quite frequently, I thought I could
> just
> invoke "net start w32time" upon start up... Of course this didn't work,
> when I installed that command line in autoexec.nt. That's why I posted.
>
> (Given that I have set my computer to appeal to time server
> time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to start
> that service, w32time, to synchronize my clock to atomic time.) So I
> suppose I could use Task Scheduler for this.
>
> Better still, NIST provided me with a convenient executable for the
> purpose
> of periodic synchronization: nistime-32bit.exe.
>
> That being said, I am still curious about autoexec.nt. When, quite
> specifically, is it executed, may I ask? It doesn't seem to happen for
> me.
>
> Thanks for the replies.

 

[John B]

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.

--
Sent via OE by John, from MERCURY
"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:8B3A1292-E03E-4C9A-91F2-50E3221BD8BB@microsoft.com...
> Why not use the Windows Time service?
>
> net time /querysntp
>
> net time /setsntp:132.163.4.101
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "John B" wrote:
> > Thanks for the astute suggestions. Yes, those two methods are quite
> > appropriate. I want to invoke a clock synchronization scheme to NIST,
and
> > since I turn my computer off and on quite frequently, I thought I could
> > just
> > invoke "net start w32time" upon start up... Of course this didn't work,
> > when I installed that command line in autoexec.nt. That's why I posted.
> >
> > (Given that I have set my computer to appeal to time server
> > time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to start
> > that service, w32time, to synchronize my clock to atomic time.) So I
> > suppose I could use Task Scheduler for this.
> >
> > Better still, NIST provided me with a convenient executable for the
> > purpose
> > of periodic synchronization: nistime-32bit.exe.
> >
> > That being said, I am still curious about autoexec.nt. When, quite
> > specifically, is it executed, may I ask? It doesn't seem to happen for
> > me.
> >
> > Thanks for the replies.
>

 

[John B]

First of all, I had never before invoked "start, run, command" only "start,
run, cmd" under Windows 2000. There is a difference. The former invokes
autoexec.nt, while the latter does not. So we have accomplished something
there, at least.

Secondly, your "echo" does indeed work as expected. I just see "We come on
the sloop John B" on a separate line, in the resultant command window, with
no protests whatsoever from the operating system.

But other reasonable line entries are rejected as "Bad." (See reply to
David Patrick.) I don't know why "net time /querysntp [enter]" works in a
command window, but not in autoexec.nt.

Thanks for your replies.

The sloop John B.

--
Sent via OE by John, from MERCURY
"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:ewsnI4R0HHA.2484@TK2MSFTNGP06.phx.gbl...
> It happens for you too. Open up autoexec.nt, add this
> line as a second line, then save the file:
>
> echo We come on the sloop John B
>
> Now click Start / Run / command{OK]
>
> and watch the screen, then remember that command.com
> is a legacy 16-bit command processor that should not be
> used under Win2000.
>
>
> "John B" <jb@nospam.com> wrote in message
news:KEHqi.8$991.4@newsfe06.lga...
> > Thanks for the astute suggestions. Yes, those two methods are quite
> > appropriate. I want to invoke a clock synchronization scheme to NIST,
and
> > since I turn my computer off and on quite frequently, I thought I could
> > just
> > invoke "net start w32time" upon start up... Of course this didn't work,
> > when I installed that command line in autoexec.nt. That's why I posted.
> >
> > (Given that I have set my computer to appeal to time server
> > time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to start
> > that service, w32time, to synchronize my clock to atomic time.) So I
> > suppose I could use Task Scheduler for this.
> >
> > Better still, NIST provided me with a convenient executable for the
> > purpose
> > of periodic synchronization: nistime-32bit.exe.
> >
> > That being said, I am still curious about autoexec.nt. When, quite
> > specifically, is it executed, may I ask? It doesn't seem to happen for
> > me.
> >
> > Thanks for the replies.
> >
> >
> >
> > --
> > Sent via OE by John, from MERCURY
> > "Pegasus (MVP)" <I.can@fly.com> wrote in message
> > news:ep7zq5J0HHA.2312@TK2MSFTNGP05.phx.gbl...
> >>
> >> "John B" <jb@nospam.com> wrote in message
> >> news:_xqqi.17$U_5.3@newsfe05.lga...
> >> >I am running under Windows 2000 Pro + sp4. I have gone into a CMD
> >> >window
> >> > and typed "autoexec.nt" + [enter]. A file executes OTHER than the
one
> > and
> >> > only autoexec.nt file that I can find in my computer... The one I
find
> > is
> >> > at %systemroot%\system32\autoexec.nt.
> >> >
> >> > How can this be?
> >> > Can anyone refresh my memory? It seems there were various "autoexec"
> >> > files
> >> > under Windows 95...a long time ago. I have used "attrib" to scan the
> >> > system32 directory, which should ferret out hidden files, but I only
> >> > see
> >> > autoexec.nt...the same one I can edit.
> >> >
> >> > TIA
> >> > John
> >> >
> >>
> >> There is only one autoexec.nt. It's the one you found in the System32
> >> folder. Why do you want to execute it? It's a legacy file meant for
> >> legacy applications! If you want a certain command to run at logon
> >> time, place its shortcut into your Startup folder! If you want a
certain
> >> command to run at boot time, use the Task Scheduler!
> >>
> >>
> >
> >
> >
>
>

 

[Dave Patrick]

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.

 

[Pegasus \(MVP\)]

Since we have agreed that autoexec.nt is a tool for
legacy applications and that its use is inappropriate
under Win2000, why persist in exploring its idiosyncracies?


"John B" <jb@nospam.com> wrote in message
newskRqi.489$cV6.424@newsfe04.lga...
> First of all, I had never before invoked "start, run, command" only
> "start,
> run, cmd" under Windows 2000. There is a difference. The former invokes
> autoexec.nt, while the latter does not. So we have accomplished something
> there, at least.
>
> Secondly, your "echo" does indeed work as expected. I just see "We come
> on
> the sloop John B" on a separate line, in the resultant command window,
> with
> no protests whatsoever from the operating system.
>
> But other reasonable line entries are rejected as "Bad." (See reply to
> David Patrick.) I don't know why "net time /querysntp [enter]" works in a
> command window, but not in autoexec.nt.
>
> Thanks for your replies.
>
> The sloop John B.
>
> --
> Sent via OE by John, from MERCURY
> "Pegasus (MVP)" <I.can@fly.com> wrote in message
> news:ewsnI4R0HHA.2484@TK2MSFTNGP06.phx.gbl...
>> It happens for you too. Open up autoexec.nt, add this
>> line as a second line, then save the file:
>>
>> echo We come on the sloop John B
>>
>> Now click Start / Run / command{OK]
>>
>> and watch the screen, then remember that command.com
>> is a legacy 16-bit command processor that should not be
>> used under Win2000.
>>
>>
>> "John B" <jb@nospam.com> wrote in message
> news:KEHqi.8$991.4@newsfe06.lga...
>> > Thanks for the astute suggestions. Yes, those two methods are quite
>> > appropriate. I want to invoke a clock synchronization scheme to NIST,
> and
>> > since I turn my computer off and on quite frequently, I thought I could
>> > just
>> > invoke "net start w32time" upon start up... Of course this didn't
>> > work,
>> > when I installed that command line in autoexec.nt. That's why I
>> > posted.
>> >
>> > (Given that I have set my computer to appeal to time server
>> > time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to
>> > start
>> > that service, w32time, to synchronize my clock to atomic time.) So I
>> > suppose I could use Task Scheduler for this.
>> >
>> > Better still, NIST provided me with a convenient executable for the
>> > purpose
>> > of periodic synchronization: nistime-32bit.exe.
>> >
>> > That being said, I am still curious about autoexec.nt. When, quite
>> > specifically, is it executed, may I ask? It doesn't seem to happen for
>> > me.
>> >
>> > Thanks for the replies.
>> >
>> >
>> >
>> > --
>> > Sent via OE by John, from MERCURY
>> > "Pegasus (MVP)" <I.can@fly.com> wrote in message
>> > news:ep7zq5J0HHA.2312@TK2MSFTNGP05.phx.gbl...
>> >>
>> >> "John B" <jb@nospam.com> wrote in message
>> >> news:_xqqi.17$U_5.3@newsfe05.lga...
>> >> >I am running under Windows 2000 Pro + sp4. I have gone into a CMD
>> >> >window
>> >> > and typed "autoexec.nt" + [enter]. A file executes OTHER than the
> one
>> > and
>> >> > only autoexec.nt file that I can find in my computer... The one I
> find
>> > is
>> >> > at %systemroot%\system32\autoexec.nt.
>> >> >
>> >> > How can this be?
>> >> > Can anyone refresh my memory? It seems there were various
>> >> > "autoexec"
>> >> > files
>> >> > under Windows 95...a long time ago. I have used "attrib" to scan
>> >> > the
>> >> > system32 directory, which should ferret out hidden files, but I only
>> >> > see
>> >> > autoexec.nt...the same one I can edit.
>> >> >
>> >> > TIA
>> >> > John
>> >> >
>> >>
>> >> There is only one autoexec.nt. It's the one you found in the System32
>> >> folder. Why do you want to execute it? It's a legacy file meant for
>> >> legacy applications! If you want a certain command to run at logon
>> >> time, place its shortcut into your Startup folder! If you want a
> certain
>> >> command to run at boot time, use the Task Scheduler!
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>
>

 

[John B]

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.
>

 

[John B]

OK. I'll simply conclude that "autoexec.nt" is not only idiosyncratic, but
flawed. No big deal... as you imply. It's isolated in its "antiquity." I
suppose I could use a PIF of something like that, if I ever need to raise
some antiquated use, with preliminary settings. I did that some ten years
ago, under Windows 95.

Thanks for your fine responses.

Regards,
John B

--
Sent via OE by John, from MERCURY
"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:OksSoJa0HHA.1336@TK2MSFTNGP04.phx.gbl...
> Since we have agreed that autoexec.nt is a tool for
> legacy applications and that its use is inappropriate
> under Win2000, why persist in exploring its idiosyncracies?
>
>
> "John B" <jb@nospam.com> wrote in message
> newskRqi.489$cV6.424@newsfe04.lga...
> > First of all, I had never before invoked "start, run, command" only
> > "start,
> > run, cmd" under Windows 2000. There is a difference. The former
invokes
> > autoexec.nt, while the latter does not. So we have accomplished
something
> > there, at least.
> >
> > Secondly, your "echo" does indeed work as expected. I just see "We come
> > on
> > the sloop John B" on a separate line, in the resultant command window,
> > with
> > no protests whatsoever from the operating system.
> >
> > But other reasonable line entries are rejected as "Bad." (See reply to
> > David Patrick.) I don't know why "net time /querysntp [enter]" works in
a
> > command window, but not in autoexec.nt.
> >
> > Thanks for your replies.
> >
> > The sloop John B.
> >
> > --
> > Sent via OE by John, from MERCURY
> > "Pegasus (MVP)" <I.can@fly.com> wrote in message
> > news:ewsnI4R0HHA.2484@TK2MSFTNGP06.phx.gbl...
> >> It happens for you too. Open up autoexec.nt, add this
> >> line as a second line, then save the file:
> >>
> >> echo We come on the sloop John B
> >>
> >> Now click Start / Run / command{OK]
> >>
> >> and watch the screen, then remember that command.com
> >> is a legacy 16-bit command processor that should not be
> >> used under Win2000.
> >>
> >>
> >> "John B" <jb@nospam.com> wrote in message
> > news:KEHqi.8$991.4@newsfe06.lga...
> >> > Thanks for the astute suggestions. Yes, those two methods are quite
> >> > appropriate. I want to invoke a clock synchronization scheme to
NIST,
> > and
> >> > since I turn my computer off and on quite frequently, I thought I
could
> >> > just
> >> > invoke "net start w32time" upon start up... Of course this didn't
> >> > work,
> >> > when I installed that command line in autoexec.nt. That's why I
> >> > posted.
> >> >
> >> > (Given that I have set my computer to appeal to time server
> >> > time-a.timefreq.bldrdoc.gov as a reference, all I need to do is to
> >> > start
> >> > that service, w32time, to synchronize my clock to atomic time.) So I
> >> > suppose I could use Task Scheduler for this.
> >> >
> >> > Better still, NIST provided me with a convenient executable for the
> >> > purpose
> >> > of periodic synchronization: nistime-32bit.exe.
> >> >
> >> > That being said, I am still curious about autoexec.nt. When, quite
> >> > specifically, is it executed, may I ask? It doesn't seem to happen
for
> >> > me.
> >> >
> >> > Thanks for the replies.
> >> >
> >> >
> >> >
> >> > --
> >> > Sent via OE by John, from MERCURY
> >> > "Pegasus (MVP)" <I.can@fly.com> wrote in message
> >> > news:ep7zq5J0HHA.2312@TK2MSFTNGP05.phx.gbl...
> >> >>
> >> >> "John B" <jb@nospam.com> wrote in message
> >> >> news:_xqqi.17$U_5.3@newsfe05.lga...
> >> >> >I am running under Windows 2000 Pro + sp4. I have gone into a CMD
> >> >> >window
> >> >> > and typed "autoexec.nt" + [enter]. A file executes OTHER than the
> > one
> >> > and
> >> >> > only autoexec.nt file that I can find in my computer... The one I
> > find
> >> > is
> >> >> > at %systemroot%\system32\autoexec.nt.
> >> >> >
> >> >> > How can this be?
> >> >> > Can anyone refresh my memory? It seems there were various
> >> >> > "autoexec"
> >> >> > files
> >> >> > under Windows 95...a long time ago. I have used "attrib" to scan
> >> >> > the
> >> >> > system32 directory, which should ferret out hidden files, but I
only
> >> >> > see
> >> >> > autoexec.nt...the same one I can edit.
> >> >> >
> >> >> > TIA
> >> >> > John
> >> >> >
> >> >>
> >> >> There is only one autoexec.nt. It's the one you found in the
System32
> >> >> folder. Why do you want to execute it? It's a legacy file meant for
> >> >> legacy applications! If you want a certain command to run at logon
> >> >> time, place its shortcut into your Startup folder! If you want a
> > certain
> >> >> command to run at boot time, use the Task Scheduler!
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>

 

[Dave Patrick]

If the mobo can't keep good time then go after that problem first.

--

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 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