Date   
Re: TQSL 2.5 Release now available

Rick Murphy
 

This has been covered repeatedly in the past. If the update within
TQSL fails, go to http://www.arrl.org/tqsl-download and download the
installer. Double click it and it should install.

If that doesn't work, then details, please.
73,
-Rick

On Thu, Nov 14, 2019 at 10:20 PM Ing. Edgardo Bonion Alves Rolo
<ebonion@...> wrote:

Hello Friend´s



Mi name is Eddy



I could never install version 2.4.7 every time it starts I ask to update but it never updates, gives error, win 10





Tks Greeting



Eddy

XE2OCM and LW1EB



Enviado desde Correo para Windows 10



De: Rick Murphy
Enviado: jueves, 14 de noviembre de 2019 14:50
Para: ARRL-LoTW@...
Asunto: Re: [ARRL-LoTW] TQSL 2.5 Release now available



The 2.5 release hasn't been picked up by ARRL yet (fortunately, given

the INVALID ENTITY botch).

73,

-Rick



On Thu, Nov 14, 2019 at 3:49 PM Wes Attaway (N5WA)

<wesattaway@...> wrote:

Same here. Good question.
-------------------
Wes Attaway (N5WA)
(318) 393-3289 - Shreveport, LA
Computer/Cellphone Forensics
AttawayForensics.com
-------------------
________________________________
From: ARRL-LoTW@... [mailto:ARRL-LoTW@...] On Behalf Of K8BL BOB LIDDY
Sent: Thursday, November 14, 2019 2:38 PM
To: arrl-lotw@...; ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available
My TQSL is 2.4.7 and "Check for Updates" says I already
have the latest version. And, I'm seeing posts from people
having problems with the Beta 2.5. Is there a compelling
need to go to 2.5 before all the problems are ironed out?
TNX/73, Bob K8BL
On Wednesday, November 13, 2019, 12:11:17 PM EST, iain macdonnell - N6ML <@N6ML> wrote:
Hi Jason.
You're not stupid. Rick was just asking for clarifying information.
I just reproduced the problem that you describe. My regular N6ML cert
was showing the correct DXCC entity prior to installing TQSL 2.5. Now
it shows "<UNKNOWN ENTITY>".
73,
~iain / N6ML
On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
Jason Bowen, KB5VXX
On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
Just curious, is there any support for this version yet at the ARRL LOTW help email?
I'm not sure what you're asking here about the "help e-mail" - do you
mean a way to send a mail by clicking some link in TQSL? If so, that's
actually pretty difficult to do.
I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
That's going to need some more information.
You can request a Callsign Certificate with DXCC entity set to "None",
which is what you would do for things like a Maritime Mobile operation
where there's no valid DXCC entity for the operation.
Did you do that? If so, why? And why are you not understanding why you
chose that?
TQSL displays a long warning about that choice - "will not be valid
for DXCC award credit ..." so, why did you choose that and not
understand that it's not valid for DXCC credit and only valid for MM,
Shipboard, or air mobile as described?
73,
-Rick






--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA









--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

"Broken" is rather unspecific :)

I know it works up through Catalina. All I can assume is that you're
trying to install the unsigned installer and the OS is blocking it.

73,
-Rick

On Thu, Nov 14, 2019 at 10:20 PM dalzellf via Groups.Arrl.Org
<dalzellf=mac.com@...> wrote:

Broken on Mac OS 10.13.6 (High Sierra (64-bit). Reverting to 2.4.7 resolves the issue.

Fred KI7BCL


--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Ing. Edgardo Bonion Alves Rolo
 

Hello Friend´s

 

Mi name is Eddy

 

I could never install version 2.4.7 every time it starts I ask to update but it never updates, gives error, win 10

 

 

Tks Greeting

 

Eddy

XE2OCM and LW1EB

 

Enviado desde Correo para Windows 10

 

De: Rick Murphy
Enviado: jueves, 14 de noviembre de 2019 14:50
Para: ARRL-LoTW@...
Asunto: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

The 2.5 release hasn't been picked up by ARRL yet (fortunately, given

the INVALID ENTITY botch).

