mTimeSync Support

Note: mTimeSync version 1.5.3 (and all previous versions) has now been superseded with Mobile TimeSync 2.3.3. Support for mTimeSync 1.5.3 will continue until 01 January 2006 after which time it will no longer be supported. Existing customers should contact us to arrange for a discounted upgrade.

Current Version (1.5.3 - 25 April 2005)
FAQs
Tips
Downloads
NTP String Formats

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

support@slipstreamsolutions.co.uk

Current Version

Top

The current version of mTimeSync is 1.5.3 and features the following additions and bug fixes:

[Minor] Default time format string for t1.timegps.net updated.
[Minor] Incorrectly formatted time string error now displays in status field to allow application to attempt another sync without user intervention.

Previous versions have featured the following:

[Bug/Add] Default secondary time server changed from ntp2a.mcc.ac.uk to t1.timegps.net.
[Bug/Minor] Error on failed Sync in Options screen now displays correctly.
[Add] 'Next Sync' time now displayed.
[Add] Improved handling of next sync trigger times (if date/time on device shifts by a large amount).
[Add] New secondary time server feature.
[Bug] Bug fix for when time server returns single-digit day-of-the-month.
[Minor] None-characters are now displayed as a space (" ") when 'Test Primary/Secondary' button is used (Tools -> Options).
[Add] New tick-box option to enable/disable Smart-minimize on soft reset.
[Bug] Improved error handling during Smart-minimize on soft reset.
[Minor] Program icon edited.
[Add] Smart-minimize on start-up.
[Bug/Add] Improved multi-threading no longer locks-up application.
[Bug/Add] Improved multi-threading.
[Bug] Change of region whilst product un-registered no longer causes program crash.
[Add] Multi-threading added to 'Sync'.
[Add/Bug] Various minor bug fixes + 'Allow operating system to close program' option.
[Minor] PC program name in Add/Remove Programs changed from 'mTimeSync' to 'Slipstream Solutions mTimeSync'.
[Minor] Pocket PC program name in Remove Programs changed from 'SlipstreamSolutions.co.uk mTimeSync' to 'Slipstream Solutions mTimeSync'.
[Add/Bug] Various.
[Bug] 'Check Every' now works correctly to reduce CPU load.
[Bug] Number of 'Retries' now functions as intended. Zero (0) retries now works correctly (single sync with no retries).
[Add] Program avoids being shutdown by operating system unless selected from the Tools > Exit menu.
[Add] New registry keys for administrator control of menus, see Tips (below).
[Add] 'Failed to connect' status message now includes name of server.
[Bug] Correct installation and operation with international versions of Pocket PC.
[Bug] Various issues with registration corrected.

FAQs

Top

I've just installed mTimeSync...but my 15-day trial period has already run out, why?
There are two possible reasons that this could have happened:
1. First of all, if you install mTimeSync on a device with the date set to 15-days (or more) before the current date, then when mTimeSync corrects the date and time, you will exceed the trial period and the software will be deactivated.
2. Secondly, mTimeSync 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 mTimeSync sometimes stops responding...
If you have Spb Pocket Plus installed you may find that the mTimeSync 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 mTimeSync that stops the program from being shut down by the operating system. To avoid this from happening, either:
1. Disable the 'Close Button' option in Spb Pocket Plus (Start > Settings > System > Spb Pocket Plus and un-tick 'Close Button').
2. Alternatively, if you want the operating system to shut down mTimeSync gracefully, enable the 'Allow operating system to close the program' option in mTimeSync (Tools > Options).

