x
This website is using cookies. We use cookies to ensure that we give you the best experience on our website. More info. That's Fine
HPC:Factor Logo 
 
Latest Forum Activity

Significant TinyBook Bug

Moderators: CE Geek

Jump to page : 1 2
Now viewing page 1 [15 messages per page]

Forums · Technical Support · Windows Embedded CE 6.0 & 7.0

Page Icon Posted 2016-01-27 6:41 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
It's a date bug.

As far as my own TinyBook goes, I can not set the date past December 31 2015. Trying to set the current date makes the TinyBook default back to same date in 2010.

This obviously wreaks havoc on date-specific software such as rss readers.

Can another TinyBook owner replicate this? And can anybody suggest a workaround (can the date be set another way?)?

Y2K anybody,
Jake
 Top of the page
Page Icon Posted 2016-01-27 7:00 PM
#
Avatar image of CE Geek
Global Moderator
H/PC Oracle

Posts:
11,994
Location:
Southern California
Status:
Two possibilities:

1) Have you tried synching it with a PC via ActiveSync? If you establish a partnership it's supposed to sync the time and date.

2) When I need to reset the time and date on one of my non-synchronizable netbooks after a power loss, I use a program that syncs the device's time and date directly with Internet time in my time zone (which the app finds automatically). I usually use SPTimeSync:

http://www.spdialer.com/timesync/

A couple of other such programs are GTimeSync and iTime:

http://qsot.net/gtimesync/download.php

http://download.cnet.com/Angel-iTime/3000-2094_4-10914681.html

I've never encountered this issue on any device (though I've had a couple reset to dates in the future after a power loss), so I can't guarantee any of these will work, but since they're all free, they're certainly worth a try.
 Top of the page
Page Icon Posted 2016-01-27 7:41 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
Many thanks for your quick response. Just before your post, your ActiveSync workaround occurred to me, but it only syncs time, not date.

SP TimeSync safely installed, shows my incorrect local date of Jan 27 2010, but when I hit "adjust clock," it goes right back to 2010

edit: gTimeSync won't run and Angel iTime no longer available

This is the darndest thing...

I have very little software installed, and everything else, wifi, ActiveSync remains in working order.

Jake

Edited by Jake 2016-01-27 7:47 PM
 Top of the page
Page Icon Posted 2016-01-27 8:17 PM
#
Avatar image of CE Geek
Global Moderator
H/PC Oracle

Posts:
11,994
Location:
Southern California
Status:
I'm wondering if a temporary power loss might resolve the problem by resetting the date and time to factory default.

FWIW, there's a link in the middle of this page on this thread -

http://www.hpcfactor.com/forums/forums/thread-view.asp?tid=13923&st...

- to FriendlyARM.net, which has several Samsung S3Cxxxx ROM images, including the S3C6410 (which the TinyBook has). Maybe someone can figure a way to cook a ROM for the TinyBook using the image there. If so, then we'd have a possibility of correcting problems with the TinyBook by reflashing it.
 Top of the page
Page Icon Posted 2016-01-27 8:25 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
Now that I think about it, my TinyBook--when I dug it out after a year--was completely dead. I hadn't thought about the date until this morning and found it around 2002, thought I had set it to Jan 27, 2016, and then I saw the trouble I was in.

Thanks for the flashing link, but wow, that is far above my paygrade.

Jake
 Top of the page
Page Icon Posted 2016-01-28 12:21 PM
#
Avatar image of Rich Hawley
Global Moderator
H/PC Guru

Posts:
6,902
Location:
USA
Status:
So if you set the date to Dec 31, 2015 and then just let it run until the next day, what does the date show then? 2016 or 2010?
 Top of the page
Page Icon Posted 2016-01-28 1:42 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
Great minds think alike. That's exactly what I tried last night and it kicked back to 2010. I took CE Geek's advice as well and pulled the battery and let the machine sit unpowered for the night. This morning, the date was Jan 1 2009. But when I set it to Jan 28 2016, it went back to Jan 28 2010.

Does anyone have a TinyBook to see if this my problem or all TB owners?

