Thanks to the few folks who sent me comments about the new data
updater. I've put a new version on the web:
http://dx4win.ad1c.us/updater/beta/dx4wupd_20130326.zip
Just download the ZIP file above, extract dx4wupd.exe and save this
file in your DX4W### directory, over-writing the version that should
already be there.
IMPORTANT: if you tried version 6.01, you MUST delete your
DX4WUPD.INI file before running this version! When you start the
program, the settings will be imported from your existing DX4WUPD.RC
NOTE: future beta versions of the new updater can now be obtained
using the Update button, no download/installation needed (it will
recognize when there is a new version).
NOTE: the "Restore" button is disabled. It's only a place-holder for now.
Here is a link to the original notes about 6.01:
http://mailman.qth.net/pipermail/dx4win/2013-March/019453.html
CHANGES from version 6.01:
- migration of settings from .RC to .INI file didn't work very well, fixed now
You MUST delete DX4WUPD.INI before running this version! (just the first time)
- download of IOTA database (fulllist.xml) now updates the progress
bar during download
- date of the Calendar file is shown properly
- adif.pmp file is now downloaded on country file update, included in totals
- DX4WIN.MAS (master callsigns for 7.07 [or 7.05] and earlier) is
always downloaded
when DX4WIN.MAS1 is downloaded (Master Callsigns is checked).
There is no way
to get just one or the other, they're a package deal.
- "DX4WIN Data Updater" checkbox added. If the button is checked, the
updater will always
download an update if one is available. If it is unchecked, it will
prompt you first. In -auto
mode, with the box unchecked, you will be told there is a new version dated
DD-MMM-YYYY but it will not download. You will have to look at
DX4WUPD.LOG to tell.
- Added "Restore" button, inactive for now
- If a DX Cluster node in the DX4WIN.TCP file was not in the expected
format (required for merge),
the error message would not have been displayed properly.
- The updater was using two different techniques (and accesses) to
determine whether
a file needed to be updated from the web. This meant extra
Internet traffic. Now it
uses one technique, and passes the results on to the second
consumer (this is more
of a note for my revision history).
NOTE: if you have an existing calendar file, the new one will be
downloaded twice - once to determine whether there is a new one, and
again to actually download it. The code to download the file only
once got very convoluted, because this is the only file for which the
update program can not determine its creation time. I'll work on this
some more later.
Please try the new version and send me comments, thanks!
--
Jim Reisert AD1C, <[email protected]>, http://www.ad1c.us
______________________________________________________________
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
