Well, Well! I am ignorant vis-a-vis JTAlert machinations I guess, Bill. Many thanks indeed! So I guess if my DxKeeper mdb is 13000 kb then that's a lot of reading-in . tnx again. -- 73 Bob

I should note that I am current on .NET 4.8 with the 2020-KB4576484 update.

Next thing is to try DriverEasy and see if you don't have some drivers to update. Mike W9MDB

Yes we did & also ran through the DISM. Just for completeness we also changed keyboards (ensured we are not using anything wireless, etc). I'm open to try anything, but feel free to read through my

Have you tried uninstalling your keyboard driver? Mike W9MDB

Hi Mark, I have been through those steps yesterday and spent a significant amount of time ensuring that the correlation between keyboard latency & JTAlert is not just a 'canary'. I have also created a

I using jtalert for more than a year I using now version 2.16.10 because when I Install 2.16.13 the qso's I make are not logged in HRD. I checked everything but I don't find the errors All UDP ports

-- 73, Jim / de/ K9JDP

Yes I made a reconstruction of the database. but how to make an analysis ? Thank you J. Cl. F1DSZ

Bob This is due to the fact Canadians have a red flag and are somewhat socialist. cheers Barry

Have you done a scan & rebuild of the JTAlert database? Mike W9MDB

Hello to all I am using JTalert version 2.16.13, and I've noticed for some time that when I contact a station, JTDX tells me B4 signal but JTalert always announces "First QSO" permanently....view

https://www.drivereasy.com/knowledge/4-easy-fixes-for-keyboard-lag-in-windows-10/ Don't think a bug report will help....this sounds like a system problem even though JTAlert may be the canary and

Thanks for confirming Mike. Does anyone know the process for filing a bug with the devs here? 73, W9PDS

Thanks Neil Good suggestions David

The first instance is reading the database from your log. The second and additional instances get the data from cache. -- Bill Barrett 352-437-4758

I mentioned this a couple of times over the last couple of years. I can't say exactly when it started, but there was a definite point at which it started and I suspect it's a keyboard trapping

David, are you using a Windows account with admin privileges? I'm assuming you downloaded the latest version of JT-Alert from the Hamapps webstie, are you sure its Windows telling you this about no

Windows 10-Pro x64 JTAlert 2.16.13 WSJTx 2.2.2 I run three instances of both. The first instance of JTAlert ALWAYS takes circa 23 seconds to start. The remaining two roughly 4-6 seconds

Thanks!