73,

    -Rick

 

On Thu, Nov 14, 2019 at 3:49 PM Wes Attaway (N5WA)

<wesattaway@...> wrote:

> Same here.  Good question.

>    -------------------

> Wes Attaway (N5WA)

> (318) 393-3289 - Shreveport, LA

> Computer/Cellphone Forensics

> AttawayForensics.com

>    -------------------

> ________________________________

> From: ARRL-LoTW@... [mailto:ARRL-LoTW@...] On Behalf Of K8BL BOB LIDDY

> Sent: Thursday, November 14, 2019 2:38 PM

> To: arrl-lotw@...; ARRL-LoTW@...

> Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

> My TQSL is 2.4.7 and "Check for Updates" says I already

> have the latest version. And, I'm seeing posts from people

> having problems with the Beta 2.5. Is there a compelling

> need to go to 2.5 before all the problems are ironed out?

> TNX/73, Bob K8BL

> On Wednesday, November 13, 2019, 12:11:17 PM EST, iain macdonnell - N6ML <ar@...> wrote:

> Hi Jason.

> You're not stupid. Rick was just asking for clarifying information.

> I just reproduced the problem that you describe. My regular N6ML cert

> was showing the correct DXCC entity prior to installing TQSL 2.5. Now

> it shows "<UNKNOWN ENTITY>".

> 73,

>     ~iain / N6ML

> On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:

> >

> > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.

> >

> > Jason Bowen, KB5VXX

> >

> > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:

> >>

> >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:

> >> >

> >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?

> >>

> >> I'm not sure what you're asking here about the "help e-mail"  - do you

> >> mean a way to send a mail by clicking some link in TQSL? If so, that's

> >> actually pretty difficult to do.

> >>

> >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.

> >>

> >> That's going to need some more information.

> >>

> >> You can request a Callsign Certificate with DXCC entity set to "None",

> >> which is what you would do for things like a Maritime Mobile operation

> >> where there's no valid DXCC entity for the operation.

> >> Did you do that? If so, why? And why are you not understanding why you

> >> chose that?

> >>

> >> TQSL displays a long warning about that choice - "will not be valid

> >> for DXCC award credit ..." so, why did you choose that and not

> >> understand that it's not valid for DXCC credit and only valid for MM,

> >> Shipboard, or air mobile as described?

> >> 73,

> >>    -Rick

> >>

> >>

> >>

> >

>

 

 

 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

 

 

 

Re: TQSL 2.5 Release now available

dalzellf@...
 

