Date   

locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

Dan Bathker
 


Laurie
My apologies for my previous inaccurate words, "
Net Framework is installed"

What is installed here is "Microsoft Windows Desktop Runtime" - 5.0.6 (x64) - installed since May 22 2021.
Which can be seen as the third item up from bottom of the list in my screen-capture immediately below:


And allow me to Assure you Laurie my HP 12 GB machine and MS W-10 sw are both 64 bit here.

Question #1 (one Q at a time):
Is MSW Desktop Runtime 5.0.6 (x64) good enough for your latest HamApps JTAlert (x64) 2.50.5 as was reinstalled here Again only 2 days ago?

Respectfully,
K6BLG
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------



On 8/24/2021 6:18 PM, HamApps Support (VK3AMA) wrote:
On 25/08/2021 11:03 am, Dan Bathker wrote:

Net Framework is installed on Win10

If that statement is accurate, than that is the problem. You need to install the correct .NET 5.0.x Desktop Runtime. <- note there is no "Framework" in that title.

You don't say exactly what doesn't work, except that JTAlert doesn't work with any WSJT-X version.

If you haven't been able to get JTAlert to work after 6 months of trying (that seems like an exaggeration to me), I suggest your next course of action is to find an Elmer who can assist in resolving your broken installation.

de Laurie VK3AMA


-- 
Dan Bathker
PO Box 23
La Canada CA 91012

d.bathker@...

Virus-free. www.avast.com


locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

Michael Black
 

Hi Dan,
Will you be around tomorrow we could hook up and see about getting you running?

I'm normally around after 0800 Central time.
I help a lot of people.

Call me 217-960-0233

Mike W9MDB





On Tuesday, August 24, 2021, 08:03:23 PM CDT, Dan Bathker <d.bathker@...> wrote:



I too am unable get any issue of JTAlert to work with any version of WSJT-X including latest ver. 2.50.1.

Net Framework is installed on Win10 12 GB machine here and after still another fresh reinstall of both WSJT-X and JTAlert the confirmation popup
continues to indicate it remains "aboard and well".

I have read, reread and reread again everything I can get my eyes on including the Incredible amount traffic generated by this group addressing endless problems.
 
I have also tried to understand directions given on this group as written by Laurie such as the need to "populate" a log.
But there is no such direction dealing with "populate" a log in any user instructions I can find for JTAlert, only mention of "populate" I have seen was on this group by Laurie.

I am close to throwing in the towel.
6 months effort struggling with fussy software still not operating is too much to ask of anyone, even an 83 year old ham licensed for 68 years.

And yes I well realize Laurie is considered by many as a hero.
Unfortunately with my continued negative results with JTAlert Laurie is not yet my hero.

My considered suggestion:
Give Up adding even more 'bells and whistles' to such Already Complicated software and produce a stripped-down "lite" version that hams can actually get running.

respectfully
K6BLG
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------    


On 8/24/2021 5:08 PM, HamApps Support (VK3AMA) wrote:
On 25/08/2021 9:17 am, jrpascucci via groups.io wrote:
Hi, 

I sympathize with the person in another thread who said, simply, 'nothing works' - I was also having troubles for a couple of days and had never seen it approaching working until I (a software engineer with 30+ years background) dug down a bit deeply and found the problem.

Symptoms: Title bar says ???m where it should read the band, no Help->About box spawns, literally no audio of any kind plays, many of the windows didn't function (a few did, which made it impossible to understand from someone who has never seen it working), but certainly no interactions with wsjt-x worked in any way.

