Date   

locked menu has disappeared

EDMUNDO CAMPUSANO
 

Hi to all

First thank the hard work after JTALERT, install version 2.16.6 and a menu has disappeared at the bottom, how do I activate it again?

2.15
image.png

2.16.6

image.png

73 Edmundo CE2EC

--
Edmundo 73, CE2EC
La Serena


locked Re: missing jtalertsettings.exe

Hasan Schiers N0AN
 

Your virus program probably quarantined it. See how to:

1) Release it
2) List it to not be scanned next time by this program

73, N0AN
Hasan


On Fri, May 22, 2020 at 10:46 AM Terry N8JX <n8jx100@...> wrote:
I installed jtalert but could not bring up the  jtalertsettings.exe said missing. Then tried to delete everything I could and reloaded but installation error-ed out with this message




Any help would be appricated
Thanks N8JX


locked JTAlert 2.16.6 is available. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.6 is now available @ https://hamapps.com/JTAlert/
 

Please see the release notes below.

de Laurie VK3AMA


Release Notes.

2.16.6 (22-May-2020)

  *** Includes Callsign database file version 2020-05-21 (2020-May-22)

  Changes:

    - Menus: All top level menus now have an accelerator character defined.

    - Band changes: Now when there is a band change, decodes will not be alerted
       or spotted to HamSpots for one full mode-period regardless of when in the
       period the band change occurred. There are no attempts made to determine
       if the decodes are from the old or the new band, they are simply discarded.

  Fixes:

    - Callsign Tooltip: Not showing Country or Continent. (2.16.5 defect)

    - Callsigns display: Intermittent non-display of Callsigns and QSO logging.

    - Band changes: When changing band mid-period the early-in-the-period decodes
       could be alerted (and spotted) for the new band when they were from the
       old band.

    - WSJT-X Docking: Docking would break when switching WSJT-X configurations.
       This only occured for the 2.2.0-rc1 release candidate.


locked Appending state to callsigns

Ed Deichler
 

I just re-launched JTAlert-X (V2.15.2) and do not see the state appended to callsigns in the billboard.  How to I add the states?

73 de Ed


locked missing jtalertsettings.exe

Terry N8JX
 

I installed jtalert but could not bring up the  jtalertsettings.exe said missing. Then tried to delete everything I could and reloaded but installation error-ed out with this message




Any help would be appricated
Thanks N8JX


locked Re: Saving configs

John Petrocelli
 

Hello Jeff,

   I use a very similar CMD file the the WSJT-X files --  All.txt, INI, & log.
   For the All.txt file the CMD file actually "moves" the file rather than simple make a backup copy.

73
John - WA2HIP
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 5/22/2020 9:57 AM, Jeff Campbell wrote:
Great John; thank you for sharing that.  It works a treat and until Laurie is able to release the next version (v3) it will add another level of safety.  I made several changes recently within JTAlert and it no longer worked as it should have, and for the life of me I couldn't remember exactly what I'd changed.  Being able to easily backtrack would have saved me a considerable amount of effort!  
Do you have any idea when v3 will be ready for release Laurie (or is that a question you cannot answer yet???).

Thanks again for that very useful utility John.

Jeff - G4IUA


Virus-free. www.avast.com


locked Re: More "no sound" problems

lmeeny
 

Hello,

The worst has happened. Last night sound came back on.I can say I didn't change anything but must have. I apologize for wasting the groups time.

73 W2GHD


locked Re: Saving configs

Jeff - G4IUA
 

Great John; thank you for sharing that.  It works a treat and until Laurie is able to release the next version (v3) it will add another level of safety.  I made several changes recently within JTAlert and it no longer worked as it should have, and for the life of me I couldn't remember exactly what I'd changed.  Being able to easily backtrack would have saved me a considerable amount of effort!  
Do you have any idea when v3 will be ready for release Laurie (or is that a question you cannot answer yet???).

Thanks again for that very useful utility John.

Jeff - G4IUA


locked Re: DxMarathon alert

Carlo - IK2RPE
 

Resent - probably the first one disappeared somewhere


Il lun 18 mag 2020, 20:03 Carlo - IK2RPE via groups.io <ik2rpe=gmail.com@groups.io> ha scritto:
Hallo Laurie,
I'm following DxMarathon.
I had this year several contacts with TA1 (European Turkey): they are logged in DxKeeper Award pane as TA1 region.
However an alert starts every time (and on any band) that a TA1 call appears.
Once I make in JTAlert the "Scan Log and rebuild" (linked to DxKeeper .mdb) program, WAE European Turkey is *NOT* put in the "not wanted" list. I also tried to add manually this WAE callsign to the "not wanted" list. No joy, the alert continues to start.
Furthermore: WAE ITU Vienna is also not put in the "not wanted" list (but for this call there are not so many possible alerts). On the contrary doing the Scan Log prg. WAE African Italy and WAE Bear Island (both never connected by me this year) are put - wrongly - in the "not wanted" list and I have to manually move them to the "wanted" one.
Lastly, WAE Shetland Island and WAE Sicily - both worked - are, with the Scan Log prg., correctly put in the "not wanted" list.
Did I miss some setup? What can I do?

