The issue is not that the program threw an error code. Of course
it should throw an error. The issue is that it didn't exit
cleanly and was hung and unresponsive on the computer at least
15 minutes later when I used force quit to blow it away.
73 Bill AE6JV
On 5/3/21 at 6:45 AM,
To put Gary’s response another way: Imagine you’re taking to someone standing
on front of you and, mid-conversation, the person to whom you’re speaking
suddenly disappears without a trace. I think you’d throw an error code, too. :)
Jim S.
N2ADV
> On May 3, 2021, at 12:32 AM, Gary McDuffie
> On May 2, 2021, at 8:28 PM, Bill Frantz wrote:
>
> I had been operating FT8 on 15M and 40M. I powered down my K3 (upgraded with
> the internal sound card) and got the "Rig Control Error" message.
This is normal for every computer I’ve had. That’s the error message when the
port goes away
wsjt-x hung -- not responding
I had been operating FT8 on 15M and 40M. I powered down my K3
(upgraded with the internal sound card) and got the "Rig Control
Error" message. I think I clicked "Cancel", closed the lid on my
MacBook Pro and took the computer back to my apartment. When I
got
