9.1.0

Timing a race is high-pressure; you shouldn't have to fight your software or lose your place during a live data sync. In the past, heavy data streams could cause system freezes, and setting up multiple laptops was a tedious, manual process. RunScore 9.1.0 rebuilds the foundations the software is built on and ships a long list of fixes across listings, timing hardware, remote stations, and online registration to resolve these issues.

Critical System Requirement

Windows 10 or 11 is required. Windows 7 is no longer supported starting with 9.1.0 to allow for a modernized, crash-resistant foundation.

Streamlining Your Setup

• One installer, three choices: A single installer now handles RSServer, RSClient, or both, letting you pick the combination you want during setup rather than running separate installers.
• Move settings between machines: Preferences and External Timers configurations can be exported to and imported from JSON files so setting up a new laptop no longer means re-entering everything by hand. Saved credentials are left out of the export for secure fleet sharing.
• Calculate Ages Your Way: Age calculations no longer have to be based on the event date. You can set a custom AGE AS OF DATE in your Entries.INI file to calculate entrant ages relative to a specific date (like Dec 31 for USAT or series scoring).
• No missing file popups: Opening a race that contains a newly added or unscored event automatically creates empty .FN2 and .TM4 files instead of stopping you with error dialogs.

Holding Steady During Live Operations

• Keep your place (Alt+K): Turn selection tracking on with Alt+K so your choice is remembered between sessions. Background updates no longer throw the window back to its default order, and sorting by a different column moves the view to wherever your highlighted record landed.
• Stop accidental duplicates: The F11 database backup shortcut has been relocated exclusively to Browse mode, preventing you from accidentally creating duplicate participant records from the Enter screen.
• Smooth live timing: Live Results handles incoming timing data without the crash and freeze risks it carried before, and releases memory properly during long sessions.
• Client & Server parity: RSClient reads Entries.INI through the same entry-processing code as RSServer, ensuring age calculations, entry rules, and control sections match.

Hardware & Cloud Integrations

We have fortified connections to your vital hardware and registration platforms to prevent data drops and crashes.

Integration	Key Updates & Fixes
MyLaps Cloud Timing	The integration connects to api-cloudtiming.mylaps.com and now requires two keys: your MYLAPS-integration-key and an Ocp-Apim-Subscription-Key.
ChampionChip	The payload buffer grew from 30 to 256 characters to prevent crashes and text truncation on long location names.
iPico & Macsha	Fixed iPico gun-start (ab) packet processing over live TCP connections and resolved Macsha port reader ID validation errors.
Summit Timing	Malformed data from Summit timing devices no longer crashes RunScore, and you are notified when faulty hardware data arrives.
Registration Platforms	Fixed Race Roster multi-event download stops, RunSignUp infinite retry loops, and TFRRS DirectAthletics login failures.

Under the Hood: Scripting & Diagnostics

• Faster Support Resolution: RunScore's crash reporting now runs on BugSplat 8.1. If an unhandled error occurs, the crash report dialog appears while the program is still visible behind it. Logs are registered at startup so complete diagnostics are sent to support even if the program freezes.
• Listing & Scripting Fixes: Plain-file exports now honor the Records Per Page setting in your listing file, and .include files receive their parent's parameters again (like %1 and %2).
• Formatting Protection: The valid MM/DD/YYYY date format in a listing command no longer raises an invalid date error. We also prevented crashes caused by invalid PAGE LENGTH, negative LINE FEED, or a TIMES/WAVE value of zero or less.