Date   

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


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

asobel@...
 

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: Can't get to JTALER "Manage Setting'

Ed Fuller
 

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 Re: Can't get to JTALER "Manage Setting'

HamApps Support (VK3AMA)
 

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 Re: Can't get to JTALER "Manage Setting'

Ed Fuller
 

Mike, that was it.  Thanks much, I would not have thought of that.  What a great program and a wonderful support group.

 

Ed WA5RHG

 


From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Sunday, January 26, 2020 12:29 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Can't get to JTALER "Manage Setting'

 

Try the 32 bit version.



On Jan 26, 2020, at 12:21 PM, Ed Fuller <emfuller70@...> 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


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

Michael Black
 

Try the 32 bit version.


On Jan 26, 2020, at 12:21 PM, Ed Fuller <emfuller70@...> 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


locked Can't get to JTALER "Manage Setting'

Ed Fuller
 

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


locked Re: JTAlert won't open

Jim Cooper
 

On 26 Jan 2020 at 6:56, edward bishop via Groups.Io
wrote:

Ok the crazy thing is that 2.15.8
works okay on one computer but not the
other, I had 2.15.7 it works but dx
keeper was logging a state In the
province for dx thanks
I have noticed for quite some time,
thru several versions, that in the lookup
info line if a previous lookup was USA
with a state shown, and the next lookup
is DX without a province the state info
is not cleared.

I didn't 'complain' as Laurie has had
enough on the plate lately to worry about
such a minor glitch, but it's probably why
you are getting a state in the province slot.

w2jc


locked Re: Worked B4 mainly on 5T5PA

rogich@...
 

I reloaded it a few times but thanks for explaination. .. Jerry


locked Re: JTAlert QRZ Lookup stopping

Morris WA4MIT
 

Hi Laurie thanks for your reply. Majority of times sleep is used is like at night when I am going to bed or leaving house for a period of time. I try to set sleep to never when going to be at radio and I generally do not leave Alert or other ham programs running only ham program I may leave on is HRD and only if not leaving the house but at night everything is closed then when stopping ham operation set sleep back on.
Thanks I will try to be more observant of any particular things happening. FT8 operation is so quick it is hard to follow exactly what happens if your in QSO. 
73 Morris WA4MIT