Date   

locked Re: Unsuccessful Logging warning in LOG40M2

w4ihi3
 

TNX Laurie & Mike 15sec is the ticket. Failure notice gone success working. Wow is it slower compared to V1! Wonder how it would work in contest mode rapid logging?
Tnx agn,
73 Gary W4IHI


locked Text Message App Crashes

ve7gtc
 

I have for the last several months, through all releases, had a text message issue. Someone sends me a text. It pops up and I answer. As soon as I type the first letter of the answer, the app closes. It doesn't matter if I am answering a text or initiating a new one. It crashes about 50% of the time. I get a lot of text messages, and don't know if that causes the problem. If I close JTAlert and open it again, that may or may not solve the problem. Any thoughts?
Thans,
Gus K2GT


locked Re: Can't get to JTALER "Manage Setting'

Michael Black
 

You have to manually install this....it doesn't come with anything other then Visual Studio I think.

Mike




On Sunday, January 26, 2020, 10:40:34 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/01/2020 3:15 pm, Michael Black via Groups.Io wrote:
The mySQL failure when opening Settings -- fixed by installing the latest VC

Mike
Tnx Mike,

So there are two possible errors, the JTAlert "MySQL Failure" error and the "VC RUNTIME is missing" error reported by Ed WA5RHG.

I wonder what version of Windows is affected and how up-to-date they were?

I will wait to hear back from the users reporting the "MySQL failure" error now that they have a build of JTAlert with the old libmysql.dll file. If they report problem solved, I'll go with rolling-back the file rather than getting people to load the VC runtime.

de Laurie VK3AMA


locked Re: Can't get to JTALER "Manage Setting'

HamApps Support (VK3AMA)
 

On 27/01/2020 3:15 pm, Michael Black via Groups.Io wrote:
The mySQL failure when opening Settings -- fixed by installing the latest VC

Mike
Tnx Mike,

So there are two possible errors, the JTAlert "MySQL Failure" error and the "VC RUNTIME is missing" error reported by Ed WA5RHG.

I wonder what version of Windows is affected and how up-to-date they were?

I will wait to hear back from the users reporting the "MySQL failure" error now that they have a build of JTAlert with the old libmysql.dll file. If they report problem solved, I'll go with rolling-back the file rather than getting people to load the VC runtime.

de Laurie VK3AMA


locked Re: Unsuccessful Logging warning in LOG40M2

HamApps Support (VK3AMA)
 

On 27/01/2020 3:22 pm, w4ihi3 wrote:
This may be a repeat so sorry in advance. Have the latest version of both Jtalert and LOg40m2. All is working but keep getting the unsuccessful log alert when I log a qso. It is logging in WSJT and Log40m2 but keep failing to get rid of the warning alert. I have check the paths and they are correct as well as the udp ports. I am out of options I cannot seem to fix this problem. Thanks for listening and any help.
73,Gary W4IHI
Gary,

Log4OMV2 is much slower in writing the QSO to its log file/database compared to V1. If the QSOs are indeed getting logged you will need to increase the "Check QSO Log Record" time. See the Logging section of the JTAlert Settings window.

de Laurie VK3AMA


locked Re: Unsuccessful Logging warning in LOG40M2

Michael Black
 

If it's logging then you need to increase the time in Logging for Check QSO Log Record.  I've got mine at 15 seconds now.

de Mike W9MDB




On Sunday, January 26, 2020, 10:22:54 PM CST, w4ihi3 <w4ihi3@...> wrote:


This may be a repeat so sorry in advance. Have the latest version of both Jtalert and LOg40m2. All is working but keep getting the unsuccessful log alert when I log a qso. It is logging in WSJT and Log40m2 but keep failing to get rid of the warning alert. I have check the paths and they are correct as well as the udp ports. I am out of options I cannot seem to fix this problem. Thanks for listening and any help.
73,Gary W4IHI


locked Unsuccessful Logging warning in LOG40M2

w4ihi3
 

This may be a repeat so sorry in advance. Have the latest version of both Jtalert and LOg40m2. All is working but keep getting the unsuccessful log alert when I log a qso. It is logging in WSJT and Log40m2 but keep failing to get rid of the warning alert. I have check the paths and they are correct as well as the udp ports. I am out of options I cannot seem to fix this problem. Thanks for listening and any help.
73,Gary W4IHI


locked Re: Can't get to JTALER "Manage Setting'

Michael Black
 

The mySQL failure when opening Settings -- fixed by installing the latest VC

