[Dx4win] DX4WIN 9.01 country file

[Jim Reisert AD1C]

PY2YP is the only one who has sent me feedback on differences between
the 8.05 and 9.01 country file.  I would like to publish an update
this week to fix his problem and a few others (including a couple I
found myself!)

On Fri, Oct 20, 2017 at 8:32 AM, Jim Reisert AD1C wrote:

> There were some changes to the DX4WIN 9.01 country file.  Most notably:
>
>> Callsign exceptions and mappings in the country database have now a start-
>> and end-date allowing multiple date ranges to be specified.
>
> Though I have tested this many times, there could be some subtle
> differences in your DXCC totals.  The easiest way to identify the
> problems is to follow these steps.
>
> NOTE:  It's best if both the OLD and NEW versions of DX4WIN are using
> the *same* country file release, either from 21-Sep-2017 or
> 20-Oct-2017.
>
> NOTE:  If you have "Pfx=" errors in your original log, it will be more
> difficult to find the new errors specific to DX4WIN 9.01.
>
> 1.  Export an ADIF file from your old DX4WIN version.
>
> 2.  Create a new, empty log in DX4WIN 9.01
>
> 3.  Import the ADIF file from step #1 above into the empty log you
> created in step #2.
>
> 4.  Using F8, search for the text "Pfx=" in the "Notes for this QSO"
> field.  I do not care about ZONE errors, there could be many of these.
> However, if the errors are on portable calls in either BY, UA9, VE or
> VK, I am interested in those.
>
> Only if you are *convinced* that the old country file was correct, and
> the 9.01 country file is incorrect, please send me the following:
>
> - callsign
> - date of QSO (please spell out the month, or use the DD-Mmm-YYYY format)
> - what DXCC entity you believe it *SHOULD* be
>
> I will be happy to make corrections in the next release of the DX4WIN
> country file.

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us