Date   

locked upgrade issues

Joe
 

Releases 2.16.5 for me isn't so good.  It hangs regularly.  Only once have I had to restart it, but every 5-10 minutes it goes to sleep.

Environment is Flex 6600M, SmartSDR, WSJTX release candidate.  Something amiss.


locked Re: JTAlert titlebar problem

JTAlert Support (VK3AMA)
 

On 13/05/2020 11:44 am, Katsuhisa Ishikawa wrote:
I'm using JTAlert. Suddenly the titlebar doesn't open as shown the attached (6MB cellphone image removed) and right upper box □ also doesn't work.
I tried several view setting but nothing changed.
Please advise how to resolve.
 
Thanks in advance.
de  Katz JH1WUC  

This is a known problem with no fix. The only solution is to use the "Alt Layout" build of JTAlert.

Your image (removed to to excess size) shows your running JTAlert 2.15.11. The simple fix is to use one of the "Alt Layout" JTAlert shortcuts. Alternatively, and recommended, is to upgrade JTAlert to 2.16.5 which uses the Alt Layout build of JTAlert exclusively. The old traditional layout with menus in the titlebar has been permanently retired.

de Laurie VK3AMA


locked JTAlert titlebar problem

Katsuhisa Ishikawa
 

 
Hi, 
I'm using JTAlert. Suddenly the titlebar doesn't open as shown the attached (6MB cellphone image removed) and right upper box □ also doesn't work.
I tried several view setting but nothing changed.
Please advise how to resolve.
 
Thanks in advance.
de  Katz JH1WUC  


locked Re: Bad My CQ or ITU Zone in JTAlert changes CQ or ITU Zone in Log4OM

Tom NS8K
 
Edited

Laurie,

I've written this up in the Log4OM forum because I think it should be corrected.  I never considered removing this data from JTAlert.  Thanks for the tip, it will be gone in about 30 seconds, problem never to occur again!

73 es tnx,

Tom NS8K

Change made, test done, worked perfectly!  Welcome back.


locked Re: No Wanted Callsign highlighting for UW5EJX/MM

JTAlert Support (VK3AMA)
 

On 13/05/2020 3:42 am, Marion D. Kitchens wrote:
I worked him yesterday, but could find no grid square info.   How do you tell where he is ?

Keep an eye on the Cluster. That is where I have seen him spotted with updated Grid information. Also he periodically Transmits F/MM Grid as a means of advertising his current Grid, that is likely a more reliable source.

de Laurie VK3AMA


locked Re: No Wanted Callsign highlighting for UW5EJX/MM

JTAlert Support (VK3AMA)
 

On 13/05/2020 1:06 am, Jim Reisert AD1C wrote:
Please see the following image.  Both K5PI and UW5EJX/MM are in my Wanted Callsign list.  I have previously worked both on 17 meters.  Wanted Callsigns are the highest-priority alert.  K5PI is being highlighted, but UW5EJX/MM is nowhere to be found.  Why?

Your image shows you have Alert Filters applied. My guess is that filtering is causing UW5EJX/MM to not be displayed. What Filters do you have active?

de Laurie VK3AMA


locked Re: Losing connection to 2.2.0-rc1

JTAlert Support (VK3AMA)
 

On 13/05/2020 12:59 am, PA0FVH wrote:
Removed the elevated privileges of WSJT-X and so far things are looking good.

Normally there is NEVER any need to run WSJT-X elevated. Doing so will require JTAlert to be elevated and any connected logbooks will likely also require elevation than any programs they interact may need elevation. It can have a snow-ball effect until you reach a point where you have effectively bypassed Windows security on an Internet connected PC,. A recipe for disaster IMHO.

de Laurie VK3AMA


locked Re: Failure to log to HRD LB after updates

JTAlert Support (VK3AMA)
 

On 13/05/2020 12:16 am, WB5JJJ - George wrote:
Although at times, there was a significant delay in populating the grid where with the previous versions of both, it was almost instantaneous

Did those slow-downs appear to occur just after a Band Change?

de Laurie VK3AMA


locked Re: Country names no longer showing?

andypdanp@...
 

Thanks Laurie. Sorry!

73,

Andy K3NP


locked Re: registry problem Hamapps.Sounds

JTAlert Support (VK3AMA)
 

On 12/05/2020 11:59 pm, Terry N8JX wrote:

RegSetValueEx failed; code5
Access
is denied.

You messed with the Registry and created problems. Not a lot I can do about that.

The Access denied message is likely caused by you trying to remove an entry that was previously created by the Installer running with Elevated
privileges but your running Regedit non-elevated. Most Installers get elevation in order to write necessary files to protect Windows directories. Try starting Regedit with Run As Adminstrator elevation. If that doesn't work, sorry your on your own.

