|
I GOT A MESSAGE THAT I WAS REPORT THE WRONG BAND. I WENT TO HAMSPOTS UNDER FT8 AND MADE THE CORRECTION. I HAVE HAMSPOTS CHECK TO SEND SPOTS. BUT WHEN I CHECK 40M FT8 I AM NOT SEEING ANY OF MY SPOTS POSTED OR MY CALL SPOTTED.
WHAT AM I DOING WRONG?? -- 73 NU4N Dave
|
|
|
|
locked
Re: Wanted States Alert
Jim N6VH
On 11/26/2021 5:03 AM, Jim Austin wrote:
General Wanted States question:Jim, There was a defect in Log4OM 2.17 (and possibly earlier). When a QSO was confirmed by LOTW, and the state was WV, Log4OM changed the state to VA. This has been corrected in Log4OM 2.18, so it would be helpful to do the upgrade. Once you do that, you can either: 1. Go through your log and change each incorrect state to WV. One way to do this is to use a filter in Log4OM QSO Manager. Filter for "State EQUAL VA" and "Cnty LIKE_STARTING_WITH WV. This should show all the WV QSOs that were confirmed by LOTW, but the state was changed to "VA" Then, still in the QSO Manager, select all of those QSOs. Since the QSOs listed should all be the ones with an incorrect state, click Select/deselect near the lower left of the QSO Manager. Then, just go to Single Field Update. In the "Field to update" box, select "State". In "New value", enter "WV". Then click "Update". That should do the trick. 2. The other method, and less complicated, is to use the Log4OM QSL Manager. Once set to LOTW, and you are in the "Download confirmations" screen, click "Date range". Set the "QSO from" date to the earliest date you need. Set the "QSO to" date to the latest date you need - even using the current date will be fine. The do the download. This should change every incorrect state to the correct one. You might want to check a few QSOs, just to be certain. After doing either "1" or "2", do a "Rebuild Alert Database" in JTAlert. Everything should work correctly now. Hope this helps. 73, Jim N6VH
|
|
|
|
locked
Re: Wanted States Alert
Michael Black
You'll find you should do a complete LOTW download too to update all your old WV QSOs. Mike W9MDB
On Friday, November 26, 2021, 10:10:58 AM CST, Jim Austin <w4kcm1@...> wrote:
Thanks Mike. All good to go... The original file had WV as WVR 73 General Wanted States question: Regards, Jim
|
|
|
|
locked
Continent decode off but still alerting
Michael Black
Seems when you turn off continent decoding for any continents you still get dxcc alerts even though the decodes aren't showing up in the Callsigns window. They still show up in the decodes window as expected. Mike W9MDB
|
|
|
|
John
I wish more hams would make the effort to use ANY QSL service, I use the log at QRZ.com, eQSL and LOTW and others as well. John VE7KKQ
On Fri, Nov 26, 2021 at 7:22 AM Robert Ahrens <robertahrens52@...> wrote:
|
|
|
|
locked
Re: Wanted States Alert
Jim Austin
Thanks Mike. All good to go... The original file had WV as WVR 73
General Wanted States question: --
Regards, Jim
|
|
|
|
locked
JTAlert has stopped remembering logging s\ware, docking posn etc
geoff wiggins
Hi group.
I went to use JTAlert today and find that NO LOG is shown in the tool bar along side [20m,FT8 NO LOG,#1]. Also cannot dock the window any more, always defaults to independent position. I select LOG4OM2, select sqlite file etc etc, save then ok. JTAlert doesn't remember these settings. My locator, ITU zone, CQ zone and locator are also no longer remembered. I thought this might have been an issue with version 2.50.8 but doesn't appear to be so since I've gone back to version .7 and the same errors occur. Apart from completely uninstalling every file and starting again, any ideas please? Could this be something to do with Win 11? I doubt it but then........ 73 Geoff.
|
|
|
|
locked
Problem with JTalert 2.50.8
Hello,
Since auto installation of JTalert 2.50.8, and update of windows desktop runtime 5.0.12
win 64 i have an error message which appears.
I have been using JTA for a long time, this is the first time this has happened.
My setup;
Je signale que la version 2.50.7 fonctionne bien sans aucun problème.
Il n’y a que moi ou quelqu’un qui a cela.
How is the solution.
Thanks 73
|
|
|
|
Robert Ahrens
It worked better with the longer cycle times of jt65. I don't use it as much as I used to, but you will always find me online. I am more bothered by the dx ops who still require qsl by mail. I would much rather via LoTW. I don't even mind paying the $5 OQRS fees. Still feels less expensive than the 3 green stamps, an envelope, an SASE, a qsl card, and a trip to the post office. My hobby is radio, not stuffing envelopes. Getting off of my soapbox now... 73 de NT5A - Bob
On Fri, Nov 26, 2021, 06:26 Joe Subich, W4TV <lists@...> wrote:
|
|
|
|
Joe Subich, W4TV
If I wanted to send a message I would use my cellphone or CW.
toggle quoted messageShow quoted text
73, ... Joe, W4TV
On 2021-11-26 7:05 AM, Dave Tucker Nu4N wrote:
I WISH MORE PEOPLE WOULD USE THE MESSAGE FEATURE. I LIKE TO EXCHANGE COMMENTS WITH THE STN'S I WORK.
|
|
|
|
Same here Dave, de VE2EDM
Le ven. 26 nov. 2021 à 08:47, Storm, PG5FRL <pg5frl@...> a écrit :
|
|
|
|
locked
Re: Wanted States Alert
Michael Black
Replace the states.csv in C:\Users\[username]\AppData\Roaming\Log4OM with this one Mike W9MDB
On Friday, November 26, 2021, 07:03:45 AM CST, Jim Austin <w4kcm1@...> wrote:
General Wanted States question: Win 7 SP2 WSJT - V2.4.0 JTAlert 2.50.6 LOG4OM 2 V 2.17.0.0 WAS confirmed via LOTW on 80,40,30,20,17,15,12, and 10 meters. Several times a day I receive an alert for WV as a wanted state. I have cleared the state several times in the wanted /unwanted state settings of JTAlert. However, when I rebuild the JTAlert Alert database, the alert will return. This happens on several bands. At present, it occurs on 80, 40, 30, 20, 17, 12, and 10 meters but not on 15. So is this issue within the JT Alert program or all tied to the OSO/QSL database? It's not a major problem but any hints would be appreciated. 73's W4KCM Jim
|
|
|
|
Storm, PG5FRL
I almost always use that function. Comments are always welcome! Op 26-11-2021 om 13:05 schreef Dave
Tucker Nu4N:
I WISH MORE PEOPLE WOULD USE THE MESSAGE FEATURE. I LIKE TO EXCHANGE COMMENTS WITH THE STN'S I WORK.
|
|
|
|
locked
Wanted States Alert
Jim Austin
General Wanted States question:
Win 7 SP2 WSJT - V2.4.0 JTAlert 2.50.6 LOG4OM 2 V 2.17.0.0 WAS confirmed via LOTW on 80,40,30,20,17,15,12, and 10 meters. Several times a day I receive an alert for WV as a wanted state. I have cleared the state several times in the wanted /unwanted state settings of JTAlert. However, when I rebuild the JTAlert Alert database, the alert will return. This happens on several bands. At present, it occurs on 80, 40, 30, 20, 17, 12, and 10 meters but not on 15. So is this issue within the JT Alert program or all tied to the OSO/QSL database? It's not a major problem but any hints would be appreciated. 73's W4KCM Jim
|
|
|
|
I wish more people would use LoTW. I like exchanging confirmations with the stations I work.
Just a thought.
My point is, we cannot dictate what hams use or don't use. Many see the message feature as a pain.
No different than some feel 'setting up LoTW' is a pain.
Jose
N4BAA
-----Original Message-----
From: Dave Tucker Nu4N <dwtucker19@...> To: Support@HamApps.groups.io Sent: Fri, Nov 26, 2021 7:05 am Subject: [HamApps] MESSAGE #FT8 I WISH MORE PEOPLE WOULD USE THE MESSAGE FEATURE. I LIKE TO EXCHANGE COMMENTS WITH THE STN'S I WORK.
JUST A THOUGHT. -- 73 NU4N Dave
|
|
|
|
I WISH MORE PEOPLE WOULD USE THE MESSAGE FEATURE. I LIKE TO EXCHANGE COMMENTS WITH THE STN'S I WORK.
JUST A THOUGHT. -- 73 NU4N Dave
|
|
|
|
locked
Re: 2.50.8 Defender
After a bit of back and forth with Malwarebytes, all issues have now been resolved.
|
|
|
|
locked
Re: 2.50.8 Defender
Have submitted a false positive report to Malwarebytes
|
|
|
|
locked
Re: JT Alert 2.50.0 - Win 10 - Call signs window blank
Joe, AF6G
Mike,
Sharp eye! Yes, the address was set incorrectly by me. Changed it to 224.0.0.1 and it now things work. Also, page now shows both the WSJT-X UDP multicast on loop back settings menu & the outgoing interfaces options. Problem solved. Thanks! Joe
|
|
|
|
locked
Re: Windows 11
Tim Reimers KA4LFP
"an in-place OS upgrade on a computer that's older than 3 years old is a complete waste of time and effort"
"Bravo! I am glad somebody finally said this" I don't know that I would go so far as 3 years. And I work in IT professionally, in a large enterprise org. 5 years is probably more the limit and is considered the replacement cycle lifetime for most desktop hardware. That said the jump from windows 7 to Windows 10 made a lot more older computers more usable. Almost everything I own was originally windows 7, and is now 5 to 8 years old. and and when I upgraded it to Windows 10, essentially got a new life since 10 is much better written at its kernel level.. Most folks I have heard complaining about Windows 10 either do not run their systems properly or have hardware far older than that that they want to work Windows 10 with.
|
|
|