[ct-user] Bug in C2A.EXE?

Jim Reisert AD1C Jim Reisert AD1C <jjreisert@alum.mit.edu>
Thu, 9 Mar 2000 17:25:00 -0500

The CT to ADIF conversion does not do any callsign processing to try to 
determine the country from the callsign.  Thus, I can't easily separate out 
the Canadian provinces from the States/Sections.

However, this is an EASY problem to fix on the import side, since the 
logging software (logger) has the smarts built into it to determine the 
country from the prefix.  Contact that software author about fixing the 

DXbase and DX4WIN users have not complained about this problem, so 
obviously those programs have a method of dealing with it.

73 - Jim AD1C

At 03:55 PM 3/9/00 -0500, Rob Kennedy wrote:

>Hello all,
>Below is an interesting message posted on the Logger reflector.  Apparently,
>the contest program CT does not create a proper ADIF file for importing the
>CT contest log into other logging programs like Logger.  All QSO's where a
>Canadian Province is logged are not properly exported by CT into an ADIF
>file.  The Canadian Provinces are put in the "State field" of the ADIF file,
>not the "Canadian Province" field of the ADIF File.  To my knowledge, Canada
>is not (yet) part of the US - Hi
>If CT does produce a proper ADIF file, please let me know.
>So if you use CT during contests and try to import your QSO's  from CT into
>other logging programs like Logger using ADIF you may run into problems.
>There may be a workaround.  There is a program called LOGCONV by KA5WSS that
>will convert a CT version 7, 8 or 9 .BIN file into ADIF  (or many other file
>formats like .CAB).   The URL is http://www.qsl.net/ka5wss/logconv/
>I have not had a chance to try LOGCONV to convert a CT .BIN file generated
>by my old CT 8.52 program into ADIF.  But I have used LOGCONV for other
>applications.  It works well.
>For those who are having troubles importing the ADIF file generated by CT
>(using C2A.EXE) into another logging program, you may want to give LOGCONV a
>try.  It may work.
>Are there any plans to fix the bug C2A.EXE?
> >From: "Jim Kehler" <kh2d@kuentos.guam.net>
> >To: logger@eGroups.com
> >Subject: [Logger] Re: ADIF and VE Provinces
> >Date: Thu, 09 Mar 2000 08:53:27 -0800
> >
> >
> >The problem converting CT files to ADIF and importing them into
> >Logger is caused by the C2A.EXE program. It incorrectly puts
> >STATE:<Canadian Provence> into any ADIF record that it makes
> >for a contact with Canada. AD1C wrote the program, and he's not
> >interested in fixing it.
> >
> >Canadian Provinces are NOT states. In other words, you can't
> >put PQ or NB or FOOBAR in for a state. You can only put a
> >valid 2 letter state code in an ADIF record following the
> >STATE: identifier.
> >
> >Logger doesn't have a CANADIAN PROVINCE field. So even
> >if the C2A.EXE made a correct ADIF record (which it does
> >not) Logger would not import CANADIAN PROVINCES....
> >
> >Logger's ADIF import routine works fine.
> >
> >To work around the C2A.EXE problem, edit the BAD.ADI file, and
> >using a global search/replace funtion of the editor, replace all
> >the STATE: with BALONEY: - Then save the file to another file
> >name, like TEMP.ADI and it will import correctly into Logger.
> >
> >73, Jim KH2D
> >
>Submissions:              ct-user@contesting.com
>Administrative requests:  ct-user-REQUEST@contesting.com
>WWW:                      http://www.k1ea.com/
>Questions:                owner-ct-user@contesting.com

Jim Reisert AD1C <jjreisert@alum.mit.edu>

Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.k1ea.com/
Questions:                owner-ct-user@contesting.com