Jake
 Top of the page
Page Icon Posted 2016-01-28 2:04 PM
#
Avatar image of Rich Hawley
Global Moderator
H/PC Guru

Posts:
6,902
Location:
USA
Status:
What happens if you try to input 2017 into the year? Same thing?

Funny thing is that 2010 had the dates on the same days as 2016. That is Jan 28th is on a Thursday.

Have you search the registry to see if there is anything you can edit?
 Top of the page
Page Icon Posted 2016-01-28 2:28 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
Yes, any date in Jan 2016 or beyond (2017, etc) makes it fall back to 2010. Your comment about the matching weekdays was something that I considered, too. But when I picked other Jan 2016 dates, it would default back to the same specific number date (i.e. 28) in 2010 rather than the same weekday.

Using "date" as my search word, the only viable registry entry is in \HKLM\SOFTWARE\Microsoft\Calendar\LastDate: a REG_BINARY value type with a value named DATE and value data of DA 07 02 00 04 00 04 08 00 26 00 0D 00 00 00.

In Date/Time Properties, the date is Jan 28 2010--I don't know if that value data has any relation...

EDIT: When I set the date to Dec 1 2015, and reboot machine, the value data changes to: DF 07 0C 00 02 00 08 09 00 1E 00 04 00 00 00

Jake

Edited by Jake 2016-01-28 2:33 PM
 Top of the page
Page Icon Posted 2016-01-28 3:30 PM
#
Avatar image of Rich Hawley
Global Moderator
H/PC Guru

Posts:
6,902
Location:
USA
Status:
Change the DF to E0 and tell me the year then...2015 hex is 07DF, 2016 would be 07E0

I suspect that is the little endian value in the key value above...

BTW, 07DA is 2010.
 Top of the page
Page Icon Posted 2016-01-28 3:37 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
Thanks for weighing in on this. Changed to E0, and the change was persistent, but date of Dec 1 2015 remains the same, even after reboot.
 Top of the page
Page Icon Posted 2016-01-28 3:41 PM
#
Avatar image of Rich Hawley
Global Moderator
H/PC Guru

Posts:
6,902
Location:
USA
Status:
Did you try warm reset after last change?
 Top of the page
Page Icon Posted 2016-01-28 4:40 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
The TinyBook has a reset hole in the bottom, but that simply turns the machine off. After pressing that, restarted machine, value data remains same as does date of Dec 1 2015.

Tried the PHM reset, but it doesn't support this machine. apparently.
 Top of the page
Page Icon Posted 2016-01-28 4:49 PM
#
Avatar image of Jake
Subscribers
H/PC Elder

Posts:
1,978
Location:
Choking on the stench of ambition in Washington DC
Status:
Okay, I THINK I've found a workaround. Rich's play with the numbers made me start playing with the date years into the future. When I set the date to Jan 28 2020, it went back to Jan 28 2014, not Jan 28 2010.

I held my breath, set the date exactly six years ahead to Jan 28 2022. Voila, the date was set to Jan 28 2016. And it's persistent.

Very, very weird, a six-year bug,
Jake
 Top of the page
Page Icon Posted 2017-01-09 10:24 PM
#
Avatar image of CE Geek
Global Moderator
H/PC Oracle

Posts:
11,994
Location:
Southern California
Status:
Well, after I open my big mouth, it happened to me - except it went from 2017 to 2011. (Maybe mine was manufactured after yours, Jake.) The same fix solved it (except I had to go to 2023, of course).

I wonder if there was something missing in the registry entries regarding date and time. I note that there are 14 possible calendars, not six. (Note that 2016 was a leap year, so everything was different from 2010 after 28 February.)
 Top of the page
hpc:factor« View previous thread · Windows Embedded CE 6.0 & 7.0 · View next thread »

Jump to page : 1 2
Now viewing page 1 [15 messages per page]

Jump to forum :
Search this forum
Printer friendly version
E-mail a link to this thread
Seconds to generate: 0.125 - Cached queries : 71 - Executed queries : 8
Server Time now is: Monday, 17 June 2019 - 18:34