A.R.R.O.W. Spelling may be freely installed from a network location rather than the DVD. Simply copy the contents of the DVD to a shared network directory and run setup.exe on each client from there.
Each client machine will still need a Topic DVD in the drive to run.
A.R.R.O.W. Spelling was designed as standalone software. It is possible however to run it from a server, though you should consider carefully the advantages and disadvantages of doing so. This information is intended for experienced system administrators only, is used at your own risk, and A.R.R.O.W. will not normally provide support for unusual installation scenarios. Running ARROW Spelling remotely via Remote Desktop, Citrix etc is not supported, and we strongly advise against attempting to do so.
A.R.R.O.W. Spelling requires a number of standard Windows controls to be registered, as well as DirectX 7 or higher. These are normally handled by the installer. If you intend to run Spelling from a central location, you will need to take steps to ensure these are registered yourself.
The full list of dependencies is:
Many of these may already be registered, depending on your OS version and other applications that may be installed. Any that are not will need to be registered, via REGSVR32 in the case of DLL and OCX files, and REGTLB in the case of TLB files.
Alternately, you can simply install A.R.R.O.W. Spelling on the local machine to handle the registrations, then delete (NOT uninstall) the local copy and run from the server.
A.R.R.O.W. Spelling by default writes temporary files to the user's home directory (normally "c:\documents and settings\< user>\My Documents" on Windows XP, or "c:\users\< user>\Documents" on Windows Vista). If this location is mapped to a network share, as it commonly is in networked environments, AND multiple users are logged on as the same Windows user, issues will occur as they overwrite one another's temporary files. This can be avoided through the use of the registry key: HKEY_CURRENT_USER\Software\ARROW\Spelling\Settings\Local Path, which is created when the program is first run, and defaults to the My Documents directory mentioned above. This should be changed on each machine to a different location, whether networked or local, where the user has full filesystem access. In the scenario described above, especially where users have no write access to the local hard drive, we recommend using: < My Documents>\< Machine Name>
Any further problems? Please let the A.R.R.O.W. Centre know by e-mail or by phoning 01278 652863.