(05-09-2020, 12:49 PM)EA3GCV Wrote: Hello Roland,
This case is really strange... Have tried to run Swislsog, WSJT-X and JT Alert as administrator? You don't have to worry to give administrator rights to a known software like these ones.
If you still have the same issues running all as admin, please disable HAMQTH reading and try. we have to found out whch is causing this but the TAB key not working is very strange.
Please I know I insist a lot but make sure you have added exceptions to WSJT-X, JT Alert and Swisslog in your antivirus, firewall and all other antispyware software.
I would need to do a remote session with you via Teamviewer to check carefully what may happen but this is a very strange issue.
Best 73
I do not want to interrupt Roland's thread and search for a solution, however in thinking about the issue I have that seems similar, though not necessarily the same, I did not think it appropriate to start a new thread that could well be duplication. So, this is what the problem for me is in the latest versions. I do not use JTAlert, only JTDX attached to Swisslog via UDP. Sometimes, maybe once in 5 sessions, Swisslog stops updating the QSO input window as I initiate calling a station in JTDX. It is as if some kind of synchronisation is lost. I have stable but slow internet. Sometimes it will right itself if there is enough time (for example I have been CQing for some minutes and no other call has been sent to Swisslog) but then if any logging takes place it is without the dB reports - RST-S and RST-R get the value of 0. But usually is it simply stuck and I have to add my QSOs manually to Swisslog at the end of a session. It does not help that the mode starts with RTTY even though in WSJTx/JTDX RTTY is not possible. I always see RTTY change to FT8, back to RTTY and then again to FT8. Why is this? During these operations, Swisslog appears to not do anything else so therefore queuing the next actions instead of moving briskly on. If JTDX or WSJTx is attached, Swisslog cannot know the mode initially but it sure is not going to be RTTY. I believe the UDP link should force the mode at FT8, only to be changed if a new mode notification is received (such as FT4). I too have checked internet activity and can see the requests to the online database but not necessarily in sync with the callsign reaching Swisslog and when the issue starts these requests are well out of time. Closing and restarting JTDX does not help. Only restarting Swisslog clears the issue. For me, this problem started with 5.99f.
