Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
|
Here is the link:
Bruce McLain bruce.mclain@...
toggle quoted message
Show quoted text
On May 8, 2025, at 1:28?PM, Bruce - K5WBM via groups.io <bruce.mclain@...> wrote: DXLab will directly interact with WSJT-X. ?
Unfortunately, I can¡¯t get to the DXLab Wiki page to reference how to do that.
Bruce McLain - K%WBM bruce.mclain@...
On May 8, 2025, at 1:12?PM, Peter Dougherty via groups.io <lists@...> wrote: Last November I had a catastrophic system crash that required me to do a full rebuild with new hardware. I cloned the old drive and got the OS running, no data was lost, and DX Lab Suite reinstalled painlessly. But somehow, something corrupted JT Alert. I've tried purging every last vestige of it from my system, reinstalling about a dozen different versions but no matter what I do, it will not operate in any kind of stable fashion. It will delay QSO logging by 45-90 seconds, not allow me to interact with it during that time and in general make logging or even operating the WSJT software itself impossible. I had been using JT Alert 2.16.6 for a few years and until the crash it had been perfect, and quite frankly I preferred it to the newer versions, but I'll take anything at this point.
?
As a result I had no choice but to delete it and I'm no longer able to log directly into DX Keeper, having to regularly import an ADIF from WSJT's log file. This is getting very old very fast. Are there any alternatives to JTAlert that will allow me to run the JT modes and log directly into DXKeeper? Honestly, if I could just get JT Alert 2.16.4 or 2.16.6 working again I'd be happy but that ship has apparently sailed.
Please and thank you.
|
