|
locked
Can not get JT Alert to install correctly
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
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
|
By
W8UV Phil
·
#27381
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan
~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
~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
|
By
HamApps Support (VK3AMA)
·
#27380
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan
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
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
|
By
WB8ASI Herb
·
#27379
·
|
|
locked
Re: Long logging time
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
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
|
By
John Holmes W9ILY
·
#27378
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan
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
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
|
By
WB8ASI Herb
·
#27377
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan
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
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
|
By
Laurie, VK3AMA
·
#27376
·
|
|
locked
Suggestion Box
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
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
|
By
WB8ASI Herb
·
#27375
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan
Something seems wrong. Download time is taking forever.
Something seems wrong. Download time is taking forever.
|
By
WB8ASI Herb
·
#27374
·
|
|
locked
Latest JTAlert Beta, 2.15.7 build 0006, for Log4OMV2. Fixed Marathon Scan
This is the latest build of JTAlert with Log4OMV2 support.
It fixes the broken Marathon Scan which was returning nothing as worked this year.
This is the latest build of JTAlert with Log4OMV2 support.
It fixes the broken Marathon Scan which was returning nothing as worked this year.
|
By
HamApps Support (VK3AMA)
·
#27373
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
RRR, already fixed, just waiting on the compilation to complete & upload (~30 mins).
de Laurie VK3AMA
RRR, already fixed, just waiting on the compilation to complete & upload (~30 mins).
de Laurie VK3AMA
|
By
HamApps Support (VK3AMA)
·
#27372
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
OK. Bedtime in the UK now. Have a great day coding and thanks for the hard work.
Mike, G0KAD (OP GX3WSC)
OK. Bedtime in the UK now. Have a great day coding and thanks for the hard work.
Mike, G0KAD (OP GX3WSC)
|
By
Mike Davies
·
#27371
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
Don't bother checking against V1. The V2 Marathon scan is broken. I'll post a new build once corrected.
de Laurie VK3AMA
Don't bother checking against V1. The V2 Marathon scan is broken. I'll post a new build once corrected.
de Laurie VK3AMA
|
By
HamApps Support (VK3AMA)
·
#27370
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
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
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
|
By
HamApps Support (VK3AMA)
·
#27369
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
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
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
|
By
Mike Davies
·
#27368
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
Have you run the JTAlert Scan Log? That needs to be done to get the Marathon lists updated.
de Laurie VK3AMA
Have you run the JTAlert Scan Log? That needs to be done to get the Marathon lists updated.
de Laurie VK3AMA
|
By
HamApps Support (VK3AMA)
·
#27367
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
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!
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!
|
By
Mike Davies
·
#27366
·
|
|
locked
Re: Long logging time
One thing to check is if you can exclude that file/directory from your antivirus antimalware scanning.
de Mike W9MDB
One thing to check is if you can exclude that file/directory from your antivirus antimalware scanning.
de Mike W9MDB
|
By
Michael Black
·
#27365
·
|
|
locked
Re: Long logging time
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.
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.
|
By
HamApps Support (VK3AMA)
·
#27364
·
|
|
locked
Re: Long logging time
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
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
|
By
John Holmes W9ILY
·
#27363
·
|
|
locked
Re: Latest JTAlert Beta, 2.15.7 build 0003, for Log4OMV2. Multi-instance DX Call sending now working.
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
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
|
By
HamApps Support (VK3AMA)
·
#27362
·
|