Date   

locked Re: Auto Sequence Behavior #WSJTX_config #QSO_practices #IssueReport

Roger
 

On 13/05/2020 14:20, Bill Somerville wrote:
On 13/05/2020 12:56, wewilsonjr@... wrote:
I've noticed what I perceive as odd behavior of the Auto Seq function.  When the other station has responded with their report and I'm sending mine (Tx 3), they will sometimes temporarily go work another station as band conditions change.  As soon as they send their RR73 message to the OTHER station, my Auto Seq goes immediately back to Tx 1, essentially starting my QSO at the beginning.  If I catch this quickly, I will click Tx 3 to resume sending their report and complete the QSO.

Is this the planned behavior, or is there something I can do about this with some different option choices?
Hi OM,
you are correct that this behaviour is unhelpful, it is one of the several edge cases where we expect the operator to be alert and select the correct response. I hope you understand that we do not want to create an automated QSO machine, so we do not consider such issues to be a high priority.
73
Bill
G4WJS.
I've encountered a 2 or 3 stations in the RSGB FT4 contests who seem to be deliberately running two QSOs on alternate transmit cycles. I presume there is some application which allows the to do this?


locked Re: Message Buffer

Herb Blue - WB8ASI
 

Yes, I see that now Bill.  I must have tried to jump back to some Tx prior to 5 when deciding to abandon the clearing upon logging option.  Guess I should give it another try. Thanks, Herb

On May 13, 2020 at 12:10 PM Bill Somerville <g4wjs@...> wrote:

Herb,

the Tx5 message is not cleared for that very reason.

73
Bill
G4WJS.

On 13/05/2020 17:09, Herb Blue wrote:
The only caution in using the "Clear DX call and grid after logging" option is when the 73 is sent and/or received, and you auto log....if a decode is missed and you need to resend to complete the QSO, the call is no longer there.  73 Herb WB8ASI
On May 13, 2020 at 12:00 PM Bill Somerville <g4wjs@...> wrote:

On 13/05/2020 16:51, Harold Miller wrote:

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

Hi Hal,

to abandon a QSO hit the ESC key. You can also clear down the DX Call and DX grid along with QSO partner specific messages by hitting F4 at any time. Note that with this last option, it only works if the band/frequency drop down list do not have focus, that control does something different with F4.

Double-clicking a decode will always abandon and clear down any previous QSO. You can also check the option "Settings->Reporting->Clear DX call and grid after logging", this last option is probably the one you really need.

73
Bill
G4WJS.

73
Bill
G4WJS.




 


locked Re: Message Buffer

Bill Somerville
 

Herb,

the Tx5 message is not cleared for that very reason.

73
Bill
G4WJS.

On 13/05/2020 17:09, Herb Blue wrote:
The only caution in using the "Clear DX call and grid after logging" option is when the 73 is sent and/or received, and you auto log....if a decode is missed and you need to resend to complete the QSO, the call is no longer there.  73 Herb WB8ASI
On May 13, 2020 at 12:00 PM Bill Somerville <g4wjs@...> wrote:

On 13/05/2020 16:51, Harold Miller wrote:

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

Hi Hal,

to abandon a QSO hit the ESC key. You can also clear down the DX Call and DX grid along with QSO partner specific messages by hitting F4 at any time. Note that with this last option, it only works if the band/frequency drop down list do not have focus, that control does something different with F4.

Double-clicking a decode will always abandon and clear down any previous QSO. You can also check the option "Settings->Reporting->Clear DX call and grid after logging", this last option is probably the one you really need.

73
Bill
G4WJS.

73
Bill
G4WJS.



locked Re: Message Buffer

Herb Blue - WB8ASI
 

The only caution in using the "Clear DX call and grid after logging" option is when the 73 is sent and/or received, and you auto log....if a decode is missed and you need to resend to complete the QSO, the call is no longer there.  73 Herb WB8ASI

On May 13, 2020 at 12:00 PM Bill Somerville <g4wjs@...> wrote:

