The guide

Installing on the church PC

How to put ScriptureCaster on the projection computer, check it before a service, and copy a working setup from one machine to another.

Copy the folder

ScriptureCaster is portable. There is no installer and nothing is written to the Windows registry — the whole application is one folder. Copy it to the projection PC and run ScriptureCaster.exe from wherever you put it.

A sensible home is C:\ScriptureCaster\. Avoid the Desktop and avoid OneDrive-synced folders; syncing a running application causes odd file locks.

Check it before you need it

From a command prompt in that folder:

ScriptureCaster.exe --selftest

This starts everything without showing a window and reports:

  • which Bible translations loaded, and how many verses are indexed
  • how many screens Windows can see, their sizes and positions
  • whether any screen uses display scaling
  • whether the window fits the screen it is on
  • whether NDI output is available

Run it on the machine that will be used on Sunday, not on your laptop. The two most common surprises — a projector Windows has not extended onto, and display scaling making everything larger — only show up on the real machine.

Display scaling

If the self-test warns about scaling, Windows is enlarging everything. That makes the buttons bigger, but it also makes the window need more room. On a 1366×768 screen with 125% scaling there may not be enough space.

Either set that display to 100% in Windows, or reduce Button size in Settings.

Copying a working setup

Settings live in a plain text file next to the application. Once one machine is configured the way you want — screens, colours, fonts, translations — copy that file to the other machine and it comes up the same.

The Bible database is a single file in data\. Copy it too and the new machine has the same translations without downloading anything.

Keeping it up to date

From version 1.2 the program updates itself: Settings → Updates. It looks once a day in the background, downloads only what changed, and installs it the next time the program starts — never in the middle of a service. Your settings and your Bible library are not part of an update and are never touched.

Coming from 1.0 or 1.1 there is one manual step first: see updating.