Network Installation

In order to minimize network and software upgrade support issues, the GLWIN.EXE file should be loaded in a central directory accessible to all workstations. Multiple copies of the GLWIN.EXE should not be distributed across the network as this will cause future problems if some EXE files are missed when the software is upgraded.

The software may be installed on each workstation off the original system disks or CD (to the same central directory each time) or the CAPGL.INI file from the first installation can be copied directly into each workstation's Windows directory.

CAPGL.INI is the only file that needs to be copied locally onto each machine. The [Environment] section should specify the correct paths to access the program, help and data files from the "server" computer.

No registry or environment variables need be set.

In order to maintain backward compatibility with earlier versions of CAPITAL, custom modules supplied by third-parties, and other non-Microsoft operating systems (such as OS/2, Linux, Novell, etc.) path settings should be set in the traditional drive letter/path name format. Under Windows this may require mapping of a drive letter using Windows Explorer.

Never directly map the \CAPITAL directory to a drive letter. CAPITAL Office programs must not appear to be sitting in the root directory of a drive. If you wish to create a drive letter dedicated to CAPITAL only, place the CAPITAL program within another directory. Imagine you wish to dedicate drive G to CAPITAL. From your "server" store CAPITAL within this directory structure:

\PROGRAMS\CAPITAL\...

And then map the \PROGRAMS directory to drive G.