On 13/05/2020 16:51, Harold Miller wrote:

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

Hi Hal,

to abandon a QSO hit the ESC key. You can also clear down the DX Call and DX grid along with QSO partner specific messages by hitting F4 at any time. Note that with this last option, it only works if the band/frequency drop down list do not have focus, that control does something different with F4.

Double-clicking a decode will always abandon and clear down any previous QSO. You can also check the option "Settings->Reporting->Clear DX call and grid after logging", this last option is probably the one you really need.

73
Bill
G4WJS.

73
Bill
G4WJS.



 


locked Re: Auto Sequence Behavior #WSJTX_config #QSO_practices #IssueReport

Bill Somerville
 

Hi Joe,

if the Tx1 message is being selected that is effectively answering a called, i.e. RR73 is probably being interpreted as a grid square in this case.

73
Bill
G4WJS.

On 13/05/2020 17:00, Joe Subich, W4TV wrote:
Bill,

Should not the RR73 message contain *my* callsign in order to be
valid for my report?  IOW, if I'm in the middle of an exchange
with P5DX and he sends G4WJS P5DX RR73, why - even as an edge
case - would the software consider that a valid acknowledgement
to me?

73,

   ... Joe, W4TV


On 2020-05-13 9:20 AM, Bill Somerville wrote:
On 13/05/2020 12:56, wewilsonjr@... wrote:
I've noticed what I perceive as odd behavior of the Auto Seq function.  When the other station has responded with their report and I'm sending mine (Tx 3), they will sometimes temporarily go work another station as band conditions change.  As soon as they send their RR73 message to the OTHER station, my Auto Seq goes immediately back to Tx 1, essentially starting my QSO at the beginning.  If I catch this quickly, I will click Tx 3 to resume sending their report and complete the QSO.

Is this the planned behavior, or is there something I can do about this with some different option choices?

Hi OM,

you are correct that this behaviour is unhelpful, it is one of the several edge cases where we expect the operator to be alert and select the correct response. I hope you understand that we do not want to create an automated QSO machine, so we do not consider such issues to be a high priority.

73
Bill
G4WJS.



locked Re: Transmit Delay after Double Click (WSJT-X 2.2.0-rc1)

Joe
 

Tx starts when it's supposed to start: at the 15-second boundary.  

You are double-clicking well before that boundary, because the program is now displaying decodes earlier.

  -- 73, Joe, K1JT


locked Re: Message Buffer

Herb Blue - WB8ASI
 

Thanks for the tip Rick.  Good to know.  I've forever been clearing the call from the DX Call box which clears everything, but will start using F4.  73 Herb WB8ASI

On May 13, 2020 at 11:57 AM ve3ki <ve3iay@...> wrote:

To abandon an incomplete QSO, use the F4 key.

73,
Rich VE3KI


On Wed, May 13, 2020 at 11:51 AM, Harold Miller wrote:

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

 



 


locked Re: Message Buffer

Bill Somerville
 

On 13/05/2020 16:51, Harold Miller wrote:

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

Hi Hal,

to abandon a QSO hit the ESC key. You can also clear down the DX Call and DX grid along with QSO partner specific messages by hitting F4 at any time. Note that with this last option, it only works if the band/frequency drop down list do not have focus, that control does something different with F4.

Double-clicking a decode will always abandon and clear down any previous QSO. You can also check the option "Settings->Reporting->Clear DX call and grid after logging", this last option is probably the one you really need.

73
Bill
G4WJS.

73
Bill
G4WJS.


locked Re: Auto Sequence Behavior #WSJTX_config #QSO_practices #IssueReport

Joe Subich, W4TV
 

Bill,

Should not the RR73 message contain *my* callsign in order to be
valid for my report? IOW, if I'm in the middle of an exchange
with P5DX and he sends G4WJS P5DX RR73, why - even as an edge
case - would the software consider that a valid acknowledgement
to me?

73,

... Joe, W4TV

