Thanks Michael

Thanks Joe.   zm only chasing band-entity.  You answered my question in the affirmative

Jim K7EG

It would be nice to have an alternative to Windows.

The "By individual Mode (JT9, JT65, FT8, FT4)" is not necessary.
Any of the four options for mode will still provide an alert
when any new band/country is decoded. DXCC Challenge (DeSoto
Cup) does not recognize band/mode/countries only band/countries
on 160-6 meters.

73,

... Joe, W4TV

Hello Brain Trusts

My HP Laptop is dying a slow death.

New machines come with Win 11.

I've read many threads with complaints and fixes... too many to have absorbed all the knowledge.

Looking initially for an answer to a simple question.


Is it safe for me, a non computer savvy person, to make this migration   e.g. programs like  N1MM, WSJTX, JTALERT, DX Labs, transition easily to the new OS or  should I wait for WIN 11 updates in the next year or so...or until the final spark of life leaves my current machine?

--
73

Bob

Ko6Lu



--
Bob
KO6LU

I am trying to focus on alerts for new band-entities for DeSoto Challenge, I am at 2448 in my pursuit for 2500 award. I have attempted to rebuild Alert database. There does not appear to be a choice that specifically looks for Wanted DXCC by individual band.  I am not sure that "Wanted DXCC" choice accomplishes my need.  I am at the top of DXCC Honor Roll already and trying to focus on missing entities by band.  Is there an Alert rebuild that accomplishes my search?  I have not seen any alert in a long time which makes me suspicious that Wanted DXCC accomplishes my wish.

Jim K7EG

I'm not being asked for 2-factor auth. But Google will want you to "enable less secure applications" I think. I've got this same scenario with a few apps.

Seth

Thanks Laurie, yes you did. At the time enabling logging made me loose my worked B4 data (because I couldn't select the WSJT-X ADIF file and you loose the ability to select a worked B4 database.
Since I don't use any other logging software it was a bit hard to point JTAlert to a populated ADIF file because I only use WSJT-X and you can't use that file for JTAlert logging. I had to figure out that I had to make my own ADIF up from a copy the WSJT-X ADIF file to enable JTAlert to log and also have the worked B4 data.
All sorted now, am very happy to have the software now all working as it's intended.
It's great software!
Cheers, Mark VK3BU

Thanks Rob, I just fixed the problem then before I read your post unfortunately, ... would have saved me some time. Yes that was the problem. I'm only using WSJT-X, JTAlert and QRZ.com at the moment, no other logging software. Everything was working well except for the QRZ issue and the "Show QSO's History" popup not populating with data, but with JTAlert all good as far as worked B4 stations apart from that.
I was using the WSJT-X ADIF file as the worked B4 database file (loading it once initially) and I hadn't enabled Standard ADIF File Logging because I didn't have any other ADIF file to use other than the WSJT-X ADIF file and you can't use that. I ended making a copy of the WSJT-X ADIF file and JTAlert is now using that for both logging and worked B4 data. Both the WSJT-X ADIF file and the JTAlert ADIF files are now being updated when I make a contact.
On making that change, i.e. enabling standard ADIF file logging and making a log file for JTAlert to use, QRZ.com XML data works and the "Show QSO's History" popup is fully populated with data.
Thank you all for your help and suggestions.
Cheers, Mark VK3BU

I did point out in this message posted a week ago, the first bullet point, that no QSO History could be due to not having a logger enabled in JTAlert

de Laurie VK3AMA

Thanks Rob, I just fixed the problem then before I read your post unfortunately, ... would have saved me some time. Yes that was the problem. I'm only using WSJT-X, JTAlert and QRZ.com at the moment, no other logging software. Everything was working well except for the QRZ issue and the "Show QSO's History" popup not populating with data, but with JTAlert all good as far as worked B4 stations apart from that.
I was using the WSJT-X ADIF file as the worked B4 database file (loading it once initially) and I hadn't enabled Standard ADIF File Logging because I didn't have any other ADIF file to use other than the WSJT-X ADIF file and you can't use that. I ended making a copy of the WSJT-X ADIF file and JTAlert is now using that for both logging and worked B4 data. Both the WSJT-X ADIF file and the JTAlert ADIF files are now being updated when I make a contact.
On making that change, i.e. enabling standard ADIF file logging and making a log file for JTAlert to use, QRZ.com XML data works and the "Show QSO's History" popup is fully populated with data.
Thank you all for your help and suggestions.
Cheers, Mark VK3BU

Thanks guys. Yes I meant QRZ.COM, ... I shouldn't post when I'm tired!
QRZ still isn't showing QSO's that are being confirmed in WSJT-X this morning, so I guess I must have a problem my end since it's been over 8 hours since I paid the QRZ subscription.
I just turned off Norton and Malwarebytes and still no luck.
I have enabled QRZ.com under Web Services>Online Logbooks and entered my API Key.
I'll now have a bit of a search in the forums to see if anyone else has had this problem.
Thanks for your suggestions.
Cheers, Mark VK3BU

Thanks Dave, yes I did mean QRZ.COM, that's what happens when I post too late at night. Yes the commercial transaction went through quite quickly. It's been 15 hours since then, so the XML functionality should be up and running by now one would think. I just have to log a contact this morning to test it out. No propagation at the moment though, ... frustrating!
Cheers, Mark VK3BU

The QRZ.com key is under "my Logbook", "settings"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, wsjtx-2.5.2-win64_improved_widescreen+MAP65-3.0.0.exe, JTAlert 2.50.7, HRD Deluxe v6.7.0.391
FTdx-3000, SignaLink USB

Google forced it on November 9th for all "free" accounts, at least here in the USA.  I have three of them and they all went on 11/9/2021.  Thanks for the info on setting up the app password, that is probably the solution and I'll give it a try!

After you enter your password, you’ll complete a second step on your phone. Keep your phone nearby when you sign in.

2-Step Verification will be turned on automatically on November 9. You can turn this on sooner if you want — your account is all set.

On 22/11/2021 15:06, Brian wrote:

FYI when Google forced TFA on for free accounts on Nov 9, my email alerts stopped working (using swithmail).

I did find I could go in to Google account settings and turn two-factor back off, and alerts started working again.

I even tried signing in on that PC with a browser with TFA and made sure remember this device was checked, but I think that is just a browser cookie and did not work for swithmail.

Anyone else have this issue, and anyone know how to manage a TFA sign-in from the command line (alert.bat) with swithmail?

thanks

Brian N3OC

Brian,

TFA on Google accounts was not enforced, just recommended with a nag message.

With TFA enabled, for external applications that do not use the "Login with Google" facility, you must set up an "App password" for the host and application pair that you wish to authenticate for access to Google Mail. That 16 character password that is generated can then be used for authentication on the smtp.gmail.com servers with your gmail account id instead of the Google account password you used before enabling TFA.

Note that this also avoids the need to enable "less secure access" in your Google account.



--
73
Bill
G4WJS.