[wsjt-devel] Proposing Fox & Hound Operation on 1810kHz for A35JT - can JA access direct?

Folks, I am proposing to use a somewhat unorthodox frequency for F/H mode on 160m from Tonga in September in order to allow both JA and the rest of the world to call us in F/H mode. My current thinking is to use 1810kHz dial (USB). This means that the fox transmissions will be between

Re: [wsjt-devel] Error in Sound Output Message

Microsoft will force you to update whenever they see fit It's their thing. One of the myriad of reasons why I run Linux at home for nearly everything. 73 de AI8W, Chris On Sat, Apr 6, 2019 at 11:53 AM August Treubig wrote: > That is an indication of RFI issues. Grounding and moving things

Re: [wsjt-devel] Debian install comes up V1.1

On 07/04/2019 00:23, G8DQX (WSJT developers on SF) wrote: *3)* Thus we conclude that though you *thought* that the downloaded *wsjtx_2.0.1_amd64.deb* package had been installed, it had *not* been. Robin, that may not be correct, more likely it did install into /usr/local, which is correct,

Re: [wsjt-devel] Debian install comes up V1.1

Glen, after a rapid forensic analysis it appears that: *1)* you're running Ubuntu, or some variant of it, such as Mint [that information is important for debugging, especially when it's other people helping one!] *2)* *version 1.1 is the default version* in the *Ubuntu

Re: [wsjt-devel] Debian install comes up V1.1

On 06/04/2019 23:00, Glen Brown wrote: New to Linux here, but downloaded the file named wsjtx_2.0.1_amd64.deb  and installed it.  Runs great, but it's version 1.1 - from before FT8. Did I miss something? Glen W6GJB Hi Glen, I

[wsjt-devel] Debian install comes up V1.1

New to Linux here, but downloaded the file named wsjtx_2.0.1_amd64.deb and installed it. Runs great, but it's version 1.1 - from before FT8. Did I miss something? Glen W6GJB ___

Re: [wsjt-devel] Error in Sound Output Message

That is an indication of RFI issues. Grounding and moving things around can help. Aug AG5AT Sent from my iPad > On Apr 6, 2019, at 9:35 AM, Bill Somerville wrote: > >> On 06/04/2019 15:30, Richard Solomon wrote: >> Everything was working fine yesterday, turned the rig on tday, tried to call

Re: [wsjt-devel] Error in Sound Output Message

Says USB Audio Codec and that it's working. I re-booted the computer and it now seems to work, but this is the second time I have had this issue. The previous time was about a week ago. Up until these two incidents, everything worked fine ever since I upgraded to Ver. 2.0 and then 2.0.1. That's

Re: [wsjt-devel] Bug: transmit watchdog timeout leads to receiving own message

On Fri, 2019-04-05 at 20:16 +0200, Christoph Berg wrote: > > > IIRC this fake transmission appeared in the waterfall window, > > > also. It > > > seems like the audio output was being looped back into the > > > decoder. > > Not sure about that part, but I remember being fairly certain that > the

Re: [wsjt-devel] Error in Sound Output Message

Check your Device Mangler for your sound card. It’s working? 73 de W8NET Miles / “Gene” Secretary, Portage County Amateur Radio Service (PCARS) 3905 Century Club - Master #47 Licensed since 1974 > On Apr 6, 2019, at 10:37 AM, Richard Solomon wrote: > > One more thing I noticed. The waterfall

Re: [wsjt-devel] Error in Sound Output Message

One more thing I noticed. The waterfall shows no signals and the receive strength meter (vertical meter on left) is blank. Looks like no signal getting to FT8 ??? A Microsoft update issue ?? 73, Dick, W1KSZ Sent from Outlook From:

Re: [wsjt-devel] Error in Sound Output Message

On 06/04/2019 15:30, Richard Solomon wrote: Everything was working fine yesterday, turned the rig on tday, tried to call a station, Transmit was aborted about 1-2 seconds into the call. This error message popped up: Any idea on the cause ? Tnx, Dick, W1KSZ Hi Dick, two possible causes

[wsjt-devel] Error in Sound Output Message

Everything was working fine yesterday, turned the rig on tday, tried to call a station, Transmit was aborted about 1-2 seconds into the call. This error message popped up: [cid:b5548389-7bda-4cc5-8ef8-073d197cddd3] Any idea on the cause ? Tnx, Dick, W1KSZ Sent from