On 2020-05-13 9:20 AM, Bill Somerville wrote:
On 13/05/2020 12:56, wewilsonjr@... wrote:
I've noticed what I perceive as odd behavior of the Auto Seq function.  When the other station has responded with their report and I'm sending mine (Tx 3), they will sometimes temporarily go work another station as band conditions change.  As soon as they send their RR73 message to the OTHER station, my Auto Seq goes immediately back to Tx 1, essentially starting my QSO at the beginning.  If I catch this quickly, I will click Tx 3 to resume sending their report and complete the QSO.

Is this the planned behavior, or is there something I can do about this with some different option choices?
Hi OM,
you are correct that this behaviour is unhelpful, it is one of the several edge cases where we expect the operator to be alert and select the correct response. I hope you understand that we do not want to create an automated QSO machine, so we do not consider such issues to be a high priority.
73
Bill
G4WJS.


locked Re: Message Buffer

Joe
 

Hit the ESC key.


locked Re: Message Buffer

ve3ki
 

To abandon an incomplete QSO, use the F4 key.

73,
Rich VE3KI


On Wed, May 13, 2020 at 11:51 AM, Harold Miller wrote:

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

 


locked Re: Collapased Waterfall and Decoding

Bill Somerville
 

On 13/05/2020 16:47, Marty Tressell wrote:
The issue was resolved...found the audio input cable was not seated fully in the connector and thus had loosened to a point where the audio was not fully into the computer sound card.  Once seated the problem was resolved!

Thank you all for your support!
--
Marty Tressell, K0BBK
Hi Marty,

thanks for the update, glad you up and running again.

73
Bill
G4WJS.


locked Re: Coming soon: WSJT-X 2.2.0-rc1

Paul Selwood G3YDY
 

Hi Jo,
All installed and worked first time as expected.
In FT8 mode I like the early decodes at 13.5, 11.8 and finally at 14.7 seconds. It takes a little getting used to see the decodes with out the TX immediately going into transmit. I have wondered if it would be good to change the colour of the decode button at each of the three points, then the operator would know it's going into TX after a particular colour. This could be arranged as traffic lights for example Red at the 11.8 decode, Amber at 13.5 decode and Green at 14.7.
73
Paul
G3YDY

-----Original Message-----
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Joe
Sent: 05 May 2020 17:51
To: WSJTX@groups.io
Subject: [WSJTX] Coming soon: WSJT-X 2.2.0-rc1

Hi all,

This message is to let you know of some important WSJT-X development plans. We plan to make a first candidate release of WSJT-X 2.2.0 next Monday, May 10.

WSJT-X 2.2.0-rc1 will be a beta-quality release candidate providing a number of new features and capabilities. These include:

- Improvements to the decoders for five modes:

FT4: Corrected bugs that prevented AP decoding and/or multi-pass
decoding in some circumstances. The algorithm for AP
decoding has been improved and extended.

FT8: Decoding is now spread over three intervals. The first
starts at t = 11.8 s into an Rx sequence and typically yields
around 85% of the possible decodes for the sequence. You
therefore see most decodes much earlier than before. A second
processing step starts at 13.5 s, and the final one at 14.7 s.
Overall decoding yield on crowded bands is improved by 10% or
more. (Systems with receive latency greater than 0.2 s will see
smaller improvements, but will still see many decodes earlier
than before.)

JT4: Formatting and display of Averaged and Deep Search decodes
has been cleaned up and made consistent with other modes. JT4
remains the digital mode of choice for EME and other extreme
weak-signal work on microwave bands.

JT65: Many improvements for Averaged and Deep Search decodes and
their display to the user. These improvements are particularly
important for EME on VHF and UHF bands.

