--- ON4AOI <[EMAIL PROTECTED]> wrote:

> In the list it has changed already but it isn't changed in LOTW
> So if you upload qso's with E7 prefix it will not be recognized as T9
> Bosnia & Herzegovina prefix

Not true.  When a DX4WIN log is exported to ADIF (with the intent of signing to
be uploaded to LoTW), each exported QSO has the ADIF number of the DXCC entity,
so the actual prefix does not matter (it's not even in the ADIF file).  So the
QSOs will upload correctly either way.

The reason I changed it from E7 back to T9 was to be consistent with the DXCC
Credit listing and the LoTW Award Credit matrix, which still use T9 for the
prefix.  People who want to check their DXCC credits by hand want to see Bosnia
come up in the same place in both the ARRL and DX4WIN listings.

73 - Jim AD1C


--
Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us
From [EMAIL PROTECTED]  Mon Jan 28 12:55:02 2008
From: [EMAIL PROTECTED] (Jim Reisert AD1C)
Date: Mon Jan 28 12:58:04 2008
Subject: [Dx4win] Import LogEQF?
Message-ID: <[EMAIL PROTECTED]>

Hi,

Someone sent me some files from LogEQF but I don't know how to import them into
DX4WIN:

  <call>.T_K
  <call>.L_G (this is the largest file)
  <call>.N_T

I looked at the DX4WIN import filters, and LogEQF says something about dBase
conversion.

How can I help this person import his files into DX4WIN?

Thanks & 73 - Jim AD1C


--
Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us
From [EMAIL PROTECTED]  Mon Jan 28 18:27:13 2008
From: [EMAIL PROTECTED] (Roger Marrotte)
Date: Mon Jan 28 18:30:32 2008
Subject: [Dx4win] Problem with FILE|IMPORT/EXPORT Screen
Message-ID: <[EMAIL PROTECTED]>

Last night after working a few contacts in the 160m contest I tried to
import the contacts from Writelog to DX4WIN as I usually do after each
contest.  I have DX4WIN Ver. 7.03.16, which I believe is the latest version
available.  I converted the the Writelog contest file to ADIF, ran DX4WIN,
clicked on FILE, then on Import/Export.  The screen that showed up consisted
mostly of garbage characters.  I could see the three columns that are
usually there, ID, USAGE and DESCRIPTION.  Some of the text that usually
shows up in each column look correct but most of the text was pure garbage.
As a former programmer, it looked to me as if a table of text was messed up,
or an index was wrong or a format statement was wrong, or something like
that.  I eventually guessed the correct place to click on and successfully
imported the data.  I've never seen this before with DX4WIN.  Has anyone
else seen this?  Is this a known problem.  Do I have a corrupted file.
Except for this one window with funny characters in it, DX4WIN seems to be
working correctly.
 
Roger, W1EM
From [EMAIL PROTECTED]  Mon Jan 28 18:53:47 2008
From: [EMAIL PROTECTED] (=?iso-8859-1?Q?Isidro_Acosta_Hern=E1ndez?=)
Date: Mon Jan 28 18:57:00 2008
Subject: [Dx4win] DX4WIN.CTY Release #46 released 28 January 2008
Message-ID: <[EMAIL PROTECTED]>

Hi Jim.  Thanks for your answers...

About the E7/T9 prefixes, I had only used the "DXCC plain text" list, which
has already the E7 prefix.  As I am not (yet) involved in LOTW, I will
continue using E7.

I tried to merge the countries list in various ways, and these were the
results:

1) I merged only the prefixes:  nothing was updated.  I did a binary
compare of my old cty file against the merged one (obviously, after saving
it and closing the DX4WIN).  Both were identical.

2) I merged all the databases:  everything got updated, EXCEPT the
prefixes/dates changes.

3) I first deleted a country (FJ) in my original database and then merged
all the databases:  everything got updated, but the FJ country was not
added, nor the changed dates.

I had noted only the (1) sometime ago, and since then I used to update
things by hand.  Is there a (logical) explanation for the other two
results?

Best 73 de Isidro, EA8NQ
E-mail:  [EMAIL PROTECTED]   (remove the _ )

----------------------------------------
Visit the EA8NQ's web page (in Spanish):
http://ea8nq.ure.es/
----------------------------------------

Reply via email to