Date   

locked Re: Problem with 2.5.0 setup #install #Windows07

chas cartmel
 

Agreed.
Added to that is the issue that some software or peripherals  requires runtimes or drivers which are installed with Windows 10 but need to be sourced and installed separately for earlier editions of the OS, and this can cause other issues as well as being more complicated than the Windows 10 upgrade itself. There is no guarantee than some newer products will even work with windows 7, especially as windows 11 is imminent.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Pietro Molina
Sent: 29 September 2021 12:05
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Problem with 2.5.0 setup #install #Windows07

 

Hi Tom, you're right, no flame.

 

I don't understand why people that have W7 on their PC do not upgrade. W10 is less demanding, so if the PC is not very very old (born with XP, I mean), it will run better, in our experience.

Despite Microsoft offering (with payment) an EOS, our privacy & security supervisor wanted us to move to W10. Good experience, however. Free of charge.

 

73

 

I2OIM

 

 

Il giorno mer 29 set 2021 alle ore 11:20 Tom Melvin <tom@...> ha scritto:

Hi Pietro

 

Don’t want to start an flame but …

 

For Windows 7 Home and general users you are correct in saying EOS was Jan 2020 BUT FYI if you have the Extended Security Updates (ESU) package it can be up to another three years - support to Jan 10th 2023

 

 

Downside it does cost but many organisation have a Volume Licences  for internal/staff  use so it does depend on your company and or resources.  This is Win 7 Pro / Enterprise.

 

While this applies just to security fixes - as  99% of Windows 7 programs are stable and if there was going to be an issue it would have been resolved. 

 

You should really quantify any EOS comment made, they don’t apply across the board. Majority of users yes but not all.

 

Have a good day 

 

Regards and 73

 

Tom

GM8MJV

 



On 28 Sep 2021, at 19:03, Pietro Molina <pietro@...> wrote:

 

Your mind. Windows 7 support ended on 2020, January.
I know that a lot of people has W7 running (my company ha a couple, too) bu support is ended and I bet that prog does not try setup on w7.

Pietro I2OIM

PS: for the second, wait for reply... a lot of time I had that problem with SW that does not install in program (x86) directory.

 




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


locked Re: Problem with 2.5.0 setup #install #Windows07

Pietro Molina
 

Hi Tom, you're right, no flame.

I don't understand why people that have W7 on their PC do not upgrade. W10 is less demanding, so if the PC is not very very old (born with XP, I mean), it will run better, in our experience.
Despite Microsoft offering (with payment) an EOS, our privacy & security supervisor wanted us to move to W10. Good experience, however. Free of charge.

73

I2OIM


Il giorno mer 29 set 2021 alle ore 11:20 Tom Melvin <tom@...> ha scritto:
Hi Pietro

Don’t want to start an flame but …

For Windows 7 Home and general users you are correct in saying EOS was Jan 2020 BUT FYI if you have the Extended Security Updates (ESU) package it can be up to another three years - support to Jan 10th 2023


Downside it does cost but many organisation have a Volume Licences  for internal/staff  use so it does depend on your company and or resources.  This is Win 7 Pro / Enterprise.

While this applies just to security fixes - as  99% of Windows 7 programs are stable and if there was going to be an issue it would have been resolved. 

You should really quantify any EOS comment made, they don’t apply across the board. Majority of users yes but not all.

Have a good day 

Regards and 73

Tom
GM8MJV


On 28 Sep 2021, at 19:03, Pietro Molina <pietro@...> wrote:

Your mind. Windows 7 support ended on 2020, January.
I know that a lot of people has W7 running (my company ha a couple, too) bu support is ended and I bet that prog does not try setup on w7.

Pietro I2OIM

PS: for the second, wait for reply... a lot of time I had that problem with SW that does not install in program (x86) directory.







locked Re: Error while opening the program: (invalid ADIF header). #IssueReport

Dave Garber
 

sounds like you are running/installing an older version...

Dave Garber
VE3WEJ / VE3IE


