I have been a Dx4win user for over ten years. Don't have the exact date of
the change, but I think it was very early in the life of Dx4win. Made the
change to Dx4win  because of very poor and expensive service on two other
logging programs.
Now running version 7.03.16.  Have found the program kinda like Timex- just
keeps on tickin!!
Thanks to Paul, Steve and Jim.
Bill-W5VW
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.13/1213 - Release Date: 1/7/2008
9:14 AM
From [EMAIL PROTECTED]  Mon Jan  7 15:45:12 2008
From: [EMAIL PROTECTED] (Jim Reisert AD1C)
Date: Mon Jan  7 15:46:05 2008
Subject: [Dx4win] Country editor bug
Message-ID: <[EMAIL PROTECTED]>

Hi Folks,

I just tested DX4WIN 7.02 and did not run across the country editor bug when
adding FJ/St. Barthelemy.

For anyone who *did* have log data corruption, were ANY of you using a version
of DX4WIN *other than* 7.03?

73 - Jim AD1C


--
Jim Reisert AD1C/?, <[EMAIL PROTECTED]>, http://www.ad1c.us
From [EMAIL PROTECTED]  Mon Jan  7 16:18:03 2008
From: [EMAIL PROTECTED] (=?iso-8859-1?Q?Isidro_Acosta_Hern=E1ndez?=)
Date: Mon Jan  7 16:19:31 2008
Subject: [Dx4win] Unhappy with DX4WIN
References: <[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Hi all.

I have read about so many problems adding an entity to the DX4WIN, that I
think necessary to recall a word nobody should forget:  BACKUP.

1) Before making any changes in the databases, make a backup copy of your
log files (*.dxl), the country file (dx4win.cty) and the configuration file
(dx4win.cfg).  If anything goes bad, recover the backed up files and the
problem is gone.

2) Do not press Alt-S (to save the log) unless you are sure it is ok (check
states/counties information, etc.).  If something is bad, re-load the log
(File > Open...).  But doing this will lose any contact added after the
latest save.

By the way, I added FJ without any trouble (I had not to recover the backed
up files... hi).  I proceeded as follow:

1) Close the log.  You cannot access the country database with the log
open.

2) Click on File > Databases > Country.  Go to St. Martin (Country > Find >
St. Martin) and check that the main prefix is not FJ (should be FS).  If
you have to change the main prefix, Click on Country > Update.

3) Click on Mapping and, in the mapping prefixes list, add an end date for
FJ.  It must be the same start date for St. Barthelemy.  Click on Mapping >
Update.

5) Click on Country > Add.  Write down all the details for the new entity
(FJ, Saint Barthelemy, etc.).  Make sure "Has states = N".  After all data
is ok, click on Country > Update.

6) Clic on Mapping > Add.  Add the FJ prefix, including the zone and the
start date.  Click on Mapping > Update.

7) Click on File > Check for errors.  It should only show one line "End of
error listing".  If some error is found, correct it before exiting.

8) After all is ok, click on File > Save changes and Exit.  If you cannot
correct the errors, click on Cancel Changes and Exit, and look for help.

9) Open the log.  Check the new entity addind a "dummy QSO" with a FJ call
with a date BEFORE the start date for St. Barthelemy.  It should be logged
as "St. Martin".  Now add another QSO with a FJ call with the start date
for St. Barthelemy.  It should log as St. Barthelemy.  If all is ok, delete
the "dummy" QSOs and and check some USA QSOs to verify that the State and
County is unharmed.  If anything is wrong, DON'T PRESS ALT-S.  Close the
program (without saving the log), reopen it and recheck the log.

10) If something is still bad, recover the backed up files and start all 
from the beginning.

Good luck!

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