[Dx4win] DX4WIN does not count contact with RST_RCVD with Zero as a valid contact

[Jim Reisert AD1C]

On Tue, Sep 9, 2025 at 6:37 PM N5PA <n5pa at n5pa.com> wrote:

I was auditing my DXCC Band and Mode counts against LOTW and my numbers did
> not match.  What I found in my auditing process was that if the RST_RCVD
> field had a value of Zero, it did not count that contact towards DXCC
> Credit.
>
> To test and resolve this I exported my entire log to an ADIF file and then
> used ADIF Master to export the entire file to a CSV file.  Then I brought
> it up in Excel and searched and replaced the RST_RCVD records that were
> Zero.  There were 432 contacts that had a Zero in the RST_RCVD field and
> were replaced with a “-1” to test my theory.  Then I moved it from a CSV
> file to an ADIF file and imported it back into DX4WIN.  After doing this,
> my numbers matched LOTW.
>
> Searching the internet I found that "rstR = 0 or ValidDX = Invalid are
> indicating an invalid QSO for any award".
>
> When using the Digital Modes, “0” is a valid RST value since it stands for
> Zero dB.  There may be a workaround that I do not know about, but what is
> the proper method to resolve a RST with a value of Zero so that our numbers
> match LOTW? I don’t like the idea of changing what the real RST value of
> Zero is to a +/- number because it will not match what was really exchanged
> in the QSO.
>

Hi Alan,

You can use the award flags at the bottom of the QSO window to invalidate a
QSO for any given award.  For DXCC, you would want to set Mixed, Mode and
Band all to 'I'.

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