What you want is a command line to update the clock? I imagine there is a
way, I just don't know it. I could do it with a sloppy script, using
SendKeys, but such scripts are unreliable, since any other keystroke that
occurs while the script is running causes it to fail.
Of course, the other problem is that which is being encountered so much by
so many, recently: The internet time servers are for some reason not
cooperating with XP's update mechanism (or probably, vice versa.) One I know
that usually works is tick.usno.navy.mil
As noted, if the clock loses time primarily when the machine is turned off,
the issue is the BIOS battery (a small coin-sized battery on the
motherboard. Otherwise, I'd want to identify the background app that's
causing the clock to lose time so quickly. This issue was common in Win9x
systems, but much less so in XP systems. I'd use MSCONFIG to methodically
disable background apps one at a time until the clock behaves. But I'd first
use MSINFO32, copy out the info under Software Environment>Startup Programs
and post the list here for comment. Once the app is identified, perhaps it
can be done away with, replaced with some other app, updated, etc.