Date   

locked JTAlert Changes Display Settings

jm9998@...
 

I am running a Windows 10 PC with three monitors.  Over the past few days, when I run JTAlert it changes my display settings, such as screen resolution and display arrangement.  I have reinstalled the display drivers, but that did not help.  Also, the position of the JTAlert window spontaneously changes periodically.  Has anyone else experienced this problem and/or found a solution?

Thanks.

Brad W1XI


locked Re: B4 is NOT showing

HamApps Support (VK3AMA)
 

On 11/12/2018 7:35 am, Frank de Wilde wrote:

But when running this setup WSJT-X show stations worked B4 correct as 'GREEN' but most worked B4 stations are not marked by JTalert as worked-B4, also I keep getting new DXCC alerts for stations/countries I worked many times before (Grid chase is disabled !

I tried 'Scan & rebuild' but doesn't help, problem stays the same!

Also I got the logging to Log4OM working again, but JTAlert-X keeps announcing that it could not confirm the QSO has been logged by Log4OM (but it is logged O.K.!)

I use the same setup on my laptop (used it during my DXpedition last November) without any problem, both setups use the same database for Log4OM on my GoogleDrive!

I hope You can help!

73 de Frank PH2M

Frank,

If JTAlert is not showing B4 for previous worked callsigns in your log and JTAlert warns that it cannot confirm logged QSOs, suggests that you have JTAlert using a different Log4OM Log file from that which Log4OM is set to use. Double-check the log file path specified within JTAlert is correct and matches Log4OM.

Please note that The Scan Log function has NO EFFECT of B4 reporting. The only purpose of the Scan Log is to update the different Wanted Alert Lists based on you log entries. B4 checks are done in real-time against your log file independent of teh Wanted Alert lists updated by the Scan.

de Laurie VK3AMA




locked Re: Multiple QTHs

HamApps Support (VK3AMA)
 

On 11/12/2018 5:39 am, William Thomas wrote:
Laurie, thanks for offering to support my remote/portable operation in New Mexico.  As such, please add the following to the database:

WT0DX/P  NM

For those interested in why I am choosing this call letter configuration for my remote operation, it will be compatible with WSJT-X V2.0 without loss of any features (such as showing the Grid when doing a CQ, or operating one of the supported contests), LOTW and eQSL logging.

73 Bill WT0DX

Bill,

This has been actioned.

HamSpots has already been updated and WT0DX/P in NM will appear in the next HamApps Callsign database (and all future builds).

de Laurie VK3AMA


locked Re: Error trying to load 2.12.7

HamApps Support (VK3AMA)
 

On 11/12/2018 9:57 am, Larry Banks wrote:
Hi all,
 
When trying to load 2.12.7 (Win7 pro64) I get the following error message:
-------------------------
 
\...\JTAlert\plugins\JTAlertBandData.Plugin
 
An error occured while trying to replace the existing file:
DeletFile failed: code 5
Access id denied
 
-------------------------
I tried twice, aborting the first time and ignoring the second time.  When I ignored it, another plugin generated another error. I then aborted again.
 
I never completed the install as far as I could see.  HOWEVER, 2.12.7 is now up and running OK as far as I can tell.  What is the meaning of the error?  Does it really matter?  How did 2.12.7 get installed when I aborted the install.

73 -- Larry -- W1DYJ

Larry,

Errors about replacing files during the JTAlert install/update are typically due to the file trying to be replaced still running. This would be the case for you.

You should never ignore a failed file replacement during an install/update, that can lead to older incompatible plugin files being used by the newer JTAlert.

When you get this type of error, the easiest solution is a simple PC restart to ensure that any zombie processes and file locks are cleared. After the PC restart, the install/upgrade will proceed without error.

I strongly suggest you perform the JTAlert 2.12.7 update again first stopping JTAlert (perhaps perform the PC restart to be sure that you wont get the file replacement errors again). There is no harm in repeated running of the setup program for the same version.

de Laurie VK3AMA



locked Re: Log Error Followup

HamApps Support (VK3AMA)
 

On 12/12/2018 8:03 am, Don - kx9q wrote:
 I am attaching two pictures showing the error I received from ACL and JTAlertX error.  The third picture shows the entry in ACL.  I am not sure why this is happening, however, from the ACL you can see the log entry showing mode to be DIGU rather than FT8.  The contact below that shows mode as FT8.  I am thinking something is happening in JTAlertX to cause this but that is just speculation on my part.  It is somewhat random.  This is the first time this has happened since I last posted on this site a while back.

Don - kx9q
Don,

Sorry, I don't know where the random changing of FT8 to DIGU in JTAlert logged QSOs in ACLog is coming from.
JTAlert definitely, NEVER logs DIGU. In the 43000+ lines of JTAlert code there is no occurrence of the word  "DIGU". If JTAlert was logging "DIGU" it would be for all qsos, not a random selection, and this forum would have seen many such complaints.

My guess as to the cause, is that something your doing within ACLog either pre or post JTAlert logging is updating the QSO mode.
  • Are you performing any sort of lookup after logging?
  • Are you making changes to the data JTAlert initially populates in ACLog or performing some sort of lookup that updates the data before JTAlert sends the Log this QSO TCP command to ACLog?
The data entry fields of ACLog are initially populated when you first start a QSO with a Station (change in WSJT-X DXCall) and it is not until the Log QSO is actioned in WSJT-X that JTAlert instructs ACLog to log the data. If there have been changes to any of the data entry fields within ACLog before the log QSO instruction is sent by JTAlert, some of these changes may persist.

If your frequently seeing this, then it should be easy enough to track down if JTAlert is the cause. Please do the following...

  • Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  • Restart JTAlert, that is close JTAlert and then start JTAlert.
  • Operate and log FT8 QSOs as normal and once you observe ACLog with an incorrect mode for a recently logged QSO, use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. Include in that request the Callsign and utc time when this bad mode logging occurred.
  • After sending the support request you can turn off debugging.

de Laurie VK3AMA


locked Re: what file to save ?#help

HamApps Support (VK3AMA)
 

On 13/12/2018 4:28 am, David Michael Gaytko // WD4KPD wrote:
i need to squirrel away the necessary files from hamapps/jtalert to preserve the states/dxcc entities worked.

i normally save the two hamapps directories in my appdata/local to do this, but i wish to clean out everything regarding the program (temp basis) and reinstall it.

which files must i save to preserve/restore this data vice the whole hamapps/local directories ?

david/wd4kpd
David,

To ensure that you don't loose any JTAlert config data, save all files and subdirectories under the %localappdata%\HamApps directory.

See the JTAlert Help file, "Frequently Asked Questions  -> Move JTAlert to a New PC" topic.

de Laurie VK3AMA


locked Re: Hamspots Grid-square Search?

HamApps Support (VK3AMA)
 

On 13/12/2018 3:46 am, g4wjs wrote:
Hi Laurie,

maybe a bit late for the Grid Chase but I wonder if you have considered a "stations active from a specified grid-square" search?

73
Bill
G4WJS.

Bill, it has been on the todo list since the Grid Chase was first announced. I initially coded the gathering of Grid data from the incoming spot feeds, but never progressed to providing the search facility. Maybe over the Holidays I will find time to delve back into the HamSpots code.

de Laurie VK3AMA


locked Re: Windows 8 and .NET Framework 4.7.2

HamApps Support (VK3AMA)
 

On 11/12/2018 8:43 pm, vk2csw@... wrote:
Just a heads up:

.NET Framework required for the current version is not supported on Windows 8.

Regards

Colin
VK2CSW
Colin,

While that is true, my question is why are your still running Windows 8?

From Microsoft, dated May 5, 2014 ....
Windows 8.1 Update is a cumulative set of security updates, critical updates and updates. You must install Windows 8.1 Update to ensure that your computer can continue to receive future Windows Updates, including security updates.

Windows 8.1 supports the latest 4.7.2 framework and 8.1 is a free update.

IMHO, running Windows 8 without the Security updates provided by 8.1 is no better than running XP. Both of which should not be used with a live Internet connection.

de Laurie VK3AMA


locked Re: JTAlert and long callsigns

HamApps Support (VK3AMA)
 

On 10/12/2018 11:38 pm, Tony Dixon G4CJC wrote:
The two calls were DL70PADER and SX60RAAG. Attached are a couple of screen snips. Also what I noticed was that my call was entered into JTAlert at one point. I tried to snip that but it disappeared before I could get it. Hope this helps.

Cheers
Tony
Tony,

Thanks.

Now that FT8 77 bit handles these sort of non conventional naming style callsigns, typically used by special event Stations, I have had to extend the JTAlert Callsign validation code to now pass these sort of Callsigns.

From the release notes of the next JTAlert release...
Callsign validation extended to accept non-traditional callsign naming.
       eg "DM152ZYA", "TC630MECCA", "DL70PADER", "SX60RAAG"
       Typically seen with special event Station callsigns that are now being
       decoded by 77 bit FT8 (since WSJT-X 2.0.0).

Note: The new validation code doesn't use hard-coded Callsigns, it uses regex pattern matching, so that future new Callsigns should be validated and shown by JTAlert (provided the Callsigns get through WSJT-X decoding) without the need for a new JTAlert build.

de Laurie VK3AMA


locked Re: Lots of error messages

g4wjs
 

On 12/12/2018 18:29, k6vib@q.com wrote:
When trying to install WSJT-X v2.0 I get a lot of errors in my WIN-10. What the heck? Same thing with other versions like the RCS installs. Back to V 1.9.1...
OM,

a vague question on the wrong list, you are lucky anyone bothers!

A possible cause is your trying to upgrade WSJT-X while it is still running. We don't support servicng while the wheels are still turning.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Lots of error messages

k6vib@q.com
 

I will have to go back and install v2.0 again and write down the errors for you. I knew you would say "doesn't tell us much". HI, hi.
Thanks de Bob K6VIB


locked Re: Lots of error messages

Michael Black
 

"Lots of errors" doesn't really tell us much.
Thousands have installed without any problems (other than the lotw error which is fixable if you read the manual).

de Mike W9MDB




On Wednesday, December 12, 2018, 12:29:56 PM CST, k6vib@q.com <k6vib@q.com> wrote:


When trying to install WSJT-X v2.0 I get a lot of errors in my WIN-10. What the heck? Same thing with other versions like the RCS installs. Back to V 1.9.1...


locked Lots of error messages

k6vib@q.com
 

When trying to install WSJT-X v2.0 I get a lot of errors in my WIN-10. What the heck? Same thing with other versions like the RCS installs. Back to V 1.9.1...


locked what file to save ?#help

David Michael Gaytko // WD4KPD
 

i need to squirrel away the necessary files from hamapps/jtalert to preserve the states/dxcc entities worked.

i normally save the two hamapps directories in my appdata/local to do this, but i wish to clean out everything regarding the program (temp basis) and reinstall it.

which files must i save to preserve/restore this data vice the whole hamapps/local directories ?

david/wd4kpd


locked Hamspots Grid-square Search?

g4wjs
 

Hi Laurie,

maybe a bit late for the Grid Chase but I wonder if you have considered a "stations active from a specified grid-square" search?

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Windows 8 and .NET Framework 4.7.2

g4wjs
 

On 11/12/2018 09:43, vk2csw@wia.org.au wrote:
.NET Framework required for the current version is not supported on Windows 8.
Hi Colin,

it's fine on Windows 8.1 and 7 SP1, I believe Windows 8.1 is a free update from 8.



--
73
Bill
G4WJS.


locked Re: Windows 8 and .NET Framework 4.7.2

neil_zampella
 

That's not right ... its working fine on my WIndows 8.1 computer.

Neil, KN3iLZ


locked Windows 8 and .NET Framework 4.7.2

vk2csw@...
 

Just a heads up:

.NET Framework required for the current version is not supported on Windows 8.

Regards

Colin
VK2CSW


locked Log Error Followup

Don - kx9q
 

 I am attaching two pictures showing the error I received from ACL and JTAlertX error.  The third picture shows the entry in ACL.  I am not sure why this is happening, however, from the ACL you can see the log entry showing mode to be DIGU rather than FT8.  The contact below that shows mode as FT8.  I am thinking something is happening in JTAlertX to cause this but that is just speculation on my part.  It is somewhat random.  This is the first time this has happened since I last posted on this site a while back.

Don - kx9q


locked Re: More on B4 is NOT showing (supplemental)

K9MK
 

Greetings,

 

     Last night I spent a bit more time monitoring and trying to understand why these are not showing as B4.

     Here are two screen shots that represent two B4's not seen here in the JTAlert table.

 

     First screen shot was V31MA which I worked 3 days ago and was a dupe then.

     The second I checked at random and W1BCL was worked ~3 months ago. 

     Any suggestions on what settings to check that might be the reason would be appreciated.

 

Thanks

 

73  Mike K9MK/5

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of K9MK
Sent: Monday, December 10, 2018 4:04 PM
To: Support@HamApps.groups.io
Subject: [HamApps] More on B4 is NOT showing

 

Hi Laurie and the group,

 

     I thought I had my not seeing B4's issue resolved with the guidance you provided in response to my previous email.

     But here recently whatever I have/had setup wrong crept back, or so I think.

 

    FLEX6700 + HB-i7-PC w/W10 Home, WSJT-X 1.9.1, and JTAlert 2.12.7

 

     This past week I started looking harder to see if there was something specific I could point to.

     Best I can tell it is not band, entity, or related to station specifics. 

     Example: Last week I noticed a station that called me that I worked days before. 

                         As I was on the band for awhile, I noticed that in the JTAlert table there was no B4 status.

                         I started  looking closer and I found other stations were showing up as eligible to work but in fact they were previously worked at least once on that band in the previous 4-5 months.

 

     I'm using a Flex 6700 with WSJT-X and JTAlert.  I do have DX-Lab active/running for spot purposes. 

     Initially I choose not to connect or link the logging database with DX-Keeper.  At least initially I wanted to keep the apps isolated. 

     Correct me if I'm wrong but I would not expect having these other apps running impact the goings on of JTAlert and WSJT-X. 

 

     I have made some simple checks of the log and *.adi files, and the previous QSO's not being seen as "B4" are there.

     But I have not done a 1:1 on the MDB file itself.

 

     Any insight or suggestions would be appreciated.

 

73  Mike K9MK/5

 

PS: It may be me, but as I spent time looking at my screens, it seems that when I change bands the time before the B4 feature starts working varies.  I made one observation where I was monitoring a busy 40m band for multiple minutes and none of the JTAlert stations indicated worked B4.  Then I worked a station and then on the following pass the board lit up with multiple B4's. 

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Frank de Wilde
Sent: Monday, December 10, 2018 2:36 PM
To: Support@HamApps.groups.io
Subject: [HamApps] B4 is NOT showing

 

Hello Laurie,

Due to a virus I had to reinstall my shack PC again, I reinstalled and I 'am running latest JAlert-X, WSJT-X (1.91 or 2.0.0 GA) + latest Log4OM again.

But when running this setup WSJT-X show stations worked B4 correct as 'GREEN' but most worked B4 stations are not marked by JTalert as worked-B4, also I keep getting new DXCC alerts for stations/countries I worked many times before (Grid chase is disabled !

I tried 'Scan & rebuild' but doesn't help, problem stays the same!

Also I got the logging to Log4OM working again, but JTAlert-X keeps announcing that it could not confirm the QSO has been logged by Log4OM (but it is logged O.K.!)

I use the same setup on my laptop (used it during my DXpedition last November) without any problem, both setups use the same database for Log4OM on my GoogleDrive!

I hope You can help!

73 de Frank PH2M

 

 

15981 - 16000 of 38435