toggle quoted messageShow quoted text
Hi Bob, Thank you so much! I never thought of database
exception, only clicked the third item which validated the country
code. Now it works fine. BTW: This made my dx spot window work! B4
no dx spots from cluster window have been displayed in the spot
There are some other road works but i try to solve the problem
Thanks again 73 Matthias
Am 02.01.2020 um 17:35 schrieb Bob:
Now you know why
no DXCC information is being logged. Logger32 doesn't know where
you are. Click SETUP | UPDATES | COUNTRY DATABASE EXCEPTIONS
FROM CLUB LOG | LOOK FOR UPDATES NOW. When updates have finished
downloading/installing, try entering DK4WD id the Logbook Entry
Window again. Does Logger32 know you are in Germany now?
On January 2, 2020 at 11:17 AM Matthias
Bellmann <Dk4wd@...> wrote:
instead of dl eu14 it shows "** ?? ??"
Am 02.01.2020 um
17:05 schrieb Bob:
... and if you type DK4WD in the Logbook Entry Window,
what Country does Logger32 say that is? 73.
On January 2, 2020 at 10:41 AM Matthias Bellmann <
I enter my qso in the (normal ?) way into the nput
window. Usually cw,
but sometimes ft8 and ssb. by pressing the enter key
the just logged
qsdo is transferred into logbool page, but dxcc column
accepted". When a former qso with the station is
alread logged the dxcc
is displayed correctly.
Am 02.01.2020 um 16:05 schrieb Bob:
So, how are you entering the QSO in the logbook,
What mode are you operating? SeventyThree(s).
On January 2, 2020 at 9:51 AM Matthias Bellmann
When qsoing a new statioin the dxcc column in the
logbook page remains
empty. This column is filled only after using
updates menue. This is
pretty inconvenient, because the worked/confirmed
window also remains
empty. So when i qso a new station i can not check
appropriate country is already in my log.
I remember that in former versions of logger32
there has been a
dxcc-table. Is it still available or must i carry
out the above
By the way: Happy new year to all of you