Date   

locked Re: Title Bar

HamApps Support (VK3AMA)
 

On 18/03/2020 12:17 pm, WB8ASI Herb wrote:
I lasted longer than most with the old regular version until finally switching over to the ALT version which now I don't even remember the difference.  Laurie, maybe we only need one version???
Herb,

My thoughts as well, and will avoid the issues with users who fail to read the Webpage, Release Notes, the text of the shortcuts installed or past forum posts.

This has been raised a number of times with the Test Team, but some are reluctant to loose the old version as it increases the amount of vertical space taken up by the GUI.

I am very close to dropping the hammer on the old version (menus in the titlebar), but not likely with the next release.

de Laurie VK3AMA


locked Re: Audio Alerts Stop Working - Resolved

richardson_ed
 

Upgrading to the latest version of WSJT-x has resolved the issued. Audio alerts now work as expected after 24 hours of continuous use.

 

Sometimes the most obvious solutions are overlooked!

 

Thanks for the assistance and great software!

 

Ed VE4VT

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Laurie, VK3AMA
Sent: March 15, 2020 2:54 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Audio Alerts Stop Working

 

 

On 16/03/2020 3:25 am, richardson_ed wrote:

I upgraded to 2.16.1 on Friday. Since then I have discovered the audio alerts function correctly for several notifications and then stop all together. Even the “Calling me” will not work.  If I shutdown the program and restart, everything works fine again for several notifications.

This is on a windows 10 machine and had been working perfectly prior to the upgrade.

Ed VE4VT


I note on PSKReporter your using the very old 2.0.1 version of WSJT-X. Try updating to 2.1.2 and report back if that fixes the problem.

de Laurie VK3AMA

_._,_._,_


locked Re: Decodes History Fatal Error Crash

HamApps Support (VK3AMA)
 

On 17/03/2020 12:57 am, Ed Fuller wrote:
This morning I'm getting a similar error msg (See Attached).  No changes that I know of since yesterday when it was working perfectly.  I'm running the Beta that Laurie sent.  Win7 64 home premium.

Ed WA5RHG

Ed,

Your problem is different from the other users experiencing an unexpected fatal error with the Decodes Window. Yours is a malformed database disk image, or more simply your decodes.sqlite file is corrupt. You will need to manually delete the file before starting JTAlert.

The file will be found at %localappdata%\HamApps\JTAlert\<YOUR_CALLSIGN>\Decode\decodes.sqlite

de Laurie VK3AMA


locked Re: Title Bar

WB8ASI Herb
 

I lasted longer than most with the old regular version until finally switching over to the ALT version which now I don't even remember the difference.  Laurie, maybe we only need one version???

On March 17, 2020 at 9:11 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:

On 18/03/2020 6:43 am, Greg Yates via Groups.Io wrote:
I downloaded new version of JT Alert twice  and  I get no title bar.  What am I doing wrong.

Thanks,
Greg, WB2BIN

From the webpage where you download JTAlert, at the very top...
A number of Windows 10 users, especially with the 1903 update, have experienced missing or misplaced menus and Band Activity display from the JTAlert titlebar or non-responsive minimize and close buttons. An alternate layout build of JTAlert is available to workaround this defect, that at this time has been unreproducible in testing. The "Alt Layout" build of JTAlert uses a conventional placement of the menus below the titlebar.

Switching to the "Alt Layout" build is handled by executing the appropriate shortcut created by the installer. There is no longer a separate installer for the "Alt Layout" build.

You need to use one of the (AL) shortcuts to start JTAlert.

de Laurie VK3AMA


 


locked Re: Decodes History Fatal Error Crash

HamApps Support (VK3AMA)
 

