From time to time, my XP's clock would become late. Eg, last night it was
OK, but this morning, it was 15 minutes later. And every time I had to click
on the clock's "Internet time" to manually sync it.

I'd like to know if there's any command to accomplish this thing, so I could
put it in a batch and make it a schedule task.

TIA

I've found half answer to my own question. It seems like the command is "net
time".

The NTP server is already set, but I can't find how to launch the
synchronization using this command.

Any help is appreciated.

Ha ha, I've found answers to my own questions

For the record, the command is "w32tm /resync"

"Airman" wrote:

> Or this little freeware thing:
> http://www.archive.org/details/tucows_219295_EZTimeSync

Thank you. But even if it's free, if Windows' supplied softwares could do
the same job, ie w32tm + scheduler, I don't see the necessity to use
additional application, esp this is memory-resident program.

Hi Airman,
The Windows default time updater (w32time) only update the
clock once a week by default. You have to know how to edit the registry and
convert hexadecimals to change it to once a day. There is an older [NT4]
util from Microsoft called timeserv.exe which, when installed creates
another Time Service that can be configured to update up to four times a
day. This older utility can be had at:

http://www.tacktech.com/download.cfm...2/timeserv.zip

--

Cheers, Tim Meddick, Peckham, London.


"TFS" <(E-Mail Removed)> wrote in message
news:239D8676-E52E-4646-91EB-(E-Mail Removed)...
> "Airman" wrote:
>
>> Or this little freeware thing:
>> http://www.archive.org/details/tucows_219295_EZTimeSync
>
> Thank you. But even if it's free, if Windows' supplied softwares could do
> the same job, ie w32tm + scheduler, I don't see the necessity to use
> additional application, esp this is memory-resident program.

"Tim Meddick" wrote:
> The Windows default time updater (w32time) only update the
> clock once a week by default.
> [snipped]

Really? That's strange! Because my scheduled task also works. It's been
working since yesterday -- four updates, and I've no problem nor do I have to
modify any registry key.

"TFS" <(E-Mail Removed)> wrote in message
news:BF876746-B2B9-46AA-A1B2-(E-Mail Removed)...
> "Tim Meddick" wrote:
>> The Windows default time updater (w32time) only update the
>> clock once a week by default.
>> [snipped]
>
> Really? That's strange! Because my scheduled task also works. It's been
> working since yesterday -- four updates, and I've no problem nor do I have
> to
> modify any registry key.

Tim said "By Default". Your calling it from a scheduled task is not "By
Default"!

Alister

"Alister" wrote:

>
> "TFS" <(E-Mail Removed)> wrote in message
> news:BF876746-B2B9-46AA-A1B2-(E-Mail Removed)...
> > "Tim Meddick" wrote:
> >> The Windows default time updater (w32time) only update the
> >> clock once a week by default.
> >> [snipped]
> >
> > Really? That's strange! Because my scheduled task also works. It's been
> > working since yesterday -- four updates, and I've no problem nor do I have
> > to
> > modify any registry key.
>
> Tim said "By Default". Your calling it from a scheduled task is not "By
> Default"!
>
> Alister

Of course I saw he wrote the words "by default", but since he was
replying directly to my mail (as my message was included), and since I had
specifically written out "scheduler", it's natural to think he was implying
that even in scheduler, the "default" behaviour is only one update per week.

Unless he had made double mistake: this one and the fact that he
thought I'm Airmain!

All,
The API (on tab3 Adjust Date/Time) has a registry defined update
interval of one week.
--

Cheers, Tim Meddick, Peckham, London.


"TFS" <(E-Mail Removed)> wrote in message
news:772E51ED-860B-4745-BD32-(E-Mail Removed)...
>
>
> "Alister" wrote:
>
>>
>> "TFS" <(E-Mail Removed)> wrote in message
>> news:BF876746-B2B9-46AA-A1B2-(E-Mail Removed)...
>> > "Tim Meddick" wrote:
>> >> The Windows default time updater (w32time) only update the
>> >> clock once a week by default.
>> >> [snipped]
>> >
>> > Really? That's strange! Because my scheduled task also works. It's
>> > been
>> > working since yesterday -- four updates, and I've no problem nor do I
>> > have
>> > to
>> > modify any registry key.
>>
>> Tim said "By Default". Your calling it from a scheduled task is not "By
>> Default"!
>>
>> Alister
>
> Of course I saw he wrote the words "by default", but since he was
> replying directly to my mail (as my message was included), and since I had
> specifically written out "scheduler", it's natural to think he was
> implying
> that even in scheduler, the "default" behaviour is only one update per
> week.
>
> Unless he had made double mistake: this one and the fact that he
> thought I'm Airmain!

TFS,
I'm sorry my former answer was so complicated, I admit, I'm still
learning and only discovered the "w32tm.exe /resync" command. Previously, I
had installed the NT4 util timesrv.exe, which updates time automatically,
four times a day.
--

Cheers, Tim Meddick, Peckham, London.


"TFS" <(E-Mail Removed)> wrote in message
news:772E51ED-860B-4745-BD32-(E-Mail Removed)...
>
>
> "Alister" wrote:
>
>>
>> "TFS" <(E-Mail Removed)> wrote in message
>> news:BF876746-B2B9-46AA-A1B2-(E-Mail Removed)...
>> > "Tim Meddick" wrote:
>> >> The Windows default time updater (w32time) only update the
>> >> clock once a week by default.
>> >> [snipped]
>> >
>> > Really? That's strange! Because my scheduled task also works. It's
>> > been
>> > working since yesterday -- four updates, and I've no problem nor do I
>> > have
>> > to
>> > modify any registry key.
>>
>> Tim said "By Default". Your calling it from a scheduled task is not "By
>> Default"!
>>
>> Alister
>
> Of course I saw he wrote the words "by default", but since he was
> replying directly to my mail (as my message was included), and since I had
> specifically written out "scheduler", it's natural to think he was
> implying
> that even in scheduler, the "default" behaviour is only one update per
> week.
>
> Unless he had made double mistake: this one and the fact that he
> thought I'm Airmain!