On 03/22/2018 01:31 AM, Palle Preben-Hansen, OZ1RH wrote:
Hi Palle & all,
> I suggest a feature so WSJT-X in DXpedition mode can't TX on the
> 'standard' frequencies.
Like the protection of the WSPR frequency areas ? I approve this
proposal. This seems to be a reasonable choice because the verba
Wed, 21 Mar 2018 18:26:25 -0700
Jim Brown kirjoitti:
> On 3/21/2018 3:16 PM, Ray Jacobs wrote:
> > You were right they were on the same frequency as regular ft 8
> > instead of another frequency, somehow they will have to announce
> > what frequency they are on. But how do they get the word out?
Wed, 21 Mar 2018 18:00:38 -0400
"James Shaver" kirjoitti:
> And the “normal” 17 meter frequency as well with the same results…
I was on 17m calling too... Twice got report, but never rr73.
Saw that happened some others too. Think we all need much more
practice, so fox as hounds
Jarmo
On 3/21/2018 3:16 PM, Ray Jacobs wrote:
You were right they were on the same frequency as regular ft 8 instead
of another frequency, somehow they will have to announce what
frequency they are on. But how do they get the word out?
The DX Cluster system.
73, Jim K9YC
-
Date: Wed, 21 Mar 2018 18:16:39 -0400
From: Ray Jacobs
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Ft 8 in Exhibition Mode
Message-ID: <1624aa2adf3-c88-c...@webjas-vae058.srv.aolmail.net>
Content-Type: text/plain; charset="utf-8"
You were right they were on the same frequency as r
New theory on this one, I think it may be occurring more (if not exclusively)
when I am operating remotely using TeamViewer, something I’ve done without
incident through several versions… Not sure if this bears any resemblance to
your scenario?
Jason.
From: Gene H
Sent: 21 March 2018 14:06
To
You were right they were on the same frequency as regular ft 8 instead of
another frequency, somehow they will have to announce what frequency they are
on. But how do they get the word out?
Sent from AOL Mobile Mail--
Ch
And the “normal” 17 meter frequency as well with the same results…
From: James Shaver [mailto:n2...@windstream.net]
Sent: Wednesday, March 21, 2018 5:59 PM
To: 'WSJT software development'
Subject: RE: [wsjt-devel] Split mode ft 8
Unfortunately, they’re using the DXPedition mode on the “no
Unfortunately, they’re using the DXPedition mode on the “normal” 15 meter
frequency and ops are inadvertently stomping all over several QSO’s in
progress. I witnessed several busted contacts and had a few myself as a
result.
From: Ray Jacobs [mailto:rjacobs...@verizon.net]
Sent: Wednesday
Just worked PJ-5/SP9FIH in the hound mode! Tuned up past 1000 he was on 274 .
Now I put my rig on fake it. The program says it advised me it should be in dx
exbition mode!
So it worked for me and others no problem.
Sent from AOL Mobile Mail---
Good Evening
While I am able to received and decode all the messages that come out of
WSJT-X via UDP, I have some difficulties to get WSJT-X client to accept
the server type 4 messages.
I have checked in the settings all 3checkboxes "Accept UDP requests",
"Notify on accepted UDP request", "
The multiple optional boxes on the main window cause the initial geometry
restore to not be able to minimize completely.
So if you minimize the window width, quit and restart wsjt-x, it resizes to a
notably larger width unnecessarily.
This patch solves most of the problem...perhaps there's anoth
For what it is worth, I am seeing the same issue on two different
Windows 7 64-bit computers running the new 1.9 rc3. Never saw this on
prior versions of any WSJT since inception.
I tried to connect CAT directly through the WSJT program and also
through HRD program and had same results. Also h
- Original Message -
>
>
> - Original Message -
> >
> >
> > - Original Message -
> > > The gcc reponse to this problem is "not a bug" since the standard
> > > requires
> > > len=1 as the only valid thing for type c_char in the iso_c_binding
> > > The FORTRAN group respon
Hi Doug,
We should probably take all this off line, but, the cdimage-daily-live image is
definitely showing 7.3, where the package system is showing 7.2 … why, I do not
know. How apt show is rendering 7.2 and gcc -v shoeing 7.3 is another good
question.
>From the 18.04 daily-live manife
Hi Doug,
I’m tied up the next couple days, but after, I’ll pull a new ISO and see if I
can decipher what going on there. You may want to try:
apt-cache policy gcc
Maybe there are multiple versions installed and they are using alternatives or
something along those lines. The repo def
16 matches
Mail list logo