WSPR: Significant improvements have been made to the WSPR
decoder's sensitivity, its ability to cope with many signals in
a crowded sub-band, and its rate of undetected false decodes.
We now use up to three decoding passes. Passes 1 and 2 use
noncoherent demodulation of single symbols and allow for
frequency drifts up to ±4 Hz in a transmission. Pass 3 assumes
no drift and does coherent block detection of up to three
symbols. It also applies bit-by-bit normalization of the
single-symbol bit metrics, a technique that has proven helpful
for signals corrupted by artifacts of the subtraction of
stronger signals and also for LF/MF signals heavily contaminated
by lightning transients. With these improvements the number of
decodes in a crowded WSPR sub-band typically increases by 10 to
15%.

- New format for "EU VHF Contest" Tx2 and Tx3 messages

When "EU VHF Contest" is selected, the Tx2 and Tx3 messages
(those conveying signal report, serial number, and 6-character
locator) now use hashcodes for both callsigns. This change is
NOT backward compatible with earlier versions of _WSJT-X_, so
all users of EU VHF Contest messages should be sure to upgrade
to versiion 2.2.0.

- Accessibility

Keyboard shortcuts have been added as an aid to accessibility:
Alt+R sets Tx4 message to RR73, Ctrl+R sets it to RRR.

As an aid for partial color-blindness, the "inverted goal posts"
marking Rx frequency on the Wide Graph's frequency scale are now
rendered in a darker shade of green.

- Minor enhancements and bug fixes

"Save None" now writes no .wav files to disk, even temporarily.

An explicit entry for "WW Digi Contest" has been added to
"Special operating activities" on the "Settings | Advanced" tab.

Contest mode FT4 now always uses RR73 for the Tx4 message.

The Status bar now displays the number of decodes found in the
most recent Rx sequence.

Release candidate WSJT-X 2.2.0-rc1 will be available for beta-testing for one month starting on May 10, 2020. We currently plan a General Availability (GA) release of WSJT-X 2.2.0 on June 1, 2020.

For those looking even farther ahead: We are well along in the development of two new modes designed for the LF and MF bands. One mode is for WSPR-like activity and one for making 2-way QSOs. Both use Low-density Parity Check (LDPC) codes, 4-GFSK modulation, and two-minute T/R sequences. The QSO mode reaches threshold SNR sensitivity around -31 dB on the AWGN channel, and the WSPR-like mode better than -32 dB.

With best wishes,

-- Joe, K1JT, Steve, K9AN, and Bill, G4WJS


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: Copy log from Windows to Linux

Bill Somerville
 

On 13/05/2020 16:40, Bart N5BLP via groups.io wrote:
I've been running WSJTX under windows for quite awhile and have a considerable log.  I've recently set up Ubuntu as a dual boot and installed the linux version of WSJTX.   I would like to copy my Windows version log over to the linux version.

I tried copying it from the windows version to a dropbox folder and then from there into the linux version, but it seems the files are named a little differently and may be incompatible.

Is there a way to do this?

Bart N5BLP
Hi Bart,

there should be no problem with that, are you copying the file "%LocalAppData%\WSJT-X\wsjtx_log.adi" to ~/.local/share/WSJT-X/ ?

73
Bill
G4WJS.


locked Transmit Delay after Double Click (WSJT-X 2.2.0-rc1)

Jeff, W8TB
 

Just an observation, when double-clicking on a callsign with 2.2.0-rc1, there is a noticeable delay before the rig goes in to transmit.  I switched back to the 2.1.2 version to test and compare and it is back to normal, which is nearly immediate. 

Rig: IC-7300, connected USB to i5 PC

 

Jeff

 


locked Message Buffer

Harold Miller
 

New to WSJT and like it so far.

 

Do have one question, have not found this in the Help file. 

 

Is there a way to “CLEAR” the Transmit Msg Buffer.   Say I try to work a station and due to conditions, he disappears.  Is there a way other than manually clearing all 5 rows of the Msg Buffer.

 

Thanks

 

Hal, KB1ZQ

 


locked Re: Collapased Waterfall and Decoding

Marty Tressell
 

The issue was resolved...found the audio input cable was not seated fully in the connector and thus had loosened to a point where the audio was not fully into the computer sound card.  Once seated the problem was resolved!

