Obviously, I had a misunderstanding of how the Reply message worked. Thanks
for straitening me out.
73, Steve K5FR
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Thursday, November 2, 2017 06:46 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] UDP Reply Message
On 02/11/2017 23:22, Steve Nance wrote:
I now need to use the acknowledgement message from the message #4 I
send to WSJT. However, I’m not receiving anything back from WSJT. I
have the 3 checkboxes on the Setup|Reporting|UDP Server group
selected. Am I missing something else? All the other mess
Bill, et.al,
I now need to use the acknowledgement message from the message #4 I send to
WSJT. However, I'm not receiving anything back from WSJT. I have the 3
checkboxes on the Setup|Reporting|UDP Server group selected. Am I missing
something else? All the other messages are decoding correctly.
On 02/11/2017 02:01 p.m., Ervin Hegedüs wrote:
I confirm this bug - until the Debian package test, I also had
this problem.
I have also seen this happen from time to time on my XP64 platform. I
attributed it to ancient, potentially unstable hardware, but maybe not.
When this happens to me,
hi folks,
On Thu, Nov 02, 2017 at 06:38:12PM +, Mac wrote:
> Dear developers !
> As I did not read any other posting dealing with this subject I assume that
> I am the only one having this problem.
I confirm this bug - until the Debian package test, I also had
this problem.
73, Ervin
HA2OS
Dear developers !
As I did not read any other posting dealing with this subject I assume
that I am the only one having this problem.
Randomly the waterfall freezes in my configuration (Win7 64bit,
JT-Alert-X, IC-7600 via USB-cable, Rig-Control via HRD).
Sometimes it runs for an hour or so but
Here's a patch that fixes this problem.
https://www.dropbox.com/s/rgxjefm3nsuwnpv/bandchanged.patch?dl=1
de Mike W9MDB
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.or
I guess you could call it a bug.
I am able to reproduce this behavior. I'll look at the code and see how
feasible this is to fix.
de Mike W9MDB
On Thursday, November 2, 2017, 11:58:56 AM CDT, DG2YCB, Uwe
wrote:
Hi,
I am using WSJT-X v1.8.0 r8193 together with my Yaesu FT-991 conne
Hi,
I am using WSJT-X v1.8.0 r8193 together with my Yaesu FT-991 connected to my
PC via USB cable (CAT control via COM5, PTT via COM7). As my FT-991 seems to
need different audio power levels at different bands, I've checked the
"Transmit" checkbox for "Remember power settings by bands". Everythi
Hi folks,
I've made a new package for Debian (SID). I'm not a wsjtx expert,
so I would welcome that anybody could help me to test it.
Important: this package works only on Debian SID (amd64 arch),
as I know, the other Debian derivated systems (Ubuntu, Mint, ...)
doesn't contains the dependent lib
I did see that. I guess at some point it will be opened back up after further
Fox/hound work?
Sent from my iPad
> On Nov 2, 2017, at 4:22 AM, Richard Lamont wrote:
>
>> On 02/11/17 11:13, Gary Rogers wrote:
>>
>> I tried to build a couple of nights ago and got the message that 1.7.1 was
>> n
On 02/11/17 11:13, Gary Rogers wrote:
> I tried to build a couple of nights ago and got the message that 1.7.1 was
> not ready for on air use after I built it. After clicking the ok I got a
> fatal error message. Is this related?
No. See Joe Taylor's post to this list of Oct 29, headed "Don't u
And it told me to use 1.8.0.
Sent from my iPad
> On Nov 1, 2017, at 10:47 PM, Greg Beam wrote:
>
> Hi Mike,
>
> Try cleaning your build tree / cache. ft8_params.f90 was in fsk4hf, but, I
> believe Steve moved some things around not long ago. It’s now in lib/ft8 and
> builds OK here @8207,
I tried to build a couple of nights ago and got the message that 1.7.1 was not
ready for on air use after I built it. After clicking the ok I got a fatal
error message. Is this related?
Sent from my iPad
> On Nov 1, 2017, at 10:47 PM, Greg Beam wrote:
>
> Hi Mike,
>
> Try cleaning your buil
14 matches
Mail list logo
