If you have problems in installing IF/Prolog, you can always get in touch with your IF Computer. The installation procedure creates an installation log install.log in the directory where you started the installation.

Below we list some known sources of trouble.

Tape read errors

Before reading the tarfiles and extracting them, make sure that you have enough disk space.

First check whether you use the correct device entry. Then try to read the tape from a tape drive on a different machine. If this works, please install over a network connection as explained above.

IF/Prolog binary cannot be generated

IF/Prolog makes some system dependent assumptions on the places where certain libraries are to be found. Please check the paths in the file link_sys.sh and change if different on your machine. Also, it usually calls the C compiler to bind the IF/Prolog kernel. If a C compiler ( cc ) cannot be found, it tries to use the linker ( ld). As a last resort a prelinked kernel will be installed. Please check the commands in the file link_com.sh and adapt to your machine. If you have some advanced knowledge of Unix you can also try to trace the installation script or link_prolog in order to locate and fix problems.

Licensing problems

Please make sure that the license is correct for the machine you installed IF/Prolog on, that the license information was correctly entered in the file Key , and that this file has read permission for you.

Shared Library problems

If IF/Prolog cannot find some shared libraries at startup, please check whether you have these libraries on your machine. If they are not on your machine, you cannot run IF/Prolog before installing them. Otherwise your environment must be configured to include the respective directories in the lookup path. For example, on a Sun machine there is an environment variable LD_LIBRARY_PATH that has been set to /usr/X11R5/lib:/usr/IXMOTIS12B/lib in order to allow access to X and OSF/Motif shared libraries.