On 16/03/2020 7:46 pm, faafaafuey via Groups.Io wrote:
Hello all. Since the last 2 or 3 JTalert-X updates, my Decodes History window crashes intermittently, usually after several hours. I've included a screenshot below for the "unexpected fatal error". It appears to be related to SQLite. I've not changed any settings and no changes to my computer (Dell Inspiron15 3000, 32GB RAM, i3-7100 CPU 2.40 GHz, 500 GB SSD). WSJT-X v2.1.2, JTalert-X v2.16.1. I can't seem to figure out what is causing this. Has anyone else had this occur? Thanks for any ideas.
Jim K2JL

Jim,

A known problem that is actively being worked on. The latest build received by the Test Team is looking promising with respect to these errors.

Until the next public release your only option is to restart the Decodes window, there is no need to restart JTAlert.

de Laurie VK3AMA


locked Re: JTAlert_AL.exe not found

HamApps Support (VK3AMA)
 

On 18/03/2020 5:18 am, phredyh@... wrote:
After re downloading and installing JTAlert the "JTAlert_AL.exe" icon (Properties, Open File Location) produced the
attached screen shot and I haven't been able to find the .exe file anywhere on my computer.

--

de Fred KE0EF


Run the JTAlert installer again and any missing files will be re-created. There is no harm in running the Setup multiple times.

de Laurie VK3AMA


locked Re: Title Bar

HamApps Support (VK3AMA)
 

On 18/03/2020 6:43 am, Greg Yates via Groups.Io wrote:
I downloaded new version of JT Alert twice  and  I get no title bar.  What am I doing wrong.

Thanks,
Greg, WB2BIN

From the webpage where you download JTAlert, at the very top...
A number of Windows 10 users, especially with the 1903 update, have experienced missing or misplaced menus and Band Activity display from the JTAlert titlebar or non-responsive minimize and close buttons. An alternate layout build of JTAlert is available to workaround this defect, that at this time has been unreproducible in testing. The "Alt Layout" build of JTAlert uses a conventional placement of the menus below the titlebar.

Switching to the "Alt Layout" build is handled by executing the appropriate shortcut created by the installer. There is no longer a separate installer for the "Alt Layout" build.

You need to use one of the (AL) shortcuts to start JTAlert.

de Laurie VK3AMA


locked Re: Title Bar

John
 

"Did you try the JTAlert (AL) shortcut? That might solve the problem."

What is that and how do you get to it

John


--
This email has been checked for viruses by AVG.
https://www.avg.com


locked Re: JTAlert_AL.exe not found

Dave Garber
 

it looks like it was not installed in the correct directory


Dave Garber
VE3WEJ / VE3IE


On Tue, Mar 17, 2020 at 2:18 PM <phredyh@...> wrote:
After re downloading and installing JTAlert the "JTAlert_AL.exe" icon (Properties, Open File Location) produced the
attached screen shot and I haven't been able to find the .exe file anywhere on my computer.

--

de Fred KE0EF


locked Re: Title Bar

Jim N6VH
 


On 3/17/2020 12:43 PM, Greg Yates via Groups.Io wrote:
I downloaded new version of JT Alert twice  and  I get no title bar.  What am I doing wrong.

Thanks,
Greg, WB2BIN
_._,_._,_


Greg,

Did you try the JTAlert (AL) shortcut? That might solve the problem.

73,.

Jim N6VH


locked Title Bar

Greg Yates
 

I downloaded new version of JT Alert twice  and  I get no title bar.  What am I doing wrong.

Thanks,
Greg, WB2BIN


locked JTAlert_AL.exe not found

Frederick C Hollendorfer
 

After re downloading and installing JTAlert the "JTAlert_AL.exe" icon (Properties, Open File Location) produced the
attached screen shot and I haven't been able to find the .exe file anywhere on my computer.

--

de Fred KE0EF


locked Re: SSL Error Downloading 2.16.1

Richard Black
 

Thanks Herb. I'm good to go. I'll remember this for the next update :)

Rich - N0FXQ


locked Re: SSL Error Downloading 2.16.1

WB8ASI Herb
 