Thank you all for your support!
--
Marty Tressell, K0BBK
mtressell@...


locked Copy log from Windows to Linux

Bart N5BLP
 

I've been running WSJTX under windows for quite awhile and have a considerable log.  I've recently set up Ubuntu as a dual boot and installed the linux version of WSJTX.   I would like to copy my Windows version log over to the linux version.

I tried copying it from the windows version to a dropbox folder and then from there into the linux version, but it seems the files are named a little differently and may be incompatible.

Is there a way to do this?

Bart N5BLP


locked Re: 2.2.0-rc1 rigctld-wsjtx -- Hamlib error with IC-7300

Karza
 

Hello Devs,
I wonder if anyone noticed this issue I reported yesterday...
https://groups.io/g/WSJTX/message/9902

Today I used Wireshark to see what is going on 'on the wire':

Here's the latter part of the trace:

This part is where I think WSJT-X is finding out VFO granularity.

All OK so far.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 36 e1 e7 40 00 40 06 5a d8 7f 00 00 01   E..6áç@.@.ZØ....
0020   7f 00 00 01 b3 22 11 b4 e2 00 7c a0 bc 9a b0 80   ....³".´â.| ¼.°.
0030   80 18 02 00 fe 2a 00 00 01 01 08 0a bb ef c7 f8   ....þ*......»ïÇø
0040   bb ef c7 f6 66 0a                                 »ïÇöf.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 41 72 d0 40 00 40 06 c9 e4 7f 00 00 01   E..ArÐ@.@.Éä....
0020   7f 00 00 01 11 b4 b3 22 bc 9a b0 80 e2 00 7c a2   .....´³"¼.°.â.|¢
0030   80 18 02 00 fe 35 00 00 01 01 08 0a bb ef c8 34   ....þ5......»ïÈ4
0040   bb ef c7 f8 35 33 35 37 30 30 30 0a 56 46 4f 41   »ïÇø5357000.VFOA
0050   0a                                                .

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 45 e1 e8 40 00 40 06 5a c8 7f 00 00 01   E..Eáè@.@.ZÈ....
0020   7f 00 00 01 b3 22 11 b4 e2 00 7c a2 bc 9a b0 8d   ....³".´â.|¢¼.°.
0030   80 18 02 00 fe 39 00 00 01 01 08 0a bb ef c8 35   ....þ9......»ïÈ5
0040   bb ef c8 34 46 20 35 33 35 37 30 35 35 2e 30 30   »ïÈ4F 5357055.00
0050   30 30 30 30 0a                                    0000.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 3b 72 d2 40 00 40 06 c9 e8 7f 00 00 01   E..;rÒ@.@.Éè....
0020   7f 00 00 01 11 b4 b3 22 bc 9a b0 8d e2 00 7c b3   .....´³"¼.°.â.|³
0030   80 18 02 00 fe 2f 00 00 01 01 08 0a bb ef c8 5f   ....þ/......»ïÈ_
0040   bb ef c8 35 52 50 52 54 20 30 0a                  »ïÈ5RPRT 0.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 45 e1 e9 40 00 40 06 5a c7 7f 00 00 01   E..Eáé@.@.ZÇ....
0020   7f 00 00 01 b3 22 11 b4 e2 00 7c b3 bc 9a b0 94   ....³".´â.|³¼.°.
0030   80 18 02 00 fe 39 00 00 01 01 08 0a bb ef c8 5f   ....þ9......»ïÈ_
0040   bb ef c8 5f 46 20 35 33 35 37 30 30 30 2e 30 30   »ïÈ_F 5357000.00
0050   30 30 30 30 0a                                    0000.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 3b 72 d4 40 00 40 06 c9 e6 7f 00 00 01   E..;rÔ@.@.Éæ....
0020   7f 00 00 01 11 b4 b3 22 bc 9a b0 94 e2 00 7c c4   .....´³"¼.°.â.|Ä
0030   80 18 02 00 fe 2f 00 00 01 01 08 0a bb ef c8 87   ....þ/......»ïÈ.
0040   bb ef c8 5f 52 50 52 54 20 30 0a                  »ïÈ_RPRT 0.

