Re: Hamlib error

Dave Garber

#28159

does your cat work on any other software? 991a has usb for cat, right? is it unplugged

Dave Garber

VE3WEJ / VE3IE

Show quoted text

On Sun, Mar 1, 2020 at 9:38 AM John Scheuer <na6y@...> wrote:

The rig is a FT-991A with a SignaLink USB. The OS is Win10. Been running the digital modes for a few years now. When I open JTAlert and WSJT-x I now get the message "Rig failure Hamlib error: I.O. error while trying to connect". When I click on "Test CAT" it goes red. Uninstalled and re-downloaded JTAlert to 2.15.11 and WSJT-x. NOTE: this problem started prior to the new revision. Up until the last couple of days I've never had any problems that were of any consequence. I've run into this before but it only took a COM port change to fix it. Obviously something has change but I sure can't find it. Would appreciate any suggestions. I don't know if this is where this should be posted but I am really at my wits end here.

Thanks, 73's
John NA6Y

Re: Hamapps web site is down

catfish3649

#28158

Still can't download database or sound.... Rich k4tft

Hamlib error

John

#28157

The rig is a FT-991A with a SignaLink USB. The OS is Win10. Been running the digital modes for a few years now. When I open JTAlert and WSJT-x I now get the message "Rig failure Hamlib error: I.O. error while trying to connect". When I click on "Test CAT" it goes red. Uninstalled and re-downloaded JTAlert to 2.15.11 and WSJT-x. NOTE: this problem started prior to the new revision. Up until the last couple of days I've never had any problems that were of any consequence. I've run into this before but it only took a COM port change to fix it. Obviously something has change but I sure can't find it. Would appreciate any suggestions. I don't know if this is where this should be posted but I am really at my wits end here.

Thanks, 73's
John NA6Y

Re: Download error

Michael Black

#28156

This should have your answer...

TLS security setting

Can’t connect securely to this page This might be because the site uses outdated or unsafe TLS security settings...

de Mike W9MDB

Show quoted text

On Sunday, March 1, 2020, 07:32:50 AM CST, km4djo@... <km4djo@...> wrote:

This morning I tried again, making sure that Firefox was updated to the latest version. i was able to download the callsign install, but when I clicked on the sounds, I got the following error. i then tried microsoft edge and google chrome and all 3 gave errors and would not allow me to download the sounds.

Microsoft edge error -

Can’t connect securely to this page

This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

Try this:

Go back to the last page

Google Chrome Error

This site can’t provide a secure connection

dnl.hamapps.com sent an invalid response.

Not sure what I am doing wrong, but figured I'd share the actual error messages just in case it helps.

Mark
KM4DJO

Re: Download error

km4djo

#28155

This morning I tried again, making sure that Firefox was updated to the latest version. i was able to download the callsign install, but when I clicked on the sounds, I got the following error. i then tried microsoft edge and google chrome and all 3 gave errors and would not allow me to download the sounds.

Microsoft edge error -

Can’t connect securely to this page

This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

Try this:

Go back to the last page

Google Chrome Error

This site can’t provide a secure connection

dnl.hamapps.com sent an invalid response.

Not sure what I am doing wrong, but figured I'd share the actual error messages just in case it helps.

Mark
KM4DJO

Amazing behaviour

F8RZ

#28154

Hello...

The ONLY Z61DX callsign is displayed in red on a yellow background, and I hear a "DX" announce.

I never saw this for any other call.

What about it ?

73

JR F8RZ

Re: Virus detected??

David Kozinn, K2DBK

#28153

I believe it said that you can also just wait and they will automatically get updated, the procedure they gave was if you didn't want to wait.

Re: Users with missing B4s, some questions to help isolate the cause.

HamApps Support (VK3AMA)

#28152

On 1/03/2020 2:10 pm, Tom NS8K wrote:

For those users who are experiencing missing B4 display on decoded Callsigns some questions...

Is this with Log4OM V2 or some other logger? Log4OM V2

Is this with Callsigns logged in the current JTAlert session only. That is, is it only happening for newly logged QSOs? Yes

Is the missing B4s fixed by performing a JTAlert restart? Yes. Also, I can just go into Settings and then Cancel to fix.

Do you have the "Do not check or report logging success/failure" option enabled in JTAlert (Logging section of the Settings)? Yes.

