ForScore stores configuration information in three locations.  Version 2.0 changes the details of this slightly.

 

1.Config.tps is the main configuration file.  This is stored in the DATA folder along with the other data files used by the software.  It contains most common configuration items.

2.INI files are used to score machine-specific information. They are now stored in the DATA folder

3.The Windows Registry is used to store a few items that don't fit well into either of the other locations.

 

Networking Implications

Ordinarily, you won't need to be aware of this information.  If you are using ForScore in a multi-computer network setting, though, it is important to understand.

In a multi-computer score entry situation, there are three basic ways of proceeding

1.The client runs ForScore from its hard drive, but points its data location to a share on the server (using datapathset).

2.The client runs ForScore from the server and automatically uses the server for its data location.  This, however, will not work correctly with Vista client machines - use the next option.

3.The client runs ForScore from the server and specifically points its data location to a share on the server (using datapathset).  This will work correctly with Vista client machines.

 

config.tps

If you have networked two or more computers to work on the same set of data, they're obviously reading and writing to the same set of files.  (I'm not talking here about two computers just being used for Compare.)

That means they will both (or all, if more than two) be using the settings defined in config.tps.  For most configuration items - club name, report format preferences, Compare alternate screen color, etc. - this is appropriate.

 

INI files

Some items, however, are inherently specific to a computer.

For example, if I've specified a custom graphic for web results, I've had to tell ForScore where that logo is on my hard drive.  There's a good chance that that graphic doesn't exist on the server and client machines in exactly the same location.  Similarly, ForScore remembers window positions; those may differ if the different machines have different size monitors and resolution.

Those parameters along with the last choices you've made when creating web results and various printouts are stored in INI files.

ForScore creates several INI files - one specifically for the custom logo graphic, another for the last date you checked for program updates; and a third for most other configuration items that I've chosen to store as INI items.  Other INI files get created when you produce score sheets, nametag badges, etc.

•In order that multiple machines can access their INI files when they're running from a server and/or getting their data from the server, the INI file names are customized.  The name begins with the computer's NetBIOS name.  So for example, with my laptop that's named P4X, the INI files it will use are named P4X-forscore.ini, P4X-graphic.ini, P4X-update.ini. etc.

NOTE:  If you are used to the INI settings on your machine and you now want to connect it to a server, you will want to copy those INI files manually to the data folder you are sharing on the server.

 

Windows Registry

A few items are stored here that need to be accessed before ForScore is up and running.

•The default program location, used to tell my installer programs where to find ForScore when you install an update to the software.

•Alternate data file locations, used when you start ForScore using /DATA /DATA1 /DATA2 /DATA3 or /DATA4 command-line switches (set in Program Preferences and with the datapathset.exe utility program.)

•The folder location you have specified to do background data file backups while you're entering scores.

•The license file location you specify when you start ForScore using the /local switch.

Because these need to be stored in a common location (not dependent on which user account is logged onto the machine), you need to be logged onto your computer as an administrator.

In addition, on a Vista machine you must be running the program as an administrator.

When you run datapathset.exe, it will bring up the elevation screen and require you to be running with full administrator privileges.

For the items that are set directly in Program Preferences in ForScore, however, you will need to right-click your ForScore shortcut and specify Run as administrator.