Re: CE 5.0, TIMESVC fails to set clock back to correct time

I have followed your repro steps and see the same bug that you do. Our
apologies for this problem. The real time clocks on systems that we test
with always have their clocks set to sometime in the past on first boot, not
this far in the future. Out of curiosity (not that it changes the fact this
is a bug), is your system clock this far in the future or did you hit this
just via experimentation?

Please contact your technical account manager or whoever you contact for
support and let them know about this issue if you want a QFE. (I'll open a
bug in our product bug database no matter what.) You should not get charged
for a support incident when it is a bug in an MS product. You can
definitely use my name as someone in MS who has confirmed this issue.

--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation

Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.

"AJM42" <software@xxxxxxxxxxxxxx> wrote in message
news:1134402074.824752.120950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>A bit more on this.
> It is not simply due to unsigned maths as I first thought.
> It seems to depend how far the clock is wrong.
> For example, if the clock is 2020 then it sets it back to 2005 OK.
> I am continuing to investigate - but if anyone welse has any ideas in
> mean time?
>


.

Relevant Pages

  • Re: CE 5.0, TIMESVC fails to set clock back to correct time
    ... I will open up a documentation bug so that people know to get their clocks ... Microsoft Corporation ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > Also be aware this may be some sort of protol limitation, as in the clock ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 5.0, TIMESVC fails to set clock back to correct time
    ... Also be aware this may be some sort of protol limitation, as in the clock ... Microsoft Corporation ... This posting is provided "AS IS" with no warranties, and confers no rights. ... >I have followed your repro steps and see the same bug that you do. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: C Slower than Python?
    ... char * a = NULL; ... char * buf = NULL; ... I hardly ever use clock so I looked it up. ... Memory leak (i.e. the real big bug I spotted). ...
    (comp.lang.c)
  • Re: clock scan (once again)
    ... to *not* do the right thing anymore in that particular case, ... to me seems highly orthogonal to all the restructuring. ... I vaguely remembered some discussion about this change in clock scan, ... bug that I fixed, or an 8.5 bug that I introduced. ...
    (comp.lang.tcl)
  • Re: clock suddenly slipping behind
    ... >> calibrate the hardware clock off a faulty software clock). ... >> just keep working forwards and backwards until you trigger the bug ... > ii adjtimex 1.18-1.1 ... and see if i still notice a drift at the end of the day ...
    (Debian-User)