Broken on Mac OS 10.13.6  (High Sierra (64-bit). Reverting to 2.4.7 resolves the issue.

Fred KI7BCL

Re: TQSL 2.5 Release now available

Gary Hinson
 

Cool! Thanks Rick, and thanks of course for maintaining the software.

73
Gary ZL2iFB

-----Original Message-----
From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 15 November 2019 09:50
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

On Thu, Nov 14, 2019 at 3:19 PM Gary Hinson <Gary@...> wrote:

Oh.



Given that the [main] ARRL reflectors are now consolidated under Groups.IO, and since TQSL is clearly relevant to the LoTW reflector, I’ll repeat my suggestion to post info about planned changes to TQSL, and invitations to beta-test them, right here – maybe not every detail (the sourceforge reflector still makes sense for that), just the occasional update or reminder would be nice. Please.

You mean like I've always done? :)
Every release candidate is announced here. Generally early releases (i.e. beta) go to the sourceforge reflector.
73,
-Rick



73

Gary ZL2iFB



From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf
Of Rick Murphy
Sent: 15 November 2019 03:10
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available



Actually, that's a closed list.



The right list is trustedqsl-testing@...

Subscribe at
https://sourceforge.net/p/trustedqsl/mailman/trustedqsl-testing/

73,

-Rick





On Wed, Nov 13, 2019 at 10:45 PM Rick Murphy <k1mu.nospam@...> wrote:

The early releases are posted to the "tqsl-beta@..." mailing list.

73,

-Rick



On Wed, Nov 13, 2019 at 10:27 PM Jason B <sydbowen@...> wrote:

I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX



On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.



I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.



Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.



Will you be announcing betas on the LoTW reflector in future? You have a pool of potential crash test dummies right here!



73

Gary ZL2iFB



From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf
Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available



So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.



Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.



I've built a 2.5.1 release with this fix in place. Usual place:



https://www.rickmurphy.net/lotw/tqsl-2.5.1.msi (Windows)

https://www.rickmurphy.net/lotw/tqsl-2.5.1.dmg (Mac 64-bit)

https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.1.msi (Legacy Mac)

https://www.rickmurphy.net/lotw/tqsl-2.5.1.tar.gz (Linux, BSD)



73,

-Rick





On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen.
At the moment, I suggest not installing 2.5 while I investigate.

73,

-Rick



On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs.

I'll let y'all know if I can figure out the cause.

73,

-Rick



On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <@Tex> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf
Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available





On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....





73,



~iain / N6ML





On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:

Well, damn. Where are you seeing this? Mine are showing as "UNITED
STATES OF AMERICA" when I display the callsign certificate properties.
73,
-Rick

On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <@N6ML> wrote:

Hi Jason.

You're not stupid. Rick was just asking for clarifying information.

I just reproduced the problem that you describe. My regular N6ML
cert was showing the correct DXCC entity prior to installing TQSL
2.5. Now it shows "<UNKNOWN ENTITY>".

73,

~iain / N6ML


On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:

Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.

Jason Bowen, KB5VXX

On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:

On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:

Just curious, is there any support for this version yet at the ARRL LOTW help email?
I'm not sure what you're asking here about the "help e-mail" -
do you mean a way to send a mail by clicking some link in TQSL?
If so, that's actually pretty difficult to do.

I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
That's going to need some more information.

You can request a Callsign Certificate with DXCC entity set to
"None", which is what you would do for things like a Maritime
Mobile operation where there's no valid DXCC entity for the operation.
Did you do that? If so, why? And why are you not understanding
why you chose that?

TQSL displays a long warning about that choice - "will not be
valid for DXCC award credit ..." so, why did you choose that
and not understand that it's not valid for DXCC credit and only
valid for MM, Shipboard, or air mobile as described?
73,
-Rick




--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA





--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Wes Attaway (N5WA)
 

OK Rick. Thanks for the info and your attention to all this.

-------------------
Wes Attaway (N5WA)
(318) 393-3289 - Shreveport, LA
Computer/Cellphone Forensics
AttawayForensics.com
-------------------

-----Original Message-----
From: ARRL-LoTW@... [mailto:ARRL-LoTW@...] On Behalf
Of Rick Murphy
Sent: Thursday, November 14, 2019 2:51 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

The 2.5 release hasn't been picked up by ARRL yet (fortunately, given
the INVALID ENTITY botch).
73,
-Rick

On Thu, Nov 14, 2019 at 3:49 PM Wes Attaway (N5WA)
<wesattaway@...> wrote:

Same here. Good question.



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

Wes Attaway (N5WA)

(318) 393-3289 - Shreveport, LA

Computer/Cellphone Forensics

AttawayForensics.com

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

________________________________

From: ARRL-LoTW@... [mailto:ARRL-LoTW@...] On
Behalf Of K8BL BOB LIDDY
Sent: Thursday, November 14, 2019 2:38 PM
To: arrl-lotw@...; ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available



My TQSL is 2.4.7 and "Check for Updates" says I already
have the latest version. And, I'm seeing posts from people
having problems with the Beta 2.5. Is there a compelling
need to go to 2.5 before all the problems are ironed out?

TNX/73, Bob K8BL

On Wednesday, November 13, 2019, 12:11:17 PM EST, iain macdonnell - N6ML
<@N6ML> wrote:





Hi Jason.

You're not stupid. Rick was just asking for clarifying information.

I just reproduced the problem that you describe. My regular N6ML cert
was showing the correct DXCC entity prior to installing TQSL 2.5. Now
it shows "<UNKNOWN ENTITY>".

73,

~iain / N6ML


On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:

Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll
just email ARRL at the LOTW help email account.

Jason Bowen, KB5VXX

On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:

On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:

Just curious, is there any support for this version yet at the ARRL
LOTW help email?

I'm not sure what you're asking here about the "help e-mail" - do you
mean a way to send a mail by clicking some link in TQSL? If so, that's
actually pretty difficult to do.

I have a certificate issue I just noticed. The dxcc entity says
"unknown" on the certificate select panel, and when you go to the
certificate properties it says none under dxcc entity.

That's going to need some more information.

You can request a Callsign Certificate with DXCC entity set to "None",
which is what you would do for things like a Maritime Mobile operation
where there's no valid DXCC entity for the operation.
Did you do that? If so, why? And why are you not understanding why you
chose that?

TQSL displays a long warning about that choice - "will not be valid
for DXCC award credit ..." so, why did you choose that and not
understand that it's not valid for DXCC credit and only valid for MM,
Shipboard, or air mobile as described?
73,
-Rick





--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

The 2.5 release hasn't been picked up by ARRL yet (fortunately, given
the INVALID ENTITY botch).
73,
-Rick

On Thu, Nov 14, 2019 at 3:49 PM Wes Attaway (N5WA)
<wesattaway@...> wrote:

Same here. Good question.



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

Wes Attaway (N5WA)

(318) 393-3289 - Shreveport, LA

Computer/Cellphone Forensics

AttawayForensics.com

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

________________________________

From: ARRL-LoTW@... [mailto:ARRL-LoTW@...] On Behalf Of K8BL BOB LIDDY
Sent: Thursday, November 14, 2019 2:38 PM
To: arrl-lotw@...; ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available



My TQSL is 2.4.7 and "Check for Updates" says I already
have the latest version. And, I'm seeing posts from people
having problems with the Beta 2.5. Is there a compelling
need to go to 2.5 before all the problems are ironed out?

TNX/73, Bob K8BL

On Wednesday, November 13, 2019, 12:11:17 PM EST, iain macdonnell - N6ML <@N6ML> wrote:





Hi Jason.

You're not stupid. Rick was just asking for clarifying information.

I just reproduced the problem that you describe. My regular N6ML cert
was showing the correct DXCC entity prior to installing TQSL 2.5. Now
it shows "<UNKNOWN ENTITY>".

73,

~iain / N6ML


On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:

Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.

Jason Bowen, KB5VXX

On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:

On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:

Just curious, is there any support for this version yet at the ARRL LOTW help email?
I'm not sure what you're asking here about the "help e-mail" - do you
mean a way to send a mail by clicking some link in TQSL? If so, that's
actually pretty difficult to do.

I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
That's going to need some more information.

You can request a Callsign Certificate with DXCC entity set to "None",
which is what you would do for things like a Maritime Mobile operation
where there's no valid DXCC entity for the operation.
Did you do that? If so, why? And why are you not understanding why you
chose that?

TQSL displays a long warning about that choice - "will not be valid
for DXCC award credit ..." so, why did you choose that and not
understand that it's not valid for DXCC credit and only valid for MM,
Shipboard, or air mobile as described?
73,
-Rick





--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

On Thu, Nov 14, 2019 at 3:19 PM Gary Hinson <Gary@...> wrote:

Oh.



Given that the [main] ARRL reflectors are now consolidated under Groups.IO, and since TQSL is clearly relevant to the LoTW reflector, I’ll repeat my suggestion to post info about planned changes to TQSL, and invitations to beta-test them, right here – maybe not every detail (the sourceforge reflector still makes sense for that), just the occasional update or reminder would be nice. Please.

You mean like I've always done? :)
Every release candidate is announced here. Generally early releases
(i.e. beta) go to the sourceforge reflector.
73,
-Rick



73

Gary ZL2iFB



From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 15 November 2019 03:10
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available



Actually, that's a closed list.



The right list is trustedqsl-testing@...

Subscribe at https://sourceforge.net/p/trustedqsl/mailman/trustedqsl-testing/

73,

-Rick





On Wed, Nov 13, 2019 at 10:45 PM Rick Murphy <k1mu.nospam@...> wrote:

The early releases are posted to the "tqsl-beta@..." mailing list.

73,