On Wed, Sep 29, 2021 at 2:49 AM cfs176 via groups.io <cfs176=yahoo.com@groups.io> wrote:
Adding the "o" totally fixed my ADIF log problem. Thanks!



locked Re: Problem with 2.5.0 setup #install #Windows07

Tom Melvin
 

Hi Pietro

Don’t want to start an flame but …

For Windows 7 Home and general users you are correct in saying EOS was Jan 2020 BUT FYI if you have the Extended Security Updates (ESU) package it can be up to another three years - support to Jan 10th 2023


Downside it does cost but many organisation have a Volume Licences  for internal/staff  use so it does depend on your company and or resources.  This is Win 7 Pro / Enterprise.

While this applies just to security fixes - as  99% of Windows 7 programs are stable and if there was going to be an issue it would have been resolved. 

You should really quantify any EOS comment made, they don’t apply across the board. Majority of users yes but not all.

Have a good day 

Regards and 73

Tom
GM8MJV


On 28 Sep 2021, at 19:03, Pietro Molina <pietro@...> wrote:

Your mind. Windows 7 support ended on 2020, January.
I know that a lot of people has W7 running (my company ha a couple, too) bu support is ended and I bet that prog does not try setup on w7.

Pietro I2OIM

PS: for the second, wait for reply... a lot of time I had that problem with SW that does not install in program (x86) directory.




Karza
 

On 29.9.2021 0.51, Inbody, Don via groups.io wrote:
What happens, if anything, if I change the TX # in mid-transmission. Does that change the current ongoing transmission or just the next one?
--
Don Inbody AD0K
EM10bc
Buda, TX
Don,  answer to your question is in the user guide:

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.0.html#CONTROLS_MSGS

73's de Kari, oh2gqc


locked Re: Error while opening the program: (invalid ADIF header). #IssueReport

cfs176@...
 

Adding the "o" totally fixed my ADIF log problem. Thanks!


locked Re: Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport [edited] #IssueReport

Sam Birnbaum
 


Hi Chuck,

Actually in all previous (prior to 2.5 xx) I only had the "Log Automatically" checked.
When not in contest mode, it still popped up the Log QSO prompt screen.
It was with new version where if you did not have the "Prompt me to log"  checked
the prompt did not pop up. According to Bill, they fixed a defect that from 
my view point was actually a better implementation.

73, 

Sam W2JDB



-----Original Message-----
From: Chuck Adams <cfadams@...>
To: main@WSJTX.groups.io
Sent: Tue, Sep 28, 2021 6:02 pm
Subject: [WSJTX] Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport

I performed the latest update to WSJT-X and did the JTAlert update to 2.50.6 just now.
 
All is well on the JTAlert side so far.  😊
 
However, I DID notice that the WSJT-X update unexpectedly changed this setting:
 
Reporting > Logging > Prompt me to log QSO (check box)
(This box WAS checked in previous version but WAS unchecked after update)

Reporting > Logging > Log automatically (contesting only) (check box)
(This box WAS NOT checked in previous version but WAS checked after update)
 
This “setting flip” resulted in me suddenly not being automatically prompted after I finished QSOs (as I had done for many years previously)
 
I finally spotted the unexpected change in WSJT-X and corrected it.
 
This is a minor glitch to be sure, but one that might be worth noting for those who are updating WSJT-X.
 
Has anyone else seen this unexpected behavior from WSJT-X?
 
73,
 
Chuck Adams
KV4VT







Inbody, Don
 

What happens, if anything, if I change the TX # in mid-transmission. Does that change the current ongoing transmission or just the next one?
--
Don Inbody AD0K
EM10bc
Buda, TX


locked Re: 2.5.0 RC6 issue #Linux and K3 #linux #Elecraft

Bill Carpenter
 

I loaded v2.5.0 and the problem is no longer an issue.

Thanks to all of you!

73, Bill NZ0T


locked Re: Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport

JTAlert Support (VK3AMA)
 

On 29/09/2021 8:02 am, Chuck Adams wrote:

I performed the latest update to WSJT-X and did the JTAlert update to 2.50.6 just now.

 

All is well on the JTAlert side so far.  😊

 

