Are you seeing decodes in JTAlert? Do you get a message (success/failure) from JTAlert when logging? Mike W9MDB

What email provider are you using? And what is your return address you put in the script? Mike W9MDB On Friday, November 25, 2022 at 05:54:36 PM CST, edmscan <kevin_fisher@...> wrote: I am using y

I've got a JTAlert email powershell script on my QRZ page. Works find here to both phone and email. Mike W9MDB On Friday, November 25, 2022 at 02:14:56 PM CST, edmscan <kevin_fisher@...> wrote: I

You should just ahead and upgrade to Log4OMv2 and get it over with now. Mike W9MDB On Thursday, November 24, 2022 at 10:37:26 PM CST, AA3AE via groups.io <aa3ae@...> wrote: [Edited Mes

You want the UDP Inbound -- not the TCP Connection. It's in the Help information under Logging. Mike W9MDB On Thursday, November 24, 2022 at 02:27:57 PM CST, AA3AE via groups.io <aa3ae=yahoo.com@group

I guess you are using the ADIF file. You will need to edit it and replace all your old call signs with your new one (global search and replace). A real logging program would also solve the problem. Mi

You only want band alerts for 80M and not the others? May I ask why? Some special 80M award? Normally one would want band alerts for all bands and not just one band. Mike W9MDB On Wednesday, November

Each alert is customizable for by band or any band. So you can have WAS by band&mode and DXCC for any band and any mode. Mike W9MDB On Tuesday, November 22, 2022 at 10:11:51 PM CST, Steven Hines via g

No I did not log a test QSO. So I did a log entry on 20M (Log4OM registered 3Y0I Bouvet correctly) and repeated the test on 17M and JTAlert didn't show it as new DXCC on band -- deleted the 20M QSO an

The alert still shows as Antarctica On Sunday, November 20, 2022 at 11:45:07 AM CST, Tom Job <ve3ii@...> wrote: Hi Mike and all.... I tried it on my JTAlert and, at first it did show Antarctica b

3Y0I shows as Antarctica on JTAlert....should be Bouvet. They'll be operating coming up in 2022. Mike W9MDB

If using WSJT-X be sure "Double-click on call sets Tx Enable" is checked in Settings/General. Mike W9MDB

One of these might help.... https://www.youtube.com/watch?v=78At5nM3zbQ https://answers.microsoft.com/en-us/windows/forum/all/ipersistsave-file-failed-code-0x80070005/33c145bc-464c-4a87-a6a6-ecd1fc9e2

Turn off WSJTX sending the info. Mike W9MDB

That's the solution I gave you. Checking "No QSL confirmation" will count any worked country and prevent the DXCC from alerting. You then still have choices on if you want alerts by band and by mode t

#FT8

I thought you said you did NOT want an alert for a worked country. You were complaining seeing an alert on a worked country. Please rephrase what you want to see. Here's some of the possibilities Aler

#FT8

What issue does it create? Mike W9MDB

#FT8

You would only receive alerts for countries not worked. What the LOTW checkbox means is this: "Count a country as worked if it has been confirmed via LOTW". With the "No QSL Confirmation" checked "Cou

#FT8

Just the opposite -- It moves all "worked" countries to the "Not Wanted" list instead of just the confirmed ones. Mike W9MDB

#FT8

In the Rebuild Alert Database window check "No QSL Confirmation (Any Worked Station) for the Alerts you want to ignore for any worked station instead of confirmed. Mike W9MDB

#FT8