Joe/Bill et al,
I am finding a definite problem when using a non-standard callsign in 2.2. I am running the 64bit Windows version under Windows 7 (yes I know I should upgrade the OS). The fault is a little obtuse and occurs in a sequence like: Callsign is set to "VK20HOME" (one of the special event callsigns) 1) Start WSJT-X via N1MM (I don't think this matters but mention it for completeness) 2) Make a series of QSOs - I've made between 25 and 100 in a sitting. All QSOs complete fine. 3) Leave the software idle for an extended period (usually 4-6 hours) monitoring the channel 4) The call CQ again 5) Wonder why no one is answering - but then notice a lot of <...> entries in the Band Activity window 6) Close the program 7) Open the program 8) Band activity is now full of people calling me. 9) QSOs now complete successfully again It seems that the software over time in idle mode has corrupted the hash of its own callsign and can no longer recognise it. Start it up from cold and the problem goes away. Like I said - obtuse - but repeatable. I have had it do this to me reliably probably 5-6 times over the last 2 days I have been running WSJT-X and VK20HOME. I can of course clear the fault and continue with a restart - but when you get a chance if you could look at that one it would be appreciated. If you need any other logs or files let me know. Regards, Grant VK5GR Email: vk5gr.ra...@gmail.com Website: <https://vk5gr-iota.net/> https://vk5gr-iota.net/
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
