Double-clicking does not work on a message when the 1st call is an empty hash.
e.g.<...> W9MDB R-17
Does work OK as long as the hash tags contain a callsign on either call.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
> kern.sysv.shmall: 8129
For what it's worth, that value looks like a typo - it probably ought to be
8192, a power of 2.
> On Dec 20, 2018, at 20:13, Jim Kennedy wrote:
>
> kern.sysv.shmall: 8129
___
wsjt-devel mailing list
> A couple of weeks ago, I upgraded the Mac OS to the Mojave 10.14.2, but
> ever since first doing that, both WSJT X 1.9 and 2.0 don’t survive
> launching. Both behave in the very same way.
Hi Jim,
Are you connecting to your rig via USB? If so, you may have the same problem I
had after
Aloha Chris:
Thanks for the idea.
73,
Jim
K6MIO/KH6
> On Dec 20, 2018, at 3:21 PM, Topher Petty wrote:
>
> It could be a config file issue with wsjtx. Try renaming the config to a
> .conf.bak and re-starting wsjtx, then proceed as if you've installed wsjtx
> for the first time (enter
Hi Jim,
Before you resort to dropping back to 10.13.6, have you tried letting wsjtx
create a new, clean, .ini file? You could either move your old one out of the
way temporarily or you could start wsjtx from the command line using something
like this:
cd
It could be a config file issue with wsjtx. Try renaming the config to a
.conf.bak and re-starting wsjtx, then proceed as if you've installed wsjtx
for the first time (enter callsign, location, rig control config, etc)...
I haven't run into this issue myself, but maybe it's worth a try?
73 de
Hi Steve:
Thanks for you thoughts!
I did do John, G4KLA's procedure quite some time ago when the Mac Mini first
came on line (as it was necessary).
I have reviewed that again, and the values haven’t change on the Mini, (or the
desktop and laptop which are working fine with OS 10.13.6).
My
Bill,
Tnx for the suggestion. The BAT file presently is started 1 second BEFORE
the start of a decode period. I will switch it at least 5 seconds after the
normal :00 seconds start time. Since the first decode after a band switch
is normally flagged with a band switch, the late start won't hurt
> I seem to recall that there was a point, previously, during which some Macs
> needed to have a memory range tricked out. That was done with the Mac Mini,
> and it then worked fine with earlier versions of both the OS and the WJST
> package.
>
> Is that still an issue. Did the OS update
On 20/12/2018 15:30, Rich Zwirko - K1HTV wrote:
Any idea as to why WSJT-X is responding this way?
Hi Rich,
WSJT-X in FT8 mode is a block message decoder, messages are accumulated
throughout the whole Rx period and decoded afterwards, no attempt is
made to attribute decodes to a previous
Bill,
That’s my guess too. I have in the past excluded the WSJT-X directories from
virus scans, but perhaps I missed one. Thanks
__
Dan – K4SHQ
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Thursday, December 20, 2018 7:11 AM
To: wsjt-devel@lists.sourceforge.net
Subject:
On 20/12/2018 14:23, Gene H wrote:
A friend of mine also has same issue with his ICOM IC-7600 using Fake
It. He went back to Split to get around the issue.
73 Gene K5PA
Hi Gene,
problems with Icom CAT control are often due to not disabling "CI-V
Transceive Mode" on the rig.
73
Bill
A friend of mine also has same issue with his ICOM IC-7600 using Fake
It. He went back to Split to get around the issue.
73 Gene K5PA
On 12/20/2018 8:15 AM, Steven Greer wrote:
Hey bill last time we touched base on this was right after release and
you mentions you could send me a build with
On 20/12/2018 14:15, Steven Greer wrote:
I tried to enable a mirror to see what was passing however wsjtx won't
connect to the radio because it's not responding fast enough.
Hi Steven,
some emulators use a device with a built in bootloader that is active
for a second or two after a chip
Hey bill last time we touched base on this was right after release and
you mentions you could send me a build with CAT trace enabled, if you
could that would be great. I did notice that another user was using
ft-857d interface and had the same problem. I have been able to connect
directly to
Hi Dan, Try renaming the file. i.e. ALL.TXT to ALL.XTX. If WSJT-X starts up
without an error, you will get a brand new ALL.TXT. If that works, try to copy
ALL.XTX to ALL.TXT. (be careful on the copy). Hope this helps. 73, Sam W2JDB
-Original Message-
From: Bill Somerville
To:
On 20/12/2018 12:52, Dan Malcolm wrote:
affected file is ALL.TXT. I will proceed with tracking down the
offending application, but it would have been helpful if there was a
timestamp on the error dialog. That would narrow down the things to
look at. Thanks.
__
Dan – K4SHQ
Hi
I have been getting a File Open Error from v2.0. It occurs every night, and
I’ll have multiple notifications. The affected file is ALL.TXT. I will
proceed with tracking down the offending application, but it would have been
helpful if there was a timestamp on the error dialog. That would
18 matches
Mail list logo
