[Dx4win] Missing QSOs

Jim Reisert AD1C jjreisert at alum.mit.edu
Mon Dec 21 01:35:01 EST 2015


On Sun, Dec 20, 2015 at 10:15 AM, Duane Calvin AC5AA wrote:

> There is another, more sinister possibility.  If you worked them, and didn't
> expressly do a save of the new data, then MS applied updates, causing a
> shutdown without saving, that can bite your log bigtime.

I have to agree, especially considering the timing of the lost QSOs.
The other possibility, as someone else suggested, is logging them to a
different log file.

I run Windows 10 Professional on both my "important" computers, which
allows one to defer the automatic reboot. Of course, those two
computers were upgraded from Windows 7 Pro.  You can't get a free
update from 7 Home -> 10 Pro.

I also don't walk away from the operating position without saving my
QSOs using File | Save (ALT-S), well, most of the time.  I usually
catch the error when I refresh the log on my non-ham computer and the
newest QSO(s) don't show up.

HOWEVER, having said all that, if DX4WIN terminated without your
intervention, when you restarted, DX4WIN should say that there is an
unsaved backup log, and ask if you want to save it.  I always answer
YES, even if I'm 100% sure that I did save my log.  This happened to
me the other day. The two .DXL files were the same size, but
supposedly contained different data.  When I exported each to DX4WIN8
format, and compared the .DXQ and .DXN files, they were exactly the
same.  So I knew it was OK to delete the second (backup) copy.

Please read this application note in its entirety:

    http://dx4win.ad1c.us/appnotes/backup.html

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


More information about the DX4WIN mailing list