Yes, and so are the #2 and #3 issues that Bob raised. They are both bad operating practice and bad manners. I disagree about #1 -- there are (at least) 100,000 QSOs in my log without a grid as part of

Carey, No, I want EVERYONE to have a QSO with me 24/7. But, when I post to a Ham Radio Group, I always include my Name/Call so everyone knows who I am. That's called good manners. GL/73, Bob

GM0PJD - I'm also running a TS-2000 here and had the same "No Audio" problem after I updated both Windows10 and WSJT in the same session. Microsoft pushed out yet another update about the same day

AL1VE's currently (2020-06-21) active on 6m FT8 from the DN47/48 line. He was in DN73 and DN75 last week too. He's not on LoTW yet, but plans to get it set up when he gets back home. 73, ~iain

>It's too bad the logic is set up to detect the "73" string instead of just whether TX4 is being sent, as I've pointed out in a similar parallel thread on this forum. This way, I can't send my 73 and

Marlo, As mentioned previously, all the settings, logs, and so on are kept completely separate from the WSJT directory tree.  Even if the uninstallers take out the v2.2.1 directory, a simple

Correct- I'm just wanting to clean up Windows 10's installed Applications which lists many versions of WSJT-X. I am running WSJT-X V2.2.1 and want that to stay. However, it appears that there is

I have in the past. However, I have been supporting serial interface products for 15+ years and multiple generations of Elecraft, Kenwood, Icom, TenTec and Yaesu transceivers. See:

Thanks Bill, that got me there. A shaking fist at ms - damn those fools! Really curious... First that it is not triggering a failure message on windows or in the device manager! That's just

Sorry for the broken link. Reino’s link is OK. It seems that Microsoft has been aware of the audio bug since April. In spite of that they made a general release, including the bug, of 2004.

I mainly run Ubuntu Linux and my TS590SG,but my backup rig is my older IC746PRO, RIGblaster, and everything works justfine using the latest version of Windows 10. I am glad the USB cablereinstalled

I was able to duplicate the issue with FT4 mode not dupe checking correctly. I have corrected the issue and it will be in the next build before Field Day. This only effected FT4 mode. 73 Rick

Pet peeves are bad for your health. I have a pet cat. Her name is Sally. She frequently makes me laugh. I also try not to have high expectations. That way I am more often pleasantly surprised. Life

I just did another test to change TX4 from RR73 to RRR and find in that case, the TX will remain enabled and stick on TX4 until receiving the final "73" as TX5 from the remote. After receiving that

FIXED: I uninstalled the USB Audio Codec, disconnected the USB and then reconnected. Now working. You guys have me nervous to install the 2004 Windows 10 update. Maybe after Field Day. Thanks.

Wow, you sure have a lot of pet peeves! Do you have a list of rules people should use when contacting you? -- 73, Carey, WB4HXE

Hi Got a strange logging error with the start time of a QSO. We definitely didn't start the QSO at 12:45 I did a look in All.txt and AB4IQ answered my CQ at 13:16.

John, that's Microsoft's fault with their funky URL scheme. Try this: https://docs.microsoft.com/en-us/windows/win32/debug/error-handling You will have to

Hi Greg, I suspected that you were only getting Rx audio via the built in mic. You still could have a hardware issue with the line-in/mic socket, but given the coincidence with a Windows Update there

Bill: Agreed that "the built in mic should be disabled when you plug in something to the line in, or combined line in/mic socket. If your mic is live then I would check that the plug is correctly