swc
Tue Aug 19 09:36:28 PDT 2008
ah, that's right. forgot about that. thanks.
that means LogicPD is limiting the date/time.
I'll bug them.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:OcgYUUhAJHA.5900@TK2MSFTNGP04.phx.gbl...
> Yes, and, if the hardware can only go up to 2049 or whatever, that's
> exactly what I'd expect to see happen. When you do a SetLocalTime() that
> results in an OEMSetRealTime() call to your HAL, which writes the
> date/time information to the 'clock' hardware. When you do a
> GetLocalTime() (or use the Control Panel, which calls GetLocalTime()),
> this results in a call to OEMGetRealTime() in your HAL which retrieves the
> date/time from the hardware and returns it. If the hardware range only
> goes up to 2049, you'd get exactly what you're seeing.
>
> I just did this on my CE5-based device, setting the date/time to 8/19/2061
> and it works just fine; the same is true of 8/19/2086. Of course, if
> you're using PC-based hardware, it's quite likely that you'd run into the
> same limitations regardless of whether you're running desktop Windows or
> Windows CE.
>
> Paul T.
>
> "swc" <news.10.swc@spamgourmet.com> wrote in message
> news:O3V4QLhAJHA.3648@TK2MSFTNGP02.phx.gbl...
>>I don't think hardware is the issue as I am simply changing the time using
>> the data/time control in the control panel.
>> I simply change to the time to be out of this range, click OK,
>> bring up the date/time control again, and I see the problem.
>> I am testing this on the LogicPD SDK, which does not have a hardware RTC.
>>
>> Even on a PC(XP Pro SP2), I find out about a week ago, the date/time
>> control GUI limits you to this range.
>> So, I believe CE does have this range limitation, but it isn't
>> documented(having find it).
>>
>> "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
>> DOT com> wrote in message news:ew0rX7gAJHA.4148@TK2MSFTNGP05.phx.gbl...
>>>I don't think there's any limitation enforced by the OS. How is the
>>>date/time kept on your hardware? That's far more-likely to be the
>>>limiting factor...
>>>
>>> Paul T.
>>>
>>> "swc" <news.10.swc@spamgourmet.com> wrote in message
>>> news:eXoFOpgAJHA.4064@TK2MSFTNGP02.phx.gbl...
>>>> I'm using a custom build ver CE5.0.
>>>>
>>>> it doesn't matter if I use the MS build datetime GUI or my own program
>>>> call to SetLocalTime(),
>>>> there seems to be a limit on the date I can change(year only?). But I
>>>> cannot find any documentation on it.
>>>>
>>>> it seems like year over 2099 and under 1980. If I enter a date outside
>>>> this range, the date set fails and the clocks
>>>> show some time in year 2046/2047.
>>>>
>>>> is this true, there is a limit and if so what is it.
>>>> a pointer to the actual documentation would be nice.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>
>>>
>>
>>
>
>