Skip to main content

Troubleshooting

Quick fixes for common error messages and unexpected behavior.

Chip files behave strangely when loaded from the Desktop​

Avoid loading chip files (File > Load Chip File, or Ctrl-F9) directly from the Windows Desktop — this can cause read problems. Keep chip files in the race folder or a sub-folder of it instead; that also keeps the file bundled with the race if you hand the folder off to someone else.

"Can't find file" errors from a Look Up command​

If entering a race shows an error like Can't find file: ZIP.frm (or another lookup name from a Look Up command in entries.ini), the lookup's .frm/.dta files aren't in your race folder — that's where RunScore looks for them by default. Add the missing files there, or point the command at a full path. Answering "OK" lets RunScore continue running; you just won't get that lookup's auto-fill.

"Problem initializing COM 5" (or similar) at startup​

This happens when an External Timer is initialized with the Auto enable external timer on start-up preference on, but the configured COM port isn't available yet when RunScore starts. Make sure the COM port is set up and the cable is attached before launching, or turn off Auto enable external timer on start-up in Tools > Preferences.

Results or entries don't add up​

Try, in order:

  1. Run Update All (Alt+F4 from Enter/Edit Names, server only) to recalculate lookup and derived fields for every record — see Updating many records at once.
  2. Close and reopen the race.