Date   

locked Wanted Grids

Dave NT9E
 

Wanted Grids are not showing up in an alerts box. Only the audible alarm is working.

Dave NT9E


locked Re: Port 2237

Jim Denneny
 

Hi Laurie

FT8filter is an app written by Al Rovner K7RA.  It opens a window and displays only DX callsigns that appear in the second call spot. (i.e.  xxxx de DL3AB for example).  It eliminates calls from NA stations You can select other preferences..  


locked Re: Port 2237

JTAlert Support (VK3AMA)
 

On 6/06/2019 8:18 am, Jim Denneny wrote:
Both WSJT and JTAlert use port 2237.  If I try to load a third app like FT8filter, port compatibility throws a fit.  Is there any way to have more than two apps using a port?  Is there a simple work-around or do I have to turn off either JTAlert or FT8filter?

Jim K7EG
Jim,

Never heard of FT8Filter, what is its purpose? I did a Google search and came up with a single hit, but the download links 404.

If FT8Filter allows for changing the port it expects to find WSJT-X, than change it to match the UDP rebroadcast port in JTAlert.

   

de Laurie VK3AMA


locked Port 2237

Jim Denneny
 

Both WSJT and JTAlert use port 2237.  If I try to load a third app like FT8filter, port compatibility throws a fit.  Is there any way to have more than two apps using a port?  Is there a simple work-around or do I have to turn off either JTAlert or FT8filter?

Jim K7EG


locked Re: JT Alert won't run

JTAlert Support (VK3AMA)
 

On 5/06/2019 6:18 am, n6rsh wrote:
 New here. I downloaded and am trying to install version 2.11.5 During the install I get this warning:

 IPersistFile::Save Failed; code 0x80070002.
The system cannot find the file Specified.

I get this warning 3 or 4 times then the install continues and finishes. When I try to run JTAlert, after "Reading Settings Data, Standby" , I get a window that says "Fatal ERROR Missing or invlid Callsign. Program will now exit."

That's as far as I can get. I have tried to uninstall and reinstall including redownloading the installer "HamApps_JTAlert_2.11.5_Setup.exe" I still get the vary same result.

 I must be doing something wrong. Please help,
Steve - N6RSH
Steve,

Your JTAlert installation is compromised, you will need to uninstall JTAlert and reinstall. But you will need to first address the "IPersistFile::Save Failed; code 0x80070002" error being thrown by Windows. This is not a JTAlert generated error, but an error generated by your Windows OS. The typical cause is your Virus/Malware protection interfering with the install of JTAlert, most often Windows Defender with the "Controlled folder access" option enabled.

See https://answers.microsoft.com/en-us/windows/forum/windows_10-files/ipersist-0x80070002-error/83992e3f-2233-4ed7-a5e0-de8bf52fe035

If this is the problem, that raises the question why your trying to install such an old version of JTAlert?
2.11.5 should only be used by XP & Vista users who can't/wont upgrade Windows as it was the last build to support those aging and now very insecure OS's
.

de Laurie VK3AMA


locked JT Alert won't run

n6rsh
 

Hi,
 New here. I downloaded and am trying to install version 2.11.5 During the install I get this warning:

 IPersistFile::Save Failed; code 0x80070002.
The system cannot find the file Specified.

I get this warning 3 or 4 times then the install continues and finishes. When I try to run JTAlert, after "Reading Settings Data, Standby" , I get a window that says "Fatal ERROR Missing or invlid Callsign. Program will now exit."

That's as far as I can get. I have tried to uninstall and reinstall including redownloading the installer "HamApps_JTAlert_2.11.5_Setup.exe" I still get the vary same result.

 I must be doing something wrong. Please help,
Steve - N6RSH


locked Re: Blocked on Hamspots

 

I solved the problem, Sorry for the post.
--
DAVE NU4N


locked R: [HamApps] callsign B4 color green? - Defect Confirmed

frank
 

Ok Laurie,

thank you  for your help.

73’s IK5SRE Frank

 

 

Inviato da Posta per Windows 10

 

Da: HamApps Support (VK3AMA)
Inviato: martedì 4 giugno 2019 11:05
A: Support@HamApps.groups.io
Oggetto: Re: [HamApps] callsign B4 color green? - Defect Confirmed

 