Mike


On Sunday, January 26, 2020, 06:37:05 PM CST, Laurie, VK3AMA <hamapps.support@...> wrote:




On 27/01/2020 11:27 am, Michael Black via Groups.Io wrote:
Yes...

On Sunday, January 26, 2020, 06:24:00 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/01/2020 9:24 am, Michael Black via Groups.Io wrote:
Which version of vc_redist.x86?

2015 mabye?  2013 didn't fix it for another person.

de Mike W9MDB
Mike,

This person your helping, are they getting the VC error or the JTAlert generated "MySQL start failure" msgbox when opening the Settings?

de Laurie VK3AMA

?? Yes to what, the VC error or the JTAlert MySQL failure error?

de Laurie VK3AMA


locked Re: SCAN LOG NO HIGHLIGHTER

HamApps Support (VK3AMA)
 

On 27/01/2020 1:39 pm, Bob Elliot wrote:
V2.15.8   New update entry's to log are NOT highlighted..  I just use the regular setup for JTDX. Ideas?
--
73 Bob K1RI

I'm confused. What are you describing? What is not being highlighted, what app/window?

de Laurie VK3AMA


locked Re: SCAN LOG NO HIGHLIGHTER

Bob Elliot
 

I was using only enabled DXCC. I enabled all and then removed a couple DXCC countries from the NOT WANTED.  Then scanned all categories.  Results were all highlighted EXCEPT: DXCC .  The scan updated the 2  removals as DXCC NOT WANTED, but no highlight..
--
73 Bob K1RI
Sent from my Rotary Phone


locked SCAN LOG NO HIGHLIGHTER

Bob Elliot
 

V2.15.8   New update entry's to log are NOT highlighted..  I just use the regular setup for JTDX. Ideas?
--
73 Bob K1RI
Sent from my Rotary Phone


locked Re: Can't get to JTALER "Manage Setting'

Laurie, VK3AMA
 



On 27/01/2020 11:27 am, Michael Black via Groups.Io wrote:
Yes...

On Sunday, January 26, 2020, 06:24:00 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/01/2020 9:24 am, Michael Black via Groups.Io wrote:
Which version of vc_redist.x86?

2015 mabye?  2013 didn't fix it for another person.

de Mike W9MDB
Mike,

This person your helping, are they getting the VC error or the JTAlert generated "MySQL start failure" msgbox when opening the Settings?

de Laurie VK3AMA

?? Yes to what, the VC error or the JTAlert MySQL failure error?

de Laurie VK3AMA


locked Re: Can't get to JTALER "Manage Setting'

HamApps Support (VK3AMA)
 

On 27/01/2020 6:53 am, Ed Fuller wrote:

Laurie,  at Mike's suggestion I ran vc_redist.x86.exe and that solved the error opening settings.   I tried your test version and it also worked FB, but I'm not sure that is a fair test as I didn't roll back the 32 bit redist.  Anything else I can do to help?  I do have a restore point from before all the distros.

 

Ed

Ed,

Don't worry about testing by loading the last restore point.
I have sent the new build to a couple of affected users and am waiting on their response.

Thanks
de Laurie VK3AMA


locked Re: Can't get to JTALER "Manage Setting'

Michael Black
 

Yes...




On Sunday, January 26, 2020, 06:24:00 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/01/2020 9:24 am, Michael Black via Groups.Io wrote:
Which version of vc_redist.x86?

2015 mabye?  2013 didn't fix it for another person.

de Mike W9MDB
Mike,

This person your helping, are they getting the VC error or the JTAlert generated "MySQL start failure" msgbox when opening the Settings?

de Laurie VK3AMA


locked Re: Can't get to JTALER "Manage Setting'

HamApps Support (VK3AMA)
 

On 27/01/2020 9:24 am, Michael Black via Groups.Io wrote:
Which version of vc_redist.x86?

2015 mabye?  2013 didn't fix it for another person.

de Mike W9MDB
Mike,

This person your helping, are they getting the VC error or the JTAlert generated "MySQL start failure" msgbox when opening the Settings?

de Laurie VK3AMA


locked Re: Can't get to JTALER "Manage Setting'

Ed Fuller
 

The web site says the latest for 2015, 2017, 2019   see: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads


locked Re: Can't get to JTALER "Manage Setting'

Michael Black
 

Which version of vc_redist.x86?

2015 mabye?  2013 didn't fix it for another person.

de Mike W9MDB


