Voacap was disabled.
I've wiped and reinstalled Windows 10 and everything again. Now the edit window opens in 1.5 seconds. Much better.
04:28:39.209 Info: [LogWriter] : ### LOG LEVEL CHANGED FROM Info TO Debug
04:28:45.173 Debug: [FwFile][ComposeFilename] : ComposeUserFilename: Returning file C ...
Search found 24 matches
- 27 Apr 2025, 04:34
- Forum: General discussions
- Topic: Performance / System Requirements
- Replies: 10
- Views: 7837
- 06 Mar 2025, 00:57
- Forum: General discussions
- Topic: Performance / System Requirements
- Replies: 10
- Views: 7837
Re: Performance / System Requirements
Thanks Terry, your attached log was exactly what I was looking for to compare with my tests. You only needed 1.8s vs my 4.1s so there is definitely something odd with my computer. I reinstalled Log4OM, ran it in Windows Safe Mode but no improvements. It's using that much time.
I did find another ...
I did find another ...
- 04 Mar 2025, 23:03
- Forum: General discussions
- Topic: Performance / System Requirements
- Replies: 10
- Views: 7837
Re: Performance / System Requirements
Terry, it runs like an American freight train, reliable and solid, just not fast.
I did try it without anti virus. MariaDB is stored and run on the same computer.
I'd be curious to see your debug log when you open the Edit QSO window to compare to mine.
Claus

I did try it without anti virus. MariaDB is stored and run on the same computer.
I'd be curious to see your debug log when you open the Edit QSO window to compare to mine.
Claus
- 04 Mar 2025, 22:27
- Forum: General discussions
- Topic: Performance / System Requirements
- Replies: 10
- Views: 7837
Performance / System Requirements
Like others I've been experience less than optimal system performance with Log4OM. For example to open the Edit QSO window takes more than 4 seconds. I only have 7759 QSOs.
I've investigated multiple options to improve performance but none of these caused any difference:
Moved from SQLight to ...
I've investigated multiple options to improve performance but none of these caused any difference:
Moved from SQLight to ...
- 24 Nov 2024, 01:22
- Forum: Error reports
- Topic: Defect: QSL Attachments stored in wrong location
- Replies: 1
- Views: 1250
Re: Defect: QSL Attachments stored in wrong location
BTW, a delete button is missing on the attachment page. What works is to track down the image in the file system and delete it once Log4OM is closed (not running). A delete button with confirmation dialog would really be nice. Thanks.
- 24 Nov 2024, 01:13
- Forum: Error reports
- Topic: Defect: QSL Attachments stored in wrong location
- Replies: 1
- Views: 1250
Defect: QSL Attachments stored in wrong location
I'm running version 2.34.0.0 and tried out the new QSL image attachments. I'm running multiple Log4OM profiles each using a different database file. In my K5A profile the attachment is placed under my call sign AE0S instead of K5A. Definitely not good since that QSO was done with K5A.
In the ...
In the ...
- 06 Jul 2024, 04:32
- Forum: General discussions
- Topic: LOTW upload Freezes
- Replies: 61
- Views: 122292
Re: LOTW upload Freezes
Update: The 12/13 aren't magic. I did encounter the upload issue with less than 12 and was once able to upload 16.
- 06 Jul 2024, 04:04
- Forum: General discussions
- Topic: LOTW upload Freezes
- Replies: 61
- Views: 122292
Re: LOTW upload Freezes
Did this ever get resolved? Because I'm getting the same issue:
03:19:26.858 Trace: [dje_zTQTYRYZBSAV5LGRDWP2XQ_ejd][MoveNext] : Planned scheduler executed...
03:19:29.037 Info: [LOTWManagement] : [LOTW UPLOAD] uploading LOG with 202 QSO
03:19:29.043 Info: [AdifManagement] : Begin export to ADIF ...
03:19:26.858 Trace: [dje_zTQTYRYZBSAV5LGRDWP2XQ_ejd][MoveNext] : Planned scheduler executed...
03:19:29.037 Info: [LOTWManagement] : [LOTW UPLOAD] uploading LOG with 202 QSO
03:19:29.043 Info: [AdifManagement] : Begin export to ADIF ...
- 12 Sep 2020, 20:02
- Forum: Feature suggestions
- Topic: QSL Manager: Enter Key Action
- Replies: 5
- Views: 4560
Re: QSL Manager: Enter Key Action
I don't get that this requires automatic refreshes. The program wouldn't refresh anything until the enter key is pressed in the call sign field. Nothing automatic here, nothing that should cause performance issues.
This bugs me so much that I'd learn whatever programming language Log4OM is written ...
This bugs me so much that I'd learn whatever programming language Log4OM is written ...
- 30 Jun 2020, 01:47
- Forum: Feature suggestions
- Topic: QSL Manager: Enter Key Action
- Replies: 5
- Views: 4560
QSL Manager: Enter Key Action
Usability request:
Pressing the ENTER/Return key in the callsign field of the QSL Manager should cause the same action as clicking the green search button.
Current behavior: Nothing happens when pressing enter.
Pressing the ENTER/Return key in the callsign field of the QSL Manager should cause the same action as clicking the green search button.
Current behavior: Nothing happens when pressing enter.