Log4OM

well, its been 24 hours with this test version Terry and so far, no problems. I'll report back again tomorrow

John

VK7XX wrote: 17 Jun 2020, 20:17 well, its been 24 hours with this test version Terry and so far, no problems. I'll report back again tomorrow

John

I forgot to add... the change of colours for the QSL manager upload & download are wayyyyyyy better than the previous orange text.

I have also experienced the freeze in Log4OM 2.7.0.0. I'm running Windows 64, i7 / 32 GB / 4 TB storage system. It has frozen while not running any other software. Had to use Task Manager to kill it. Once restarted, it has done well. This happened twice so far, including the first time I fired it up on the new version. The lock up does not happen immediately but at some random time later. I didn't track whether it happened during or after running WSJT-X, but I will keep an eye on that.

73, Duane

G4POP wrote: 16 Jun 2020, 07:04 Email me at g4pop (AT) arrl.net and I will send you an update to try

Good morning Terry.. It has now been 48 hours running the tryout version and I am pleased to report not a single lockup or sudden vanishing...... I think we are on a winner.

regards
John
VK7XX

VK7XX wrote: 18 Jun 2020, 20:09

G4POP wrote: 16 Jun 2020, 07:04 Email me at g4pop (AT) arrl.net and I will send you an update to try

Good morning Terry.. It has now been 48 hours running the tryout version and I am pleased to report not a single lockup or sudden vanishing...... I think we are on a winner.

regards
John
VK7XX

Thanks for testing John

OH NO..... after several days of no problems it has done it again .... sooo sad....

Just a few moments ago, for reasons unknown, the test version program locked up. It locked solid. The only way I was able to get to it was to go to task manager & shut it down and then restart it. damn damn damn

What were the circumstances? We're any other programs running, were you using the program, how long since the pc was 're started, how long had log4om been running since last restart, any other things happening on the pc etc

Oh dear.... I have been out and left Log4om (test version) running and when I got home, log4om was no longer on my screen, it just vanished while I was away. I came on to the forum to report this and saw your question below.... Sorry Terry, as far as I am aware, nothing was happening that was unusual.

Programs that were running were JTAlert version 2.16.8 and WSJT-X version 2.2.1. The lockup was approximately an hour after turning the computer on, and the "vanishing" was somewhere between 1 and 3 hours after a restart. This is sooooo weird because everything went well for 4 days. <sigh>

G4POP wrote: 22 Jun 2020, 21:10 What were the circumstances? We're any other programs running, were you using the program, how long since the pc was 're started, how long had log4om been running since last restart, any other things happening on the pc etc

John,
In Program configuration/program settings/Default log level turn on 'Trace mode'

Use and run the program normally

When the next crash occurs send me a support request from the help menu

After you have sent the support request turn off trace mode because it will slow things down a bit

Hi all. Firstly, many thanks for the program.
I've been having the freeze problem for some time on 2.7 and have just upgraded to 2.8.0.0 The program just froze again. Do you want me to send a trace log or do you have enough to be going on with?
Running windows 10 home edition and JTDX v2.10-rc151_32A
Colin MM5AGM