Today I tested everything I could think of. I changed to an empty Log4OM database file in an attempt to speed up their process. I re-installed Log4OM. I rolled JTAlert back to 2.15.9. I removed all extra, inactive UDP connections in Log4OM. I turned off CAT in Log4OM. I moved the database from OneDrive to the local SSD drive. I changed WSJT-X decodes from Deep with AP to Fast without AP. I changed the UDP port number from 2235 to 2222. I made sure I had Defender exclusions for WSJT, JTAlert and Log4OM. I increased the priority of Log4OM from Normal to High. As you can see, I'm grasping at straws but none of these changes made any difference.

All of my testing was done on FT8 signals. I didn't make any actual contacts, I would select a strong signal and then log it. I would then watch for B4 or lack of on subsequent transmissions. I made about 100 tests this way as I was making the above changes. 5 times, B4 appeared as it should. All other tests were failures. Couldn't figure out why the 5 worked. Odd that Herb and I are the only ones reporting this problem. Many folks use Log4OM V2 by now. Maybe something peculiar to our installations. Most of these tests were made with 2.15.11 Build 5. Others were with 2.15.9. My PC is 3 Ghz Core 2 Duo. 8 GB of ram. Spartan by today's standards. Right now I'm confined to the main floor so I am accessing the computer in the shack upstairs using Team Viewer. Pretty sure it acted this same way when I could get upstairs which was last week.

Tom - NS8K

Tom,

Thanks for taking the time to run these tests and report your results. When you get a chance could you repeat the tests (no need to run a large number) with the "Do not check or report logging success/failure" option unchecked. Does JTAlert start reporting the B4 status on newly logged QSOs correctly with that option off?

Thanks,
de Laurie VK3AMA

Re: Users with missing B4s, some questions to help isolate the cause.

Tom NS8K

#28151

On Fri, Feb 28, 2020 at 02:25 PM, HamApps Support (VK3AMA) wrote:

For those users who are experiencing missing B4 display on decoded Callsigns some questions...

Is this with Log4OM V2 or some other logger? Log4OM V2

Is this with Callsigns logged in the current JTAlert session only. That is, is it only happening for newly logged QSOs? Yes

Is the missing B4s fixed by performing a JTAlert restart? Yes. Also, I can just go into Settings and then Cancel to fix.

Do you have the "Do not check or report logging success/failure" option enabled in JTAlert (Logging section of the Settings)? Yes.

Today I tested everything I could think of. I changed to an empty Log4OM database file in an attempt to speed up their process. I re-installed Log4OM. I rolled JTAlert back to 2.15.9. I removed all extra, inactive UDP connections in Log4OM. I turned off CAT in Log4OM. I moved the database from OneDrive to the local SSD drive. I changed WSJT-X decodes from Deep with AP to Fast without AP. I changed the UDP port number from 2235 to 2222. I made sure I had Defender exclusions for WSJT, JTAlert and Log4OM. I increased the priority of Log4OM from Normal to High. As you can see, I'm grasping at straws but none of these changes made any difference.

All of my testing was done on FT8 signals. I didn't make any actual contacts, I would select a strong signal and then log it. I would then watch for B4 or lack of on subsequent transmissions. I made about 100 tests this way as I was making the above changes. 5 times, B4 appeared as it should. All other tests were failures. Couldn't figure out why the 5 worked. Odd that Herb and I are the only ones reporting this problem. Many folks use Log4OM V2 by now. Maybe something peculiar to our installations. Most of these tests were made with 2.15.11 Build 5. Others were with 2.15.9. My PC is 3 Ghz Core 2 Duo. 8 GB of ram. Spartan by today's standards. Right now I'm confined to the main floor so I am accessing the computer in the shack upstairs using Team Viewer. Pretty sure it acted this same way when I could get upstairs which was last week.

Tom - NS8K

Re: v2.15.11 Malware-gen

neil_zampella

#28150

I have tried everything but AVG is still saying it contains Win32:Malware-gen virus.

Anyone else having problems?

John W3ML

What version of AVG .. and AVG Internet Security just does a 15 second scan, and allows in the installation.

Neil, KN3ILZ

Re: Virus detected??

neil_zampella

#28149

Wait .. what?

You have to manually run something to clear out the old definitions?? What a joke.

Neil, KN3ILZ

Re: Users with missing B4s, some questions to help isolate the cause.

vk7cmv

#28147

Of course - thanks Laurie - I was getting ahead of myself :)

rgds, Julian

Re: How do I uninstall Sound File 2.5.2?

HamApps Support (VK3AMA)

#28146

On 1/03/2020 12:57 am, Michael Black via Groups.Io wrote:

Laurie...you'll find doing words for acronyms works pretty well in computer generated systems.

