Installation

Chapter 2 - Installation

2.1. Overview
2.2. Unix Installation
2.3. Windows NT (CssNT) Installation
2.4. Windows Client Installation
2.5. Installation Programs

2.1. Overview

This chapter provides the information necessary to get started using CSS. The setup program also allows you to remove an old CSS version while upgrading to this release. Information about the installation and basic configuration is presented in a cookbook manner. For detailed configuration information, please refer to chapters 3, Program descriptions and 4, Configuration.

If you upgrade from an earlier version of CSS, all the control files in the directory /etc will be preserved. First time installations will install a minimal configuration with one dumb printer on device /dev/lp. To use the full power of CSS however, requires you to properly define the local environment in the configuration files.

Note!

All Unitec products require the license manager ULM to run properly.
The setup(I) program for the Unix CSS software will install all components in the proper locations.

2.2. Unix Installation

As a first step, an empty directory has to be created on the hard disk of the target system to install all the CSS files. Throughout the following sections we use the directory /tmp/css as the base for the installation. If you prefer to choose another directory, you should substitute the default name with the your selection.

login as root
mkdir /tmp/css

Next, the data on the distribution media must be stored in the /tmp/css directory on your hard disk. Normally Unix CSS is shipped on 3˝" MS-DOS DD or HD diskettes. Special formats are available upon request:

3˝" DD or HD diskette, Unix tar(1) format
5Ľ" MS-DOS format, 720KB or 1.2MB
5Ľ" 96 Tpi, 720KB or 1.2MB, Unix tar(1) format
QIC 24 tape cartridge, Unix tar(1) format

MS-DOS Format

MS-DOS diskettes contain one file css.tar or css.tzr. This file has to be transferred to the Unix file system. Several methods are possible. If you are using PC/TCP, Pathworks or PC-NFS the standard DOS copy command can be used to copy the software to any mounted Unix device. If you are using ftp, you must use binary transfer mode. Some Unix implementations provide a command to read DOS diskettes (e.g. SCO doscp -r).

Important!

Some copy utilities distinguish between text and binary files. The CSS files have to be transferred in binary mode in order to prevent any cr/lf conversions. As an example, the SCO doscp command must be used with the r-option and ftp must be set to binary mode.

Once you have copied the CSS software to your /tmp/css directory, login as root and change to it (cd(1) command). If the suffix of the filename is .tzr, use the following shell commands:

mv css.tzr css.tar.Z
uncompress css.tar

To extract all files use:

tar xvf css.tar

If the tar(1) command reports a Directory checksum error, try:

dd if=css.tar conv=swab | tar xvf –

Important! Before you upgrade from a previous CSS version, we urge you to save your data! If you do not want to perform a full save, make sure that you are able to rollback to your current version in case of installation problems. For this, you need your current software including the setup program, a save of the CSS base directory (normally /usr/lib/css) as well as a save of your reports in the CSS spool directory (normally /usr/spool/css). Unitec can not be made responsible for any damage caused by installation problems. Please also read the Unitec License Agreement.

You are now ready to run the setup program:

./setup

Note: If you are upgrading from a previous CSS version with WinCss clients, you must stop and restart the cssws(U) program. Since the invocation of this server process at boot time may be configured in several different ways (see WinCss(C)), setup(I) is unable to perform this action automatically. Please use ps(1) to get the process id (look in the PID column) and kill(1) to stop the (old) program. Then restart the new version as usual. If you implemented cssws(U) in /etc/inittab(4) the new server will be respawned by the Unix init(1) process immediately after the old program has been stopped without any user interaction. Failing to start the newly installed Windows server will most likely result in a version conflict or a protocol conflict error on the client systems. Although not very Unix like, you can of course also choose to reboot your server system.

Unix Format

If your distribution media is in Unix format, use the tar(1) command to extract the CSS files:

tar xvf /dev/x

where /dev/x is the device name of the drive required (e.g. /dev/tape, /dev/ct0, /dev/fd, /dev/fd0135ds18). If you are unsure about the device name, pleas consult your Unix manual. Some systems define a default device for the tar(1) command, so just tar xv may do the job.

