Date   

locked Re: Putting some context to the JTAlert 2.11.x release and the difficulties some are having.

Brad Rich <brad.rich@...>
 

I have been a happy user of JTAlert and have none of the issues I see posted.  Yes, my AV likes to talk about JTAlert but I simply tell my Av to ignore  Guy’s email if accurate informed me that JTAlert is payware.  I always wondered how this great piece of software could be free along with lauries outstanding support. 

 

What is the license amount and how can I pay?

 

Thanks,

Brad

N6GR

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Guy G4DWV 4X1LT
Sent: Tuesday, June 5, 2018 9:12 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Putting some context to the JTAlert 2.11.x release and the difficulties some are having.

 

Hi Laurie,

Please do not let that schmuck ruin your day. I also have pride in my work as a dentist and it only takes on ungrateful git to ruin my day as I take such things personally.

I am sure that everybody else who used JT-Alert is grateful for your contribution to amateur radio. I, for one, would not use JT modes if it were not for JT-Alert.

I just wish you were faster in sending out the purchase invoices. I have been waiting over 2 years for mine.

Take care


--
73 de Guy G4DWV 4X1LT


locked Re: Putting some context to the JTAlert 2.11.x release and the difficulties some are having.

Guy G4DWV 4X1LT
 

Hi Laurie,

Please do not let that schmuck ruin your day. I also have pride in my work as a dentist and it only takes on ungrateful git to ruin my day as I take such things personally.

I am sure that everybody else who used JT-Alert is grateful for your contribution to amateur radio. I, for one, would not use JT modes if it were not for JT-Alert.

I just wish you were faster in sending out the purchase invoices. I have been waiting over 2 years for mine.

Take care


--
73 de Guy G4DWV 4X1LT


locked Re: How to get alarms from WSJT-X via JTAlertX?

dk1wb
 

Thanks Laurie,

all is set now :-)

73, Hans

HamApps Support (VK3AMA) schrieb am 05.06.2018 00:14:

On 4/06/2018 11:24 PM, dk1wb@... wrote:
I am using WSJT-X 1.9.1 together with JTAlertX 2.10.1 for logging to HRD on a Windows 7 machine.
Now I am trying to initiate alarms by JTAlertX for certain calls.  I entered the wanted calls in settings/Wanted Callsigns and set the sound card accordingly (checked by settings/Test Sound Card). JTAlertX shows all received calls but does not sound any alarm even if one of the wanted calls is received.
Can anyone tell me what could be missing?
Thanks and 73,
Hans, DK1WB
Hans,

Make sure you have a sound file set for the Wanted Callsign alert. The same applies to any of the other Wanted Alerts.

de Laurie VK3AMA

 


locked Re: Putting some context to the JTAlert 2.11.x release and the difficulties some are having.

Hank W6IR
 

All in favor say "aye".


locked Positive note here - display speed - virus (not)

WB5JJJ - George
 

One of the most noticeable changes is recent releases is the speed up of the decoded display.  It's now about 1 second or less, after the Decode button turns off that the first call is displayed and the voice announcement begins.  Well within the ability to click on one and start a contact without having to wait a cycle.  A great move. 

And yes, Windows Denfender balks on many programs with the blue screen where you have to tell it to "Run Anyway", but that's no big deal.  If you know where the installer comes from, just move on.  I have put an exception in WD for all my ham radio program folders so it leaves them alone after that.  I would suggest that users of other malware programs put exceptions in there to avoid future issues. 

I just don't understand why some guys post images of JTA with so many lines of contacts.  To me this is just clutter as WSTJx already shows all of this in greater detail.  Some time back, I saw a guy asking for MORE LINES.  For me, I only display 6 across of stations that are calling CQ that are LoTW users and that I have not worked before on the current band.  So I typically see none to maybe 5 or 6, but I have seen maybe 10 on occasion.  Letting JTA filter all the unnecessary data produces a much cleaner display that is easier to quickly scan. 

Thanks Laurie for the program and all your work, even among the naysayers that hide in the shadows of anonymity you efforts are outstanding.  I have been using JTA to log to HRD LB (keep that going) for a few months now and very seldom does it fail to do so.  When it does, a simple manual insert solves the problem.  I will move from 2.11.1 to 2.11.3 when it's released skipping 2.11.2 just "because". 
--
73's
George - WB5JJJ


locked Re: JTAlert 2.11.1 Fails install

Mike N4LKB
 

Today's update to MalwareBytes (v3.5.1) allowed my JTAlert 2.11.2 to run, where it did not yesterday.. I would expect same of JTAlert 2.11.1

Two of us had notified MalwareBytes, and I believe this update addressed that.

Mike
N4LKB


locked Re: JTAlert 2.11.1 Fails install

 

Yes Laurie, you are correct.  There is nothing for you to do here.  I believe another user has been in contact with Malwarebytes.  Let’s hope there will be a better solution than setting up an exception to scanning.

 