However, I DID notice that the WSJT-X update unexpectedly changed this setting:

 

Reporting > Logging > Prompt me to log QSO (check box)
(This box WAS checked in previous version but WAS unchecked after update)

Reporting > Logging > Log automatically (contesting only) (check box)
(This box WAS NOT checked in previous version but WAS checked after update)

 

This “setting flip” resulted in me suddenly not being automatically prompted after I finished QSOs (as I had done for many years previously)

 

I finally spotted the unexpected change in WSJT-X and corrected it.

 

This is a minor glitch to be sure, but one that might be worth noting for those who are updating WSJT-X.

 

Has anyone else seen this unexpected behavior from WSJT-X?

 

73,

 

Chuck Adams

KV4VT


Chuck,

The "Prompt me to log QSO" setting didn't become unchecked when I did the 2.5.0 upgrade, BUT, I notice that the two "
Prompt me to log QSO" & "Log automatically (contesting only)" check-boxes are behaving like radio-buttons being mutually exclusive in operation. Tick one and the other becomes un-ticked, it is impossible to have both ticked at the same time..

Looks like a regression to me. Having WSJTX set to auto-log Contest QSOs should not be affecting the non-contest mode auto-prompting setting. IMHO.

de Laurie VK3AMA


locked Re: Now getting shared memory error on iMac with wsjtx 2.4 #macOS #install

Joe Burnham
 

THANKS Bill.  I will grab version 2.5 and hopefully that will fix things.
73, Joe WD4KAV


locked Re: Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport

Sam Birnbaum
 

Hi Chuck,

Actually in all previous (prior to 2.5 xx) I only had the "Log Automatically" checked.
When not in contest mode, it still popped up the Log QSO prompt screen.
It was with new version where if you did not have the "Prompt me to log"  
the prompt did not pop up. According to Bill, they fixed a defect that from 
my view point was actually a better implementation.

73, 

Sam W2JDB



-----Original Message-----
From: Chuck Adams <cfadams@...>
To: main@WSJTX.groups.io
Sent: Tue, Sep 28, 2021 6:02 pm
Subject: [WSJTX] Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport

I performed the latest update to WSJT-X and did the JTAlert update to 2.50.6 just now.
 
All is well on the JTAlert side so far.  😊
 
However, I DID notice that the WSJT-X update unexpectedly changed this setting:
 
Reporting > Logging > Prompt me to log QSO (check box)
(This box WAS checked in previous version but WAS unchecked after update)

Reporting > Logging > Log automatically (contesting only) (check box)
(This box WAS NOT checked in previous version but WAS checked after update)
 
This “setting flip” resulted in me suddenly not being automatically prompted after I finished QSOs (as I had done for many years previously)
 
I finally spotted the unexpected change in WSJT-X and corrected it.
 
This is a minor glitch to be sure, but one that might be worth noting for those who are updating WSJT-X.
 
Has anyone else seen this unexpected behavior from WSJT-X?
 
73,
 
Chuck Adams
KV4VT




locked Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport

Chuck Adams
 

I performed the latest update to WSJT-X and did the JTAlert update to 2.50.6 just now.

 

All is well on the JTAlert side so far.  😊

 

However, I DID notice that the WSJT-X update unexpectedly changed this setting:

 

Reporting > Logging > Prompt me to log QSO (check box)
(This box WAS checked in previous version but WAS unchecked after update)

Reporting > Logging > Log automatically (contesting only) (check box)
(This box WAS NOT checked in previous version but WAS checked after update)

 

This “setting flip” resulted in me suddenly not being automatically prompted after I finished QSOs (as I had done for many years previously)

 

I finally spotted the unexpected change in WSJT-X and corrected it.

 

This is a minor glitch to be sure, but one that might be worth noting for those who are updating WSJT-X.

 

Has anyone else seen this unexpected behavior from WSJT-X?

 

73,

 

Chuck Adams

KV4VT


locked Re: Pi4 HAMLIB error message WSJT-X #install #WSJTX_config #raspberryPi #Yaesu

Andy Talbot
 

