Thank you for your prompt reply...most appreciated frank N1GDO

Bob, My reasons for abandoning HRDV6 has been discussed numerous times within this group. I wont repeat them. I will say however, the removal of RR from HRDLLC

Did you search the archive? Laurie has made several definitive and succinct statements on this topic: https://au.groups.yahoo.com/neo/groups/HamApps/conversations/messages/13378

Not trying to get anything started here but why is this: HRD V6 logging is no longer supported by JTAlert starting with version 2.9.0. Went to up grade from 2.8.7 to 2.9.0 and saw that. I understand

Thanks Dan, That's disappointing, as the JTAlert version your running (the Azimuth patched version) contains some code changes to try and avoid these occasional Log4OM UDP logging

Doesn't bother me, but does sometimes make me cringe when it is "over the top" and I am left thinking this Guy has watched too many Paul Hogan movies (eg. Crocodile Dundee) :-) de Laurie VK3AMA

David, It would be a trivial addition, but for what purpose? The Mode is already set within the QSO record of you log, why the need to duplicate that information in the Comments or QSL

Jim, JTAlert doesn't care about multi-line QSO records in the ADIF. Similarly, all the superfluous HRD clutter in the ADIF file is of no consequence, they are ignored. JTAlert will work with an

Jacques, You don't need to do anything. JTAlert automatically checks the B4 status of decodes against whatever log type JTAlert is configured to use, including an ADIF file. de Laurie VK3AMA

Frank, The Alert filters apply universally across all Alert types, they cannot be applied to individual Alerts. My Suggestion is to turn

Is there a way to trigger Wanted Continent but only when the station is calling CQ? If I turn on Wanted CQ I get too many alerts for every station calling CQ. If I turn on Wanted Continent I get the

Hello all Bill here N3GTY new to the group and JTalert. I thought I had problems in the past with my setup and JTalert and I have discovered that the problem was with the program I was using for JT65.

OK James, scratched all and restarted and all is ok now and restored my B4 cells show up . Thanks Jacques

Thanks James well this is what I did but when I scan log it shows scanning 10K contacts but does not update anything and take milli seconds to complete ... Strange .. must have missed something

Jacques, Hopefully Laurie will chime in with the best answer. When I went to Ver 2.9, I lost my +8,500 JT QSOs that had been used in the B4 check. I exported my JT QSOs from HRD Logbook in ADIF

HI, if- when changing to version 2.9 and save log as ADI I can import to HRD 6.3 etc simple enough. What is best way to get the scan log to check the worked before status? do I need to import

Great work mate! Yeah know, I bet you hate it when a Yank tries to talk Aussie.

Hi Laurie, Was wondering if it could be possible to add %Mode% to the current available above list? Not a biggie and more than happy to wait for vers 3 if you’re busy :^) Thank you for a

Laurie, I should have mentioned it, but I did that this time. I’ve had this happen previously, but before now the second attempt worked. It did not this time.

Hi Rory, I was also thinking that UDP might be an issue. I have altered the Log4OM UDP handling to explicitly close and reopen the UDP socket prior to logging. A Test version with this change is