
                        Running Third-Party Software


COHERENT runs many packages from third-party vendors that were designed for
use with  other operating systems,  in particular SCO  UNIX.  COHERENT runs
these packages,  but some require some minor  reconfiguration of either the
package, of COHERENT, or both, to run smoothly.

The following  sections describe  some of  the packages that  Mark Williams
Company  has tested,  and gives  directions on how  to perform  these minor
reconfigurations.   Note that  we  continually test  new  packages, so  the
following list probably is  incomplete.  For the latest information on what
packages  run under  COHERENT,  and how  you  can run  them, telephone  the
company  from which  you  purchased the  software, check  the MWC  bulletin
board, or telephone Mark Williams Company.

                             General Directions

To  install  third-party  UNIX software  onto  COHERENT,  be  aware of  the
following general rules:

1. COHERENT does  not support  the command  custom. To install,  you should
   read the product's manual and determine what must be done to install the
   product.  Some  products come with a shell script  that performs all the
   tasks of  installation; you can use  the Bourne shell sh  to invoke that
   script.   Other  products  use  tar  or  cpio; look  in  your  package's
   installation or  release notes for instructions.   Please note that when
   untarring or cpioing floppy disks from other UNIX systems, you sometimes
   must use  the complex UNIX device  names that are now  supported in this
   release.  For  information on floppy-disk device  names, see the Lexicon
   entries for fd and floppy disk.

2. Some third-party packages  support many different operating systems, and
   when you  install the package let  you pick the operating  system from a
   menu.  If this is the case, you should pick COHERENT first, if it is one
   of the  options.  If COHERENT  is not an  option, pick SCO  UNIX; if SCO
   UNIX is not  available, then Interactive UNIX; and if  none of those are
   available, then  USL UNIX System  V release 3.2.   If none of  those are
   available, then select generic UNIX system V release 2.

3. Some packages offer  a variety of console devices.  If  you have a color
   console,  select colorcons.  If  this is  not available,  try at386.  If
   neither is  an option,  or if  you have a  monochrome console,  then you
   should select monochrome; in most cases, this works correctly, even with
   color devices.

4. If  possible,  install  all  available  terminal types.   Some  packages
   require that you reinstall the entire package should you need a terminal
   type that you have not yet installed.

5. The SCO impementation of the  link command ln will overwrite an existing
   file by default.  This behavior does not comply with the POSIX Standard.
   Under COHERENT, you  must use the option -f to  force ln to overwrite an
   existing file.   Some installation scripts, however,  depending upon the
   non-standard  behavior  of ln.  If  this problem  arises  while you  are
   installing a  package, you must edit the  installation script and insert
   the flag -f where appropriate.

6. COHERENT  does not  support the  brand utility  from SCO.   This utility
   ``brands'' (or serializes) executables using a serial number and license
   activation key.  Any package that requires brand for proper installation
   and execution will not work under COHERENT.

                            Third-Party Packages

The following  gives information on  using some of the  more popular third-
party UNIX packages under COHERENT.

Aide de Campe

This package installs and runs correctly.

BBX Progression/4

The installation  of this package  requires that you use  the command cpio.
Because the installation program  does not prompt for the two supplementary
disks, you must re-issue the command

     cpio -icB

for each disk in the distribution.

The newest  version from BASIS runs  BASIS International's regression suite
without error.

Blast

The package works correctly.

ccsh

As  of this  writing, the  shell-script  compiler ccsh  does not  run under
COHERENT  4.2.   That  is  due  to  the  fact  that  its  internal  library
/usr/lib/libccsh.a is  not in  the COFF format.   It does run,  however, on
release 3.2 of COHERENT.

For details, please contact the publisher of ccsh.

Codebase

The Kernighan-and-Ritchie source compiles.

Dataflex

This package installs and runs correctly.

dBASE III

The package works correctly.

dBASE IV

To install dBASE IV under COHERENT, do the following:

1. Type the command

        cd /


   to change to the root directory.

2. Insert System Disk 1 into a floppy-disk drive.

3. Type the command

        tar -xvf /dev/rfvaX ./tmp/install

   where X  is `0'  or `1',  depending upon whether  you have  inserted the
   system disk into drive 0 (i.e., A:) or 1 (i.e., B:).

4. When the file is extracted, issue the following command:

        cp ./tmp/install ./tmp/coh-install


   Then,  use the  editor of  your choice  to edit  file ./tmp/coh-install.
   Change line 33 from:

        label=`dd if=$disk count=1 | dd bs=100 count=1 2>/dev/null | tr`


   to

        label=`dd if=$disk count=1 | dd bs=100 count=1 2>/dev/null`


   Save the edited file.

5. Make sure you are in the  root directory!  This is crucial at this stage
   to installing correctly.

6. Execute the new install script by typing:

        /bin/sh ./tmp/coh-install /dev/rfvaX


   Once again, substitute `0' or `1' for X depending upon which floppy-disk
   drive you have inserted the system disk.

7. Continue  doing   the  installation   normally,  as  described   in  the
   documentation that comes with the dBASE-IV package.

8. When  you  have concluded  installing  dBASE IV,  you  must execute  the
   following final commands:

        cd /usr/local/lib/dbaseiv
        rm dbase1.res
        ln ./dbase1.res.us ./dbase1.res
        rm /tmp/coh-install


You should now have a working implementation of dBASE IV!

Some users  have encountered problems with  this package's license manager.
They report that the first time  they added a license to the data base, the
license  manager corrupted  the entry, thus  prompting some  surly behavior
from dBASE when they attempted to use the package.

To correct  this problem,  use the  dBASE utility editlic  to add  a second
license  entry.  It  appears that  dBASE stores  and processes  this second
entry correctly.  After you  confirm that the new entry functions properly,
re-invoke editlic  and remove the original entry.   After that, all appears
to work as it should.

You may  experience some problems  with console output and  the handling of
function  keys.  If  this is  the  case, you  need a  version of  the dBASE
terminal-description file  that is corrected for  COHERENT.  You can obtain
this  file from  site  raven on  the  Intenet, or  from  the Mark  Williams
bulletin board.   If all else  fails, send mail to  support@mwc.com, and we
will mail a copy to you.

Some users of dBASE IV have reported that the package, for whatever reason,
does not  recognize directory or  file names that  contain capital letters.
If dBASE IV has trouble saving  files, check the name of the directory, and
make sure it is all in lower-case letters.

FilePro

The package works correctly.

Flexilint

The tool Flexilint compiles and runs under COHERENT release 4.2.

To install  the package, you must  make one small change:  edit header file
custom.h and change the prototype for void to int.

Lotus 1-2-3

To install Lotus 1-2-3, do the following:

1. Install Lotus  by hand with tar  (not with custom), as  described in the
   Lotus documentation.

2. Before you run the command setup123, type the following command:

        echo -n ' 33[?8l'

   The first command set erase mode on the console.

The sample  files as stored in  /u/lotus/123.v11/smpfiles/misc will fail if
the  current working  directory is  not  /u/lotus/123.v11/smpfiles/misc. To
enter this directory from within Lotus, use the following command:

     /WGDD/u/lotus/123.v11/smpfiles/misc

As  of this  writing, graphs  did not  work because  of limitations  of the
COHERENT console driver.  We are working to correct this problem.

mc -- MacroCALC

MacroCALC installs  and runs correctly  under COHERENT 4.0  and 4.2.  Users
should have  no problems  installing this  package.  If you  are installing
MacroCALC  onto COHERENT  4.2,  do not  copy  onto your  system the  ansipc
termcap entry  that comes with the package: the  one included with COHERENT
4.2 already works correctly

RMCobol

RMCobol works  out of the  box, without modification.  You  may notice some
slight discrepancies with  regard to colors and the number  of lines on the
screen,  which  are  easily corrected  by  resetting  the COHERENT  console
device.

SlickEdit

This editor  works properly.  However,  it comes with  an internal language
that it  uses for enhanced editing, macros, etc.,  that requires a compiler
named st. This compiler  is on the SlickEdit's distribution disks; however,
it  is in  Microsoft a.out  binary format, which  cannot be  executed under
COHERENT.

SlickEdit works  best with a customized  terminal-information file that has
been prepared by Mark Williams Company.  To obtain a copy, contact the Mark
Williams BBS as described earlier in these notes.

TERM Communications Package

Because the  distribution disks are  not high density, you  must use device
/dev/fqaX (where X is 0 or 1) to load the distribution.

When you execute the install script after you have loaded the distribution,
you must to choose the first option in the index:

     UNIX System V/386 (Including Altos, AT&T and Interactive)

Once installed, our tests show that the package works well.

WordPerfect and WordPerfect Office

Before you  can print anything on  your COHERENT system, you  must start up
and configure the MLP print spooler.  Do this before you attempt to install
WordPerfect.  For details on MLP, see the Lexicon entry for printer.

When you load the initial boot disk, if you choose to un-tar the disk using
the device /dev/fva0, tar complains:

     This doesn't look like a tar archive.
     Skipping to next file...


This   behavior  also   occurs  with   devices   /dev/fva0,  /dev/dsk/f03h,
/dev/dsk/f0q18dt, and  /dev/fd0135ds18. Note that this  does not affect the
installation: it is just a curiosity.

When  you   perform  the  actual   installation,  in  some   instances  the
installation program exhibits strange behavior.  It will say:

     *Please Wait*    0% complete

It  then prints what  appears to  be a  process id on  top of  the fragment
*Plea, moves the cursor down another line, and prints:

     *Please Wait*   1% complete

The  1% stage  continues  for a  lengthy  period of  time; the  floppy-disk
drive's light glows, to show that the disk is being read, but otherwise the
installation program  displays nothing to indicate  that useful activity is
occurring.  Do not panic: the installation program is working; it simply is
not updating the screen properly.

If your console is monochrome, insert the command

     export WPTERM51=scocons

into file /etc/profile. If you console is color, insert the command:

     export WPTERM51=scoconscol

WordPerfect expects  this variable to  be set before it  can run correctly.
Note that  after you insert  it, you must  log out and log  in again before
that variable can become part of your environment.

If you  wish to run either  package under X Windows,  use the terminal type
VT102 and insert the following instructions into the file $HOME/.Xdefaults:

     xterm*VT102.Translations: #override \
          <Key> F1 : string(0x1b) string("OP") \n \
          <Key> F2 : string(0x1b) string("OQ") \n \
          <Key> F3 : string(0x1b) string("OR") \n


Some systems have experienced  problems with printing under the lp spooler,
when logged  in as anyone other  than the superuser.  This  should not be a
problem, but  if it is, try switching the  WordPerfect spooler command from
lp to  hpr -B or  lpr -B, respectively,  depending upon whether  you have a
laser  printer  or  a dot-matrix  printer.   If  all  else  fails, try  the
following workaround:


1. Set WordPerfect's spool command to:

        cat -u > /tmp/PRINT.ME


   When   WordPerfect  prints,   it  will   dump   its  output   into  file
   /tmp/PRINT.ME, instead of sending it directly to the spooler.

2. To print WordPerfect's output, open another virtual console and type the
   command:

        cat /tmp/PRINT.ME > /dev/lp

   With  WordPerfect  Office,  you  cannot  receive  mail from  within  the
   application because it expects either  SCO's MMDF, or a version of smail
   that COHERENT does not yet support.