If the tar(1) command reports a Directory checksum error, try:

dd if=/dev/x conv=swab | tar xvf –

If just one file named css.tar.Z is extracted use:

uncompress css.tar
tar xvf css.tar

and then

./setup

Setup

After calling the CSS setup(I) utility, just follow the on screen instructions. For a detailed description of this program, please refer to the program documentation later in this Chapter.

The contents of the various directories after successful installation is listed below:

Name	Contents
/etc	Configuration files css.* and ulm.default. Programs csa(U) and ulm(I).
/usr/lib/css	Default CSS base directory as defined by CSS_BASE_DIR. Will hold the CSS databases, a copy of setup(I) for potential uninstallation and internal information.
support	Subdirectory of CSS_BASE_DIR: read.me and other support files.
/usr/lib/ulm	Default ULM base directory as defined by ULM_BASE_DIR. Will hold the ULM database ulm.dat, a copy of setup for potential uninstallation and internal information.
support	Subdirectory of ULM_BASE_DIR: read.me and other support files.
cwd	CSS files, sample programs and functions.

After the download of the software, you may find additional information on CSS in the READ.ME file.

This concludes the basic installation and configuration. Many parameters may be set to change the behavior of the CSS software. The description of the configuration files can be found in the remainder of this manual.

Note!

In order to run the server program cssws(U), you will have to configure your TCP/IP network. Please consult the appropriate sections in Chapter 4, Configuration.

2.3. Windows NT (CssNT) Installation

The installation procedure of CssNT follows the usual Windows guidelines. All information required will be prompted by the setup program.

login as Administrator
start the Setup program

The CssNT software is shipped as self extracting ZIP archive or on floppy disks.

Setup

The CssNT setup program will guide you through each step of the installation process.

The contents of the various directories that are created in the CssNT folder during installation is listed below:

Name	Contents
etc	Configuration files css.* and ulm.default. Programs csa(U) and ulm(I).
lib	Default CSS base directory as defined by CSS_BASE_DIR. Will hold the CSS databases, a program for potential uninstallation and internal information.
support	Subdirectory of CSS_BASE_DIR: ReadMe.txt and other support files.
ulm	Default ULM base directory as defined by ULM_BASE_DIR. Will hold the ULM database ulm.dat and internal information.

This concludes the basic installation and configuration. Many parameters may be set to change the behavior of the CssNT software. The description of the configuration files can be found in the remainder of this manual.

Quick configuration

The configuration files can be found in the directory etc. You have to make sure, that each printer in the file etc\css.devices has a dv parameter specified. The printer devices must be given in Universal Naming Convention (UNC):

//host-name/printer-share-name

Please note, that in css.devices(C) all file names must be entered using the Unix directory separator '/'. The colon ':' after the drive letter, must be preceded by the backslash '\' (BS). Failing to do so would cause CSS to assume the end of the parameter entry:

C\:/dev/printer1

The setup program installs a printer with dv=C\:/CssDev1.txt. Therefor, output will be directed to the disk file C:\CssDev1.txt.

Changes in etc\css.devices and etc\css.forms are active after successful compilation through csa(U) only.

Where to find error information

If you encounter errors during CssNT operation, you should start the NT Event Viewer and check the Application Log for software messages. Information may also be found in the file lib\CssErrlog.txt.

If CssNT fails to operate correctly, use the Services applet in the Control Panel to check if the CssNT process is active. This service can be started manually if necessary.

2.4. Windows Client Installation

Start MS-Windows and insert the WinCss Setup diskette into drive A:
In the Program Manager choose File - Run
Enter a:\setup and hit <Return>

Configuration information can be found in WinCss(C).

2.5. Installation Programs

This section contains descriptions of the CSS installation programs in alphabetical order. The page headers for the descriptions contain the name and a brief description of the utility.

The Synopsis section contains the command line syntax, showing all possible options and arguments.

The Description section explains the purpose of the utility and any command line arguments.

The Options section explains each of the possible command line options.

Where applicable, program configuration details are listed in the Configuration section.

Program	Title
setup	Product Installation.
ulm	License Manager.

	Back to top