Short: SynClock clone for AmiTCP. V1.41. Author: izzy@ancient.demon.co.uk (Simon Dainty) Uploader: izzy ancient demon co uk (Simon Dainty) Type: comm/tcp Architecture: m68k-amigaos A binary executable replacement for the 'SynClock' DOS and AREXX hybrid script that is a part of the AmiTCP package. Synchronize your local system clock and/or battery-backed clock with that of a remote host. Says it all, really. History V1.0 ---- - Initial release, no known bugs. Limited distribution. V1.1 ---- - Optimized executable compilation by utilizing inline library calls. Shaved off around 200 bytes from the binary. - SynCro will return a specific code in the event of an error. V1.2 ---- - Optimized executable size. Now down to 4.8K. - Modified the ordering of the error-specific return codes into something a little more logical. - Fixed a bug where SynCro would complain about an invalid FQDN argument, when the argument was indeed valid. V1.3 ---- - Optimized executable size. Now down to 3.5K. - SynCro now goes directly through the "bsdsocket.library", as opposed to earlier versions that used the TCP: device. This affords the user several benefits: * Not restricted to only giving an FQDN as the reference to a remote site; SynCro will also accept an IP address. * No need to mount the TCP: device if SynCro was the only program that needed it. * A CONTROL-C from the Shell that SynCro was started from will now stop it dead in its tracks. - Once more, several modifications have been made to the error- specific return codes. V1.4 ---- - Limited tester release. - Problems arose when SynCro was used with the Multilink AmiTCP and RS225 emulator (in beta). Thanks to Osma Ahvenlampi for pointing the deficiency out. - If SynCro was unable to resolve the remote host, AmiTCP would not shutdown correctly. This was a problem with version 1.3 of SynCro not closing the bsdsocket.library when it should have done. Any other time and it would have worked fine. My fault entirely - it is now fixed. - Minor changes to the error-specific return codes. Again. V 1.41 ------ - Modified the way the remote time is processed. Instead of relying on the location-specific time string as received via the 'daytime' port, SynCro now goes through the 'time' port, and calculates the current time by processing the number of seconds since midnight of January the 1st 1900. - Because of the above changes, SynCro now requires the local system's GMT offset to be set within the Locale preferences.