de Laurie VK3AMA
 


locked Re: Bad My CQ or ITU Zone in JTAlert changes CQ or ITU Zone in Log4OM

JTAlert Support (VK3AMA)
 

On 13/05/2020 11:45 am, Tom NS8K wrote:
I've discovered that if I have my ITU zone set differently in JTAlert than it is in Log4OM and then log a contact from JTAlert, My ITU zone in Log4OM gets changed to what it is in the JTAlert logging "transaction".  The same thing happens with the CQ zone if they are different. I don't consider this a JTAlert problem and will report this behavior in the Log4OM forum.  However, Laurie I know many checks are made when JTAlert starts up.  Are CQ or ITU zone differences worth verifying and warning about?

Tom  NS8K

Tom,

I suggest you remove the CQ and ITU zones from your JTAlert Settings (under the Station Callsign section) this way that will not be sent to Log4OM during logging.

de Laurie VK3AMA


locked Re: Country names no longer showing?

JTAlert Support (VK3AMA)
 

On 13/05/2020 11:34 am, andypdanp@... wrote:
I upgraded to v2.16.5 last week and am just getting some time to sit down and operate tonight. When I hover over the callsign names, I don't see the country names like I used to. There may be some info lower down showing that the call is a wanted prefix, etc, and there it may show the wanted state or province--but no country name up top. See example screenshot. Any tips on how to get the country name to display again like it used to?

73,

Andy K3NP
This is a defect. Previously reported and acknowledged here https://hamapps.groups.io/g/Support/message/29581

de Laurie VK3AMA


locked Re: Country names no longer showing?

andypdanp@...
 

screenshot of country name showing again after downgrading to v.2.16.4.


locked Bad My CQ or ITU Zone in JTAlert changes CQ or ITU Zone in Log4OM

Tom NS8K
 

I've discovered that if I have my ITU zone set differently in JTAlert than it is in Log4OM and then log a contact from JTAlert, My ITU zone in Log4OM gets changed to what it is in the JTAlert logging "transaction".  The same thing happens with the CQ zone if they are different. I don't consider this a JTAlert problem and will report this behavior in the Log4OM forum.  However, Laurie I know many checks are made when JTAlert starts up.  Are CQ or ITU zone differences worth verifying and warning about?

Tom  NS8K


locked Country names no longer showing?

andypdanp@...
 
Edited

I upgraded to v2.16.5 last week and am just getting some time to sit down and operate tonight. When I hover over the callsign names, I don't see the country names like I used to. There may be some info lower down showing that the call is a wanted prefix, etc, and there it may show the wanted state or province--but no country name up top. See example screenshot. 

I then installed v.2.16.4 (downgrading from 2.16.5) and now the country names and info are showing again like they used to.  Bug?

73,

Andy K3NP


locked Re: Zones Problem

Jim N6VH
 


On 5/12/2020 3:04 PM, WB8ASI Herb wrote:
Jim,  I'm a Log4OM user.  I know I can change the column positions on log page, but can we change it on the Main UI window since that's where I look first?  That would be great.  73 Herb WB8ASI


Herb,

I see what you mean. No, I don't think that can be changed. That would be an issue for the Log4OM team.

73,

Jim N6VH


locked Re: Zones Problem

WB8ASI Herb
 

Jim,  I'm a Log4OM user.  I know I can change the column positions on log page, but can we change it on the Main UI window since that's where I look first?  That would be great.  73 Herb WB8ASI

On May 12, 2020 at 12:18 PM Jim N6VH <N6VH@...> wrote:


On 5/11/2020 10:13 PM, HamApps Support (VK3AMA) wrote:
On 12/05/2020 12:11 pm, Joe Subich, W4TV wrote:

Please don't!  CQ is the only one that is associated with a useful award
and should always come first.  I would not even mind if ITU zone were
not displayed at all.

73,

   ... Joe, W4TV

Don't worry Joe there will be no changes.

I have always referred to zone pairs as CQ first ITU second. To me it feels more natural because "C" comes before "I" in the alphabet I am guessing.
 
Referring to the Gold-Standard, DXLab, I note DXView is CQ first, same for DXKeeper and the Capture window. A qucik look at ACLog it is the same. I don't bother checking any other loggers.

de Laurie VK3AMA


 


locked Disable "Select Sound Output Device" Pop-Up?

we2s_jim
 

My station is located in my brother's house.  I operate it remotely using TeamViewer.  Thus I definitely do not want to use the JTAlert audio alerts either intentionally or unintentionally.  Is there a way to disable the "Select Sound Output Device" pop-up that appears when JTAlert starts up?

Thank you very much for all the good work you put into JTAlert! 

Jim, WE2S