Now command 's' is sent to get split VFO.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 36 e1 ea 40 00 40 06 5a d5 7f 00 00 01   E..6áê@.@.ZÕ....
0020   7f 00 00 01 b3 22 11 b4 e2 00 7c c4 bc 9a b0 9b   ....³".´â.|ļ.°.
0030   80 18 02 00 fe 2a 00 00 01 01 08 0a bb ef c8 88   ....þ*......»ïÈ.
0040   bb ef c8 87 73 0a                                 »ïÈ.s.

I's VFOB, thank you very much.

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 3b 72 d6 40 00 40 06 c9 e4 7f 00 00 01   E..;rÖ@.@.Éä....
0020   7f 00 00 01 11 b4 b3 22 bc 9a b0 9b e2 00 7c c6   .....´³"¼.°.â.|Æ
0030   80 18 02 00 fe 2f 00 00 01 01 08 0a bb ef c8 9b   ....þ/......»ïÈ.
0040   bb ef c8 88 30 0a 56 46 4f 42 0a                  »ïÈ.0.VFOB.

Now here is where the trouble begins: WSJT-X sends command 'v'
followed by a carriage-return:

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 36 e1 ec 40 00 40 06 5a d3 7f 00 00 01   E..6áì@.@.ZÓ....
0020   7f 00 00 01 b3 22 11 b4 e2 00 7c c6 bc 9a b0 a2   ....³".´â.|Ƽ.°¢
0030   80 18 02 00 fe 2a 00 00 01 01 08 0a bb ef d0 a1   ....þ*......»ïС
0040   bb ef c8 9b 76 0a                                 »ïÈ.v.

Rigctrld is not happy with that query and sends back negative acknowledgement:

0000   00 00 03 04 00 06 00 00 00 00 00 00 00 00 08 00   ................
0010   45 00 00 3d 72 d7 40 00 40 06 c9 e1 7f 00 00 01   E..=r×@.@.Éá....
0020   7f 00 00 01 11 b4 b3 22 bc 9a b0 a2 e2 00 7c c8   .....´³"¼.°¢â.|È
0030   80 18 02 00 fe 31 00 00 01 01 08 0a bb ef d0 a2   ....þ1......»ïТ
0040   bb ef d0 a1 52 50 52 54 20 2d 31 31 0a            »ïСRPRT -11.

After this WSJT-X closes down the network connection and an error
is reported.

Same response is returned if command 'v' is sent using netcat connection.

73's de Kari, oh2gqc






locked Re: WSJTX_2-2-0-RC1 dont start ---

Andy McMullin
 

John,

While that might sound like a good reason — I am running the “international” version of Windows 10: set for the UK, with a UK keyboard, UK date format etc. and version 2.2.0-rc1 (64 bit) is working just fine here. Both windows open as per normal. 

One thing I did do for installation was to uninstall the previous version though: I did not install “over the top”; that had caused me troubles in the past.

I hope this helps identify the issue better.

Regards
Andy, G8TQH

On 13 May 2020, at 15:29, JP Tucson, AZ <samcat88az@...> wrote:

I wonder if this could be related to the "international" versions of MS WIN10 (or perhaps international settings for kb or display, etc.) ; as it seems like most of these folks having this issue have international callsigns.

One being the reversal of commas & periods for example.



73 - John - N7GHZ

On Wed, May 13, 2020, 6:15 AM Vassilis , SV1CNS via groups.io <vorfanos=yahoo.com@groups.io> wrote:
Hi to all,

The same here with 2.2.0 RC1. Tried with 32 Bit version also 64 Bit and I have exactly the same behavior.
wsjtx.exe is running but no window or taskbar icon appear. Only visible in task manager.No problem at all with previous version
Any help please (win 10 64 bit)