|
locked
Re: Special callsigns
Take a look at the JTA Decodes window. I use it all the time because I can scan everything vertically much faster, and you can fine tune any filtering you desire. Try it and I think you'll like it. 73 Herb WB8ASI
|
|
|
|
locked
Re: JTAlert 2.16.7 is available
I'm in the same boat with ESET Internet Security. Unable to get JTALERT installed
|
|
|
|
locked
JTalert and 2m imported ADIF log does not rebuild - 4m GREEN and CANCEL in REBUILD
Hi Laurie
I'm having some problems with REBUILD which I don't know if it's my problem and what I need to configure. There are three working problems on the ADIF LOG: 1. I can't make the rebuild understand the vision of the fields in 2m.
I use an imported ADIF LOG, on all bands it works but not in 2m, I tried with BAND and FREQ but it is always zero on all fields even if I have enabled 2m (see images) 2. the 4m field is always green (I have no QSO in the 4m band), even after more rebuilds it is still green as if there were "new" 3. during the rebuild the CANCEL key remains active, if I press it, at the end of the analysis it asks me whether to exit or continue. If I EXIT LOG SCAN, it only exits the table it is doing but continues anyway, resetting everything and putting the table in green as if there were "new" I can't correct these and I don't know if I'm wrong somewhere in my configuration.
|
|
|
|
locked
Re: JTAlert stops updating for about 2 minutes
John Singler
Windows Defender and I already put the WSJT-X, JTAlert, and HRD data and program directories on the exception list
John S
|
|
|
|
locked
Re: JTAlert 2.16.7 is available
Hasan Schiers N0AN
Further hints: For Defender ...and spare us the "Defender sucks" comments. This is advice for those who run Defender and are staying with it. On another machine Chrome blocked it but allowed me to let it continue after I read the warning at the file download window. If you can't get the file to download at all: (Do this ONLY if you are confident that the file is safe) Any file from Laurie is SAFE as far as I am concerned) Virus & Threat Protection > Manage Settings > 1. Turn Real-time protection OFF 2. Turn Cloud-delivered OFF 3. Turn Automatic sample submission OFF 4. Turn Tamper Protection OFF (Do this ONLY if you are confident that the file is safe) Any file from Laurie is SAFE as far as I am concerned) Download the file Then turn all of the above back ON 73, N0AN Hasan
On Tue, Jun 9, 2020 at 5:51 AM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:
|
|
|
|
locked
Re: JTAlert 2.16.7 is available
Hasan Schiers N0AN
2.16.7 Downloaded and Installed without any issues with Win10Pro and Windows Defender, as long as 1. Windows Defender is Up to Date and... 2. Proper exclusions were set up ahead of time (and they have been for months) Running just fine on two different machines. 73, N0AN Hasan
On Tue, Jun 9, 2020 at 3:51 AM <dk1wb@...> wrote:
|
|
|
|
locked
Re: JTAlert 2.16.7 is available
dk1wb@...
Laurie, Windows Defender warned that Trojan:Win32/Azden.A!cl was found in x86)\HamApps\JTAlert\plugins\JTAlertSettings.exe and deleted it. Please confirm. 73, Hans, DK1WB Carlos Reboreda schrieb am 09.06.2020 10:18 (GMT +02:00):
|
|
|
|
locked
Re: JTAlert 2.16.7 is available
Carlos Reboreda <ea1dwi@...>
Hi all,
My experience here is the same… when there are abt 100 Kb left to finish the download, the ESET (for the first time) cancels the download, because it has detected something dangerous on dnl.hamapps.com … I’m not saying that this is the real matter, I just describe what ESET is doing about this download. I’m user of this antivirus for more tan 15 years, every euro i pay every year for it is worth it. I tried the download with Opera, Edge and Chrome, so I think it isn’t a matter of the web browser you use. Lets see if there any other members experimenting the same problem or it happens to be a false detection.
73 to all!
Carlos R. EA1DWI
Enviado desde Correo para Windows 10
De: chas cartmel
Jacques 08:48 BST – all OK here in the UK. 73 Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
HI Laurie
This email has been scanned by BullGuard antivirus protection. For more info visit www.bullguard.com
|
|
|
|
locked
Re: JTAlert 2.16.7 is available
chas cartmel
Jacques 08:48 BST – all OK here in the UK. 73 Charlie G4EST www.g4est.me.uk
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
HI Laurie This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com
|
|
|
|
locked
JTAlert 2.16.7 is available. WSJT-X 2.2.x fix + new features.
#NewRelease
#Announcement
HamApps Support (VK3AMA)
The latest JTAlert version 2.16.7 is now available @ https://hamapps.com/JTAlert/
toggle quoted messageShow quoted text
Please see the release notes below. de Laurie VK3AMA Release Notes:
2.16.7 (09-Jun-2020)
|
|
|
|
locked
Re: needed grids not updating once needed one worked
Jim Cary
Thanks.
73, Jim
|
|
|
|
locked
Re: needed grids not updating once needed one worked
Hi Jim,
Same as DXCC or WAS, the scan is required.
73 -- Larry -- W1DYJ
From: Jim Cary
Sent: Monday, June 08, 2020 13:27
Subject: [HamApps] needed grids not updating once needed one
worked When
I work a needed grid, the needed list is not being updated and the grid still
shows as needed. The only way I can get it to update is to do a complete
log scan. What am I doing wrong? Jim W2SM
|
|
|
|
locked
needed grids not updating once needed one worked
Jim Cary
When I work a needed grid, the needed list is not being updated and the grid still shows as needed. The only way I can get it to update is to do a complete log scan. What am I doing wrong?
Jim W2SM
|
|
|
|
locked
Re: Using WSJT-X, JTAlert and MacLoggerDX together nicely
Jay
That was the work around. I keep changing the entry in "Logging" for retransmission and the evidently only works on 127.0.0.1. Never saw the WSJT-X/JTDX entry.
Thanks jb N4NQY
|
|
|
|
locked
Re: JTAlert stops updating for about 2 minutes
Michael Black
What antivirus are you using? Mike W9MDB
On Monday, June 8, 2020, 10:26:38 AM CDT, John Singler <jes148@...> wrote:
I've been trying to solve this for a couple of months and run out of ideas. JTAlert runs fine for minutes to hours and then stops updating call signs. If I mouse over the form, I get an hourglass. The form shrinks a bit (but not the displayed call signs) and the top margin text gets pale. After about 90 seconds the top margin text gets dark again, usually with a Not Responding message, and after about 2 minutes most or all the call signs decoded while the display is off get written. While all this is annoying, the thing that will eventually bite me is that if I log a QSO while JTAlert is stopped, when it comes back I get a QSO not logged message - QSO and DX Call call signs don't match.
First thing I did was follow Mike Black's guidance and put the program and data directories for WSJT-X, JTAlert and HRD5 (my logger) on the Windows Defender exception list. JTAlert stops even it it has been minutes to hours since my last transmission and WSJT-X and CAT control are not impacted so I don't see how it can be RFI (but I did put an RFI suppression kit on anyway). . I've checked the CPU load with Performance Monitor and it is 12% to 25%. There was often a spike in HDD activity just before JTAlert stopped but not while it is stopped and that was usually WSJT-X writing a .wav file. WSJT-X doesn't do that any more and JTAlert still stops. I saw message 29770 about a potential fix but missed it the first time and now I get a page not found error for the beta.
I am using Windows 10, ver 1903, WSJT-X 2.2.0, and JTAlert 2.16.6
Any ideas? Thanks John, KA5BJC
|
|
|
|
locked
JTAlert stops updating for about 2 minutes
John Singler
I've been trying to solve this for a couple of months and run out of ideas. JTAlert runs fine for minutes to hours and then stops updating call signs. If I mouse over the form, I get an hourglass. The form shrinks a bit (but not the displayed call signs) and the top margin text gets pale. After about 90 seconds the top margin text gets dark again, usually with a Not Responding message, and after about 2 minutes most or all the call signs decoded while the display is off get written. While all this is annoying, the thing that will eventually bite me is that if I log a QSO while JTAlert is stopped, when it comes back I get a QSO not logged message - QSO and DX Call call signs don't match.
First thing I did was follow Mike Black's guidance and put the program and data directories for WSJT-X, JTAlert and HRD5 (my logger) on the Windows Defender exception list. JTAlert stops even it it has been minutes to hours since my last transmission and WSJT-X and CAT control are not impacted so I don't see how it can be RFI (but I did put an RFI suppression kit on anyway). . I've checked the CPU load with Performance Monitor and it is 12% to 25%. There was often a spike in HDD activity just before JTAlert stopped but not while it is stopped and that was usually WSJT-X writing a .wav file. WSJT-X doesn't do that any more and JTAlert still stops. I saw message 29770 about a potential fix but missed it the first time and now I get a page not found error for the beta.
I am using Windows 10, ver 1903, WSJT-X 2.2.0, and JTAlert 2.16.6 Any ideas? Thanks John, KA5BJC
|
|
|
|
locked
Wider window would be nice
Mark
JTAlert is Great, but I would like to have more information available horizontally. I have JTAlert's display placed above the WSJT-X display and have room to expand JTAlert's information by four more display fields on each of the three existing rows.
Merk, K6FG
|
|
|
|
locked
Re: Special callsigns
My solution is, and has always been right in front of my face.
I just watch the WSJTx Band Activity window and let JTA do what it does the best, the voice announcements to get my attention for anything I might overlook, like a new DXCC. 1x1's and other special calls jump out at me all the time, even if they are color-coded as having been worked before for some previous special event. I spend most of my time watching the BA window as it's easier to scan with everything in a single row, whereas the JTA has things in a horizontal AND vertical plane per entry. I can scan the BA window in half the time it takes me to scan the JTA grid. I have B4 ignore turned on, CQ only unchecked and using the 8x3 display. This setup still gets a bit overwhelming to decipher in less than 15s. Don't get me wrong, but the JTA announcements and grid display are a vital part of my operation. And yes, I do scan it frequently, but as a backup to WSJTx which is a much faster visual scan for these older eyes and slower reaction times. -- 73's George - WB5JJJ
|
|
|
|
locked
Re: Special callsigns
Tom Melvin
Morning
toggle quoted messageShow quoted text
One issue, this would have to be under a UI - some users, shall we say, by their nature are nervous around computers, letting them loose with a text editor - I can imaging the traffic here. The file will as you point out will be OK for US users but as Laurie commented 'Any coded solution I develop is guaranteed to be incorrect for some users 5 minutes after a public release.’ Just playing devil’s advocate here as 1x1 US calls don’t affect me in the slightest. The saying 'Can of Worms' comes to mind. Tom -- 73
Tom GM8MJV (IO85)
|
|
|
|
locked
Re: JTAlerts Error Message When Starting WSJT-X With Slicemaster
pfullmer
Laurie,
Bottom line up front, I got it sorted out. You were correct that the error message I posted was for an earlier version of JTAlerts. While I was trying to troubleshoot the issue, I uninstalled 2.16.6 and put on an older version to see if I could get it to work. It was throwing the same error message though for 2.16.6, just the line number and the name of the executable was different. As for what Slicemaster does, it automatically configures and starts many 3rd party applications for the Flex Radio, aggregates spots and pushes them onto the screen, and lots more goodies. And in regards to how does JTAlerts work with it, it doesn't interface with it at all. When you start Slicemaster up, it sees what mode you're in then will automatically fire up the software corresponding to the mode. In digi it'll fire up WSJT-X, HRD or FLDIGI, if you're in CW it'll start the CW Skimmer etc. If you switch modes on the fly, it handles all the shutting down and starting up of the application you need. Very slick. The fix as provided by the application developer, was to delete the folder that contained all the configurations that it makes, and restart Slicemaster. He stated that it was probably a corrupt configuration file. I suppose that it was starting up WSJT-X in a way that was not allowing JTAlerts to start/communicate with WSJT-X. Thanks for responding to my question. You've got a great application. Pete Fullmer KE7W
|
|
|
