[Dx4win] Proposal for changes to DX4WIN Data Updater

Jim Reisert AD1C jjreisert at alum.mit.edu
Mon Jan 4 19:16:33 EST 2016


Based on a bad experience a user recently had, I'm thinking of making
a few changes to the DX4WIN Data Updater.  If you might be negatively
affected by any of these changes, please let me know.

1.  Don't allow the Updater to run if DX4WIN is installed under
C:\Program Files....

    Reason: permission problems might prevent the files from being
updated, or the updates might "disappear" and original files restored.

2.  Disable the Update button once one or more items has been updated.
In other words, if you want to update again, you must exit the Updater
and restart it.

    Reason: this might have caused data corruption for one user,
though I can not explain how.

3.  Copy the DX4WIN configuration file (DX4WIN.CFG) to the
DX4W###\BACKUP directory before making any changes.

4.  Copy your DX4WIN logbook (.DXL) file to the DX4W###\BACKUP
directory before making any changes.
    NOTE: if you first close your logbook before exiting DX4WIN to
perform the update, your logbook will NOT be backed up, because its
file name won't be found in the DX4WIN configuration file.  This is
how DX4WIN knows which logbook to open when you start the program.

The Updater as written today (ver. 7.12 and earlier) does NOT touch
either your logbook or your DX4WIN configuration file.  One user had
his configuration file corrupted.  I am at a loss to explain how this
could have happened.  Nonetheless, saving a copy of that file can't
hurt.

73 - Jim AD1C

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


More information about the DX4WIN mailing list