Re: clock's inaccuracy

From: Adam Turner (adturner_at_email.uophx.edu)
Date: 04/22/04 

Date: Wed, 21 Apr 2004 20:15:38 -0700

ok...once again...how is this different than a cold boot or simply rebooting?
Adam Turner

message news:i5ce80h30jjk0eb8h4h383jkjklpruuikf@4ax.com...

  On Wed, 21 Apr 2004 15:42:29 -0700, "Adam Turner"
  <adturner@email.uophx.edu> wrote:

>
> "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message news:OzmJer%23JEHA.556@TK2MSFTNGP10.phx.gbl...
> In news:%230ftEa%23JEHA.2660@TK2MSFTNGP09.phx.gbl,
> Adam Turner <adturner@email.uophx.edu> typed:
>
> > The bios battery needs to be replaced
>
>
> No, when he says "at random," he presumably means that he loses
> time while the computer is running. Before anyone whose clock is
> running slow rushes out to buy a new battery, he should first
> take note of whether he is losing time while the computer is
> running or while it's powered off. If it's while powered off, the
> problem *is* very likely the battery. But if it's while running,
> it can *not* be the battery.
>
> If the clock loses time while running, try this:
>
> Open a command prompt window (Start | Run | cmd) and enter the
> following commands:
>
> net stop w32time
> w32tm /unregister
> w32tm /register
> net start w32time
>
> --
> Ken Blake - Microsoft MVP Windows: Shell/User
> Please reply to the newsgroup
>
>
> > "marco" <anonymous@discussions.microsoft.com> wrote in
> message
> > news:267f01c427e4$5c1010c0$a101280a@phx.gbl...
> > I have XP Pro on a new hp compaq, P IV, 512 RAM, but the
> > clock shows severals minutes ago, at ramdom. I 've seen
> > this behaviour on at least another identical machine
> > here. It's there a hardware issue or it is XP?
>...and out of curiosity Ken, what will stopping the clock and starting it again resolve?
>
>Wouldn't the result be the same from a cold boot?
>Adam Turner

  Kens' advice doesn't stop the clock. It stops the time service then
  restarts it. The clock still runs during the process. The time
  service and the clock aren't the same thing.

Relevant Pages

  • Re: clocks inaccuracy
    ... It's actually stopping the service, re-registering it, and then starting it back up. ... A cold boot does not re-register the service. ... Adam Turner wrote: ... Before anyone whose clock is ...
    (microsoft.public.windowsxp.general)
  • Re: W32time event id 36
    ... >>The time service has not been able to synchronize the system time for ... The system clock is unsynchronized. ... >>as a message is logged in the event viewer when the clocks are ... net start w32time ...
    (microsoft.public.windowsxp.general)
  • Re: W32time event id 36
    ... >The time service has not been able to synchronize the system time for ... The system clock is unsynchronized. ... >as a message is logged in the event viewer when the clocks are ... net start w32time ...
    (microsoft.public.windowsxp.general)
  • Re: IIS Logs & System Clock Sync...?
    ... > using NetGenesis software. ... > able to use some sort of "atomic clock" software and just ... > IIS boxes to this "time box" running the Atomic clock ... Use the built-in Windows Time Service to update from an NTP time source. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Inaccurate Clock
    ... This will stop the time service, unregister it, re-register it and re-start ... > First of all I let XP synchronize the clock, ... > If I don't do that then the clock drifts on the MCE machine when MCE is ...
    (microsoft.public.windows.mediacenter)