-Rick



On Wed, Nov 13, 2019 at 10:27 PM Jason B <sydbowen@...> wrote:

I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX



On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.



I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.



Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.



Will you be announcing betas on the LoTW reflector in future? You have a pool of potential crash test dummies right here!



73

Gary ZL2iFB



From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available



So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.



Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.



I've built a 2.5.1 release with this fix in place. Usual place:



https://www.rickmurphy.net/lotw/tqsl-2.5.1.msi (Windows)

https://www.rickmurphy.net/lotw/tqsl-2.5.1.dmg (Mac 64-bit)

https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.1.msi (Legacy Mac)

https://www.rickmurphy.net/lotw/tqsl-2.5.1.tar.gz (Linux, BSD)



73,

-Rick





On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen.
At the moment, I suggest not installing 2.5 while I investigate.

73,

-Rick



On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs.

I'll let y'all know if I can figure out the cause.

73,

-Rick



On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <@Tex> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available





On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....





73,



~iain / N6ML





On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:

Well, damn. Where are you seeing this? Mine are showing as "UNITED
STATES OF AMERICA" when I display the callsign certificate properties.
73,
-Rick

On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <@N6ML> wrote:

Hi Jason.

You're not stupid. Rick was just asking for clarifying information.

I just reproduced the problem that you describe. My regular N6ML cert
was showing the correct DXCC entity prior to installing TQSL 2.5. Now
it shows "<UNKNOWN ENTITY>".

73,

~iain / N6ML


On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:

Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.

Jason Bowen, KB5VXX

On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:

On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:

Just curious, is there any support for this version yet at the ARRL LOTW help email?
I'm not sure what you're asking here about the "help e-mail" - do you
mean a way to send a mail by clicking some link in TQSL? If so, that's
actually pretty difficult to do.

I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
That's going to need some more information.

You can request a Callsign Certificate with DXCC entity set to "None",
which is what you would do for things like a Maritime Mobile operation
where there's no valid DXCC entity for the operation.
Did you do that? If so, why? And why are you not understanding why you
chose that?

TQSL displays a long warning about that choice - "will not be valid
for DXCC award credit ..." so, why did you choose that and not
understand that it's not valid for DXCC credit and only valid for MM,
Shipboard, or air mobile as described?
73,
-Rick




--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA





--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA




--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Wes Attaway (N5WA)
 

Same here.  Good question.

 

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

Wes Attaway (N5WA)

(318) 393-3289 - Shreveport, LA

Computer/Cellphone Forensics

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


From: ARRL-LoTW@... [mailto:ARRL-LoTW@...] On Behalf Of K8BL BOB LIDDY
Sent: Thursday, November 14, 2019 2:38 PM
To: arrl-lotw@...; ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

My TQSL is 2.4.7 and "Check for Updates" says I already
have the latest version. And, I'm seeing posts from people
having problems with the Beta 2.5. Is there a compelling
need to go to 2.5 before all the problems are ironed out?

TNX/73, Bob K8BL

On Wednesday, November 13, 2019, 12:11:17 PM EST, iain macdonnell - N6ML <ar@...> wrote:

 

 

Hi Jason.

You're not stupid. Rick was just asking for clarifying information.

I just reproduced the problem that you describe. My regular N6ML cert
was showing the correct DXCC entity prior to installing TQSL 2.5. Now
it shows "<UNKNOWN ENTITY>".

73,

    ~iain / N6ML


On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
>
> Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
>
> Jason Bowen, KB5VXX
>
> On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
>>
>> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
>> >
>> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
>>
>> I'm not sure what you're asking here about the "help e-mail"  - do you
>> mean a way to send a mail by clicking some link in TQSL? If so, that's
>> actually pretty difficult to do.
>>
>> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
>>
>> That's going to need some more information.
>>
>> You can request a Callsign Certificate with DXCC entity set to "None",
>> which is what you would do for things like a Maritime Mobile operation
>> where there's no valid DXCC entity for the operation.
>> Did you do that? If so, why? And why are you not understanding why you
>> chose that?
>>
>> TQSL displays a long warning about that choice - "will not be valid
>> for DXCC award credit ..." so, why did you choose that and not
>> understand that it's not valid for DXCC credit and only valid for MM,
>> Shipboard, or air mobile as described?
>> 73,
>>    -Rick
>>
>>
>>
>