Thanks  

Carlo  IK2RPE


locked Re: JTAlert 2.16.5 Decodes Large Database

Ron Schwartz <rs500cat@...>
 

I now see a related message topic posted today. No need to respond to this message unless it adds information to the topic. Thanks, Ron


locked JTAlert 2.16.5 Decodes Large Database

Ron Schwartz <rs500cat@...>
 

My Decodes window was not displaying any new alerts and/or occasionally displaying alerts several minutes old. My decode database had 700K records. I manually deleted the database, the system created a new smaller database and now the Decodes window appears to be working properly.

FYI, The database delete option under the File menu did not appear to delete records out of the large database. After the delete the same number of records existed. Did my database grow too large for the program to work properly?

Thanks, Ron K2RAS


locked Re: The "Decodes Window" will not clear...

HamApps Support (VK3AMA)
 

On 22/05/2020 9:00 am, Bob Stothfang wrote:
If they are not set to delete at startup does the file just get too big reach a size where the View>"Clear Display" eventually won't work again?

Yes, the database will continue to grow if there is no automated deletion setting selected.

An overly large database will (should) not produce any noticeable performance degradation. The type of disk where the database file is stored will have a minimal impact on performance.

The inability to clear the old entries is not related to the database size. There is something unusual happening that I have been unable to isolate.

FWIW, my latest Decodes stress testing had the database reach 4 million entries with no noticeable delays in populating the display or loss of decodes. This was with 10 simulated JTAlert instances sending 50 FT8 decodes per period to the Decodes Window. That was 500 decodes every 15 seconds.

de Laurie VK3AMA


locked Re: The "Decodes Window" will not clear...

Bob Stothfang
 

Thanks Laurie

That did the trick. I think I will just keep it on the Startup Options>"Delete All Records" for now.

If they are not set to delete at startup does the file just get too big reach a size where the View>"Clear Display" eventually won't work again?


locked Re: The "Decodes Window" will not clear...

Don Roden
 

Bob,

Deleting WSJTX doesn't delete settings.
WSJTX doesn't keep it's settings in it's own directory.
Why ??? Good Question.

Re-install, and you really haven't changed much.

Don W4DNR



Quoting Bob Stothfang <bobstothfang@gmail.com>:

I have been using the Decodes Window for about two months.
I have used "File>Settings" to customize the display and eliminated unwanted columns of info.
The number of records is still set to the default 100.
The "Startup Options" are set to "Delete Old Records"
The Row Colors & Height are set to "Time period" and alternating between gray and white.
I then saved these settings and it comes up with these settings when I open the Decodes Window.
When I first installed it all worked OK.

After using for the "Decodes Window" for several weeks I am now encountering an issue,,.
Now when the window opens the previous sessions decodes are still displayed and I am also unable to to use the "View">"Clear Display" selection to remove the old information. It worked properly when it was first installed.
I have tried reloading a fresh install of both JTAlert and WSJT-X and the problem still persists.
Restoring the Decodes Window back to the default settings does not fix the problem either.

To summarize---The Decodes Window displays the current received data properly,
I just cannot clear the data in the window either automatically on initial startup or with the "Clear Display" selection.

Any ideas would be appreciated?

Windows10
WSJT-X Version 2.1.2
JTAlert Version 2.16.5
Decodes Window 2.16.5


locked Re: Saving configs

John Petrocelli
 

Hello Jeff & all,

   Here is my simple CMD file with instructions.

  1) Locate your "config" directory for JTAlert.
      In my case it is in "C:\Users\<USERID>\AppData\Local\HamApps\
<Call>\config".  Note to replace <USERID> with your computer's User-ID & "<Call>" with your correct callsign.

  2) Create a NEW directory in the above location with a name of "#Backup".
      Note the result will be "
C:\Users\<USERID>\AppData\Local\HamApps\<Call>\config\#Backup".

  3) Copy the  CMD file text (below) into the directory
       
"C:\Users\<USERID>\AppData\Local\HamApps\<Call>\config"

     You can  use Notepad to create this file, but be sure it has an extension of "cmd".  You can name the file however you wish.
      In my case I named it "JTAlert_Config_Backup.cmd".