Description: After following the instructions, I already had the latest released .net, tried wsjt-x version 2.2.2, 2.4.0 and 2.5.0 (which is what I'm running now), set the multicast according to the help instructions.
    NB: the .net check tool at the end of install had never run correctly, but kept pointing me to an indistinct location, where I had followed the instructions and was told I already have the .net, but indeed I had the wrong thing (the console version in x86, I believe).

What needed to happen was that it requires the .NET 5.0 Desktop runtime.
       This is located here.

Root cause: When I ran jtalertv2.manager.exe by hand, I got the following error (which was not reported in any other way)
A fatal error occurred. The required library hostfxr.dll could not be found. If this is a self-contained application, that library should exist in [C:\Program Files (x86)\HamApps\JTAlert\pluginsX\win-x64\].If this is a framework-dependent application, install the runtime in the global location [C:\Program Files\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\InstallLocation]."
Hostfxr.dll existed in: C:\Program Files (x86)\dotnet\host\fxr\5.0.9, which is the wrong thing, it needs to exist C:\Program Files\dotnet\host\fxr\5.0.9

Recommended User Experience fix: some method of the UI detecting that jtalertv2.manager.exe is not running when started and indicating that the problem lies there might help normal people diagnose what's going on.

Anyway, I look forward to using your software. 

Thanks, and
73,

JRP
KC1MNC

The several windows not opening and sound test failing is an indication that the JTAlertV2.Manager.exe process, which handles all those, is not running. The cause in 99.99% of cases is an incorrect NET 5 install, specifically not installing the correct "Desktop" Runtime.

The framework check constantly reporting the Desktop Runtime not being installed was behaving correctly, it was doing its job.

This pinned FAQ message https://hamapps.groups.io/g/Support/message/35794 has instructions for installing the correct runtime along with the latest MS down load links.

Sorry, not much more I can do if the non-desktop version of the runtime is incorrectly installed despite the numerous postings to this group and having the framework check report a missing runtime.

de Laurie VK3AMA


--
Dan Bathker
PO Box 23
La Canada CA 91012

d.bathker@...

Virus-free. www.avast.com


locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

HamApps Support (VK3AMA)
 

On 25/08/2021 11:03 am, Dan Bathker wrote:

Net Framework is installed on Win10

If that statement is accurate, than that is the problem. You need to install the correct .NET 5.0.x Desktop Runtime. <- note there is no "Framework" in that title.

You don't say exactly what doesn't work, except that JTAlert doesn't work with any WSJT-X version.

If you haven't been able to get JTAlert to work after 6 months of trying (that seems like an exaggeration to me), I suggest your next course of action is to find an Elmer who can assist in resolving your broken installation.

de Laurie VK3AMA


locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

Dan Bathker
 


I too am unable get any issue of JTAlert to work with any version of WSJT-X including latest ver. 2.50.1.

Net Framework is installed on Win10 12 GB machine here and after still another fresh reinstall of both WSJT-X and JTAlert the confirmation popup
continues to indicate it remains "aboard and well".

I have read, reread and reread again everything I can get my eyes on including the Incredible amount traffic generated by this group addressing endless problems.
 
I have also tried to understand directions given on this group as written by Laurie such as the need to "populate" a log.
But there is no such direction dealing with "populate" a log in any user instructions I can find for JTAlert, only mention of "populate" I have seen was on this group by Laurie.

I am close to throwing in the towel.
6 months effort struggling with fussy software still not operating is too much to ask of anyone, even an 83 year old ham licensed for 68 years.

And yes I well realize Laurie is considered by many as a hero.
Unfortunately with my continued negative results with JTAlert Laurie is not yet my hero.

My considered suggestion:
Give Up adding even more 'bells and whistles' to such Already Complicated software and produce a stripped-down "lite" version that hams can actually get running.

respectfully
K6BLG
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------    


On 8/24/2021 5:08 PM, HamApps Support (VK3AMA) wrote:
On 25/08/2021 9:17 am, jrpascucci via groups.io wrote:
Hi, 

I sympathize with the person in another thread who said, simply, 'nothing works' - I was also having troubles for a couple of days and had never seen it approaching working until I (a software engineer with 30+ years background) dug down a bit deeply and found the problem.

Symptoms: Title bar says ???m where it should read the band, no Help->About box spawns, literally no audio of any kind plays, many of the windows didn't function (a few did, which made it impossible to understand from someone who has never seen it working), but certainly no interactions with wsjt-x worked in any way.

Description: After following the instructions, I already had the latest released .net, tried wsjt-x version 2.2.2, 2.4.0 and 2.5.0 (which is what I'm running now), set the multicast according to the help instructions.
    NB: the .net check tool at the end of install had never run correctly, but kept pointing me to an indistinct location, where I had followed the instructions and was told I already have the .net, but indeed I had the wrong thing (the console version in x86, I believe).

What needed to happen was that it requires the .NET 5.0 Desktop runtime.
       This is located here.

Root cause: When I ran jtalertv2.manager.exe by hand, I got the following error (which was not reported in any other way)
A fatal error occurred. The required library hostfxr.dll could not be found. If this is a self-contained application, that library should exist in [C:\Program Files (x86)\HamApps\JTAlert\pluginsX\win-x64\].If this is a framework-dependent application, install the runtime in the global location [C:\Program Files\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\InstallLocation]."
Hostfxr.dll existed in: C:\Program Files (x86)\dotnet\host\fxr\5.0.9, which is the wrong thing, it needs to exist C:\Program Files\dotnet\host\fxr\5.0.9

Recommended User Experience fix: some method of the UI detecting that jtalertv2.manager.exe is not running when started and indicating that the problem lies there might help normal people diagnose what's going on.

Anyway, I look forward to using your software. 

Thanks, and
73,

JRP
KC1MNC

The several windows not opening and sound test failing is an indication that the JTAlertV2.Manager.exe process, which handles all those, is not running. The cause in 99.99% of cases is an incorrect NET 5 install, specifically not installing the correct "Desktop" Runtime.

The framework check constantly reporting the Desktop Runtime not being installed was behaving correctly, it was doing its job.

This pinned FAQ message https://hamapps.groups.io/g/Support/message/35794 has instructions for installing the correct runtime along with the latest MS down load links.

Sorry, not much more I can do if the non-desktop version of the runtime is incorrectly installed despite the numerous postings to this group and having the framework check report a missing runtime.

de Laurie VK3AMA


--
Dan Bathker
PO Box 23
La Canada CA 91012

d.bathker@...

Virus-free. www.avast.com


locked Re: Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

HamApps Support (VK3AMA)
 

On 25/08/2021 9:17 am, jrpascucci via groups.io wrote:
Hi, 

I sympathize with the person in another thread who said, simply, 'nothing works' - I was also having troubles for a couple of days and had never seen it approaching working until I (a software engineer with 30+ years background) dug down a bit deeply and found the problem.

Symptoms: Title bar says ???m where it should read the band, no Help->About box spawns, literally no audio of any kind plays, many of the windows didn't function (a few did, which made it impossible to understand from someone who has never seen it working), but certainly no interactions with wsjt-x worked in any way.

Description: After following the instructions, I already had the latest released .net, tried wsjt-x version 2.2.2, 2.4.0 and 2.5.0 (which is what I'm running now), set the multicast according to the help instructions.
    NB: the .net check tool at the end of install had never run correctly, but kept pointing me to an indistinct location, where I had followed the instructions and was told I already have the .net, but indeed I had the wrong thing (the console version in x86, I believe).

What needed to happen was that it requires the .NET 5.0 Desktop runtime.
       This is located here.

Root cause: When I ran jtalertv2.manager.exe by hand, I got the following error (which was not reported in any other way)
A fatal error occurred. The required library hostfxr.dll could not be found. If this is a self-contained application, that library should exist in [C:\Program Files (x86)\HamApps\JTAlert\pluginsX\win-x64\].If this is a framework-dependent application, install the runtime in the global location [C:\Program Files\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\InstallLocation]."
Hostfxr.dll existed in: C:\Program Files (x86)\dotnet\host\fxr\5.0.9, which is the wrong thing, it needs to exist C:\Program Files\dotnet\host\fxr\5.0.9

Recommended User Experience fix: some method of the UI detecting that jtalertv2.manager.exe is not running when started and indicating that the problem lies there might help normal people diagnose what's going on.

Anyway, I look forward to using your software. 

Thanks, and
73,

JRP
KC1MNC

The several windows not opening and sound test failing is an indication that the JTAlertV2.Manager.exe process, which handles all those, is not running. The cause in 99.99% of cases is an incorrect NET 5 install, specifically not installing the correct "Desktop" Runtime.

The framework check constantly reporting the Desktop Runtime not being installed was behaving correctly, it was doing its job.

This pinned FAQ message https://hamapps.groups.io/g/Support/message/35794 has instructions for installing the correct runtime along with the latest MS down load links.

Sorry, not much more I can do if the non-desktop version of the runtime is incorrectly installed despite the numerous postings to this group and having the framework check report a missing runtime.

de Laurie VK3AMA


locked Solution: 2.50.5 and net 5.0 incompatibility - no about box, no audio test, random things don't function

jrpascucci@...
 

Hi, 

I sympathize with the person in another thread who said, simply, 'nothing works' - I was also having troubles for a couple of days and had never seen it approaching working until I (a software engineer with 30+ years background) dug down a bit deeply and found the problem.

Symptoms: Title bar says ???m where it should read the band, no Help->About box spawns, literally no audio of any kind plays, many of the windows didn't function (a few did, which made it impossible to understand from someone who has never seen it working), but certainly no interactions with wsjt-x worked in any way.

Description: After following the instructions, I already had the latest released .net, tried wsjt-x version 2.2.2, 2.4.0 and 2.5.0 (which is what I'm running now), set the multicast according to the help instructions.
    NB: the .net check tool at the end of install had never run correctly, but kept pointing me to an indistinct location, where I had followed the instructions and was told I already have the .net, but indeed I had the wrong thing (the console version in x86, I believe).

What needed to happen was that it requires the .NET 5.0 Desktop runtime.
       This is located here.

Root cause: When I ran jtalertv2.manager.exe by hand, I got the following error (which was not reported in any other way)
A fatal error occurred. The required library hostfxr.dll could not be found. If this is a self-contained application, that library should exist in [C:\Program Files (x86)\HamApps\JTAlert\pluginsX\win-x64\].If this is a framework-dependent application, install the runtime in the global location [C:\Program Files\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\InstallLocation]."
Hostfxr.dll existed in: C:\Program Files (x86)\dotnet\host\fxr\5.0.9, which is the wrong thing, it needs to exist C:\Program Files\dotnet\host\fxr\5.0.9

Recommended User Experience fix: some method of the UI detecting that jtalertv2.manager.exe is not running when started and indicating that the problem lies there might help normal people diagnose what's going on.

Anyway, I look forward to using your software. 

Thanks, and
73,

JRP
KC1MNC


locked Re: Music note colors

HamApps Support (VK3AMA)
 

On 25/08/2021 8:19 am, Gordon Brown wrote:
What is the JTDX crashing about. I was getting that when I tried jtdx.
You need to update your JTAlert version to avoid the JTDX crashes. This was fixed many versions ago.
Note, the fix is not a fix for JTDX, but simply a workaround in JTAlert to avoid causing JTDX to crash due to incorrect JTDX coding.

FYI, the crashing was caused by JTDX not handling the decode coloring instructions that are part of the WSJTX UDP protocol. The JTDX people stripped the coloring code out of the UDP handling code and failed to put in measures to ignore these no-longer-supported UDP messages. Without any internal code to ignore unsupported UDP instructions, their version of the WSJTX code simply crashed with an unhandled exception.

As for the reason for the JTDX people stripping the UDP coloring code, I don't know.

de Laurie VK3AMA


locked Re: Music note colors

Gordon Brown
 

What is the JTDX crashing about. I have been getting that when I tried jtdx.


locked Re: Prob Decode Windows

HamApps Support (VK3AMA)
 

On 23/08/2021 1:02 am, Johan Barre wrote:
@laurie the translate is correct, i do the delete and test always same probleme 
@Neil just reinstall .net desktop 64 bits and jtalert64bits my system is also 64 bits last windows reinstallation yesterday without antivirus malware after test probleme always present 
snif 

regards 

Check that you have a version of the .NET 4.7.2 (or 4.8) Framework installed. It should be as it is standard for current and updated versions of Windows, but it is possible it is not. The Decodes window requires the NET Framework 4.7.2 or 4.8

de Laurie VK3AMA


locked Re: Prob Decode Windows

HamApps Support (VK3AMA)
 

On 22/08/2021 9:56 pm, neil_zampella wrote:

just didn't think someone would install the 32 bit version of JTAlert on a 64 bit Windows system.

Neil, KN3ILZ


You would be surprised. I have seen many cases of 32bit JTAlert installed under 64bit windows, which is not a problem untill the user then tries to use the the 64bit NET install.

de Laurie VK3AMA


locked Re: Music note colors

HamApps Support (VK3AMA)
 

On 24/08/2021 12:31 am, NA2NY - John Hart via groups.io wrote:
Are the music note colors to be different on the different windows?  With JTDX they are mixed red and blue, but on WSJT-X they are all red.
I think on my W7 machine the were all the same color for each program.

Running W10  20H2 build 19042.1165    JTAlert 2.50.5

Thanks  John  NA2NY

The use of different colored icons was originally used to help the user (and the me doing support) identify if they were using the correct JTAlert shortcut for operating against WSJTX and JTDX. When running against JTDX, JTAlert has to make many code changes in order to accommodate the broken behavior (eg incompatible mode identifiers) or loss of functionality (eg no decode coloring that would cause JTDX to crash if it received a decode coloring instruction) of JTDX compared to WSJTX.

The blue colored icon allowed me and the end-user know they were using JTAlert correctly for JTDX.

Prior to the JTAlert 2.50.x series releases, all JTAlert windows would have matching colored titlebar icons. With the new 2.50.x series, the only place that JTDX specific hacks & workarounds exist in the code are in the main JTAlert window (the old style window) and it is the only window now showing the blue JTDX operation mode icon. This JTDX operating state is not currently being passed to the new 2.50.x windows as it is not needed, but that has the effect that these windows don't have the ability to switch to blue icons when using JTAlert with JTDX. Adding this to the new 2.50.x windows is on my todo-list, but not high-prority.

de Laurie VK3AMA


locked Re: On-Line Chat - Defect Confirmed

HamApps Support (VK3AMA)
 

I can confirm this is a defect.
Sent messages are never received with no error notification. Fortunately it affects only a very small number of JTAlert users. Unfortunately, there is no workaround or fix that can be applied to current JTAlert releases to restore the broken functionality.
The next release of JTAlert will have the fix.

de Laurie VK3AMA


locked Re: Music note colors

neil_zampella
 

I Don't run the clone, but when properly installed by the setup program, the ICON color scheme is WJST-X red, the clone blue.

As far as showing the same color on the windows ... that may be an oversight by Laurie as he's busy doing changes all over the program.

 

Neil, KN3ILZ

 


locked Re: Logger32 +JTAlert+IC-7300

Gerard Arsenault <jerrya@...>
 

The requirement to set up multicast is new to me. Everything worked as it should before this new update which coincidentally arrived after I started using the IC-7300. I did follow the steps to do so and JTAlert does decode now when Logger32 is launched. However, I may be missing something because now it appears that QSO's do not transfer automatically from WSJT-X to Logger32. To add to the frustration, I prefer JTDX for FT8 and there does not seem to be a provision for using multicast in that program so JTAlert does not work with Logger32 now as it did before.


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

I tried various things, including a 10 sec delay.  I got the same error.  It does put something in HRD logbook but the date is missing as well as some of the other fields.  It also puts a logbook entry direct from WSJT-X with everything correct.

I am thinking that there are other settings in WSJT-X and JTALERT which may be impacting things working correctly - i.e., JTALERT talking to WSJT-X and both talking to HRD Logbook.  Perhaps not, but that is my feeling after reviewing some YouTube sessions discussing similarities with my setup.  For example, there is a "QSO Forwarding" setup page in HRD Logbook.  My current settings do not match those that I found on several YouTube sessions.  I would like to find a person who is using the same setup I have (WSJT-X and JTALERT and HRD Logbook) so I could get screen shots of their setup.

I am usually pretty good at this stuff but not this time.  The setup I have is working, albeit not the best configuration and lacking in correct B4 data.

Just as an experiment I set my HRD Logging to on, then did a  Rebuild Alert Database.  That messed up the alert data for DXCC worked and wiped out the States Worked data.  I recovered from that as I keep good records of my current stuff before messing with new stuff..

I truly appreciate your help.  But, I regret bothering you.


On Mon, Aug 23, 2021 at 12:05 PM Steve Roth - AD4K via groups.io <ad4k.steven=gmail.com@groups.io> wrote:
Okay, I will keep trying.... Thanks

On Mon, Aug 23, 2021 at 9:40 AM neil_zampella <neilz@...> wrote:

The error just said that JTAlert couldn't verify that the QSO was updated, that could mean that the delay setting in JTAlert was not long enough.   The grayed 'B4' file is not a bad thing, its normal as JTAlert is going to your main log for all the older B4 data which means its updating each time you start the program.

You said that JTAlert showed the QSO as B4, and that's what you want.     As far as it colored red, that's a personal preference, I have mine setup fo show B4 as gray.

None of that (other than the verification) is a 'bad result'.   You can try increasing the time JTAlert pauses before it verifies the QSO was logged, or just turn that verification off.

Neil, KN3ILZ


locked Re: JTALERT "B4"

Steve Roth - AD4K
 

Okay, I will keep trying.... Thanks

On Mon, Aug 23, 2021 at 9:40 AM neil_zampella <neilz@...> wrote:

The error just said that JTAlert couldn't verify that the QSO was updated, that could mean that the delay setting in JTAlert was not long enough.   The grayed 'B4' file is not a bad thing, its normal as JTAlert is going to your main log for all the older B4 data which means its updating each time you start the program.

You said that JTAlert showed the QSO as B4, and that's what you want.     As far as it colored red, that's a personal preference, I have mine setup fo show B4 as gray.

None of that (other than the verification) is a 'bad result'.   You can try increasing the time JTAlert pauses before it verifies the QSO was logged, or just turn that verification off.

Neil, KN3ILZ


locked Music note colors

NA2NY - John Hart
 

Are the music note colors to be different on the different windows?  With JTDX they are mixed red and blue, but on WSJT-X they are all red.
I think on my W7 machine the were all the same color for each program.

Running W10  20H2 build 19042.1165    JTAlert 2.50.5

Thanks  John  NA2NY


locked Re: JTALERT "B4"

neil_zampella
 

The error just said that JTAlert couldn't verify that the QSO was updated, that could mean that the delay setting in JTAlert was not long enough.   The grayed 'B4' file is not a bad thing, its normal as JTAlert is going to your main log for all the older B4 data which means its updating each time you start the program.

You said that JTAlert showed the QSO as B4, and that's what you want.     As far as it colored red, that's a personal preference, I have mine setup fo show B4 as gray.

None of that (other than the verification) is a 'bad result'.   You can try increasing the time JTAlert pauses before it verifies the QSO was logged, or just turn that verification off.

Neil, KN3ILZ


locked Re: JTALERT B4 and Wanted call

Jim N6VH
 

On 8/22/2021 9:28 AM, Bob Frostholm wrote:
Thank you Jim,

That worked

73

Bob

Ko6Lu
Bob,

Great! Glad I could help.

73,

Jim N6VH


locked Re: JTALERT B4 and Wanted call

Bob Frostholm
 

Thank you Jim,

That worked

73

Bob

Ko6Lu

On 8/21/2021 11:45 AM, Jim N6VH via groups.io wrote:

On 8/21/2021 8:44 AM, Bob Frostholm wrote:
Hi Laurie,

As many have said, THANKS for the wonderful work you do to enhance our hobby.

I have an observation that may not have a solution.

I chase grids among other things...a fun way is chasing ships at sea as they progress through many unpopulated GRID squares of our oceans. Tonight after working RA0LQ/mm for the umpteenth time, I decided to add his call to the wanted call page. It see though, that since I have worked him before, it overrides my wanted call alert. I don't want to disable worked before as that would create havoc for me while waiting for his precious call to be decoded.

Since Worked B4 does not appear on the alerts priority I don't see a way to possibly  overcome this dilemma.

Is there a solution?

73

Bob

Ko6Lu
Bob,

Go to Settings - Alerts - Miscellaneous Alerts - Wanted Callsign. Under Options, check "Alert when decoded Callsign worked B4".

73,

Jim N6VH




--
Bob
KO6LU

1781 - 1800 of 38469