On 1/06/2019 8:22 pm, ik5sre@... wrote:

hello, why the callsing B4 has the background color green? the setup is for background blak and red but is always green as the pic. This is with ver.. 2.13.6 /2.13.7.
Best 73's Frank


Hi Frank,

I can confirm this is a defect introduced with version 2.13.6.
It is due to the following code changes reported in the 2.13.6 Release Notes....

  Fixes:
    - With the "hide B4" filter active, Wanted Alerts were not shown/played when
       Callsign was a B4 and the Ignore B4 option for the Alert is enabled.


I have broken the B4 logic somewhere within the code.

Once I have a new build available (probably within a day or two), I will send you a copy to test.

Sorry for the inconvenience.

de Laurie VK3AMA

 


locked Blocked on Hamspots

 

I seem to be blocked out of Hamspots. Error message states I sent 20 m spots for 2 m ??
Not sure what to do ?
73

--
DAVE NU4N


locked Re: callsign B4 color green? - Defect Confirmed

JTAlert Support (VK3AMA)
 

On 1/06/2019 8:22 pm, ik5sre@... wrote:
hello, why the callsing B4 has the background color green? the setup is for background blak and red but is always green as the pic. This is with ver.. 2.13.6 /2.13.7.
Best 73's Frank

Hi Frank,

I can confirm this is a defect introduced with version 2.13.6.
It is due to the following code changes reported in the
2.13.6 Release Notes....
  Fixes:
    - With the "hide B4" filter active, Wanted Alerts were not shown/played when
       Callsign was a B4 and the Ignore B4 option for the Alert is enabled.

I have broken the B4 logic somewhere within the code.

Once I have a new build available (probably within a day or two), I will send you a copy to test.

Sorry for the inconvenience.

de Laurie VK3AMA


locked Re: JT Alert and Band Activity Shows a "Not Responding" Error

JTAlert Support (VK3AMA)
 

On 4/06/2019 12:20 am, ki0kk wrote:
This problem just started a few days ago. Was working initially. 

I created a new Database with a new DSN and imported my old log info. That seemed to restore JT-Alert. Seems like the original log file or its DSN was damaged somehow?

 I also excluded the JT-Alert Directory from the Norton scans.

TNX, This new Del and the new version of W10 has been a problem. It's that or I have not got Norton to behave correctly yet.

Greg KI0KK
Greg,

Thanks for the update. Good to hear the fix was relatively painless.

Good luck with Norton, you will need it, especially if you ever try to uninstall it from your PC.

de Laurie VK3AMA


locked Re: Unable to log to DXKeeper

JTAlert Support (VK3AMA)
 

On 4/06/2019 4:28 am, Jim Denneny wrote:
Running WSJT rc7.  Cannot log through JTAlert to DXKeeper.  Error message below.  Shut all other apps. I don't think it could be UDP Port : 2237 issue.  Same error occurred with rc5 today before rc7 update. Any ideas?

Jim K7EG

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\jnden\AppData\Local\WSJT-X\WSJT-X.ini
 
WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.1.0-rc7   by K1JT
  Process Command Line : 
 
Decode alerts and logging will be unavailable until corrected.

Two most common causes of this type of error...
  1. WSJT-X UDP settings incorrect. See the JTAlert Help file, "Tutorials -> WSJT-X UDP Setup" section.
  2. WSJT-X is running with elevated privileges, that is, set to "Run as Administrator". There is no need to run WSJT-X elevated.

de Laurie VK3AMA


locked Re: Needed Grids not accurate in Decode History #FT8

 

Thank you Laurie - as always a clear and concise response - I will run the Scan.  You have a wonderful program that has enabled me to collect 10 new 6M grids this season - 280 now.

Glenn
K4ZOT


locked Re: Unable to log to DXKeeper

Michael Black
 

Double-check your settings in File/Settings/Reporting

Inline image





On Monday, June 3, 2019, 1:28:07 PM CDT, Jim Denneny <57JNDenneny@...> wrote:


Running WSJT rc7.  Cannot log through JTAlert to DXKeeper.  Error message below.  Shut all other apps. I don't think it could be UDP Port : 2237 issue.  Same error occurred with rc5 today before rc7 update. Any ideas?

Jim K7EG

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\jnden\AppData\Local\WSJT-X\WSJT-X.ini
 
WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.1.0-rc7   by K1JT
  Process Command Line : 
 
Decode alerts and logging will be unavailable until corrected.
 


locked Unable to log to DXKeeper

Jim Denneny
 

Running WSJT rc7.  Cannot log through JTAlert to DXKeeper.  Error message below.  Shut all other apps. I don't think it could be UDP Port : 2237 issue.  Same error occurred with rc5 today before rc7 update. Any ideas?

Jim K7EG

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\jnden\AppData\Local\WSJT-X\WSJT-X.ini
 
WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.1.0-rc7   by K1JT
  Process Command Line : 
 
Decode alerts and logging will be unavailable until corrected.
 


locked Re: JT Alert and Band Activity Shows a "Not Responding" Error

KI0KK - Greg Wolfe
 

Laurie:

This problem just started a few days ago. Was working initially. 

I created a new Database with a new DSN and imported my old log info. That seemed to restore JT-Alert. Seems like the original log file or its DSN was damaged somehow?

 I also excluded the JT-Alert Directory from the Norton scans.

TNX, This new Del and the new version of W10 has been a problem. It's that or I have not got Norton to behave correctly yet.

Greg KI0KK


locked Re: Needed Grids not accurate in Decode History #FT8

JTAlert Support (VK3AMA)
 

On 3/06/2019 12:38 pm, GLENN PACKARD wrote:
I recently noticed that several already worked grids are appearing as "Needed Grids" on the Decode History screen.  I checked the "Wanted Grids" screen and all looked correct.  Has anyone run across this issue?

Tnx,

Glenn
K4ZOT

Previously worked Grids will continue to be flagged as Needed until they are removed from the Wanted Grids List. The Grids list cannot be manually maintained, it is handled by the Scan Log process. Are you periodically running the Scan (typically only needed after your logger has been updated with your new QSL confirmations)? Make sure the Grid Scan confirmation types are set per your QSL requirements.

de Laurie VK3AMA


locked Re: JT Alert and Band Activity Shows a "Not Responding" Error

JTAlert Support (VK3AMA)
 

On 3/06/2019 10:51 am, ki0kk wrote:
I reverted to an older version, 2.10.10 and got the APP to start where I could at least access the menus. Still no response but I got an additional error message after some time concerning a failed DB Query, Screen shot attached. There is a DSN for the HRD Database defined.

Greg
Greg,

It looks to me like a problem with your ODBC DSN. The JTAlert code for working with HRD DSNs hasn't changed for a number of years and with the large number of JTAlert/HRD users that are not reporting this problem, it is very unlikely to be a problem within the code, most likely something specific to your Windows install.

Is this a recent problem?

Try creating a new Log with a new DSN from within HRDLogbook and then setting JTAlert to use that new DSN. Does the problem persist after that DSN  change? If not, it suggests to me that your Virus/Malware protection is interfering. Try with your protection temporarily disabled to see if that is the culprit.

de Laurie VK3AMA


locked Re: Needed Grids not accurate in Decode History #FT8

Michael Black
 

What do you have for the Tracking settings on the alert?

By band or by mode perhaps?

de Mike W9MDB




On Sunday, June 2, 2019, 9:38:52 PM CDT, GLENN PACKARD <packardg@...> wrote:


First JTAlert is great and very helpful in running down needed 6M grids.  But, I recently noticed that several already worked grids are appearing as "Needed Grids" on the Decode History screen.  I checked the "Wanted Grids" screen and all looked correct.  Has anyone run across this issue?

Tnx,

Glenn
K4ZOT


locked Needed Grids not accurate in Decode History #FT8

 

First JTAlert is great and very helpful in running down needed 6M grids.  But, I recently noticed that several already worked grids are appearing as "Needed Grids" on the Decode History screen.  I checked the "Wanted Grids" screen and all looked correct.  Has anyone run across this issue?

Tnx,

Glenn
K4ZOT

15561 - 15580 of 39839