==================Here is the CMD file================================
@Echo Off
For /f "tokens=2-4 delims=/ " %%a in ('date /t') do (set mydate=%%c%%a%%b)
For /f "tokens=1-4 delims=/:. " %%a in ("%TIME%") do (set mytime=%%a%%b%%c)
rem
Echo copy JTAlertX\*.* #Backup\*.*.%mydate%-%mytime%
copy JTAlertX\*.* #Backup\*.*.%mydate%-%mytime%
Pause
=================================================================

John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 5/21/2020 3:23 PM, Jeff Campbell wrote:
Thanks both.  Certainly in the meantime your backup file utility sounds good John.  Laurie: I look forward to the release of v3!

Jeff - G4IUA


Virus-free. www.avast.com


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

HamApps Support (VK3AMA)
 

On 22/05/2020 2:46 am, Marty Tressell wrote:
Thank you for the update...I loaded it yesterday and operated off an on over the day using the JTAlert Beta version and it worked not stoppage of call signs on FT8 which was very active yesterday!!!!

Thank you for your assistance!!!
--
Marty, K0BBK
Marty,

Tnx for the feedback.

I am reasonably confident that the random non-display of callsigns experienced by some users is fixed in the Beta.
I will be rolling that change out in the next public release (later this week).

de Laurie VK3AMA


locked Re: log audio alert

HamApps Support (VK3AMA)
 

On 22/05/2020 3:44 am, Pat via groups.io wrote:
is there a audio alert to log a qso?
sometimes I get doing something else
and forget to log a qso.. to dxkeeper.
tnx
No there is no logging alert. If you have not logged the QSO in WSJT-X then JTAlert will have no way of knowing if you forgot to log a QSO. JTAlert does not keep track of your QSO progress.

Your best option is to enable WSJT-X to auto-prompt you to log the QSO.

de Laurie VK3AMA




locked Re: The "Decodes Window" will not clear...

HamApps Support (VK3AMA)
 

On 22/05/2020 6:37 am:
I have been using the Decodes Window for about two months.
I have used "File>Settings" to customize the display and eliminated unwanted columns of info.
The number of records is still set to the default 100.
The "Startup Options" are set to "Delete Old Records"
The Row Colors & Height are set to "Time period" and alternating between gray and white.
I then saved these settings and it comes up with these settings when I open the Decodes Window.
When I first installed it all worked OK.

After using for the "Decodes Window" for several weeks I am now encountering an issue,,.
Now when the window opens the previous sessions decodes are still displayed and I am also unable to to use the "View">"Clear Display" selection to remove the old information. It worked properly when it was first installed.
I have tried reloading a fresh install of both JTAlert and WSJT-X and the problem still persists.
Restoring the Decodes Window back to the default settings does not fix the problem either.

To summarize---The Decodes Window displays the current received data properly,
I just cannot clear the data in the window either automatically on initial startup or with the "Clear Display" selection.

Any ideas would be appreciated?

Windows10
WSJT-X Version 2.1.2
JTAlert Version 2.16.5
Decodes Window 2.16.5
OM,

Try deleting the decodes database. The easiest way to do that is to use the Decodes Settings, under the "Startup Options" enable the "Delete All Records" setting then close and reopen the Decodes window. It should now start up with a clean slate. Now go back into the Settings and re-select your previous  startup option.

de Laurie VK3AMA


locked The "Decodes Window" will not clear...

Bob Stothfang
 

I have been using the Decodes Window for about two months.
I have used "File>Settings" to customize the display and eliminated unwanted columns of info.
The number of records is still set to the default 100. 
The "Startup Options" are set to "Delete Old Records"
The Row Colors & Height are set to "Time period" and alternating between gray and white.
I then saved these settings and it comes up with these settings when I open the Decodes Window.
When I first installed it all worked OK.

After using for the "Decodes Window" for several weeks I am now encountering an issue,,.
Now when the window opens the previous sessions decodes are still displayed and I am also unable to to use the "View">"Clear Display" selection to remove the old information. It worked properly when it was first installed.
I have tried reloading a fresh install of both JTAlert and WSJT-X and the problem still persists.
Restoring the Decodes Window back to the default settings does not fix the problem either.

To summarize---The Decodes Window displays the current received data properly,
I just cannot clear the data in the window either automatically on initial startup or with the "Clear Display" selection.

Any ideas would be appreciated?

Windows10
WSJT-X Version 2.1.2
JTAlert Version 2.16.5
Decodes Window 2.16.5


locked log audio alert

Pat
 

is there a audio alert to log a qso?
sometimes I get doing something else
and forget to log a qso.. to dxkeeper.
tnx

3501 - 3520 of 33231