Date   

locked Can not get JT Alert to install correctly

W8UV Phil
 

My activity bar only shows v2.15,7 qnd ACL no controls such as view,\
I am running window 10 i7 processor.
This is the computer in the shack.
My laptop every thing is correct.
I have uninstalled and re downloaded the program but get same results.
Any suggestions?
Phil  W8UV

--
Phil  W8UV


locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

HamApps Support (VK3AMA)
 

On 23/01/2020 4:07 pm, WB8ASI Herb wrote:
Beta build 0003 was 16.7KB.   This one 0006 says 16.4MB.  Yes MB, and download time estimated 20min+.  I'm running great on 0003 and don't need the Marathon, but wonder what's happening?   Tried several times.  Will try again tomorrow morning.  Thanks and GN. 73, Herb WB8ASI

~16.4MB is correct, Beta 0003 was not 16.7KB, it would also ~16.4MB. Look again.

    My Windows File Explorer view of the recent builds, they are all 16.7 thousand KB

   


de Laurie VK3AMA
 



locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

WB8ASI Herb
 

Beta build 0003 was 16.7KB.   This one 0006 says 16.4MB.  Yes MB, and download time estimated 20min+.  I'm running great on 0003 and don't need the Marathon, but wonder what's happening?   Tried several times.  Will try again tomorrow morning.  Thanks and GN. 73, Herb WB8ASI.


locked Re: Long logging time

John Holmes W9ILY
 

Laurie,
My ADIF file is now 75,077 Kb and the time between when I click on "log this
QSO" to when the notice that the QSO was logged is 64 seconds timed with a
stopwatch. Also, there are more than 4 decoding passes in WSJT-X and the
beginning of a 5th before the notice pops up that the "QSO was logged" and
the decoded calls begin to appear in JTAlert again.
I have excluded JTAlert from my anti-virus scan as suggested.

John W9ILY


locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

WB8ASI Herb
 

Thanks Laurie, I'll try again. Usually they are very quick, thus when it said 20min, I was perplexed. I tried going to HamApps group direct rather than thru the email, but still the same. Must be just me since nobody else is reporting a problem. Thanks, Herb

On January 22, 2020 at 9:57 PM "Laurie, VK3AMA" <hamapps.support@vkdxer.com> wrote:




On 23/01/2020 11:55 am, WB8ASI Herb wrote:
Something seems wrong.  Download time is taking forever.
Working fine here. The HamApps server where the file is stored is US
based, so I have the VK -> US delays to contend with along with my
crappy broadband. The file downloaded to me in just under 60 secs.

de Laurie VK3AMA




locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

Laurie, VK3AMA
 

On 23/01/2020 11:55 am, WB8ASI Herb wrote:
Something seems wrong.  Download time is taking forever.
Working fine here. The HamApps server where the file is stored is US based, so I have the VK -> US delays to contend with along with my crappy broadband. The file downloaded to me in just under 60 secs.

de Laurie VK3AMA


locked Suggestion Box

WB8ASI Herb
 

Laurie,    I'm enjoying 2.15.7 Beta build 0003 with Log4OM V2 running just great!!!!    Many thanks for your quick response to the Log4OM changes.  As I find myself operating with my setup here tonight, I offer the following suggestion for consideration.......I really like using the Decodes Window.  I'm used to reading columns of data like in logging and clusters, and find it much easier than trying to quickly scan up to 4 rows of 9 slots of Call Display.  If the Main Menu bar was on the top of the Decodes window, and I could send a text message from the Decodes window, the old Header could be eliminated and provide precious screen space, and all would be that much sweeter.   Thanks for all you do.  73, Herb WB8ASI


locked Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

WB8ASI Herb
 

Something seems wrong.  Download time is taking forever.


locked Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan

HamApps Support (VK3AMA)
 

This is the latest build of JTAlert with Log4OMV2 support.
It fixes the broken Marathon Scan which was returning nothing as worked this year.

https://dnl.HamApps.com/Beta/JTAlert.2.15.7.build.0006.Beta.Setup.exe

Instructions for correct Log4OM V2 and JTAlert setup can be found here...
https://hamapps.groups.io/g/Support/message/27318

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

HamApps Support (VK3AMA)
 

On 23/01/2020 10:52 am, Mike Davies wrote:
OK.  Bedtime in the UK now.  Have a great day coding and thanks for the hard work.

Mike, G0KAD (OP GX3WSC)

RRR, already fixed, just waiting on the compilation to complete & upload (~30 mins).

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

Mike Davies
 

OK.  Bedtime in the UK now.  Have a great day coding and thanks for the hard work.

Mike, G0KAD (OP GX3WSC)


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