On Sunday, January 26, 2020, 01:54:04 PM CST, Ed Fuller <emfuller70@...> wrote:


Laurie,  at Mike's suggestion I ran vc_redist.x86.exe and that solved the error opening settings.   I tried your test version and it also worked FB, but I'm not sure that is a fair test as I didn't roll back the 32 bit redist.  Anything else I can do to help?  I do have a restore point from before all the distros.

 

Ed

 

 


From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, January 26, 2020 12:56 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Can't get to JTALER "Manage Setting'

 

On 27/01/2020 4:33 am, Ed Fuller wrote:

I upgraded from Jtalert 2.15.7 to 2.15.8 and install went fine; however when I click on Manage Setting, it throw error msg to the effect 'VCRUNTIME140 is missing'.  Sure enough it is not in system32 as on another of my machines.  Shack computer is win7 home premium.   I'm logging to Dxkeeper.  Tried installing vc_redist.x64.exe (from Visual c + + redistribution for visual studio 2015 site) and vcruntime140.dll shows up in system32 folder and now has registry entries.  Did a restart, no joy.  I'm at dead end.  Since I'm using dxkeeper, wonder if an option to bypass the loading of this dll would be possible?  Any help appreciated, been using this for several years with no problem.  Really hate to lose access to future updates.

 

Ed WA5RHG

Ed,

I am unaware which file in JTAlert is causing this error. There are several 3rd party dll files used and they are likely compiled requiring the VC runtime, it is a very common requirement. JTAlert is a 32 bit application and all the dlls are 32 bit as well. Try installing the 32bit version of the VC runtime.

I am suspicious, given some recent reports, that the updated libmysql.dll file may be the cause. I have sent you a link to an new JTAlert build that has roll-backed the libmysql.dll version give that a try and let me know the results.

de Laurie VK3AMA


locked JTAlert 2.15.8 is available but multiple instances are still not showing./ Correction.

asobel@...
 

Correction: Only the last started instance is shown.

 

Dear Laurie

 

I did upgrade to JTAlert 2.15.8, It does work Ok in 4 instances and  with my Log4OMV2 but Decode window  does still show only for the first instance. Same was for 2.15.7. Please repair this fault. I need decode window badly.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: יום ו 24 ינואר 2020 22:56
To: Support@HamApps.groups.io
Subject: [Special] [HamApps] JTAlert 2.15.8 is available. Full Log4OMV2 support. #Announcement #NewRelease

 

The Latest JTAlert version 2.15.8 is now available @ https://hamapps.com/JTAlert/

This release has support for the newly released Log4OM V2. Both SQLite & MySQL logs are supported.
Log4OM V2 users should view the Help file for proper setup instructions (they are very simple).
See the "Settings -> Logging -> Log4OM V2" topic in the help file. Using the Help button when on the Log4OM V2 section of the JTAlert Settings window will take you to the relevant help topic.

de Laurie VK3AMA

The Release Notes...

2.15.8 (24-JAN-2020)

  *** Includes Callsign database file version 2020-01-24 (2020-January-24)

  New Features:

    - Log4OM V2: Full support for Log4OM V2, both SQLite and MySQL logs.

    - Log4OM V1/V2 SQLite logs: "Test" button to check log file selected is
       a valid SQLite file for the Log4OM version and contains QSO records.
       See Settings window, "Logging -> Log4OM..." sections.

    - Logging option: New "Do not check or report logging success/failure".
       This option when ticked (off by default) instructs JTAlert to not try
       and confirm that a QSO was logged by reading the Loggers log directly.
       Once the logging instruction has been sent, JTAlert goes back to normal
       operation, there are no delays or hangs as JTAlert is stuck waiting to
       confirm the QSO was logged. JTAlert will however still report a logging
       failure when it could not initially establish the TCP or UDP connection
       to the target logger.

  Changes:

    - MySQL support: libmysql.dll file updated to v6.1.10 (previously v5.1.37)

  Fixes:

    - ADIF logging: Excessive time to confirm QSO logged successfully when using
       large adif files. 200,000 record check now takes ~1 sec (previous ~45 secs)

 


locked Re: JTAlert V2.15.18 -

Mike Adams <mikeadams@...>
 

Same issue here - starts OK but on pressing settings I get MYSQL wont start fatal error and it closes
Mike G0AMO


locked Re: Double click on spot - with JTDX

Doug Munday
 

Thanks Laurie!   This is what I suspected.  I'll post this issue to the JTDX group and see if it can be addressed on their side. 

73,
Doug - W7DRM