Before you can install TERM for UNIX from CD-ROM, you must mount the CD. Most UNIX platforms support SCSI or ISO 9660 CD-ROM drives. To find out whether or not the drive is recognized on the system, change directories to the /dev or /dev/dsk directory and type:

ls -l cd*

The permissions and device names will be displayed out, similar to the following example:

brw-rw-rw 1 root sys 51, Oct 28 08:16 cd0

In this case the CD-ROM device is cd0. Determine which device corresponds to your drive.

Mount the TERM for UNIX CD from the root directory by typing:

mount /dev/cd0 /mnt

Use the correct path for the CD-ROM device and the mount directory you prefer to use if not /mnt. Then change directories to /mnt/termunix and type ls to list the files and directories on the CD. Change directories again, this time to the directory that contains files for your platform:

For example, if your platform is SCO OpenServer 6, you would change to the u3 directory.

Next, copy the files from your chosen directory to the /tmp directory. Then change to the /tmp directory and extract each *.tar file separately with tar xvf:

tar xvf termu3.tar

At this point you can install TERM by running the install shell script:

/bin/sh ./install

Please note that on some CD releases, the files are in upper case. Any commands must refer to files in the correct case, upper or lower.

This information is also available in a screencast.

TERM for UnixWare installes from the /termunix/u3 directory on the TinyTERM/TERM CD. As it installs, it asks which UNIX you are installing to. Choose INTERACTIVE.

In order for TERM to use a serial port, the port must be set up for bidirectional access. (More information on this is in the Setup and Configuration of the UnixWare manual.) The script below should work:

pmadm -r -p ttymon3 -s 01d
pmadm -a -p ttymon3 -s 01d -s login -fu -v `ttyadm -V` -m "`ttyadm -b -h -r0 -t 60 -d /dev/term/-1s -1 9600NP -s /usr/bin/shserv -m ldterm -p "tty01 login: "`"

Change the lockfile format within the TERM setup under communications to:

/var/spool/locks/LK.%m

You must now connect to /dev/ttyxxx, not /dev/term/ttyxxx.

If your machine can’t read the media TERM came on, there are a few things to check:

1. Verify that the correct extraction command is being used. Double-check your release notes for that information.
2. Verify that the correct device name is being used for the media being read. If you are unsure of the device name and it is not listed in the “Installation and Set up of TERM” section in the manual, you can search for the correct device name by inserting the release media in the appropriate drive and typing the following at a system prompt:
   

   # for x `ls /dev/rfd”
   > do
   > echo “Device: $x ”
   > tar xvf $x
   > done
   #

   This will cause the tar command to be used on all the selected devices until the correct one is found. In order for this to work correctly, you must loop through the right files and directory. An example of some directory specifications are as follows:

   Interactive UNIX system V/386 : /dev/rdsk/* (disks)
   SCO XENIX/UNlX : /dev/rfd* (disks)
   Sun Microsystems : /dev/rst/* (cartridge tape)
   ICL DRS : /dev/rmt/* (cartridge tape)

   Century Software, Inc., has provided TERM for UNIX releases in the following formats:

   Tan 5.25 Diskette: 36OK
   Black 5.25 Diskette: 1.2M
   Black 3.5- Diskette: 720K
   Black 3.5- Diskette: 1.44M
   Cartridge Tape: Low density
   CD-ROM: ISO 9660

3. Remove the media, reinsert it and try again.
4. If the release has multiple diskettes, try executing the extraction command on each diskette received. If all diskettes fail, reboot the system and repeat steps 1 through 4. Occasionally, UNIX drives can get messed up and require rebooting to correct. If only one diskette fails, it is an indication that the diskette is bad. Call Century Software technical support.
5. If all diskettes fail again, try using a non-Century Software diskette. If it fails to read, the diskette drive probably requires cleaning. If the non-Century Software disk works, the TERM product diskettes are damaged. Call Century Software technical support.

Cartridge Tapes
lf you are having problems reading a cartridge tape, follow the steps above. lf the above steps fall, be sure to use the blocking option with the tar command. Century Software’s tapes are usually written with a block size of 20. For example:

tar xvfb /dev/rctO 20

lf adding the block size option doesn’t help, try using the dd command as follows:

dd if = /dev/ < device > | tar xvf –

lf this command doesn’t work, try:

dd if = /dev/ < device > conv = swab | tar xvf –

SCO OpenServer 6 addresses serial ports with /dev/term/XX numbering. TERM for SCO UNIX’s callin and callout routines require /dev/ttyNN format instead. While SCO OpenServer 6 also provides that format for serial ports, it’s not their preferred method.

CR 794

On Solaris 8, TERM gives the error, “Cannot open device” when connecting to a tty port. This works properly on earlier versions of Solaris. Changing the port permissions does not help, nor does starting TERM with the -i command-line parameter.

With TERM for HP-UX, if you specify a .con file on the command line:

term connection.con

it does not successfully connect via modem. You get the error, “Modem not responding” instead. The modem responds normally if the .con file is not specified.

CR 633

Run the following script command in TERM for Linux:

setkey sf1 “text”

No matter how it’s actually mapped, Shift-F1 does nothing. The same is true all the way through Shift-F12. Ctrl-function keys also fail, as do Ctrl+Shift and Alt keys. You can see this by running:

term -z ktest.cmd

In fact, Shift-F5 displays as “sf1” using that script. Shift-F8 is “sf4” and nothing past that works at all.

This also affects TERM for SCO UNIX versions 6.2.5b and 6.28 running on SCO 5.0.6 or higher. SCO maintenance pack 2 for SCO OpenServer 6 restores the system console to ANSI, instead of the default AT386. This fixes the problem on that particular OS.

CR 565

TERM for UnixWare does not properly enable or disable tty ports on OpenUnix 8. The devices apparently aren’t listed in the /etc/inittab where TERM expects to find them.

CR 495

TERM for Sun Solaris includes two cd commands in the install script, in the middle of the following if statement:

if [ $OSmajor = 5 ]
then
LASTMOD="28 Apr 95"
BIN_FILES="$BRANDIT"
cd Solaris
else
cd SunOS
fi

On the CD distribution of TERM for UNIX, neither “Solaris” nor “SunOS” exists during the install process. This makes the install script fail with the listed error. The workaround is to install TERM manually.

CR 469

The TERM for UnixWare install fails with a segmentation fault on UnixWare 7.1.1. This is caused by the brand program that licenses TERM. The fault prevents /usr/bin/term from being serialized, making it unusable.

CR 300