[ct-user] CT DOS Users Check your Log times for WPX

[Ed K1EP]

At 3/26/2007 10:27 PM, Robert A. Wilson wrote:
>Bob,
>
>CT_TOOLS for WinXP <http://www.k1ea.com/ct10/ct_tools.zip> or CT Tools for
>DOS <http://www.k1ea.com/ct10/ct_dos_tools.zip> should fix the problem for
>logs made with CT Version 10.  Those on CT Version 9 should use this
>version<http://www.k1ea.com/ct9/ct_time.zip>
>.
>
>Unzip the appropriate ZIP file to your CT directory, make a backup copy of
>your BIN file, then from the command prompt:
>
>   CT_TIME WPXCW07 -60
>
>to subtract 60 minutes from every timestamp in WPXCW07.BIN (note that you
>should omit the ".BIN" on the command line).  If you forget the syntax,
>CT_TIME without any arguments will display brief help text and examples.
>
>The problem is that the time zone rules are hard coded in the C Runtime
>Library to start in April instead of in March, and CT is not the only
>program having problems.  Any program calling tzset() (part of the C Runtime
>Library) will have the same issue, especially if the library is linked into
>the executable file, as it is with CT for DOS.
>
>I think Ken is going to have to recompile CT for DOS to fix it, unless you
>try the following trick, which basically tells tzset() to treat Eastern Time
>as 4 hours behind UTC instead of 5 hours behind.
>
>Just add ONE of the following lines to AUTOEXEC.BAT, or whatever batch file
>you use to launch CT.
>
>SET TZ=EST4EDT
>SET TZ=CST5CDT
>SET TZ=MST6MDT
>SET TZ=PST7PDT

You can also use numbers, such as 
SET TZ=4
or 
SET TZ=7

In this case, what you have to do is manually set the variable twice a year.  As pointed out, this may be tricky if the time change occurs during a contest.  I guess in that case you stop the program at 2AM local and change the variable.