Re: TQSL 2.5 Release now available

K8BL BOB LIDDY
 

My TQSL is 2.4.7 and "Check for Updates" says I already
have the latest version. And, I'm seeing posts from people
having problems with the Beta 2.5. Is there a compelling
need to go to 2.5 before all the problems are ironed out?

TNX/73, Bob K8BL

On Wednesday, November 13, 2019, 12:11:17 PM EST, iain macdonnell - N6ML <ar@...> wrote:


Hi Jason.

You're not stupid. Rick was just asking for clarifying information.

I just reproduced the problem that you describe. My regular N6ML cert
was showing the correct DXCC entity prior to installing TQSL 2.5. Now
it shows "<UNKNOWN ENTITY>".

73,

    ~iain / N6ML


On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
>
> Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
>
> Jason Bowen, KB5VXX
>
> On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
>>
>> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
>> >
>> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
>>
>> I'm not sure what you're asking here about the "help e-mail"  - do you
>> mean a way to send a mail by clicking some link in TQSL? If so, that's
>> actually pretty difficult to do.
>>
>> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
>>
>> That's going to need some more information.
>>
>> You can request a Callsign Certificate with DXCC entity set to "None",
>> which is what you would do for things like a Maritime Mobile operation
>> where there's no valid DXCC entity for the operation.
>> Did you do that? If so, why? And why are you not understanding why you
>> chose that?
>>
>> TQSL displays a long warning about that choice - "will not be valid
>> for DXCC award credit ..." so, why did you choose that and not
>> understand that it's not valid for DXCC credit and only valid for MM,
>> Shipboard, or air mobile as described?
>> 73,
>>    -Rick
>>
>>
>>
>



Re: TQSL 2.5 Release now available

Gary Hinson
 

Oh. 

 

Given that the [main] ARRL reflectors are now consolidated under Groups.IO, and since TQSL is clearly relevant to the LoTW reflector, I’ll repeat my suggestion to post info about planned changes to TQSL, and invitations to beta-test them, right here – maybe not every detail (the sourceforge reflector still makes sense for that), just the occasional update or reminder would be nice.  Please. 

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 15 November 2019 03:10
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

Actually, that's a closed list.

 

The right list is trustedqsl-testing@...

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 10:45 PM Rick Murphy <k1mu.nospam@...> wrote:

The early releases are posted to the "tqsl-beta@..." mailing list.

73,

     -Rick

 

On Wed, Nov 13, 2019 at 10:27 PM Jason B <sydbowen@...> wrote:

I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX

 

On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

Actually, that's a closed list.

The right list is trustedqsl-testing@...
73,
    -Rick


On Wed, Nov 13, 2019 at 10:45 PM Rick Murphy <k1mu.nospam@...> wrote:
The early releases are posted to the "tqsl-beta@..." mailing list.
73,
     -Rick

On Wed, Nov 13, 2019 at 10:27 PM Jason B <sydbowen@...> wrote:
I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX

On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

tqsl.PNG

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Joe Roper
 

Thanks Rick, 2.5.1 fixed it for me

 

Joe

N7IHB

 


From: ARRL-LoTW@... <ARRL-LoTW@...> on behalf of Rick Murphy <k1mu.nospam@...>
Sent: Wednesday, November 13, 2019 8:45:02 PM
To: ARRL-LoTW@... <ARRL-LoTW@...>
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available
 
The early releases are posted to the "tqsl-beta@..." mailing list.
73,
     -Rick

On Wed, Nov 13, 2019 at 10:27 PM Jason B <sydbowen@...> wrote:
I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX

On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

tqsl.PNG

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

The early releases are posted to the "tqsl-beta@..." mailing list.
73,
     -Rick

On Wed, Nov 13, 2019 at 10:27 PM Jason B <sydbowen@...> wrote:
I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX

On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

tqsl.PNG

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Jason B
 

