There is not much to tell about this program, it's pretty straightforward. Put in a directory and add it to your startup-folder. When it runs, you need to find a server that works, as the proggy is pretty old, not all the servers work anymore. I like to use the Kansas University Computer Center as it's the most reliable so far, but you can even use NASA if you like.
Turn autorun and continuous on. Set initial delay to 5 secs and interval to 5 minutes, that should do the trick. Beware that you need to disable the sites that don't work as it remembers all the ones you have enabled.
You let it calculate the string, then copy/paste the string into your config.sys where the old TZ string is located. After that you never ever have to worry about that anymore, one reboot and it's ok. Here is mine to show what it should look like in Belgium:
SET TZ=CET-1CDT,3,-1,0,3600,10,-1,0,3600,3600
It's nice to have your OS/2 on time, but what about clients? Windows for example doesn't set the time of the client by the server time when logging on. I hear you thinking, here is that NetBios dude again, well YES!!! There is a simple way to let Windows take the time from the OS/2 server without the need for the OS/2 Warp Server Logon Client. To set windows clients on time, you only need to add this to the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"Timeset"="net time \\\\server /Y /SET"
(You can also use this Timeset.reg (http://www.xs4all be/~basheij/OS2/Timeset.reg) file to add it but edit the server name to match yours!)
After this, your Windows clients will get the latest time from the OS/2 server when they boot-up. Pretty cool no? I think so. This stuff works on all versions of OS/2 as long as they are 32 bit and you have internet.
Next month is my jubilee, 10th time of OS/2 is Boring. If you have a good suggestion of
what to write about in that one, email me! Bye for now, Bas.
This article is courtesy of www.os2ezine.com. You can view it online at http://www.os2ezine.com/20030416/page_8.html.