... as v2.16.12 is the most recent version, the update message will probably indicate a new version of the HamApps.Databases. vy 73, Willi, DJ6JZ Am 27.08.2020 um 21:45 schrieb Monty Wilson:

Carl, this seems to be the website of UR5EQF https://ur5eqf.ru/download/ur5eqf_log Download not tested by me. vy 73, Willi, DJ6JZ Am 18.08.2020 um 20:29 schrieb Carl - WC4H via groups.io:

Am 03.06.2020 um 17:57 schrieb Norbert Graf - DD3KF: I already wondered if I missed a setting that would activate 4m... I support this suggestion. vy 73, Willi, DJ6JZ

I am also interested in an answer. Some days ago I reported that I got a message from an OM who was displayed as "offline". So the online / offline indication seems to be unreliable. vy 73, Willi, DJ6

I just got a text message from an OM who is displayed as "Offline". So the offline indicator seems to be unreliable. I did the tests available under Web Services -> TCP/IP Network Ports and all show "

Larry, this referred to Log4OM 2.0 which is currently tested by a restricted group. But I am also curious what will change then. vy 73, Willi, DJ6JZ Am 30.10.2019 um 18:52 schrieb Lawrence Godek:

Am 30.04.2019 um 20:11 schrieb Jim N6VH: Yes. qrz.com works but logbook.qrz.com was off most of the day. OK again at 19:05 UTC. vy 73, Willi, DJ6JZ

Neil, JTDX has filter options by continent. http://www.jtdx.tech/en/ vy 73, Willi, DJ6JZ Am 14.04.2019 um 02:24 schrieb Neil:

Bill, it is not impossible to operate several programs at one com port. Two options: 1) via Omnirig (if the programs can work via Omnirig). Just select Omnirig instead of the trx model in the external

Am 16.02.2018 um 21:47 schrieb HamApps Support (VK3AMA): Laurie and Igor, I agree - I could understand, that ZA/IW2JOP is assigned wrongly to Kosovo because of an error in the prefix list. But I can't

As Igor UA3DJY wrote, a bug in the JTDX prefix list caused the issue. In the mean time I upgraded to JTDX 18.1.0.73; ZA/IW2JOP was received again, and evereything was displayed correctly this time. Th

Today I logged a QSO that JTAlert identified as Z6/IW2JOP - this was transferred to Log4OM accordingly. Later I was informed that it should have been ZA/IW2JOP. So I checked the stored audio file with

Bry, I am not sure if the following description will solve the problem you have; it is related to UDP ports of the programs I am using: JTAlert must be set to the same UDP port number as Log4OM. But t

test de dj6jz