Good news! de Laurie VK3AMA

John, FYI, A very near future JTAlert build utilizes a new ADIF file importer that is an improvement over the current importer, which as you know was a significant improvement

Scott, Currently, only DXKeeper can provide what you want. The JTAlert "Rebuild Alert Database" operation (which scans your log) can consider QSOs that have one or more DXKeeper

This defect has been resolved. Joe WC4R, who experienced and reported this defect, has confirmed the latest JTAlert beta has corrected the problem. The next public release has the fix. The cause was

Maybe, I don't understand, but if you are running FT8 HF on one rig and MSK144 6M on a second rig, doesn’t the logged mode already tell you which is which? Although logging a MSK144 QSO does not

Hi all: Is there a way to filter the logs for needed states after a certain date? I moved to new QTH in 2000 and am trying for 5B WAS. I need to filter the my alerts for states after

thank you . that's much better wish it was 4 slots and more lines , maybe next version . but much better

I am running two rigs, usually. At the moment I am on 6m Meteor Scatter. I am also running FT8 on 10m, or before daybreak, on 60m. Thus there are two Propagation modes. I'd like the settings

Laurie This morning, I did complete rebuilding my computer on an SSD disk. Unintentionally I did also rebuild the HRD Logbook using ADIF file backup similar to your description. 12 hours later,

Thanks, Laurie. I figured that was the way to do it and glad you confirmed. 73, John W9ILY

Hi Laurie, well that is good news and something to look forward to! Many thanks, Andrew G0MBL

Argh! I’ve been up way too long. Hit me with a nerf bat! I missed your comment at the bottom stating the option does indeed delete the DB file entirely. Which answered my last message. My humble

Many thanks reply, Laurie, for your quick response. I recall seeing that feature. However, when the DB is corrupt, my thought was that brute force deletion avoids issues with Decodes program not

Tom, FYI, a quicker solution (without the ability to save the old database) is to temporarily set the Decodes startup options to "Delete All Records" then restart (close & open)

See the Settings window... No, the width cannot be changed to 4 callsigns. You can add additional lines. de Laurie VK3AMA

IS there a way to keep JTAlert always on top ? and can the window be resized so it's only 4 wide and the other 4 be under it, so I can be doing stuff and yet see when a QSO I am looking for comes up

[Nb. This is a spruced up and expanded version of a much earlier post of mine] As with many, I’ve experienced the issue of the Decodes Window not auto-starting after opening. The fix for some

Hi Laurie…. Yes, the Ignored Callsign appears as it should if it is not B4. I checked several random calls on 40m FT8 and it worked well. Then I tried a couple that were B4 and it failed.

John, "I manually import all of my FT8 ADIF files from WSXT-X and JTDX into that logging program" is the problem. You need to be importing the ADIF file that JTAlert

Tom, You only need to change the enabled state via the "Settings>Alerts" menu. The corresponding checkbox in the Settings window is automatically linked to the main gui menu.