Bill Somerville writes:
>
>
Hi Bill and all -
> On 06/03/2015 00:09, Eric NO3M wrote:
> Hi Eric,
>
>
>
> I ran into a similar situation with the following message:
> CQ NO3M DX
>
> CQ DX NO3M
> is the correct form and is a standard message form, you
On 6/03/2015 11:09 AM, Eric NO3M wrote:
> perhaps something JT-Alert does for them? Of course, JT-Alert is not
> able to run on *nix, so that's not an option here.
No. JTAlert doesn't play with the TX settings of WSJT-X.
de Laurie VK3AMA
---
Excellent... will try it later when 160 wakes up. Thanks for the info!
73 Eric NO3M
On 03/05/2015 07:30 PM, Bill Somerville wrote:
On 06/03/2015 00:09, Eric NO3M wrote:
Hi Eric,
I ran into a similar situation with the following message:
CQ NO3M DX
CQ DX NO3M
is the correct form and is a s
On 06/03/2015 00:09, Eric NO3M wrote:
Hi Eric,
I ran into a similar situation with the following message:
CQ NO3M DX
CQ DX NO3M
is the correct form and is a standard message form, you can add your
locator as well just like a normal CQ call.
Note that this only works with "CQ" "CQ DX" "QRZ"
I ran into a similar situation with the following message:
CQ NO3M DX
to keep stateside callers from answering. I had assumed the "CQ" would
have been picked up and TX Enable persist after each invocation.
However, that was not the case. I saw other DX stations at the time
using the same f
On 05/03/2015 22:07, Guy G4DWV/4X1LT wrote:
Hi Guy,
> Michael Black writes:
>
>>
>> Sounds like you have "Disable TX after sending 73" checked in
> File/Settings/General.
>
> I do, but standard CQ calls go out okay indefinitely and custom ones do not.
> The Disable after 73 setting is the same in
Michael Black writes:
>
>
> Sounds like you have "Disable TX after sending 73" checked in
File/Settings/General.
I do, but standard CQ calls go out okay indefinitely and custom ones do not.
The Disable after 73 setting is the same in both cases. The expected
behaviour is that both types of CQ
Sounds like you have "Disable TX after sending 73" checked in
File/Settings/General.
Mike W9MDB
From: Guy [mailto:g...@drteeth.co.uk]
Sent: Thursday, March 05, 2015 3:05 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Enhancement request
I am not a programmer at all, b
I am not a programmer at all, but I do follow this list and find what
I read fascinating even though I don't understand it.
I currently use the 1.3 release and it has a behaviour that I find
annoying and I wonder if it has been addressed in either 1.4 or 1.5.
When sending a custom CQ call
thanks a lot, Greg,
so I have to stay with the previuos version1.18, which runs just fine, hi
hi!
No plan to change my Windows-version as long as wsjt-x runs smoothly on XP..
So far, v1.5.0-devel runs just perfect and I make many contacts in JT9-
just right now !
73`s and thanks for your great wor
Hi Alois,
Yes, I should have noted this in my post. This min requirement should
have been set from the beginning.
WinXP is no longer supported by Microsoft, most importantly, security
updates. The installer now requires a minimum version of:
6.0.6002 ~ (Vista w/SP2 or later), which has support
Hi,
have downloaded WSJT-Suite-1.0.20-Win32.exe, but it looks like it´s not
running on my WINXP-PC´s.
It says, that the programm does´`nt run on the system my computer has
installed, while all former versions run just fine...
Thanks for your help
73 de Alois, dl8rbl
2015-03-05 20:48 GMT+01:00 KI
Hello All,
DISCLAIMER: These builds are for testing the latest development branches
(snapshots). *They are not* intended for long term use. If you have
problems with any of the applications, install the OFFICIAL release of
the app in question, compare the behavior, and send your comments to the
On 03/05/15 01:40 pm, wsjt-devel-requ...@lists.sourceforge.net wrote:
> On 05/03/2015 18:22, Neil Zampella wrote:
>
>
>
> I am certainly not thinking of adding any complexity, in fact the
> converse.
>
> I am suggesting that the "Enable Tx" button should do what it says
> i.e. not double as a "
On 05/03/2015 18:22, Neil Zampella wrote:
Hi Neil,
> Could I break in here with a comment:
Of course!
>
> As a user (and former IT programmer) I can appreciate the thought behind
> making such a change, but you have to think about the end user.
Indeed, that is what I am trying to do when commenting
Could I break in here with a comment:
As a user (and former IT programmer) I can appreciate the thought behind
making such a change, but you have to think about the end user.
Are you adding additional complexity to the interface?Will the
average user have an idea, or a need, for such a cha
Good morning my most heartfelt thanks to the whole group that provides us with
a well-functioning system
I kindly ask if you can have a copy for testing
thank you
franc
>Messaggio originale
>Da: j...@rmnjmn.demon.co.uk
>Data: 05/03/2015 9.12
>A: "WSJT software development"
>Ogg: Re: [w
On 05/03/2015 16:43, Black Michael wrote:
Hi Mike,
> I like that idea...seems intuitive too...plus more obvious that you are
> transmitting since it's pretty much right in your face.
>
> Go for it
Working on it right now. It is going to be a bit more complicated that
your change as there are
I like that idea...seems intuitive too...plus more obvious that you are
transmitting since it's pretty much right in your face.
Go for it
73
Mike W9MDB
On Thursday, March 5, 2015 10:19 AM, Bill Somerville
wrote:
On 05/03/2015 15:48, Michael Black wrote:
Hi Mike,
> I was testing with Ta
On 05/03/2015 15:48, Michael Black wrote:
Hi Mike,
> I was testing with Tab 2 which I don't normally use.
> I see that the buttons on there are "immediate" like the "Tx" buttons on tab
> 1.
Yes. That's why I didn't reply last night, thought I'd sleep on it and
try and come up with an alternative t
On 05/03/2015 00:02, Black Michael wrote:
Hi Mike,
> Not talking about swapping which minute I'm CQ'ing on.
Nor I.
> Seems quite a few people are shortcutting the QSO so I end up sending 73
> before them which means the next minute after them is mine!!!
OK, I was not clear. I meant that tail ender
I was testing with Tab 2 which I don't normally use.
I see that the buttons on there are "immediate" like the "Tx" buttons on tab
1.
I don't see a way to alter that behavior.
How about adding a checkbox on Tab 2 called "Immediate" which defaults to on
(the current behavior) and then when it's unche
Hi Joe,
The r5004 version of JT9 is doing wonders. I am seeing decodes at -25, -26,
-27 that I had not seen before.
--- John G4KLA
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by In
23 matches
Mail list logo