What is the 'NTP Server' field for?
'NTP Server' is used to enter the hostname of the time-server which you intend to use for NTP (time) queries. In most cases this is the name of a free-to-use public time-server such as time.nist.gov. You could also enter the WINS or DNS hostname of a local time-server on your own network, for example: MYTIMESERVER (WINS) or mytimeserver.ournetwork.com (DNS). You could also enter the IP address of a time-server whether local or public (but see below).
Can I use an IP address in 'NTP Server'?
Yes, for example the current IP address for time.nist.gov is 192.43.244.18 and this works fine. However, we have found a few occasions where other time-servers do not return a valid NTP response when addressed using their apparent IP address. In these instances you will have to use the time-server's hostname and you may have to check with your system administrator regarding correct hostname to IP address resolution.
What is 'Port'?
'Port' is used to enter the port number that you want to use to query your time-server. In most cases this is either 13 or 37.
What is 'NTP String Format'?
'NTP String Format' is the format of the NTP server response that will be returned from the time-server as specified in 'NTP Server'. For more information click here.
What is 'Check Every' (secs)?
'Check Every' is the amount of time in seconds that mTimeSync waits between 'checking itself' to see whether it has exceeded the amount of time between scheduled syncs (see 'Sync Every'). If the 'Sync Every' threshold is exceeded, mTimeSync will initiate a time-sync. Also, this is the amount of time in between 'Retries', as well as being the amount of time that mTimeSync waits before initiating the first sync when the application starts. See 'Tips' below for why you might want to increase this interval.
What is 'Sync Every' (mins)?
'Sync Every' is the amount of time in minutes that mTimeSync waits between trying to perform a time-sync, whether the previous attempt to sync was successful or failed.
What is 'Retries'?
'Retries' is the number of attempts that mTimeSync will make to perform a time-sync before timing-out. 'Retries' are performed at intervals equal to 'Check Every' seconds. If the number of 'Retries' is exceeded mTimeSync will wait for an amount of time equal to 'Sync Every' before trying to sync again (with another set of retries).
What is 'Last Successful Sync'?
'Last Successful Sync' is just a time-date stamp for the last successful time-sync.
What do the 'Start' and 'Stop' buttons do?
The 'Start' and 'Stop' buttons start and stop mTimeSync from performing regular syncs.
What is the 'Status' field for?
The 'Status' field is used to display the current or last status message. You might see: 'Waiting...', 'Connecting to time.nist.gov (1)...' or 'Failed to connect (attempt 1)'.
Will mTimeSync start running when I soft-reset my device?
Yes, by default the installation program copies a shortcut to your \Windows\StartUp folder. If this link has been deleted, just re-install the software.
What is 'Start sync'ing when program is run'?
This option enables mTimeSync to start sync'ing by itself when the application is first run. If the application is also starting when the device is soft reset (shortcut in the \Windows\StartUp folder) then this allows mTimeSync to fully automate itself.
Why is 'Start sync'ing' greyed out?
This option is always greyed out on the front screen of mTimeSync. If you want to change it, go to Tools -> Options.
Why is 'Start sync'ing' not ticked, when it is ticked in Options?
The most likely cause for this is that your copy of mTimeSync is not registered and you have exceeded your 15-day trial-ware period - if this is the case '0 days' will be displayed on the front screen of mTimeSync.
Will mTimeSync work in a Wireless LAN environment?
Yes, as long as mTimeSync has IP connectivity to your time-server.
Can mTimeSync 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. However, you may not need to use mTimeSync in this manner as ActiveSync will sync your clock for you anyway (see Tools -> Options -> 'Synchronize mobile device clock upon connecting') and current PC operating systems (such as Windows XP) maintain your PC clock using time-servers on the Internet or on your corporate network.
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

Is your device running slowly since you installed mTimeSync?
Increase 'Check Every' to 10 or 15 seconds (or more) to reduce the load on your device CPU.
Get the most out of your 15-day trial...
Set the date on your device to the correct day before installing mTimeSync.
Registry keys for administrator lockdown of menu options...
The registry key: \HKLM\Software\SlipstreamSolutions.co.uk\mTimeSync includes four (4) DWord values: DisableAbout, DisableExit, DisableOptions and DisableRegistration. Change any value from zero (0) to one (1) to disable the corresponding menu option. This option is useful for network administrators wanting to distribute mTimeSync to their users, but who want to stop users from accidentally changing settings.

Downloads

Top

Pocket PC

Desktop installer (PPC): EXE (58 kb)
Desktop installer (PPC): Zipped EXE (56 kb)
Device installer (PPC): CAB (81 kb)
Device installer (PPC): Zipped CAB (21 kb)

Smartphone

Desktop installer (SP): EXE (72 kb)
Desktop installer (SP): Zipped EXE (69 kb)
Device installer (SP): CAB (21 kb)
Device installer (SP): Zipped CAB (21 kb)

NTP String Formats

Top

The default NTP string format used by mTimeSync 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)'

mTimeSync 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.