I have a question regarding the Time Zone setting of the MC70 and 75A devices. On the older 8846 units, if a cold boot was performed and the time/date/time zone was reset, the device prompted you to enter your time zone after the calibration process. The newer devices do not have this prompt, and our time zone settings do not persist across Clean Boots. I realize that the time zone prompt was probably removed due to the fact that a Cold Boot on the WM based devices does not reset Time Zone.
The issue would be if a store had to run our Clean Boot process to reset the device back to its original staged state, the time zone is now incorrect. Is there a way to prompt a user to enter the correct time zone, after a Clean Boot? Ideally, it should only provide access to set the time zone for the home location. We wouldn’t want them to be able to access the alarms, or set the device “visitor” time settings. Thanks
3 Replies
I think [HKEY_LOCAL_MACHINE\nls] entries have to do with Regional Settings rather than with actual Time Zone. Things such as decimal dot or comma, date format, time format, currency and so. On the other hand, I have a question: Does anybody know if GMT_OFFSET must match Timezone Bias, and the first 4 bytes (reversed) of TimeZoneInformation? That is, if all these three entries must be the same?
Also, you could achieve the same using XML provisioning: http://msdn.microsoft.com/en-us/library/bb737513.aspx Cheers !!
Here's all the locale and Timezone information in the registry: [HKEY_LOCAL_MACHINE\Time] "TimeZoneInformation"=hex:\ 88,FF,FF,FF,46,00,4C,00,45,00,20,00,53,00,74,00,61,00,6E,00,64,00,61,00,72,\ 00,64,00,20,00,54,00,69,00,6D,00,65,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,0A,00,00,00,05,\ 00,04,00,00,00,00,00,00,00,00,00,00,00,46,00,4C,00,45,00,20,00,44,00,61,00,\ 79,00,6C,00,69,00,67,00,68,00,74,00,20,00,54,00,69,00,6D,00,65,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,03,00,00,00,05,00,03,00,00,00,00,00,00,00,C4,FF,FF,FF [HKEY_LOCAL_MACHINE\Software\Microsoft\Clock] "GMT_OFFSET"=dword:FFFFFF88 ;"AppState"=hex:\ ; 11 "TZIndex"=dword:00000023 "HomeDST"=dword:00000000 ;"AppInfo"=hex:\ ; 01,00,00,00,22,01,00,00,7D,00,00,00,00,00,00,00,00,00,00,00,3A,01,00,00,69,\ ; 00,00,00,00,00,00,00,00,00,00,00 ; Just for Convenience ;[HKEY_LOCAL_MACHINE\System\State\DateTime] ;"Time"=hex:\ ; 00,9E,82,83,8D,5C,CA,01 ;"Timezone Bias"=dword:FFFFFF88 ;"LocalDate"=hex:\ ; 80,7F,1A,6B,9D,5C,CA,01 ;"Date"=hex:\ ; 80,AF,91,A7,8C,5C,CA,01 [HKEY_LOCAL_MACHINE\nls] "DefaultOCP"=dword:00000362 "DefaultACP"=dword:000004E3 "DefaultLCID"=dword:00000422 [HKEY_LOCAL_MACHINE\nls\overrides] "LCID"=dword:00000422 Use some reg editor to fill your values and save as a .reg file in \Application Solution #2: Use MSP to provision package with timezone setting :)