HamApps Support (VK3AMA)
 

On 23/01/2020 10:35 am, Mike Davies wrote:
Yes I've run the scanlog and it seemed to pick up a lot of differences from my V1 log in DXCC and Zones which I wouldn't have expected.  I wonder if the date is being checked correctly?  I will try to compare V1 with V2 tomorrow evening when I have some more time.
Don't bother checking against V1. The V2 Marathon scan is broken. I'll post a new build once corrected.

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

HamApps Support (VK3AMA)
 

On 23/01/2020 10:00 am, Mike Davies wrote:
It seems to work except I don't seem to have worked any countries in the 2020 Marathon which is worrying as I've got 143 in the log!

Confirmed, the Marathon Scan is broken for V2 logs. V2 changed the log schemas, the Date & Time is now recorded as a single value, in V1 they were recorded as separate values. I need to recheck/test the SQL queries, they are broken with V2 (both the SQLite and MySQL logs).

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

Mike Davies
 

Yes I've run the scanlog and it seemed to pick up a lot of differences from my V1 log in DXCC and Zones which I wouldn't have expected.  I wonder if the date is being checked correctly?  I will try to compare V1 with V2 tomorrow evening when I have some more time.


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

HamApps Support (VK3AMA)
 

On 23/01/2020 10:00 am, Mike Davies wrote:
It seems to work except I don't seem to have worked any countries in the 2020 Marathon which is worrying as I've got 143 in the log!
Have you run the JTAlert Scan Log? That needs to be done to get the Marathon lists updated.

de Laurie VK3AMA


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

Mike Davies
 

It seems to work except I don't seem to have worked any countries in the 2020 Marathon which is worrying as I've got 143 in the log!


locked Re: Long logging time

Michael Black
 

One thing to check is if you can exclude that file/directory from your antivirus antimalware scanning.

de Mike W9MDB



On Wednesday, January 22, 2020, 03:56:54 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 23/01/2020 7:13 am, John Holmes W9ILY wrote:
Laurie et al,
I am using DX4WIN but not directly logging to it. I produce a full ADI log
in DX4WIN, then in JTAlert I browse to that file and choose it as my log
file. There is nothing external happening for JTAlert. I do this so I will
have my entire log scanned and new countries, etc. will be alerted. I update
this Full log every few days in DX4WIN and choose the newly created full
file in JTAlert. Is this not correct?

John W9ILY
OK John,

Your using ADIF logging. Of all the loggers supported, that should be the fastest in writing the new QSO to the log file, its a simple file append command.

In your original message you said
I have logging implemented and have noticed that a long time (about 70 seconds after I click on OK to log the contact) passes before the contact is successfully logged.

How are you determining it is taking 70 seconds to update your adif file?

What is the reported size or your adif file?

de Laurie VK3AMA


locked Re: Long logging time

HamApps Support (VK3AMA)
 

On 23/01/2020 7:13 am, John Holmes W9ILY wrote:
Laurie et al,
I am using DX4WIN but not directly logging to it. I produce a full ADI log
in DX4WIN, then in JTAlert I browse to that file and choose it as my log
file. There is nothing external happening for JTAlert. I do this so I will
have my entire log scanned and new countries, etc. will be alerted. I update
this Full log every few days in DX4WIN and choose the newly created full
file in JTAlert. Is this not correct?

John W9ILY
OK John,

Your using ADIF logging. Of all the loggers supported, that should be the fastest in writing the new QSO to the log file, its a simple file append command.

In your original message you said
I have logging implemented and have noticed that a long time (about 70 seconds after I click on OK to log the contact) passes before the contact is successfully logged.

How are you determining it is taking 70 seconds to update your adif file?

What is the reported size or your adif file?

de Laurie VK3AMA


locked Re: Long logging time

John Holmes W9ILY
 

Laurie et al,
I am using DX4WIN but not directly logging to it. I produce a full ADI log
in DX4WIN, then in JTAlert I browse to that file and choose it as my log
file. There is nothing external happening for JTAlert. I do this so I will
have my entire log scanned and new countries, etc. will be alerted. I update
this Full log every few days in DX4WIN and choose the newly created full
file in JTAlert. Is this not correct?

John W9ILY


locked Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.

HamApps Support (VK3AMA)
 

On 23/01/2020 6:50 am, Rich McCabe wrote:

Update.  Downloaded file to my notebook and it was fine. Just transferred it over to my desktop and it gook off fine.

So not sure what the deal was. It just appeared like wrong OS!

Rich

That sounds very much like a corrupted (truncated) download.
Repeated downloads from the same machine were likely get delivered a cached (by your ISP) version of the original download.

de Laurie VK3AMA

5601 - 5620 of 32849