locked Re: No Wanted Callsign highlighting for UW5EJX/MM

Larry Banks
 

He/She’s Maritime Mobile – could be anywhere and probably doesn’t apply to any award.

73 -- Larry -- W1DYJ

 

Sent: Tuesday, May 12, 2020 13:42
Subject: Re: [HamApps] No Wanted Callsign highlighting for UW5EJX/MM
 
I worked him yesterday, but could find no grid square info.   How do you tell where he is ?
 
Marion,   K4GOK
 


locked Re: Logging failures do not update worked before information

David De Coons
 

Hi Bill

My bad. I thought it was intermittently not logging. 

My friend with the laptop was having intermittent issues logging from JTALERT to HTD Logbook. In his case it was due to the laptop resources being maxed out. With the upgrades I mentioned he is running fine and he has not complained pf no or intermittent logging since. 

I apologize if the recommendations were off course. 

73
Dave wo2x

Sent from my waxed string and tin cans. 

On May 12, 2020, at 2:01 PM, g4wjs <bill.8@...> wrote:


Dave,

did you read my OP? here's a quote of it:

"it seems that when JTAlert cannot confirm logging of a QSO in the configured logging application it does not update its internal worked before database. Often these logging failures are due to slow updates to the logging application even though the log is eventually updated. Restarting JTAlert does sort it out but until then it is easy to mistakenly work the same station twice."

Note that the problem is not a failure to log QSOs, but a failure by JTAlert to check that the QSO was logged successfully. I'm sure you reply may be of use to others but it does not address the issue being discussed in this thread.

73
Bill
G4WJS.

On 12/05/2020 13:48, David De Coons wrote:
Here’s something to check.
Myfriend was having intermittent issues using a Lenovo i5 laptop. We found his CPU running @ 100% and memory around 70%. A little digging found he had two hardware issues.

1) he was running Win 10 woth only 4 GB ram. Upgraded to 12 GB. CPU still at 100% but memory better.

2) he was using a USB to HDMI adapter plugged into a USB 2.0 port for an external 36” TV as a monitor. This was the bottleneck. The laptop has a mini display port so he replaced the adapter with a mini display port to HDMI cable. CPU now around 30% and memory around 30%.

Last, yesterday he cloned the laptop drive to a solid state drive (they are cheap now here in U.S.). He put the SDD drive in the laptop in place of the original drive. Now everything is running MUCH faster.

For HRD Logbook we converted his log from Access to SQL Lite using MariaDB. With larger logs (mine has 20,000 contacts) it speeds logbook database queries up.

And last comment. For the reply on failed to log QSOs you can click on log QSO in WSJT-X as long as you haven’t started the next QSO. Just remember to check the start time.

Some of the intermittent logging issues may be due to CPU or memory bottlenecks in the PC. Not saying al are due to this but worth checking.

73
Dave wo2x


On May 12, 2020, at 6:37 AM, g4wjs <bill.8@...> wrote:


On 12/05/2020 07:22, HamApps Support (VK3AMA) wrote:
On 11/05/2020 9:37 pm, g4wjs wrote:

I am using DXKeeper for logging. My delay before checking is set to 8 seconds which is perfectly adequate 99% or more of the time, but occasionally when my machine is particularly busy it trips up. Thanks for the tip on clearing the B4 cache. How about my suggestion of a "Retry" button alongside the "Ok" button on the error message about not confirming the logging success, in my case that would cover all the cases as far as I know, assuming a successful retry that finds the logged QSO goes on to update the worked B4 cache in JTAlert.

73
Bill
G4WJS

Bill,

Do you have DXKeeper set to auto-upload new QSOs to one or more online-logbooks? If so, that is a likely cause of the occasional extended logging times. That has been experience by JTAlert/DXKeeper users in the past.

Regarding a "Retry" button, that would seem to be the most sensible if it wasn't' for the code I have to work with. All the logging code is in the main JTAlert executable and runs on the UI thread. A Retry will involve a database access and a timeout value (if the lookup was unsuccessful), both of which will block the main thread. I am hesitant to add further blocking code. I will give it some thought.

de Laurie VK3AMA

Hi Laurie,

thanks for that, the online lookups are most probably the issue as I have a WiFi connection in the shack which is a bit QRP. No problem on the issues with implementing a "Retry" button, I had assumed that as the failure message doesn't time out that the required code to retry the logbook lookup was easily accessible, but if that is not the case I fully understand the issues. Since no one else has chipped in with similar requests, I am fine with just clearing the B4 cache when this happens. Normally it is pretty obvious where a station is running a frequency and continues to call after a QSO, I have to be pretty distracted not to notice that I have just worked them.

73
Bill
G4WJS.



--
73
Bill
G4WJS.

10321 - 10340 of 39820