v1.85.3 Bug Fix Release and History File Refresh

[w7sst]

Summary

This release fixes several quality and behavior issues, including improvements to audio processing when using Bluetooth headsets. Several Call History files have been updated. See the full list of resolved issues below.

Installation

Download the Morse.Runner.1.85.3.zip file (also available in the Assets section below), Open the zip file, extract the folder to your DESKTOP, and run MorseRunner.exe within this folder. Do not add these files to a previous release folder, or place in a windows program directory as this causes errors. You can safely copy your MorseRunner.ini file from your previous install directory into the new install directory. After installing, read the Readme.txt file for more information.

Join our Community

You are invited to join our community effort. For more information, please visit the Morse Runner Community Edition project.

Our goal is to create a program you love to use, so please help by leaving any feedback you would like to share on our Announcements page or our GitHub discussions page.

Additionally, you can discuss or leave feedback at MorseRunnerCE on groups.io.

You have several ways to join in on our project and we look forward to hearing your ideas.

Release Details

Version 1.85.3 (July 2025)

General bug fixes...

• Send Station ID after 3 QSOs in Pile-Up or WPX Competition modes (Disable Station ID after 3 QSOs #421) (W7SST)
• Improve response after operator sends corrected callsign (FD won't accept corrected callsign #420) (W7SST)
• F12 Key should send 'NR?', not ' ' (F12 Key sends wrong message (sends '<call> <exch>', not NR?) #419) (W7SST)
• Delay first callsign sent when running Single Call mode (Ability to delay the first caller in Single Calls mode #424) (W7SST)

Contest-Specific improvements

• ARRL DX - Use 'ATT' for 100 Watts in Power exchange field (Use of ATT for 100 Watts in ARRL DX #392) (W7SST)
• JARL ACAG - Widen Number exchange field to display long exchange (JARL ACAG - Number exchange field is too narrow #416) (W7SST)
• ARRL FD - Update call history file
• ARRL DX - Update call history file
• K1USNSST - Update call history file

Delay first callsign sent when running Single Calls mode (#424)

When using bluetooth headsets, users have reported a problem where they will miss the first character sent after starting a contest in Single Calls mode. They must immediately send F7 ('?') to cause the first call to be repeated. To fix this issue, an additional delay can be added before the first callsign is sent in Single Calls mode.

• The following keyword is provided to specify an additional delay before the first callsign is sent:

  [Settings]
  SingleCallStartDelay=NNN

• NNN can be any value between 0 and 2500 milliseconds.
• The default value is 0.

What's Changed

• Improve Station ID after 3 QSOs, add StationIdRate keyword by @w7sst in Improve Station ID after 3 QSOs, add StationIdRate keyword #422
• Improve response after operator sends corrected callsign by @w7sst in Improve response after operator sends corrected callsign #423
• ARRL DX - Update call history file by @w7sst in ARRL DX - Update call history file #426
• 416 JARL ACAG - Number exchange field is too narrow by @w7sst in 416 JARL ACAG - Number exchange field is too narrow #427
• Delay first callsign sent when running Single Call mode by @w7sst in Ability to delay the first caller in Single Calls mode #424

Full Changelog: v1.85.2...v1.85.3

---

This discussion was created from the release v1.85.3 Bug Fix Release and History File Refresh.

[mashu]

Can Linux binaries be provieded as well ?

[w7sst]

Ah, good question. I would like to see a Linux binary at some point in the future. There is a branch of the original MorseRunner code base that has been ported to Linux, so we know the ground work has been laid. At some point I'd like to move in this direction, but health issues here at home are slowing things down. It would be a year or two out. Thanks for asking...

73,
Mike W7SST

[df7cb]

https://github.com/fritzsche/MorseRunner builds with fpc and lazarus on Linux and I packaged it for Debian: https://tracker.debian.org/pkg/morserunner

Ideally we would like to switch to this fork as it's actively maintained. The other one works but is dormant. I guess the difference is actually very small, just needs someone to understand the .lpi .lpr project files and do the necessary adjustments.