"see queue"

"dee ex"

de Mike W9MDB

Mike,

Already using those for the English voice announcements, but for the non-English voices (whoops I let the cat out of the bag) there is often a difference in the pronunciation of the individual letters and the English sound-alike words.

de Laurie VK3AMA

Re: Users with missing B4s, some questions to help isolate the cause.

HamApps Support (VK3AMA)

#28145

On 1/03/2020 10:00 am, vk7cmv wrote:

My call is a new one, so I'm going through new DXCC countries & callsigns at a faster rate than a more established station. An interesting one was working the USA on 20m this morning - the callsign became a B4 one - no problem this time. But all the other USA stations should have gone white, not yellow - because I have DXCC set (not US State). I restarted WSJT-X and JTAlert - it's still showing US as an unworked entity.

So the random B4 problem isn't the only issue

That is correct and expected behavior. Working a Callsign for a new DXCC will flag that Callsign as a B4 on subsequent decodes and will not alert as a new DXCC. Other Callsigns from the same country will continue to Alert on a new DXCC. That will only stop once that Country is removed from the JTAlert Wanted Lists, this is done when you perform a "Scan Log & Rebuild". Simply working an Entity will not automatically remove that Entity as wanted.

de Laurie VK3AMA

Re: How do I uninstall Sound File 2.5.2?

Kevin Utzy

#28144

Just a follow up. I delete and reinstalled the sound files and it works great now.
73,
Kevin
KX4KU

Re: Download error

HamApps Support (VK3AMA)

#28143

On 1/03/2020 8:47 am, km4djo@... wrote:

When I click to download the callsign database or the hamapps sounds , I get an error screen that says secure connection failed. Something about an SSL error being too long...

Anybody else getting this or did I forget to pay my subscription this month.....

i've been in the hospital for the last 4 months and trying to update my system....

Mark
KM4DJO

You may have an outdated browser without modern TLS/SSL support. Make sure it is up-to-date. Or try a different browser or clear the cache of your current browser.
Some Protection Software enable an option often called "safe-browsing" mode which is typically a form of proxy-server through which all your Internet activity passes and this can be problematic, try disabling that.

FWIW, the TLS/SSL supported by the HamApps sever is current and up-to-date. Very old and insecure protocols are turned off.
The SSL test performed by ssllabs.com gives the HamApps Server an "A" rating. You can view a very comprehensive test report at this link...
https://www.ssllabs.com/ssltest/analyze.html?d=hamapps.com

TLDR: There is nothing wrong or outdated with the SSL configuration of HamApps.com

de Laurie VK3AMA

Re: SQL file write error

HamApps Support (VK3AMA)

#28142

On 1/03/2020 3:38 am, Markus Dully wrote:

I also logged due to this failure all TU5PCT QSO´s manually.

This defect has already been corrected and a new public release of JTAlert made available.

You need to be running 2.15.11

de Laurie VK3AMA

Download error

km4djo

#28141

When I click to download the callsign database or the hamapps sounds , I get an error screen that says secure connection failed. Something about an SSL error being too long...

Anybody else getting this or did I forget to pay my subscription this month.....

i've been in the hospital for the last 4 months and trying to update my system....

Mark
KM4DJO

Re: SQL file write error

Markus

#28140

I also logged due to this failure all TU5PCT QSO´s manually.

Re: Users with missing B4s, some questions to help isolate the cause.

vk7cmv

#28139

Is this with Log4OM V2 or some other logger? HRD 6.7.0.262 with Access DB and subsequently MariaDB (I thought changing DB might fix it)
Is this with Callsigns logged in the current JTAlert session only. That is, is it only happening for newly logged QSOs? New and old - but not 100% of the time - can't figure why this is intermittent!
Is the missing B4s fixed by performing a JTAlert restart? No - this is the first thing I tried when I noticed it
Do you have the "Do not check or report logging success/failure" option enabled in JTAlert (Logging section of the Settings)? Unchecked

Using JTAlert 2.15.11 - but I've seen this before on 2.15.10 - Wiindows 10 Pro with latest updates - HRD 6.7.0.262

My call is a new one, so I'm going through new DXCC countries & callsigns at a faster rate than a more established station. An interesting one was working the USA on 20m this morning - the callsign became a B4 one - no problem this time. But all the other USA stations should have gone white, not yellow - because I have DXCC set (not US State). I restarted WSJT-X and JTAlert - it's still showing US as an unworked entity.

So the random B4 problem isn't the only issue