I ran into a similar problem.  I found it to be some new xFi Advanced Security added by Comcast/Xfinity to your gateway/router.  You need to disable this service long enough to make the download.   You can access it thru your Account, but it wasn't easy to find.  Here's the path to take you where you can disable/enable.     https://internet.xfinity.com/more/my-services/my-services-disabling  Good luck. Herb WB8ASI

On March 17, 2020 at 6:46 AM "Richard Black via Groups.Io" <jrblack99sa@...> wrote:

Yes. I certainly do! Any workaround?

Rich -N0FXQ

 


locked Re: JTAlert loses "connection" to WSJT-X and HRD Logbook

Stuart, K2YYY
 

It worked fine with the old version of wsjt-x and a previous version of JTAlert (not sure when it stopped working).

I haven't upgraded to the latest wsjt-x because I like the change frequency while transmitting feature.

Stuart


locked Re: Decodes History Fatal Error Crash

faafaafuey@...
 

Ah ok. Sounds like a known issue. I'm more than willing to wait for a solution. I just wasn't sure if it was something I caused with an errant setting checkmark. Thanks Mike.
Jim K2JL


locked Re: SSL Error Downloading 2.16.1

Richard Black
 

Yes. I certainly do! Any workaround?

Rich -N0FXQ


locked Re: SSL Error Downloading 2.16.1

WB8ASI Herb
 

Do you by chance have Comcast/Xfinity as your ISP???

On March 16, 2020 at 5:33 PM "Richard Black via Groups.Io" <jrblack99sa@...> wrote:

I've been unable to access the link to download 2.16.1. First time this has happened. After disabling AVG the following error is displayed attempting to follow the link for the download...

An error occurred during a connection to dnl.hamapps.com. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Any suggestions would be appreciated. I've tried both Firefox and Edge - same results.

 


locked SSL Error Downloading 2.16.1

Richard Black
 

I've been unable to access the link to download 2.16.1. First time this has happened. After disabling AVG the following error is displayed attempting to follow the link for the download...

An error occurred during a connection to dnl.hamapps.com. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Any suggestions would be appreciated. I've tried both Firefox and Edge - same results.


locked Re: still locking Re: [HamApps] JTAlert 2.16.1 intermittent decode

Hasan Schiers N0AN
 

...and so do all other typical applications (ignore the first one or two UDP) messages. This is perfectly normal. As I understand it the apps need to see a Type2 UDP packet before they will work correctly.

I'm working with a programmer who is doing a UDP Repeater so it will take WSJT-X UDP packets and re-purpose them for his application and we observe this 1 or 2 packets required before Sync all the time. We have a visual indicator of Sync, so we can watch what happens. It is similar to the Green LED in SpotCollector, confirming valid data from WSJT-x as Spot Source.

We have used the Rebroadcast of UDP from JTA to drive the repeater and it works very, very well.

73, N0AN
Hasan


On Mon, Mar 16, 2020 at 3:48 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 17/03/2020 4:55 am, Franco HB9oab wrote:
as at startup that the first and second decoding after the start is not displayed.
Then he leaves me alone.

No decodes displayed at JTAlert startup is normal behavior, whether is is the 1 or 2 periods of decodes that are not displayed is random and depends on what Mode is being used and when JTAlert was started with respect to the current period.

JTAlert deliberately does not display any decodes received when there has been detected a Band change within the current period, it simply has no way of knowing if the decodes are for the first Band or the new Band and WSJT-X doesn't provide that information in the decodes data, so decodes are ignored. This is what is triggering the non-display at JTAlert Startup.

When first started JTAlert doesn't know the Band until the first UDP packets arrive from WSJT-X so JTAlert treats that as a Band change and the decodes are ignored. Plus there is the initial delays as JTAlert is setting itself up for the first time.

The TLDR: It is normal for JTAlert to ignore the first one or two WSJT-X periods after it has started.

de Laurie VK3AMA
`

8521 - 8540 of 36897