|
locked
Re: 2.50.3 problems
JTAlert Support (VK3AMA)
On 13/07/2021 11:17 am, Masaaaki Maeda
wrote:
That is further indication that the JTAlertV2.Manager.exe process is not running. Three typical causes...
de Laurie VK3AMA
|
|
|
|
locked
Re: Callsign window gone after update to 2.5.3
JTAlert Support (VK3AMA)
On 13/07/2021 10:25 am, W9WO wrote:
I just updated from 2.5.0 to 2.5.3 and now the decoded callsigns window is gone. It used to be just above the actual JTAlert window. WSJT-X is decoding fine. I've done several updates in the past and don't ever remember having this issue. Any help will be greatly appreciated. Since yours was a 2.50.0 upgrade, I suspect an incompatible NET 5.0.x Desktop Runtime. Starting with JTAlert 2.50.1 the installer is distributed as separate 32bit and 64bit versions. You need to ensure that the NET 5.0.x Desktop runtime you have installed matches the JTAlert installer, both need to be 64bit(x64) or 32bit(x86), they cannot be different. See this message https://hamapps.groups.io/g/Support/message/35794 Do any of the other 2.50.x windows open? See the "star icon" entries under the main window "View" menu. de Laurie VK3AMA
|
|
|
|
locked
2.50.3
Jim N6VH
JTAlert 2.50.3 is running fine here - no problems.
73, Jim N6VH
|
|
|
|
locked
Re: new install
Marv Olnes
Jim, I agree, I downloaded version 3.50.3 with no issues whatsoever.
Currently running: Windows 10 Pro Norton 360 Acronis WSJT-X, ver. 2.4.0 JTAlert, ver. 2.50.3 Amateur Contact Log, ver. 7.0.1.6 for my daily logger
Marv Marvin Olnes Jr ARS N0MHL
-----Original Message-----
for what it's worth, I just downloaded the 64 bit version of the new general release; installed the above; did not even get a 'malware' alert this time :)) started it up; everything opens and runs just like it should.
Running it with WSJT-X v2.4.0 (did not install for JTDX) Windows 10 pro
Not a glitch to be seen ... [I better shut up before the pc gremlins hear me!]
w2jc
|
|
|
|
locked
Re: 2.50.3 Intalled but not worked
Masaaaki Maeda
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, July 12, 2021 7:15 PM To: Support@HamApps.groups.io Subject: Re: [HamApps] 2.50.3 Intalled but not worked
On 13/07/2021 8:55 am, Masaaaki Maeda wrote:
|
|
|
|
locked
Re: 2.50.3 problems
Masaaaki Maeda
Andy’s symptom is similar to mine. In addition, I can’t hear any sound.
Maeda
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Carey, WB4HXE
Sent: Monday, July 12, 2021 9:14 PM To: Support@hamapps.groups.io Subject: Re: [HamApps] 2.50.3 problems
2.50.3 running great here also.No problem with any windows. 73, Carey, WB4HXE
On Mon, Jul 12, 2021 at 6:32 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
--
|
|
|
|
locked
Re: 2.50.3 problems
Carey, WB4HXE
2.50.3 running great here also.No problem with any windows. 73, Carey, WB4HXE
On Mon, Jul 12, 2021 at 6:32 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
Carey Fisher
--
73, Carey, WB4HXE
|
|
|
|
locked
Re: 2.50.3 problems
Carey, WB4HXE
2.50.3 running great here also.No problem with any windows. 73, Carey, WB4HXE
On Mon, Jul 12, 2021 at 7:52 PM Paul Sturpe <sturpe@...> wrote:
Carey Fisher
--
73, Carey, WB4HXE
|
|
|
|
locked
Re: 2.50.3 Intalled but not worked
Masaaaki Maeda
In addition,
Thanks!
Masa
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, July 12, 2021 7:15 PM To: Support@HamApps.groups.io Subject: Re: [HamApps] 2.50.3 Intalled but not worked
On 13/07/2021 8:55 am, Masaaaki Maeda wrote:
|
|
|
|
locked
Re: 2.50.3 Intalled but not worked
Masaaaki Maeda
Lurie,
I did Windows update and defender update. Nothing has change.
Maeda
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, July 12, 2021 7:15 PM To: Support@HamApps.groups.io Subject: Re: [HamApps] 2.50.3 Intalled but not worked
On 13/07/2021 8:55 am, Masaaaki Maeda wrote:
|
|
|
|
locked
Re: Callsign window gone after update to 2.5.3
W9WO
Correction. 2.50.3 and not 2.5.3.
|
|
|
|
locked
Callsign window gone after update to 2.5.3
W9WO
Hello to all.
I just updated from 2.5.0 to 2.5.3 and now the decoded callsigns window is gone. It used to be just above the actual JTAlert window. WSJT-X is decoding fine. I've done several updates in the past and don't ever remember having this issue. Any help will be greatly appreciated. Tnx. Darrell W9WO
|
|
|
|
locked
Re: 2.50.3 Intalled but not worked
Masaaaki Maeda
Lurie,
Thank you for quick response. Yes, I am using only Windows defender. Security intelligence version 1.343.888.0 Date 7/12/2021
Is this OK?
Maeda
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, July 12, 2021 7:15 PM To: Support@HamApps.groups.io Subject: Re: [HamApps] 2.50.3 Intalled but not worked
On 13/07/2021 8:55 am, Masaaaki Maeda wrote:
|
|
|
|
locked
Re: 2.50.3 problems
No problem here with 2.50.3. Running Windows 10 pro 64 bit.
Paul Sturpe, W3GQ QSL Bureau Mgr. W4 K4 N4 Prefixes
|
|
|
|
locked
Worked B4 glitch.
DAVID MM0AMW
I've noticed if I work a station or stations on FT4 then on their next transmission after I log them, they are correctly identified as worked B4 in JTAlert. However , if I then switch to FT8, even momentarily and then return to FT4, these stations I worked a minute or so earlier, appear as unworked new stations. A restrart of JTAlert sorts it all out and these stations then correctly identify as worked B4.
I've noticed this anomaly back to at least v. 2.16.17 and it is also present throughout the new 2.50.x versions. I use JTDX 2.2.156 along with JTAlert 2.50.3. A very minor problem in a fantastic program. 73 David MM0AMW
|
|
|
|
Alan Sorum WL7CG
Task Manager shows "Audio & Visual Alerts for WSJT...". I manually updated the definition file, but it didn't change. I turned off defender, but it didn't change the behavior.
Alan WL7CG
|
|
|
|
locked
new install
Jim Cooper
for what it's worth, I just
downloaded the 64 bit version of the new general release; installed the above; did not even get a 'malware' alert this time :)) started it up; everything opens and runs just like it should. Running it with WSJT-X v2.4.0 (did not install for JTDX) Windows 10 pro Not a glitch to be seen ... [I better shut up before the pc gremlins hear me!] w2jc
|
|
|
|
locked
Re: 2.50.3 Intalled but not worked
JTAlert Support (VK3AMA)
On 13/07/2021 8:55 am, Masaaaki Maeda
wrote:
What PC Protection software are you using? Is it MS Defender? If so update its definitions. de Laurie VK3AMA
|
|
|
|
JTAlert Support (VK3AMA)
On 13/07/2021 8:44 am, Alan Sorum WL7CG
wrote:
I downloaded the 64bit version. Looking a the Task Manager, JTAlert comes and goes. I think you mean JTAlertV2.Manager.exe comes and goes, is that correct? You would not have been able to get to the "Help -> About" menu if JTAlert is not running. I am running the 64bit version here without problem on 2 PCs. Sounds like your Protection software is interfering. What are you using, is it MS Defender? If so, try forcing an update of its definitions files. JTAlert was submitted yesterday to MS for Virus/Malware analysis and they confirmed it to be infection free but did include a note to ensure definitions are up-to-date. de Laurie VK3AMA
|
|
|
|
locked
2.50.3 Intalled but not worked
_Lurie, I installed newest version. But call sign window does not appear, even dropdown menu has stars. Message window comes appear periodically. Over all very slow. (sound does not appear too) Framewok check is ok. (.NET 5.0.7 X64) Where should I change?
Masa JR1AQN
|
|
|
