I just started using the K3 memory editor (v1.5.7.20 dated 2015) for the first time and I find it behaves in a strange way, depending whether a memory has content or not.
At present I have general memories 0 thru 23 loaded with data and memories 85 thru 99 also loaded. All other memories are ‘empty’. If I try to read all memories from the K3, the editor program reaches memory 24 (empty) and stalls. If I click the Cancel button, it reports ‘cancelling’ but does nothing. I can abort the action by clicking the red close icon. When I check the ‘spreadsheet’ I find that memories 0 thru 23 are filled and displayed, but not memories 85 thru 99. The only way to read memories 85 thru 99 is to ‘select’ them first, then read selected. Attempting to read any empty memory individually results in the function stalling. I also tried clearing a single memory entry and uploading it to the K3, which seems to work OK, but attempting to read it back, results in a stall. Is this normal behavior – a bug, or do I have an old or corrupted memory editor. 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
