Thank you Mike. That did the trick! Best, Ed 73 de W2LCQ, Ed Jones Frankford Radio Club BUG 204 - CWops 701 (Life) - SKCC 5474T - FISTS 12294 - QCWA 33438 - LICWC 51 - ARRL (NLI) - DXCC “The present

You may have "Require Edit to modify logged QSOs" checked on the General tab of the config window. If this is turned on (generally a wise decision), you need to click the edit button just above the

I sent a QSL card to a QSO partner and tried to mark the sent QSL in the QSL Panel of the log display (pardon if I’m not using the proper terminology) but it would not let me enter a “Y” or the

Yesterday I suffered a complete and fatal crash of my computer due to the combination of a chinese parallel port PCI card, which obviously lies about being WHQL, and a Windows update. Thankfully, I

Norm Do you leave your computer on continuously ?  If so power down and start back up and see if the problem goes away. Also you can use windows TASK MANAGER to what programs are using the most

MS WIN 10 AUGUST UPGRADE MESSED WITH MY COM PORT ASSIGNMENTS INEXCUSABLE. ALL IS FIXED JIM

I posted this to our local club's FB page. It's WSJT-X, not JTDX, and further, it's very like that my problem was different than the problem you are having -- unless your disk space is also very low

+ AA6YQ comments below + Have you configured your anti-malware applications to consider each of your DXLab applications to be "safe"? + How many entries are present in your Spot Database? + Have

My computer has slowed down after about 3 weeks of moving to dxlabs from HRD. I almost always use with JTDX. When selecting a new station to call, it takes several seconds for the call to show up in

+ AA6YQ comments below + Presumably N1MM depends on the same PTT interface for COM13 that WinWarbler and MMTTY do. Check the settings on the PTT tab of WinWarbler's Configuration window. 73,

It can't be broken port or cable issue: Com 11 N1MM uses this port without issue for RADIO Com 12 DXL Commander or WSJT use this port without issue Com 13 N1MM uses this port for CW/PTT without

+ AA6YQ comments below Ahh, this might explain a phenomenon I see often of late, where SpotCollector displays a clump of CW spots at traditionally FT8 frequencies. They are well and truly FT8 spots,

Ahh, this might explain a phenomenon I see often of late, where SpotCollector displays a clump of CW spots at traditionally FT8 frequencies. They are well and truly FT8 spots, just (presumably

Thanks, Dave Appreciate the additional information and will follow up.

* more AA6YQ comments below + To ensure that your outgoing spot is accurately interpreted when it arrives from one or more of your spot sources, specify the mode in the outgoing spot's notes. This is

+ AA6YQ comments below I did all the w4tv steps to prevent powering down a USB port. No change in Device Manager ports Yes, I did an Win 10 update in early August. I have not been active during

Thanks, Dave will do from now on. I was just confused because the popup menu referenced FT8 in the line I selected so I did not think I had to include in the notes but will be specific going forward.

Thanks reply Dave I did all the w4tv steps to prevent powering down a USB port. No change in Device Manager ports Yes, I did an Win 10 update in early August. I have not been active during August

+ AA6YQ comments below Occasionally I will spot QSOs in Spotcollector but recently I spotted two FT8 QSOs and one showed up as RTTY and the other as CW when both were FT8. I right-clicked each time

+ AA6YQ comments below + Which functions have stopped working? + Did you check for loose connectors? + Did you check for Windows powering down a serial