__________

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, June 4, 2018 8:03 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.11.1 Fails install

 

On 5/06/2018 10:52 AM, Dan Malcolm wrote:

Laurie,

The problem with the existing shortcut is that it always said it was invalid.  Turns out that trying to start JTAlert causes Malwarebytes to delete it.  My fix was to make the HamApps folder an exception in Malwarebytes.  Works fine now.

Dan – K4SHQ

Dan,

Your description corresponds to my observation previously posted (the 2nd part)... "If your shortcut shows the invalid message, either it is pointing to JTAlert.exe installed in a different folder or the JTAlert.exe file is missing".

There is little I can do about misbehaving virus protection software on a users PC. Ultimately, sorting that out is the users responsibility.

Good to hear your now working correctly.

de Laurie VK3AMA


--
Dan - K4SHQ


locked Re: Putting some context to the JTAlert 2.11.x release and the difficulties some are having.

Mike N4LKB
 

I will second that...

Mike N4LKB


locked When trying to run a 2nd Instance JTAlertX I get error about UDP

KD7YZ Bob
 

I tried altering the UDP port number but this didn't seem to help.

I have two instances of wsjtx with and attempted two instances of
JTAlertX going.

#2 WSJTx is doing fine on 50.213 and WSJTx #1 fine on 50.260. And the
JTAlertX with this guy is nominal.

Yeah, I am overlooking something, but fail to see it for the "trees" .

Anyone offer assistance?


--
73,
Bob KD7YZ


locked Re: My PC reports that hamapps.com cannot provide a secure connection

HamApps Support (VK3AMA)
 

On 5/06/2018 7:10 PM, Tom Ramberg via Groups.Io wrote:
Thus, I cannot download the latest version of JTAlert-X.
Please advise how I can upgrade. I am currently using version 2.10.15.

73 de Tom OH6VDA
Tom,

HamApps supports both normal http and secure https access.

Use the correct secure link https://HamApps.com

Both Chrome and Firefox correctly report the site as secure if you use https.

Chrome...

Firefox...

de Laurie VK3AMA


locked My PC reports that hamapps.com cannot provide a secure connection

Tom Ramberg, OH6VDA
 

Thus, I cannot download the latest version of JTAlert-X.
Please advise how I can upgrade. I am currently using version 2.10.15.

73 de Tom OH6VDA


locked Re: JT Alert 2.11.2 will not log to HRD 6.4.0.840

Mike Steiner
 

Laurie,

 

This fix fixed my problem….  However it did take about three passes for it to start displaying callsigns… but after that no issues.

 

Mike K7QDX

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, June 04, 2018 11:16 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert 2.11.2 will not log to HRD 6.4.0.840

 

On 5/06/2018 4:12 PM, hachr-l@... wrote:

Problem here also, used 2.11.1 with no issues. Downloaded 2.11.12, and it worked fine for a while. But suddenly I noticed several QSO's missing from the logbook. Next time I tried to log, nothing happened. No error message, and of course nothing in the log... Restartet JT-Alert, and everything is back to normal again. 

73
Hans Christian LA9AKA

See this post https://hamapps.groups.io/g/Support/message/20327

All reports back from those who have tested that build have reported that JTAlert is back to normal logging and decodes display.

If you don't want to try the new build, wait until I release 2.11.3 tomorrow sometime.

de Laurie VK3AMA


locked Re: JT Alert 2.11.2 will not log to HRD 6.4.0.840

HamApps Support (VK3AMA)
 

On 5/06/2018 4:12 PM, hachr-l@... wrote:
Problem here also, used 2.11.1 with no issues. Downloaded 2.11.12, and it worked fine for a while. But suddenly I noticed several QSO's missing from the logbook. Next time I tried to log, nothing happened. No error message, and of course nothing in the log... Restartet JT-Alert, and everything is back to normal again. 

73
Hans Christian LA9AKA
See this post https://hamapps.groups.io/g/Support/message/20327

All reports back from those who have tested that build have reported that JTAlert is back to normal logging and decodes display.

If you don't want to try the new build, wait until I release 2.11.3 tomorrow sometime.

de Laurie VK3AMA


locked Re: JT Alert 2.11.2 will not log to HRD 6.4.0.840

LA9AKA
 
Edited

Problem here also, used 2.11.1 with no issues. Downloaded 2.11.12, and it worked fine for a while. But suddenly I noticed several QSO's missing from the logbook. Next time I tried to log, nothing happened. No error message, and of course nothing in the log... Restartet JT-Alert, and everything is back to normal again. 

73
Hans Christian LA9AKA


locked Re: JT Alert 2.11.2 will not log to HRD 6.4.0.840

Mike Steiner
 

Lots of emails… just got to it that you released a new version.  Downloading it now.

 

Thank you… And your right it doesn’t make sense of what you did and the problem some of us were having.

 

