Support
> GALSync Server
> Stay Connected
> TimeSync

TimeSync 2.3.8 for Windows Mobile

(Last Release Date: 28 January 2010)

Note: If you're having problems with your device clock being wrong by 1 hour and you live in the United States then this could be caused by the recent change to daylight saving. Read more here.

FAQs
Tips
Downloads
NTP String Formats

If you have a problem with that is not answered in the FAQs or Tips section, then please email:

support@slipstreamsolutions.co.uk

FAQs

Top

I've just installed TimeSync...why has my 15-day trial period run out before it should?

There are two possible reasons that this could have happened:

First of all, if you install TimeSync on a device with the date set to 15-days (or more) before the current date then when TimeSync corrects the date and time you will exceed the trial period and the software will be deactivated.
Secondly, TimeSync can detect previous installations of itself and if you have exceeded the 15-day trial period since the software was first installed you may need to buy a new Licence.

I have Spb Pocket Plus installed and TimeSync sometimes stops responding...

If you have Spb Pocket Plus installed you may find that the TimeSync icon at the bottom of the Today screen sometimes stops responding. This is caused by the 'Close Button' option in Spb Pocket Plus interfering with an option in TimeSync that stops the program from being shut down by the operating system. To avoid this from happening, either:

Disable the 'Close Button' option in Spb Pocket Plus (Start > Settings > System > Spb Pocket Plus and un-tick 'Close Button').
Alternatively, if you want the operating system to shut down TimeSync gracefully, enable the 'Allow operating system to close the program' option in TimeSync.

Can I view an online copy of the HTML help?

Yes, the online version of TimeSync online HTML help is here.

Will TimeSync work in a Wireless LAN environment?

Yes, as long as TimeSync has IP connectivity to your time-server.

Can TimeSync use 'Pass Through' when docked to my PC?

Yes, as long as your device is connected via ActiveSync (Guest or Partnership, and via USB, Serial or IR) and if you have enabled 'Pass Through' in ActiveSync (see Tools -> Options -> Rules). Also, your PC must have access to the Internet, and if your PC is running in a corporate environment you may have to check with your system administrators to enable access through the corporate firewalls.

Where can I find a list of NTP servers?

Here: http://www.eecis.udel.edu/~mills/ntp/clock1a.html and here: http://www.eecis.udel.edu/~mills/ntp/clock2a.html.

Where can I found more information on NTP responses?

Here: http://www.boulder.nist.gov/timefreq/service/its.htm and here: http://www.eecis.udel.edu/~mills/ntp/timecode.html.

Where can I find time-server software for my network?

Here: http://www.kaska.demon.co.uk/tardis.htm, but you can find plenty more on the Internet.

Tips

Top

Get the most out of your 15-day trial...

Set the date on your device to the correct day before installing TimeSync.

Registry keys for administrator lockdown of menus or tabs...

Create the following registry values in \HKLM\Software\SlipstreamSolutions.co.uk\mTimeSync to disable the corresponding menu or tab. This option is useful for network administrators who want to stop users from accidentally changing settings:

'DisableAbout': DWord, value = 1
'DisableExit': DWord, value = 1
'DisableRegistration': DWord, value = 1
'DisableOptions': DWord, value = 1
'DisableServers': DWord, value = 1

The HTML help mentions command line switches. Do you have any examples?

Yes, try these TimeSync PPC LNK file examples.

I'm having problems with my device clock being wrong by 1-hour.

If your device locale is the US then this could be caused by the recent change to daylight saving in the US. Read more here.

Downloads

Top

Pocket PC

Desktop installer (PPC): EXE (81 kb)
Desktop installer (PPC): Zipped EXE (79 kb)
Device installer (PPC): CAB (120 kb)
Device installer (PPC): Zipped CAB (44 kb)

Smartphone

Desktop installer (SP): EXE (87 kb)
Desktop installer (SP): Zipped EXE (85 kb)
Device installer (SP): CAB (37 kb)
Device installer (SP): Zipped CAB (37 kb)

NTP String Formats

Top

The default NTP string format used by TimeSync for time.nist.gov (note the seven leading dots) is: '.......yy-MM-dd HH:mm:ss'

This string format is matched against the response from the queried timeserver and used to build a correct time to apply to the device's clock. It is assumed that the time-server response is in UTC format - i.e. +0 time-zone with no Daylight Saving Time. And it should not matter what time-zone/ region / DST is applied to the device as mTimeSync should take all this into account.

As a minimum, the following must be available from the timeserver: year, month, day, hour, minute and second.

The standard string returned by time.nist.gov is in the following format: 'JJJJJ YR-MO-DA HH:MM:SS TT L H msADV UTC(NIST) OTM'. In addition, there is also a single control-code at the beginning of this string. For a more detailed explanation about each element in this string visit www.boulder.nist.gov.

Here is a time.nist.gov example corresponding to 20th October 2004, 14:00 hours and 50 seconds: '#53298 04-10-20 14:00:50 12 0 0 779.8 UTC(NIST)'

TimeSync can use the following codes in its string format:

Format Pattern	Description
dd	Numeric day of the month, with a leading zero for single-digit days. For example: 01 for the 1st, 02 for the 2nd, 31 for the 31st.
ddd	Abbreviated name of the day. For example: Mon for Monday, Tue for Tuesday.
MM	Numeric month of the year, with a leading zero for single-digit months. For example: 01 for January, 02 for February.
MMM	Abbreviated name of the month. For example: Jan for January, Feb for February.
yy	Year without the century, with a leading zero for single-digit years. For example: 04 for 2004, 15 for 2015.
yyyy	Year with the century. For example: 2004 for 2004, 2015 for 2015.
HH	Hour in a 24-hour clock, with a leading zero for single-digit hours. For example: 01 for 01:00 am, 15 for 03:00 pm.
mm	Minute, with a leading zero for single-digit minutes. For example: 01 for 1 minute past the hour, 59 for 59 minutes past the hour.
ss	Second, with a leading zero for single-digit seconds. For example: 01 for 1 second into the minute, 59 for 59 seconds into the minute.
-	Default time separator when using short dd-mm-yy. Not required, '.' can be used instead.
:	Default time separator when using hh:mm:ss. Not required, '.' can be used instead.
.	Universal spacer character. Use this at the beginning of your string when you want to ignore a character. Padding is not required at the end of the string - i.e. mTimeSync string length does not have to match the length of the time-server response (less then or equal to).

Single-digit time units such as 'd', 'M', 'y', 'H', 'm' and 's' are not supported.

Year, month and day can be separated with either a hyphen '-' or a dot '.' or a space, and can be in any order. For example: yy-MM-dd, MM-dd-yy and dd-MM-yy are all allowable, as are yy.MM.dd, MM.dd.yy and MMM dd yyyy and so on.

Hour, minute and second can either be separated with a colon ':' or a dot '.' but avoid using spaces. Time responses are almost always returned as: HH:mm:ss.

Use dots '.' as spacer characters to ignore characters at the front of a string. Padding is not required at the end of the string - i.e. mTimeSync string length does not have to match the length of the time-server response (less then or equal to).

Some time-servers pad an extra control character at the beginning of their NTP response. If in doubt add an extra dot '.' and try another Sync.

Spaces can in theory be used instead of a dot '.' or a colon ':' but it's best to avoid them. Especially avoid using spaces to pad the beginning of your string as they're difficult to count - use dots '.' instead.