This reference to PI4 is confusing - I read it initially as a reference to the beacon modulation, PI4, developed loosely from JT4G specifically for beacon idents on a faster cycle than JT4G could offer.  https://www.rudius.net/oz2m/ngnb/pi4.htm

Was wondering what it was doing appearing in this Group :-)
Then realised you meant the fruity 3.1416 version


locked Re: Now getting shared memory error on iMac with wsjtx 2.4 #macOS #install

Bill Somerville
 

On 28/09/2021 20:20, Joe Burnham wrote:
Since installing WSJTX 2.4 on my iMac (Intel chipset, 16 G RAM) , if I shut down, and power back up, when trying to run WSJTX I get the "Shared Memory Error".  Yes I did the necessary "copy and paste" from Terminal during initial install to set aside the memory, and verified that the location was correct

The only fix is to re-run the settings from terminal.  Is there a fix for this?

73, Joe WD4KAV
Hi Joe,

the current release of WSJT-X, v2.5.0, has a new procedure for configuring the macOS shared memory parameters. It is documented in the ReadMe.txt file at the top of the installer DMG. This method should persist across o/s upgrades and works on M1 hardware as well.

73
Bill
G4WJS.


locked Now getting shared memory error on iMac with wsjtx 2.4 #macOS #install

Joe Burnham
 

Since installing WSJTX 2.4 on my iMac (Intel chipset, 16 G RAM) , if I shut down, and power back up, when trying to run WSJTX I get the "Shared Memory Error".  Yes I did the necessary "copy and paste" from Terminal during initial install to set aside the memory, and verified that the location was correct

The only fix is to re-run the settings from terminal.  Is there a fix for this? 

73, Joe WD4KAV


locked Re: Pi4 HAMLIB error message WSJT-X #install #WSJTX_config #raspberryPi #Yaesu

Michael Salmi
 

I hope the attached settings for the radio work for you.  I use a Mac, but the radio menu settings are the same for Windows.

--
Mike Salmi, N9MDS


locked Re: General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

Paul Turner
 

2.5.0 installed smoothly and easily – as ever. Thanks to all the developers.

 

73, Paul G4IJE.

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Chuck Adams
Sent: 28 September 2021 03:03
To: main@WSJTX.groups.io
Subject: [WSJTX] General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo

 

From K1JT:

We are pleased to announce the General Availability (GA) release of WSJT-X version 2.5.0. New features are described in the WSJT-X User Guide here:

and also Release Notes:

On Windows platforms, WSJT-X 2.5 includes MAP65 3.0.0, a wideband polarization-matching tool intended for EME.

Links to WSJT-X 2.5.0 installation packages for Windows, Linux, and Macintosh are available here:

You can also download the packages from our SourceForge site:

It may take a short time for the SourceForge site to be updated.

WSJT-X for Windows now ships with Hamlib built as a dynamic link library (DLL). This change will allow Hamlib bug fixes to be resolved by replacing the DLL with an updated version.


Virus-free. www.avast.com


locked Re: Problem with 2.5.0 setup #install #Windows07

Bob Frostholm
 

Thanks Bill... problem solved

73

Bob

Ko6Lu
On 9/28/2021 10:54 AM, Bill Somerville via groups.io wrote:

On 28/09/2021 18:29, Bob Frostholm wrote:

Tried to load WSJT-X v2.5.0 and I get the following:

<snipped images>
-rc5 is working fine

win 7 Ultimate, 64 bit,

Help please

-- 
73

Bob

Ko6Lu

Hi Bob,

you must close down WSJT-X before trying to install an update. Try the update again and it should be fine.

73
Bill
G4WJS.





locked Re: Problem with 2.5.0 setup #install #Windows07

Pietro Molina
 

Your mind. Windows 7 support ended on 2020, January.
I know that a lot of people has W7 running (my company ha a couple, too) bu support is ended and I bet that prog does not try setup on w7.

Pietro I2OIM

PS: for the second, wait for reply... a lot of time I had that problem with SW that does not install in program (x86) directory.

8141 - 8160 of 36959