Thank you for your wonderful program and continue support!

 

Mike K7QDX

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, June 04, 2018 10:49 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert 2.11.2 will not log to HRD 6.4.0.840

 

On 5/06/2018 3:41 PM, Mike Steiner wrote:

Glad I’m not the only one….

 

Mike K7QDX

See this post https://hamapps.groups.io/g/Support/message/20327

All reports back from those who have tested that build have reported that JTAlert is back to normal logging and decodes display.

If you don't want to try the new build, wait until I release 2.11.3 tomorrow sometime.

de Laurie VK3AMA


locked Re: JT Alert 2.11.2 will not log to HRD 6.4.0.840

HamApps Support (VK3AMA)
 

On 5/06/2018 3:41 PM, Mike Steiner wrote:

Glad I’m not the only one….

 

Mike K7QDX

See this post https://hamapps.groups.io/g/Support/message/20327

All reports back from those who have tested that build have reported that JTAlert is back to normal logging and decodes display.

If you don't want to try the new build, wait until I release 2.11.3 tomorrow sometime.

de Laurie VK3AMA


locked Re: JT Alert 2.11.2 will not log to HRD 6.4.0.840

Mike Steiner
 

Glad I’m not the only one….

 

Mike K7QDX

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, June 04, 2018 3:07 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT Alert 2.11.2 will not log to HRD 6.4.0.840

 

On 5/06/2018 7:56 AM, Justin EI3CTB wrote:

Hi,

I am using Windows 7 with WSJT-X v 1.9.1 and HRD 6.4.0.840 with a MariaDB SQL database. Yesterday I updated to JT Alert X 2.11.1 it worked perfectly and logged as normal.  

This evening I updated to version 2.11.2 and it logged 1 contact and sent me an error message.  My next contact just wouldn't log at all!

I have reverted back to JT Alert X 2.11.1 and logging is working perfectly again.

It seems that 2.11.2 is not compatible with my setup.  Any ideas?

73

Justin
EI3CTB

Justin,

I would have expected the opposite, 2.11.1 failing and 2.11.2 working. I am surprised you see otherwise as the very minimal changes made to the TCP timeout value should not have cause 2.11.2 to fail.

There must be something else happening within 2.11.2 that I am unaware of.

Stay with 2.11.1 until I make a new release.

de Laurie VK3AMA


locked Re: Please add Automatic logging to these log types when QSO is logged in JT65-HF or WSJT-X

Michael Black
 


It's a FoxBase+/dBase III DBF

de Mike W9MDB



On Monday, June 4, 2018, 8:07:49 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 5/06/2018 9:11 AM:
Please add the function to automatically transfer to the log software commonly used by many stations in Japan.
Turbo HAMLOG for Windows (THW)

I have code to automatically transfer to THW in the code of WSJT-X.  ( C++ )
And , there is also a code of VB2010.
Could you incorporate this into JTAlert ?
OM,

What database type does Turbo use for its log file, mdb, sqlite, adif, MySql, MSSQL, etc?

If you have links to documentation describing the logging API for Turbo HAMLOG please forward it and I will review whether it is suitable for JTAlert integration.

de Laurie VK3AMA


locked Re: Putting some context to the JTAlert 2.11.x release and the difficulties some are having.

kk7h@...
 

GE Laurie,
You Sir, have the patience of a saint.
Thank you for the work you put into this endeavor. 
de
Mike Hamner  KK7H


locked Re: New JTAlert 2.11.2 build 0001 available for test -looks like we have a fix

HamApps Support (VK3AMA)
 

Looks like this build fixed the one time logging to HRD/DXKeeper/ACLog followed by subsequent logging failures and no decode reception from WSJT-X problem reported by some users.

I have received reports from 5 people who submitted Support Requests and they all confirm the fix. There are still some I am waiting to hear back from.

Unless I get reports of broken behaviour in this build I will publish it tomorrow as 2.11.3

de Laurie VK3AMA


On 5/06/2018 12:10 PM, HamApps Support (VK3AMA) wrote:
Interim build releases are normally only posted to the Beta Test Team.
I am making this build publicly available to get it into the hands of users as soon as possible.

To date problems reported by some 2.11.2 users have not be reproduced by myself or the test team, so there are no guarantees that this build will correct your problems, but please give it a try. It further tweaks the TCP timeout settings that are likely the root cause of Logging failures with HRD/DXKeeper/ACLog.

Whether this build corrects the non-display of decoded callsigns is unknown, but knowing the code it should not, but having said that, there is nothing in the 2.11.2 code changes that should have caused this in the first place (that I am aware off).

Upgrade your JTAlert by running this file...
https://dnl.HamApps.com/Testing/HamApps_JTAlert_2.11.2_build_0001_Setup.exe

Please advise if this corrects or not your 2.11.2 problems.

de Laurie VK3AMA

18241 - 18260 of 38532