[Dx4win] Users of Club Log who are DX4Win users please read!

Jim Reisert AD1C jjreisert at alum.mit.edu
Tue Feb 14 11:26:36 EST 2012


---------- Forwarded message ----------
From: Alan Jubb - 5B4AHJ <g3pmr at shacklog.co.uk>
Date: Tue, Feb 14, 2012 at 5:49 AM
Subject: Users of Club Log who are DX4Win users please read! (others can ignore)
To: ClubLog <clublog at googlegroups.com>, cdxc <CDXC at yahoogroups.com>,
GMDX at yahoogroups.co.uk
Cc: Jim Reisert AD1C <jjreisert at alum.mit.edu>, "Miguel S.G.Martins"
<ct1iua at gmail.com>


Hi all
There have been many error reports generated by Club Log recently
concerning ST0R and the PJs.
Club Log was reporting that the user had claimed the old entity.
I had been putting this down to users using an out of date country
file, but it turns out this was not the case.

In spite of Club Log flagging up errors, a couple of DX4Win users
claimed that DX4Win  was showing the new, correct DXCC in their log.

Between us, Mike CT11IUA, Jim AD1C, and myself, have identified the
problem, which is caused by DX4Win users not properly following the
instructions for upgrading to the latest country file.

When updating the DX4WIN country file, there is a second file to
update, which contains the country-to-ADIF mappings, ADIF.pmp.
If the country file is installed, but not ADIF.pmp, DX4Win users will
see the correct DXCC in their log, but DX4Win will create an ADIF file
with the old mappings, which, in turn, causes Club Log to flag errors.

So, in summary, if:

a) You are a DX4Win user
b) You get the correct DXCC showing in your log (especially for ST0R
and the PJs)
c) Club Log tells you have claimed the old DXCC

then you probably haven't installed ADIF.pmp.
Please go to www.country-files-com/dx4win and read and follow the
installation instructions again!
There is a tool, The DX4WIN Data Updater, that makes all the necessary
downloads.
Using this tool, Mike CT1IUA has fixed his error report.

Thanks!
--
73
Alan 5B4AHJ-5B50J-P3J


More information about the DX4WIN mailing list