3.1. Cascade Connect in Windows

Since Cascade Connect uses TCP/IP, you must make sure that the TCP/IP protocol layer has been installed and configured correctly in Windows. If not, please refer to the appendix TCP/IP Installation and Testing, then continue here.

If you are installing Cascade Connect under Windows NT, you need to have Administrator Privileges in order to install the software.

To install Cascade Connect in Windows, simply:

The Windows services file

When the installation program has completed the file transfer it launches a program that attempts to add an important line to the c:\Windows\services file on your computer. The line that is added is as follows: cascade 4501/TCP This line is critical to the installation of Cascade Connect. Your computer may contain many services files or no services file at all. The installation program may be unable to find a services file or to determine which TCP/IP protocol is being used.

In Windows NT, the installation program attempts to edit a services file in the \winnt\system32\drivers\etc directory. If a services file is not located, you will have to locate this file and add the following line:

    cascade   4501/TCP

Since each manufacturer's services file is different, you must find the services file which your TCP/IP protocol is currently using and insert the line using a text editor.

The location of the services file depends on the TCP/IP software you are using. A Microsoft TCP/IP implementation typically puts the services file in the C:\Windows (or equivalent) directory. Most third party software either installs the services file in the same directory that their software was installed or into a directory named C:\ETC. Refer to your TCP/IP documentation for the location of this file.

When the installation program has finished modifying the services file it will create a group of Cascade Connect icons. You will need to reboot your computer in order for the changes to the services file to take effect.