Installing on an Individual Computer

Do the following if you want to install on an individual computer, whether it is attached to a network or not, rather than on a network server.

• If you haven't already done so, download and run the setup program from our Web site.

• When asked for the destination location, either accept the default location or specify a different location on this computer if desired. If you specify a folder that does not exist, the setup program creates it.

If you want to share reports with other users, you may wish to specify a synchronization folder.

Installing on a Network Server

Do the following if you want to install on a network server. Note that after installing it on a server, you also have to perform a workstation installation on each computer that runs the program from the server; instructions for doing that are in the next section.

• If you haven't already done so, download and run the setup program from our Web site.

• When asked for the destination location, specify the desired folder on the server. If you specify a folder that does not exist, the setup program creates it.

Installing on a Network Workstation

Like most Windows applications, Reporting4Act! needs certain "runtime" files installed on a workstation even if the application is run from a server. After you have installed the program on a network server and want to be able to run it on a particular workstation, run WSSetup.exe from the server directory where the program is already installed and follow the instructions.

Silent Installation

Silent installation allows you to install the application without any prompts. This is helpful when you have a lot of systems to install on and want to speed up or even automate the process. To install silently, add "/VERYSILENT" to the command line. For example:

setup.exe /verysilent

In addition to /VERYSILENT, here are some other command line parameters you may find useful:

• /LOG: causes Setup to create a log file in the user's TEMP directory detailing the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why. The log file is created with a unique name based on the current date (it will not overwrite or append to existing files.) The information contained in the log file is technical in nature and therefore not intended to be understandable by most end users.

• /LOG="filename": same as /LOG, except it allows you to specify the path and filename for the log file. Existing files are overwritten. If the file cannot be created, Setup aborts with an error message.

• /DIR="x:\dirname": overrides the default installation directory. A fully qualified pathname must be specified.

• /GROUP="folder name": overrides the default program group folder.