The issue I was having with the Elecraft Frequency Memory Editor has now been resolved, thanks to a suggestion by Dick, K6KR.
Dick suggested using the Trace option to see if I could capture where the stall was taking place. When I went to turn the Trace option on, I realised that it was already on, so decided to firstly test the Editor with Trace turned off. Bingo! All works as expected with no stalling. Having only just used the Editor for the first time, I did not realise that the Trace window is does not show in normal operation. The Editor still stalls with Trace on, but this may be normal. I’m not aware whether Trace is on by default when the program is installed, probably not, but it got turned on somehow! I hope my experience will provide a fix for others who have experienced a similar ‘issue’. Once again, this proves that the choice of Elecraft is the best there can be. Where else do you get a direct reply from the author of the software within hours? Thanks Dick for taking time out of your busy schedule. I know you didn’t actually have to fix anything, but if you’d not made the suggestion about using Trace, it may have taken me many hours to find the problem. 73, Alan. G4GNX ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
