开云体育

Please ignore the message from Steve K8JQ below. I was hunting for a message from 2014, inadvertently reversed the chronological order in my message display, and then mistook Steve's messages for a

Steve, this is a quote fragment of your original message taken form groups.io web page: and this is a quote of the above Dave's reply always taken from groups.io web page: Are you sure that date

+ AA6YQ comments below 1. In TQSL's Main window, 1a . how many "Callsign Certificates" are displayed on the "Callsign Certificates" tab? —-one 1b. how many "Station Locations" are displayed on

1. In TQSL's Main window, 1a . how many "Callsign Certificates" are displayed on the "Callsign Certificates" tab? —-one 1b. how many "Station Locations" are displayed on the "Station Locations"

+ AA6YQ comments below + First, some questions: 1. In TQSL's Main window, 1a . how many "Callsign Certificates" are displayed on the "Callsign Certificates" tab? 1b. how many "Station Locations"

I’ve used DXlab for many years with zero issues. Today, when trying ?to upload to LOTW, I get a pop up stating “ no QSO’ whose LOTW QSL sent items are set to R and station calling items set to

+ AA6YQ comments below + Yes, an ARRL section that is inconsistent with its QSO's State and County will result in a QSO being considered Broken. + To get a full report of all broken QSOs, click the

That's a hard one from my QTH. Short path mostly across the north pole makes it tough. I have worked them short path on 17 meters Superfox Hound mode. I think that was with 100 watts. I see FT8 spots

Unfortunately the first spot is not CW but FT8. The rest of the times are not good for prop to NA. Paul, W6IBU

Hi Joe, I figured that out and changed the country to fix the broken Qs for KH6 call signs. Now I see that there are many others where there is no clear indication why they are "broken."

They were loud on 12M CW (and 17M SSB) this morning (1300Z). He called for NA and worked NA but I heard a lot of EU calling on 12M CW. Several NA worked on 17M about the same time but not a

+ AA6YQ comments below + If the current version of SpotCollector encounters "FH", "F/H", or "FOX" in spot notes, it sets the Spot Database Entry's Mode to FT8. + In the next version of

+ AA6YQ comments below + 10m CW operations over the last 24 hours? from 4 DX Clusters and DX Summit: Call ? DXCCCountry ? ? ? Freq ? ? ?Mode ?First? ? ? ? ? ? ?Last? ? ? ? ? ?

Bill, seems like they like to work the other side of the pond, but here are some spots from the States.. (has been a few days though) | KN9K-@ | 28033.0 | VK9XU | 02:35 21 Feb |

Bill this is a VERY small clip from DXSUMMIT.FI. You have been missing them. | W1PLSE-@ | 28000.0 | VK9XU | 14:57 24 Feb | plus 10m cw for NA now | Christmas Island | |

Now that WSJT-X has a new FT8 mode, SuperFox it might be useful if Spot Collector recognized SFH or S/FH or similar in a spot's notes as an FT8 mode to override the subband mode as it already does for

You will have to do setup from scratch if you have no Workspace backup. If you have even an old Workspace backup you may be able to use it if a lot of settings you may never or seldom change anyway to

Has anybody heard when they will be on 10m CW? Or is it wait and see? -- Bill W5EC

Are you installing on a fresh copy of Windows (or a copy with a fresh registry due to a Windows reset)? If so, follow the recommendations here:

Greetings from Athens! I have in my backup a copy of the whole DXLAB folder. How can I restore DXKEEPER setup from it? Unfortunately I don't have a latest & greatest registry backup from DXLAB. 73 de