PDA

View Full Version : Date advances one day


JustUs
November 25th 04, 01:13 AM
Not sure when this started, but guessing a few weeks ago with SP2 on XP Pro.
The date in the taskbar arbitrarily advances one day. BIOS is OK, DST is OK,
Time Zone is OK. I don't know what is triggering it. Mobo is new and clock
keeps accurate time - within a second or two a day. I use Atom Time Pro to
sync time. Any ideas? I have read other related posts, but may have missed
the fix.

JustUs
November 25th 04, 01:19 AM
Just opened up the date and time properties to Internet Time tab and noted
that the "Time has been successfully sychronized with time.nist.gov on
11/25/2004 at 2:38 P.M." That is one day advanced. It looks like the time
site where the time check is made and updated is screwed up.

"JustUs" wrote:

> Not sure when this started, but guessing a few weeks ago with SP2 on XP Pro.
> The date in the taskbar arbitrarily advances one day. BIOS is OK, DST is OK,
> Time Zone is OK. I don't know what is triggering it. Mobo is new and clock
> keeps accurate time - within a second or two a day. I use Atom Time Pro to
> sync time. Any ideas? I have read other related posts, but may have missed
> the fix.

JustUs
November 25th 04, 01:25 AM
Did a manual update in the Internet tab and it updated to the correct day.
Kind of weird :-S

"JustUs" wrote:

> Just opened up the date and time properties to Internet Time tab and noted
> that the "Time has been successfully sychronized with time.nist.gov on
> 11/25/2004 at 2:38 P.M." That is one day advanced. It looks like the time
> site where the time check is made and updated is screwed up.
>
> "JustUs" wrote:
>
> > Not sure when this started, but guessing a few weeks ago with SP2 on XP Pro.
> > The date in the taskbar arbitrarily advances one day. BIOS is OK, DST is OK,
> > Time Zone is OK. I don't know what is triggering it. Mobo is new and clock
> > keeps accurate time - within a second or two a day. I use Atom Time Pro to
> > sync time. Any ideas? I have read other related posts, but may have missed
> > the fix.

Google