2.8.0.0 Freezes

[N3PPH]

Follow-up not sure if this helps but one difference I have seen, I decided to install the previous version as my offer to try and help was met with silence. On version 2.8.0.0 when I removed a call in WSJT-X using backspace in the call window it was instantly wiped in Log4OM, in 2.7.0.0 this happens in steps, only part of the call is removed initially. Tells me this process has changed between versions. I am using JT-Alert.

Bob N3PPH

[G4POP]

Follow-up not sure if this helps but one difference I have seen, I decided to install the previous version as my offer to try and help was met with silence. On version 2.8.0.0 when I removed a call in WSJT-X using backspace in the call window it was instantly wiped in Log4OM, in 2.7.0.0 this happens in steps, only part of the call is removed initially. Tells me this process has changed between versions. I am using JT-Alert.

Bob N3PPH

Have you checked the most current version of our user guide to ensure that you have LOG4OM, WSJT and JTALERT set up in accordance with our user guide?

[N3PPH]

As a new user that is what I used to get up and running.

Bob N3PPH

[KI5IO]

As a new user that is what I used to get up and running.

Bob N3PPH

Bob,

As an assist to us in the support team to better help you out please take a look at this FAQ that Doug (W7DRM) posted some time back.

We want to do all we can, but we need basic data points from you and your installation and detailed steps of what you are experiencing.

Here is a link to Doug's (W7DRM) post: https://forum.log4om.com/viewtopic.php?f=40&t=4648

[N3PPH]

1 2.8.0.0 has problem 2.7.0.0 does not
2 Windows 10 64 bit version 2004
3 Yaesu FTDX 3000
4 WSJT-X 2.2.0 with JT-Alert 2.16.10
5 Logging from WSJT-X has always been involved. Action different between version as described on previous post. I do believe the problem has always happened after erasing a call not logged.
As nobody responded to my previous post I have already downgraded to 2.7, sorry.

[N3PPH]

So is any progress being made with the freezing issue?

73,
Bob N3PPH

[G4POP]

Bob,
Problem is that there are just a few people experiencing this out of thousands that don't.

We keep trying to emulate it but without success!

However if you want to try the latest Alpha to see if we have fixed it then drop me an email

[mm5agm]

I've now had Log4OM running for 16 hours with no problems. I disabled the following programs from my start up
Skype
Glary Utilities StartupManager
Killer Control Center - Rivet Networks LLC (This is a program that Dell puts on your PC dependent on the network card you are using)

I'd be interested to hear from other users if they have Killer.exe running and stopping it cures the lost focus problem.
I'm going to leave my start up as it is and see how Log4OM runs over the next few days.
Colin MM5AGM

[N3PPH]

None of those programs were running here. I have a Dell but did a clean install of Windows so none of their programs running. I have been testing the alpha version referred to above and have not had a lockup since.

73,
Bob N3PPH

[mm5agm]

That's interesting Bob.
I can now confirm that, on my Dell XPS 8930 running windows 10 64 bit that Killer Control Center by Rivet Networks LLC is not compatible with either V2.8.00 or the alpha version V2.8.0.5 of Log4OM. Without killer.exe running I ran Log4OM for 2 days with no crashes. I started killer.exe this morning and Log4OM froze after a couple of hours.
Note that I'm not saying that you cannot run killer.exe successfully with Log4OM, I'm saying that combination doesn't work with my configuration.
I hope this helps some of the people experiencing crashes.
Colin MM5AGM