For Windows networks, AcuLaunch software is also on CD-ROM. The files contained on the release media are described in the file "READ_ME.rcl." Note that if you move or delete any installed ".dll" files, AcuLaunch will not run.
1. Install and configure TCP/IP before installing AcuLaunch.
2. Log onto your NT server using the Administrator account or an account that belongs to the Administrators group.
3. Insert the Acucorp product CD-ROM into your disk drive. If the installation program does not start automatically, click the Start button, select Run, and enter:
D:\setup.exe
replacing "D" with the device designation of your CD-ROM drive. Follow the instructions on the screen, entering your product code and product key when prompted. During the installation procedure, you will be prompted to specify an installation directory, or to accept the default location. Do not specify a directory name that has embedded spaces. Embedded spaces prevent the PATH variable from being set properly and can cause other problems under Windows. You will also be prompted to select a component to install. Select AcuLaunch from the list of available products.
4. If you already have the files "c:\etc\AcuAccess" and "c:\etc\acurcl.cfg", the setup utility will detect them and will ask you if you want to overwrite them. Do not overwrite them unless you have a backup copy. The AcuAccess file (as delivered from Acucorp) contains one access record that gives all users access to AcuLaunch. You can modify this file later, if desired. The file "acurcl.cfg" contains the server configuration variables; when the file is first installed, these are all commented out. You can also modify this file later if desired.
5. If you want acurcl to start automatically on boot, acurcl must be installed and started as a Windows NT/Windows 2000 service. The setup program creates a sample Start Menu folder, if desired, and asks if you want to install and start these services.
Please note that installing a service on a particular port resets all start-up options for the service on that port. You can use all valid "-start" options when installing acurcl as a service. These options are stored so that the service will use them when starting.
The default service is named "AcuRCL." All other service names include the port on which to run.
The Start Menu folder contains icons that can run the various programs needed for AcuLaunch, along with icons to display the release notes and the AcuLaunch configuration file. The Start Menu folder is not required to run AcuLaunch. You can safely remove it.
6. If you choose to start AcuLaunch during the installation process, a DOS window is displayed showing the status of the Windows NT/Windows 2000 services being started or restarted automatically. You may see some error messages that can be ignored if the Windows services are not already installed and running. For example, you might see:
acurcl -kill Open/Control Service failed acurcl -remove Open/Control Service failed acurcl -install AcuRCL service installed. acurcl -start STATE: START PENDING
7. The Windows NT/Windows 2000 services that are needed for AcuLaunch can also be started manually. Here are two methods for starting the required Windows services:
From the icons:
Install AcuLaunch Service
Start AcuLaunch Service
From the command line:
acurcl -install acurcl -start
Refer to Appendix A for information about other acurcl command line options.
Please note that when AcuLaunch is started as a Windows NT or Windows 2000 service, all paths used in the configuration file or on the command line are relative to the Windows NT or Windows 2000 system directory (e.g., c:\winnt\system32). For instance, if your current directory is c:\acucorp\acucbl5xx\AcuGT\bin and you start AcuLaunch with the command "acurcl -start -le acurcl.log", the log file will not be created in the current directory, but rather in the \winnt\system32 directory. If desired, you can use full pathnames, which has the effect of using an explicit file.
8. After the services are installed and running, there should be no reason to stop them. However, if you choose to stop them, you may do so using these commands:
From the icons:
Stop AcuLaunch Service
From the command line:
acurcl -kill
You may also perform start and stop operations from the Service Control Applet. After the services are installed, there should be no reason to delete them. However, if you decide to delete them, use the following command from the command line:
acurcl -remove
Refer to Appendix A for information about other acurcl command line options.
This deletes only the services and does not delete the executables. To help in resolving service problems, we display some messages from these services in the Microsoft Event Viewer:
Start/Programs/Administrative Tools/Event Viewer/Log/Application