[Dx4win] Log corruption due to operator error.

[k2waltk]

Let me preface this by saying (or implying) that there is something
wrong with dx4win 803,  there isn't.  
 
I tried to upgrade to 8.03, following Jim, AD1C's upgrade tips, and 
somehow I munged the log.  Not only was the new log in 8.03 
corrupted but the log in 8.02 was also.   Fortunately, I have a backup on
another networked machine.  I use the 'sync' feature of the SyncBack update
app. which allows me to maintain a 'synced' (or mirrored) copy of what is on
the master, and vice-versa.  I turned off the update program before I
upgraded, 
so I still have a working copy of Dx4Win 8.02.  My sanity check after an
upgrade,
is to see if the the DXCC needed report produces the same list, before the
upgrade. 
One thing that is common between both versions is the country file.  Maybe
this
is where I went wrong?  Could it be that I used the wrong copy of
dx4win.cty?
Sorry for taking up bandwidth describing my particular situation.  Maybe it
could be apropos to other users.  No doubt, this is a result of operator
error :-)
Any ideas?
 
                             Regards,

                                           Walt Kornienko - K2WK
                                           k2waltk at gmail.com
                                           k2wk at arrl.net