I had no idea that there is a beta program. Where do you find test releases?

Jason Bowen, KB5VXX

On Wed, Nov 13, 2019, 21:10 Gary Hinson <Gary@...> wrote:

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

Gary,
Yes , I do announce "Release candidates" here.  For example, 2.5-rc1 was released in September.
73,
    -Rick

On Wed, Nov 13, 2019 at 10:10 PM Gary Hinson <Gary@...> wrote:

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

tqsl.PNG

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Gary Hinson
 

Hi Rick.

 

I’d be happy to beta test – I already do for several other radio apps – and I’m sure others will too.

 

Somehow I missed the announcement & didn’t even know TQSL was out for beta testing.

 

Will you be announcing betas on the LoTW reflector in future?  You have a pool of potential crash test dummies right here!

 

73

Gary  ZL2iFB

 

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 14 November 2019 15:41
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

 

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

 

I've built a 2.5.1 release with this fix in place. Usual place:

 

 

73,

    -Rick

 

 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:

I'm at this point not able to reproduce this. Still looking.

It appears to be just the display having the problem, so you should still be able to submit logs. 

I'll let y'all know if I can figure out the cause.

73,

    -Rick

 

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

tqsl.PNG

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


 

--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

David Chema
 

Thank you Rick!  2.5.1 fixed it for me on Windows 10 64 bit, Version 1903 (OS Build 18362 .388).  I have just one certificate.

73,
Dave, KC8V


On Nov 13, 2019, at 9:40 PM, Rick Murphy <k1mu.nospam@...> wrote:


So, pretty easy fix. Sadly, having had a test release in the wild for a couple of months, nobody saw this defect. Which means that very few people ever tried the beta or release candidates.

Please, folks, consider spending the time to install test releases. Us folks with multiple callsign certificates probably didn't see this (I never did), but common cases with only one active certificate did. If more people had bothered to actually try test releases this could have been avoided. I just don't know how to get help here as I can't do it alone.

I've built a 2.5.1 release with this fix in place. Usual place:


73,
    -Rick
 

On Wed, Nov 13, 2019 at 5:03 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:
Interesting. Deleting everything but a single callsign certificate causes this to happen. 
At the moment, I suggest not installing 2.5 while I investigate.
73,
    -Rick

On Wed, Nov 13, 2019 at 3:42 PM Rick Murphy via Groups.Arrl.Org <k1mu.nospam=gmail.com@...> wrote:
I'm at this point not able to reproduce this. Still looking.
It appears to be just the display having the problem, so you should still be able to submit logs. 
I'll let y'all know if I can figure out the cause.
73,
    -Rick

On Wed, Nov 13, 2019 at 2:55 PM ROBERT NORRIS <rpnorris1@...> wrote:

Mine is showing <UNKNOWN ENTITY> as well and <NONE> for DXCC Entity.

Bob

AK5U

<image001.png>

From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of iain macdonnell - N6ML
Sent: Wednesday, November 13, 2019 12:54 PM
To: ARRL-LoTW@...
Subject: Re: [ARRL-LoTW] TQSL 2.5 Release now available

 

 

On the "Callsign Certificates" tab, the tree shows "N6ML - <UNKNOWN ENTITY>". In Certificate Properties, "DXCC Entity: <NONE>". I'll attach a screenshot if the group allows it.....

 

<image003.png>

 

73,

 

    ~iain / N6ML

 



