[DXLog.net - Support] Very clunky

Ken K6MR k6mr at outlook.com
Sun Jan 24 18:15:04 CET 2016

You can increase the priority of DXLog by either changing it manually in the Task Manager or start it using a command line/batch file:

start /high DXLog.net.exe

When Win10 was first released in beta I was doing this but with the latest builds of Win10 I have not found it necessary. You might look in Task Manager/Performance when you have the problem and observe what the processor load is. Also look in the list of Processes and see if you have something that is hogging cycles.

Ken K6MR

From: Fred Handscombe<mailto:fredch at homeshack.freeserve.co.uk>
Sent: Sunday, January 24, 2016 08:45
To: support at dxlog.net<mailto:support at dxlog.net>
Subject: [DXLog.net - Support] Very clunky

HI All

I used DXlog in the UKEICC contest for a few hours, the latest version 2.3.1

I found it very clunky in that the CW messages were broken up by varying
length pauses, either at the beginning (started sending "late") or
during a message with a long "gap" inserted

Sometimes the letters were slow to appear as I typed a callsign also

I have Windows 10 64 bit on an AMD E1-2500 1.4GHZ computer with 6 GB

I had all other programmes shut down and have never experienced this on
other programmes like Wintest

Is there some "optimisation" I can do to stop this behaviour?


73 Fred G4BWP - A65BD https://sites.google.com/site/fhandscombe/
Support mailing list
Support at dxlog.net

More information about the Support mailing list