Date   

locked Is this supposed to happen? #FoxAndHound #IssueReport

Tony Collett
 

Hi Group
I had an intriguing experience yesterday calling a Fox on 30m

When my call was selected my Tx was correctly moved to the Fox frequency but he was not seeing my report so he kept sending his report to me while I responded with his report for 3 periods.

On the 4th period he dropped my call and went on to work a different station - my first failure to work an F&H QSO !

What I didn't expect was that my transmitter was moved off the Fox frequency to a different one (but still below 1000Hz) and WSJT kept sending my report to the Fox. It continued to do this for some time and the timer didn't come into operation which it does when you are just calling the Fox. 

Eventually I manually stopped the transmission, moved my frequency back above 1000Hz and started calling anew.
Glad to say I was selected and completed a short while later....

My question - is it supposed to continuously send a report to the Fox after the QSO has been abandoned - (I can check my all.txt file to see just how long).
The Fox called CQ several times before I stopped WSJT sending the report as it was obvious he wasn't seeing me or going to come back with the RR73 I needed.
If I had let it continue would the Fox eventually have picked me up while transmitting a report in "no mans land"?

For the record I was using V2.2.2
Thanks
Tony G4NBS


locked Call sign not being recognized as work before question #FT8 #logging

Pat
 

I have one call sign that I have worked many many times many many times on the same band and I’m sure he’s getting tired of me. It is not recognized in the log as being worked before.  The call is K4TY.
I have looked in the log to see if it looks different than any other calls signs that are in the log of the program but I don’t see anything that’s different or weird. Just not being recognized anybody else experienced this? And my apology to the owner of the car sign for calling you when it says it’s a new one and I never worked before but in my log I think I got you 30 times. I’ve tried it with the software a standalone, and also with JT alert same thing. 

73
n7uvh


locked Re: #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

Bill Somerville
 