On Wed, Nov 13, 2019 at 10:38 AM Rick Murphy <k1mu.nospam@...> wrote:
>
> Well, damn. Where are you seeing this? Mine are showing as "UNITED
> STATES OF AMERICA" when I display the callsign certificate properties.
> 73,
>     -Rick
>
> On Wed, Nov 13, 2019 at 12:11 PM iain macdonnell - N6ML <ar@...> wrote:
> >
> > Hi Jason.
> >
> > You're not stupid. Rick was just asking for clarifying information.
> >
> > I just reproduced the problem that you describe. My regular N6ML cert
> > was showing the correct DXCC entity prior to installing TQSL 2.5. Now
> > it shows "<UNKNOWN ENTITY>".
> >
> > 73,
> >
> >     ~iain / N6ML
> >
> >
> > On Wed, Nov 13, 2019 at 4:54 AM Jason B <sydbowen@...> wrote:
> > >
> > > Whoa, nevermind. Sorry I asked. I'm not stupid, something is wrong. I'll just email ARRL at the LOTW help email account.
> > >
> > > Jason Bowen, KB5VXX
> > >
> > > On Tue, Nov 12, 2019, 20:12 Rick Murphy <k1mu.nospam@...> wrote:
> > >>
> > >> On Tue, Nov 12, 2019 at 7:50 PM Jason B <sydbowen@...> wrote:
> > >> >
> > >> > Just curious, is there any support for this version yet at the ARRL LOTW help email?
> > >>
> > >> I'm not sure what you're asking here about the "help e-mail"  - do you
> > >> mean a way to send a mail by clicking some link in TQSL? If so, that's
> > >> actually pretty difficult to do.
> > >>
> > >> > I have a certificate issue I just noticed. The dxcc entity says "unknown" on the certificate select panel, and when you go to the certificate properties it says none under dxcc entity.
> > >>
> > >> That's going to need some more information.
> > >>
> > >> You can request a Callsign Certificate with DXCC entity set to "None",
> > >> which is what you would do for things like a Maritime Mobile operation
> > >> where there's no valid DXCC entity for the operation.
> > >> Did you do that? If so, why? And why are you not understanding why you
> > >> chose that?
> > >>
> > >> TQSL displays a long warning about that choice - "will not be valid
> > >> for DXCC award credit ..." so, why did you choose that and not
> > >> understand that it's not valid for DXCC credit and only valid for MM,
> > >> Shipboard, or air mobile as described?
> > >> 73,
> > >>     -Rick
> > >>
> > >>
> > >>
> > >
> >
> >
> >
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
>
>



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: DX unknown

Rick Murphy
 

This is one of those bugs that depends on what kind and how many
callsign certificates you have. It doesn't matter what OS you're
using.
I've fixed this and issued and a 2.5.1 released to correct the defect.
73,
-Rick

On Wed, Nov 13, 2019 at 2:08 PM Joe Subich, W4TV <lists@...> wrote:


*NOT* happening in Windows 10 Home build 18362.476

I have not updated my Windows 10 Pro systems as I was
waiting for the "automatic" update when ARRL signs
the files and placed them on-line.

73,

... Joe, W4TV


On 2019-11-13 1:49 PM, iain macdonnell - N6ML wrote:
On Wed, Nov 13, 2019 at 10:14 AM iain macdonnell - N6ML via
Groups.Arrl.Org <ar=dseven.org@...> wrote:

On Wed, Nov 13, 2019 at 9:58 AM Michael Keane, K1MK <@K1MK> wrote:

On 11/13/19 12:07 PM, iain macdonnell - N6ML via Groups.Arrl.Org wrote:

This appears to be a regression in TQSL 2.5. It was reported by
another user yesterday, and I confirm that I'm seeing it too.

73,

~iain / N6ML


Ian et al.,

First, thanks for reporting / confirming this

We can help Rick isolate this regression by providing additional details for those systems where the regression is present

FWIW the regression is not present on:

Windows 10 Pro 64 bit version 1903 build 18362.449

Mac OS 10.15.1

Fedora 31 (64 bit)

So it's not something that is present everywhere and had not been previously reported in the beta or release candidate testing
I've reproduced it on two different Windows 10 Pro 64-bit systems. One
is stuck on the old 1803 release (build 17134.1099). The other is
running a recent Windows Insider build - 19018.1.
Also now reproduced on Fedora 30.

73,

~iain / N6ML




--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: TQSL 2.5 Release now available

Rick Murphy
 

On Wed, Nov 13, 2019 at 8:23 PM Joe Roper <@n7ihb> wrote:

Wow!! Some people are grumpy.
Yeah, but it's a defect regardless. And, to be quite fair, I missed
the chance to fix this earlier by not understanding the problem when
it was first reported and posting my own grumpy reply.

Fail on my part, for which I apologize.
73,
-Rick



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA