![]() Other "format" or by any other "means" or "method", to any "third party" In "audio", "printed", "photographic", "electronic", "data", or in any Not be discussed with or passed onto or forwarded or re-transmitted either This entire communication including any attachments is a privileged andĬonfidential communication transmission from the sender to the addressee/sĪnd must not be disseminate distribute or copied by any means e.g. Just continues to send CQ, in the appropriate time slot.Īcer Aspire 3 - Latest updated Windows 10īeen working fine with previous 2.0.0 _ rc1 and rc2, and previous version Via the 1st call option*) the software does not respond to being called, it However, when called, and having selected the station, (*either manually or If I decide to call CQ, this appears to function OK. Send a "CQ" message on the frequency of the station I am trying to call. However, when the software starts the TX sequence the software starts to BUT does not load anything into the generated messages box. If I double click on a received call (*station calling CQ*), then itĪppears in the logging area, i.e. ON RX, the software receives and decodes callsigns etc., OK. Tried any of the other modes with this rc version, yet. I'm using FT8 and the 2nd option for the generated messages. Although, I have not read *ALL *the submissions. Īnyway, I've not noticed anything that looks like my problem, being ![]() Looking at my e-mails from the group, you have a few issues. I would very much appreciate help with this. Kenneth Wessels ZS6KEN reported 1.8 and1.9 crashing quickly with High Sierra back in June on a MAC with an SSD. I’ve searched the mailing list, and been unable to find a similar issue,although Other Macs here also running 10.13.6 but with Mac OS extended journaled work fine, with no memory use increase with time. ![]() The problem persists if the ”update spots” is unchecked, as well as if the save option is “none" The increase in memory used correlates well with the data saved to disk if the “save all” function is used. It gets very unresponsive before it finally crashes. Initially memory used is around 80 MB, this increases very repeatably at around 80 - 100 MB/hour until the program runs out of memory ( about 5 days on this machine). Unlike HDD and fusion drive Macs this means that I’m running an Intel core i5 mac mini (2011 model) with a 500GB SSD, High Sierra 10.13.6. I have had what appears to be a memory leak issue with V1.9 and now up to 2.0 rc3 used for wspr ever since I upgraded to Mac OS High Sierra.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |