Manuals >Installation and Customization Guide >Using IC-CAP on UNIX Systems
Print version of this Book (PDF file)
prevnext

Installation and Configuration Issues

Following are helpful hints for installation and configuration problems that may occur.

Viewing Installation Files

If you wish to see a list all of the IC-CAP files that have been installed, they are identified in the text-only fileset file, which can be accessed from the directory: $ICCAP_ROOT/etc.

Recovery of Temporary Files

If IC-CAP is abruptly terminated (by power failure, kill command, system shutdown and so on), temporary files may be left in one of the following locations:

    • /var/tmp
    • directory specified if $TMPDIR file is defined
    • /tmp for Linux regardless of $TMPDIR or $ICCAP_TMP

If work is lost during a crash, files beginning with an IC... filename might contain macro and transform PEL code that can be recovered. If they exist, these files will appear in the appropriate tmp directory.

Purge these files, but only when IC-CAP is not running. Avoid removing any files that are currently in use by other applications running on the CPU or cluster. IC-CAP temporary files appear in blocks that are all created at approximately the same time, and share the last four or five digits of their names.

Altering maxuers Variable on SUN systems

If you are having memory problems when running IC-CAP on a SUN system, try the following:

  1   Create a new kernel.

  2   Increase the value of the maxuers variable to 32 from 16.

This variable affects many other system variables, as it figures in the equations for calculating their value. It is recommended to limit the value of this variable to about 128, as a larger number tends to become counter-productive.

Checking XNLSPATH Variable

If you are having difficulty starting or running IC-CAP, check to see if the environment variable XNLSPATH is specified in your .cshrc (C-shell) or .profile (Bourne or Korn shell) startup file in your home directory. This variable should not be set. If it is, cancel the setting and restart IC-CAP.

Specifying Start and End Address of Instrument Searches

The INST_START_ADDR system variable specifies the start address for instrument searching during Rebuild (active list). This value should be an integer between 0 and 31, inclusively. When there is a printer, plotter, or prober on the same GPIB with measurement instruments, set INST_START_ADDR greater than any one of those non-instruments to avoid the identification process. Default is 0. You may need to change some addresses. The objective is that IC-CAP should not attempt to communicate with any printer, prober, or plotter on the GPIB bus during the rebuild.

The INST_END_ADDR system variable specifies the ending address for instrument searching during Rebuild (active list). This value should be greater than the INST_START_ADDR value and less than 31.

Differences Between IC-CAP Linux and SUN Installations

The following table shows some important installation differences between usage of Linux vs. SUN systems.

Table 8 HP vs. SUN Installations
Item
Linux Systems
SUN Systems
Default interface file
hpib or gpib1 (depending on interface)
/dev/gpib0
Card identity
Select code
Board number
Default card address
21
0
Time out value
Continuous
Discrete
Bus hang
Breakable
Rely on time out
HP-GL plotter
Supported
Supported
Character set (plotter only)
USASCII only
USASCII only
Window Manager
KDE or Gnome
Motif or OpenWindows or CDE


prevnext