On 03/02/2021 21:34, Jim Pruitt wrote:
I was decoding using WSJT-X 2.2.2 (64 bit) and today I installed the newest 2.3.0 (64 bit)  When I did WSJTX stopped working.  The waterfall is totally blank (not a single signal showing up despite LOTS of activity on the frequency.  Looking at the configuration had the Audio Soundcard input first as Default device Not found and then it showed it as blank and now it is back to not found. The USB sound card dongle was working with 2.2.2 but is not even seen by 2.3.0 and the dongle is flashing with the audio input.  How do I get it working?  Or should I just re install 2.2.2?

Thank you.

Jim Pruitt
WA7DUY

Hi Jim,

to try and dissuade users from using the same sound card for WSJT-X and for operating system or other application audio, we no longer offer the default sound card as an option. You must select the sound card that is connected to your rig.

73
Bill
G4WJS.


locked Re: #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

neil_zampella
 

I believe the choice of DEFAULT was removed as many users were not taking the time to turn off system sounds which usually head to the default sound choice, so there were WIndows sounds (as well as other audio) being Tx.

You need to properly select the correct sound inputs.  If it is indeed your computer soundcard (really not recommended) you should insure all  computer sounds are turned off.

Neil, KN3ILZ

On 2/3/2021 3:34 PM, Jim Pruitt wrote:
I was decoding using WSJT-X 2.2.2 (64 bit) and today I installed the newest 2.3.0 (64 bit)  When I did WSJTX stopped working.  The waterfall is totally blank (not a single signal showing up despite LOTS of activity on the frequency.  Looking at the configuration had the Audio Soundcard input first as Default device Not found and then it showed it as blank and now it is back to not found. The USB sound card dongle was working with 2.2.2 but is not even seen by 2.3.0 and the dongle is flashing with the audio input.  How do I get it working?  Or should I just re install 2.2.2?

Thank you.

Jim Pruitt
WA7DUY





locked Re: #WSJTX_config #WSJTX_config

Monty Wilson, NR0A
 

Thanks Neil,

 

That got the link to JTALERT working again.  Don’t know why the values I was using suddenly failed.

 

Thanks again…..now on to my other issue!

 

Cheers

 

Monty, NR0A

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of neil_zampella
Sent: Wednesday, February 3, 2021 04:36 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #WSJTX_config

 

Sorry OM .. I've just been seeing so many issues with HRD lately, I zeroed in on that. 

Have you tried changing the UDP Server IP to 239.255.0.1.  Here's what I have, and I've had no issues with JT-Alert.

Neil, KN3ILZUDP settings

On 2/3/2021 1:58 PM, Monty Wilson wrote:

Neil,

 

My message was a little long with lots of parts. But since the problem is now loss of then connection between WSJT-X and JTALERT I don’t see what the new database in HRD has to do with my issue. 

 

I do have a problem with logs getting to HRD from JTALERT. However until I can get data to JTALERT the HRD issue is immaterial. 

 

 

 

Monty Wilson



On Feb 3, 2021, at 1:29 AM, neil_zampella <neilz@...> wrote:



FWIW ... the answer can be found on the JT-Alert groups.io support group, not here as it really does not pertain to WSJT-X other than it originates the Log UDP message.

Apparently, the answer is to create a NEW database in HRD, and import your log from the old DB.   When you do that DO NOT create an access database, create one in Maria DB.   For two reasons, its a real SQL database, and it can handle many more records.

You can find out more about this on the hamapps.groups.io support list.

Neil, KN3ILZ

On 2/2/2021 10:13 PM, Monty Wilson wrote:

Yesterday, I downloaded and successfully loaded WSJT-X V 2.3.0.  On my first try I did not have a connection to JTALERT.  I was told about the new loopback option and once set, WSJT-X was communicating with JTALERT.  I was able to interact with calls on JTALERT and make contacts without any issues.  However, I found that JTALERT would not write logs to my local HRD log.

 

I spent this morning troubleshooting that issue without success and eventually shut everything down to take a lunch break.

 

I think started my HRD (version) 6.7.0.323, followed by WSJT-X (version 2.3.0) and then JTALERT (V 2.16.17).  For unknown reasons, I have now lost the link between WSJT-X and JTALERT. 

 

I have checked the settings in WSJT-X (I use multicast) and JTALERT.  All of the settings look correct.  The only error message I see is

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

JTALERT about shows:

 

JTAlert Instance      : #1

JTAlert Start Params  : /wsjtx

WSJT-X Window Title   : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"

WSJT-X   --rig-name   :

WSJT-X Config File    : C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version               :

WSJT-X Revision              :

WSJT-X Spec Op Mode          : None

WSJT-X UDP ID                :

WSJT-X UDP Port              : 2333

WSJT-X UDP Server            : 239.255.0.0

WSJT-X UDP MCast on Loopback : True

WSJT-X UDP Max Schema        :

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 54408 65471

JTAlertV2.Manager.exe : 62581 62582

JTAlertV2.Decodes.exe :

 

In background, I have been running 2.2.2 since it was released.  I was successful in connecting to JTALERT and JTALERT to HRD for logging.  For some reason, since I loaded 2.3.0 I have had problems with the connections.

 

I don’t know where to look to troubleshoot.  All of the configuration points (as far as I know) are set the same as 2.2.2 with the exception of the new Loopback field.  I am looking for ideas.

 

I may try to revert back to 2.2.2 to see if that will get me started again.

 

Thanks in advance

 

Monty, NR0A

jwilson16@...

 







 
 
 


locked Re: #WSJTX_config #WSJTX_config

Monty Wilson, NR0A
 

Bill,

 

I have the loopback feature selected.  I still am not able to exchange data with JTALERT.

 

I get the following message from JTALERT

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

  Process Command Line :

 

Decode alerts and logging will be unavailable until corrected.

 

When I first installed version 2.3.0 I set the loopback_0 in the Outgoing interfaces.  When I first set this I was able to exchange data with JTALERT.  Then it suddenly quit. 

 

I am looking for ideas on getting it to work again.

 

Monty, NR0A

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Wednesday, February 3, 2021 04:25 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #WSJTX_config

 

On 03/02/2021 04:13, Monty Wilson wrote:

Yesterday, I downloaded and successfully loaded WSJT-X V 2.3.0.  On my first try I did not have a connection to JTALERT.  I was told about the new loopback option and once set, WSJT-X was communicating with JTALERT.  I was able to interact with calls on JTALERT and make contacts without any issues.  However, I found that JTALERT would not write logs to my local HRD log.

 

I spent this morning troubleshooting that issue without success and eventually shut everything down to take a lunch break.

 

I think started my HRD (version) 6.7.0.323, followed by WSJT-X (version 2.3.0) and then JTALERT (V 2.16.17).  For unknown reasons, I have now lost the link between WSJT-X and JTALERT. 

 

I have checked the settings in WSJT-X (I use multicast) and JTALERT.  All of the settings look correct.  The only error message I see is

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

JTALERT about shows:

 

JTAlert Instance      : #1

JTAlert Start Params  : /wsjtx

WSJT-X Window Title   : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"

WSJT-X   --rig-name   :

WSJT-X Config File    : C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version               :

WSJT-X Revision              :

WSJT-X Spec Op Mode          : None

WSJT-X UDP ID                :

WSJT-X UDP Port              : 2333

WSJT-X UDP Server            : 239.255.0.0

WSJT-X UDP MCast on Loopback : True

WSJT-X UDP Max Schema        :

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 54408 65471

JTAlertV2.Manager.exe : 62581 62582

JTAlertV2.Decodes.exe :

 

In background, I have been running 2.2.2 since it was released.  I was successful in connecting to JTALERT and JTALERT to HRD for logging.  For some reason, since I loaded 2.3.0 I have had problems with the connections.

 

I don’t know where to look to troubleshoot.  All of the configuration points (as far as I know) are set the same as 2.2.2 with the exception of the new Loopback field.  I am looking for ideas.

 

I may try to revert back to 2.2.2 to see if that will get me started again.

 

Thanks in advance

 

Monty, NR0A

jwilson16@...

Hi Monty,

there is a minor defect in WSJT-X v2.3.0 when using a multicast IP group address for outgoing UDP messages. The field to set the outgoing network interface(s) can be blank. This is not supposed to be possible, and that defect is fixed for the next release. If you have all servers subscribing to the WSJT-X UDP Message Protocol, e.g. JTAlert, Gridtracker, etc. running on the same PC as the WSJT-X instances; then use the loopback network interface as the outgoing interface.

73
Bill
G4WJS.


locked Re: #WSJTX_config #WSJTX_config

neil_zampella
 

Sorry OM .. I've just been seeing so many issues with HRD lately, I zeroed in on that. 

Have you tried changing the UDP Server IP to 239.255.0.1.  Here's what I have, and I've had no issues with JT-Alert.

Neil, KN3ILZUDP settings

On 2/3/2021 1:58 PM, Monty Wilson wrote:
Neil,

My message was a little long with lots of parts. But since the problem is now loss of then connection between WSJT-X and JTALERT I don’t see what the new database in HRD has to do with my issue. 

I do have a problem with logs getting to HRD from JTALERT. However until I can get data to JTALERT the HRD issue is immaterial. 



Monty Wilson

On Feb 3, 2021, at 1:29 AM, neil_zampella <neilz@...> wrote:



FWIW ... the answer can be found on the JT-Alert groups.io support group, not here as it really does not pertain to WSJT-X other than it originates the Log UDP message.

Apparently, the answer is to create a NEW database in HRD, and import your log from the old DB.   When you do that DO NOT create an access database, create one in Maria DB.   For two reasons, its a real SQL database, and it can handle many more records.

You can find out more about this on the hamapps.groups.io support list.

Neil, KN3ILZ

On 2/2/2021 10:13 PM, Monty Wilson wrote:

Yesterday, I downloaded and successfully loaded WSJT-X V 2.3.0.  On my first try I did not have a connection to JTALERT.  I was told about the new loopback option and once set, WSJT-X was communicating with JTALERT.  I was able to interact with calls on JTALERT and make contacts without any issues.  However, I found that JTALERT would not write logs to my local HRD log.

 

I spent this morning troubleshooting that issue without success and eventually shut everything down to take a lunch break.

 

I think started my HRD (version) 6.7.0.323, followed by WSJT-X (version 2.3.0) and then JTALERT (V 2.16.17).  For unknown reasons, I have now lost the link between WSJT-X and JTALERT. 

 

I have checked the settings in WSJT-X (I use multicast) and JTALERT.  All of the settings look correct.  The only error message I see is

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

JTALERT about shows:

 

JTAlert Instance      : #1

JTAlert Start Params  : /wsjtx

WSJT-X Window Title   : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"

WSJT-X   --rig-name   :

WSJT-X Config File    : C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version               :

WSJT-X Revision              :

WSJT-X Spec Op Mode          : None

WSJT-X UDP ID                :

WSJT-X UDP Port              : 2333

WSJT-X UDP Server            : 239.255.0.0

WSJT-X UDP MCast on Loopback : True

WSJT-X UDP Max Schema        :

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 54408 65471

JTAlertV2.Manager.exe : 62581 62582

JTAlertV2.Decodes.exe :

 

In background, I have been running 2.2.2 since it was released.  I was successful in connecting to JTALERT and JTALERT to HRD for logging.  For some reason, since I loaded 2.3.0 I have had problems with the connections.

 

I don’t know where to look to troubleshoot.  All of the configuration points (as far as I know) are set the same as 2.2.2 with the exception of the new Loopback field.  I am looking for ideas.

 

I may try to revert back to 2.2.2 to see if that will get me started again.

 

Thanks in advance

 

Monty, NR0A

jwilson16@...

 









locked Re: #logging #logging

neil_zampella
 

Its up to the developer to add the new modes, or provide a means for the user to manually add them.

Neil, KN3ILZ

On 2/3/2021 12:35 PM, David Ackrill wrote:

Thanks Neil,

Does that mean an update to ADIF will be available to logging programs as well?  If so, I'll email the guy who wrote the one I use and see if he has been able to get an update.

Cheers - Dave (G0DJA)





locked #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

Jim Pruitt
 

I was decoding using WSJT-X 2.2.2 (64 bit) and today I installed the newest 2.3.0 (64 bit)  When I did WSJTX stopped working.  The waterfall is totally blank (not a single signal showing up despite LOTS of activity on the frequency.  Looking at the configuration had the Audio Soundcard input first as Default device Not found and then it showed it as blank and now it is back to not found. The USB sound card dongle was working with 2.2.2 but is not even seen by 2.3.0 and the dongle is flashing with the audio input.  How do I get it working?  Or should I just re install 2.2.2?

Thank you.

Jim Pruitt
WA7DUY


locked Re: WSJTX Install Fail on Pi64bit #install #linux #IssueReport

Bill Somerville
 

On 03/02/2021 19:56, Ken Hendrickson wrote:
Fails to install on Raspberry Pi 4 with Ubuntu installed - 64 bit version downloaded from Ubuntu website.
See attached messages.

wsjtxerror.png

wsjtxinstallerror.png

Hi Ken,

the 64-bit ARM Debian package was built on the Raspberry Pi OS beta 64-bit operating system release, it certainly installs and runs on that. I'm not sure what it is trying to write to /usr/share/appdata. The unmet dependencies is just a case of needing to install the prerequisite package dependencies. As always, if the provided package does not install you can build WSJT-X from sources.

73
Bill
G4WJS.


locked Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Bill Somerville
 

On 03/02/2021 22:10, Dave H wrote:

Hello,

I want to run multiple Instances of WSJTX, I found that I need to create 2 shortcuts with the following added

wsjtx --rig-name=FT-991 

wsjtx --rig-name=FT-891 

What I'm not clear on.? Will I end up with "2" wsjt-x adi files or is there a single shared file.

Just trying to think ahead for getting wsjt-x to Log into Log4OM

Thanks...

Hi Dave,

two separate log files, although you can make them use a single file using a symlink (use a hard link on MS Windows), with some minor restrictions on highlighting of stations worked before.

73
Bill
G4WJS.


locked Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Dave H
 

Hello,

I want to run multiple Instances of WSJTX, I found that I need to create 2 shortcuts with the following added

wsjtx --rig-name=FT-991 

wsjtx --rig-name=FT-891 

What I'm not clear on.? Will I end up with "2" wsjt-x adi files or is there a single shared file.

Just trying to think ahead for getting wsjt-x to Log into Log4OM

Thanks...


locked WSJTX Install Fail on Pi64bit #install #linux #IssueReport

Ken Hendrickson
 

Fails to install on Raspberry Pi 4 with Ubuntu installed - 64 bit version downloaded from Ubuntu website.
See attached messages.


locked Re: #logging #logging

 

Only if they’re a member of the ADIF group. If they’re not why not?

 

Phil GM3ZZA

 

Sent from Mail for Windows 10

 

From: David Ackrill
Sent: 03 February 2021 18:42
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #logging

 

Thanks Neil,

Does that mean an update to ADIF will be available to logging programs as well?  If so, I'll email the guy who wrote the one I use and see if he has been able to get an update.

Cheers - Dave (G0DJA)

 


--
73 Phil GM3ZZA


locked Re: Automatic power up of rig #WSJTX_config

David Ross
 

Hi Bill I have been away just back
I have attached the wsjtx log file as requested 
My radio is the Yaesu FTDX101MP
David 


locked Re: #WSJTX_config #WSJTX_config

Monty Wilson, NR0A
 

Neil,

My message was a little long with lots of parts. But since the problem is now loss of then connection between WSJT-X and JTALERT I don’t see what the new database in HRD has to do with my issue. 

I do have a problem with logs getting to HRD from JTALERT. However until I can get data to JTALERT the HRD issue is immaterial. 



Monty Wilson

On Feb 3, 2021, at 1:29 AM, neil_zampella <neilz@...> wrote:



FWIW ... the answer can be found on the JT-Alert groups.io support group, not here as it really does not pertain to WSJT-X other than it originates the Log UDP message.

Apparently, the answer is to create a NEW database in HRD, and import your log from the old DB.   When you do that DO NOT create an access database, create one in Maria DB.   For two reasons, its a real SQL database, and it can handle many more records.

You can find out more about this on the hamapps.groups.io support list.

Neil, KN3ILZ

On 2/2/2021 10:13 PM, Monty Wilson wrote:

Yesterday, I downloaded and successfully loaded WSJT-X V 2.3.0.  On my first try I did not have a connection to JTALERT.  I was told about the new loopback option and once set, WSJT-X was communicating with JTALERT.  I was able to interact with calls on JTALERT and make contacts without any issues.  However, I found that JTALERT would not write logs to my local HRD log.

 

I spent this morning troubleshooting that issue without success and eventually shut everything down to take a lunch break.

 

I think started my HRD (version) 6.7.0.323, followed by WSJT-X (version 2.3.0) and then JTALERT (V 2.16.17).  For unknown reasons, I have now lost the link between WSJT-X and JTALERT. 

 

I have checked the settings in WSJT-X (I use multicast) and JTALERT.  All of the settings look correct.  The only error message I see is

 

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

 

WSJT-X Detected Instance...

  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

 

Decode alerts and logging will be unavailable until corrected.

 

JTALERT about shows:

 

JTAlert Instance      : #1

JTAlert Start Params  : /wsjtx

WSJT-X Window Title   : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN

WSJT-X Command Line   : "C:\WSJT\wsjtx\bin\wsjtx.exe"

WSJT-X   --rig-name   :

WSJT-X Config File    : C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Version               :

WSJT-X Revision              :

WSJT-X Spec Op Mode          : None

WSJT-X UDP ID                :

WSJT-X UDP Port              : 2333

WSJT-X UDP Server            : 239.255.0.0

WSJT-X UDP MCast on Loopback : True

WSJT-X UDP Max Schema        :

 

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe           : 54408 65471

JTAlertV2.Manager.exe : 62581 62582

JTAlertV2.Decodes.exe :

 

In background, I have been running 2.2.2 since it was released.  I was successful in connecting to JTALERT and JTALERT to HRD for logging.  For some reason, since I loaded 2.3.0 I have had problems with the connections.

 

I don’t know where to look to troubleshoot.  All of the configuration points (as far as I know) are set the same as 2.2.2 with the exception of the new Loopback field.  I am looking for ideas.

 

I may try to revert back to 2.2.2 to see if that will get me started again.

 

Thanks in advance

 

Monty, NR0A

jwilson16@...

 







locked Re: Version 2.3.0 64 bit will not install #install

neil_zampella
 

What are you using for an antivirus?   Are you sure you're getting a good download? 

Neil, KN3ILZ

On 2/3/2021 12:14 PM, William Perry wrote:
I can’t install 2.3 either on Windows 10
N3VEZ 

On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:
I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH




locked Re: #logging #logging

David Ackrill
 

Thanks Neil,

Does that mean an update to ADIF will be available to logging programs as well?  If so, I'll email the guy who wrote the one I use and see if he has been able to get an update.

Cheers - Dave (G0DJA)


locked Re: Version 2.3.0 64 bit will not install #install

Bob Lewis
 

My Norton antivirus blocked it as “too new” and a potential threat. I just selected “install anyway” and it installed and runs fine on Windows 10. This is pretty safe if you know that you have downloaded it directly from the WSJT web site.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of William Perry
Sent: Wednesday, February 03, 2021 1:15 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Version 2.3.0 64 bit will not install #install

 

I can’t install 2.3 either on Windows 10

N3VEZ 

On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:

I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH


locked Re: Version 2.3.0 64 bit will not install #install

William Perry
 

I can’t install 2.3 either on Windows 10
N3VEZ 


On Wednesday, February 3, 2021, Gary Liebisch <glieb01@...> wrote:
I have instead found a copy of 2.2.1 and it installs fine. No uninstall. So I went from 2.1.2 to 2.2.1 without issue, then I tried 2.3.0 again with a fresh download and it still fails to do anything. So obviously there is something different about the 2.3.0 install.  I am going to sit this one out, satisfied for the time being with 2.2.1 and perhaps try again at later date. Perhaps someone else will find and contribute to a solution. Thanks.
--
Gary Liebisch
W8GEL
Powell, OH

13921 - 13940 of 35419