From: Jim Gillis <[email-masked]>
Date: Thu, 13 Feb 92 12:58:28 PST

Gentle maybe-would-be user,

The following contains the Computer Aided Review System--CARS
  (version beta 1.2--a shar "shell archive" format).
In case of trouble, refer to the README file (below), or contact one
  of us (Jim Gillis or Adam Shwartz, addresses below).

INSTALLATION  REQUIREMENTS*:

awk         -- pattern matching language
compress    -- file compression utility
csh         -- c-shell, currently most scripts are csh scripts.
latex       -- variant of tex used for documentation
sed         -- stream editor
sh          -- the bourne shell ...
tex         -- text processing language
uudecode    -- decryption of binary files made by uuencode
uncompress  -- file compression utility

* NOTE: you cannot install** CARS if one of the above programs is not available.
*       you cannot install** CARS if the name of one of the above was changed in
        your system; you will need to alias the command to the standard name.
  One way to check that a program, say awk, is available is by typing
        which awk
  or
        path awk
  If the program is available, the response will be its location.
  Otherwise, the response will be something like
        no hunt in . ./bin /paw/adam .... etc
  Don't give up - consult your local guru!

1)
 Create directory in which you wish to put the CARS system (e.g 
  "csh> mkdir IEEE" ). Then change to that directory (e.g. "csh> cd IEEE").

2)
 Copy the CARS.mail to the directory in which you wish to install the system
 and rename it CARS.shar (e.g. "csh> cp CARS.mail IEEE/CARS.shar").

3)
 Make the file CARS.shar executable (i.e. issue the command 
  "csh> chmod u+x CARS.shar"). 

 Cut the top off the file CARS.shar -- that is remove lines 1, through the
 line with "+++" across it (inclusive).  The first line of the new file 
 should be  "#! /bin/sh " -- since you did a cp these directions are 
 still in the top of the file CARS.mail.  It is fine to print the
 top of CARS.mail; however you must trim the bottom off before printing
 as it is a large encoded file.  The top of this file (CARS.mail) is 
 these instructions, the bottom is a shar format file containing the 
 CARS system.

4)
 Then execute it (by giving the command  "csh> CARS.shar"). 
     This will unpack the README file, the makefile and
     some encoded files for the system.
     These installation instructions are now available in the file MailMsg.

5) 
 Print the README file (it is a standard text file) for further instructions.

6)
 Now follow the rest of the installation notes (as given in the README file).

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#! /bin/sh
# This is a shell archive, meaning:
# 1. Remove everything above the #! /bin/sh line.
# 2. Save the resulting text in a file.
# 3. Execute the file with /bin/sh (not csh) to create the files:
#	README
#	Makefile
#	QuikRef
#	ieeerc
#	MailMsg
#	CARS.tar.Z.uu
# This archive created: Thu Feb 13 12:57:54 1992
export PATH; PATH=/bin:$PATH
if test -f 'README'
then
	echo shar: will not over-write existing file "'README'"
else
cat << \SHAR_EOF > 'README'
README for CARS   

VERSION:
beta  1.2 --- August 12, 1991

MISSION: 

This file contains the installation notes for the CARS system.  
The CARS system was developed at the Systems Research Center,
at the University of Maryland in 1990--1991.  The system is 
designed to help an IEEE Transactions on Automatic Control
Associate Editor keep track of papers and reviews for the TAC.
It is easily modified to accomodate other IEEE Transactions.

SYSTEM REQUIREMENTS*:

awk         -- pattern matching language       
compress    -- file compression utility 
csh         -- c-shell, currently most scripts are csh scripts.
latex       -- variant of tex used for documentation  
sed         -- stream editor 
sh          -- the bourne shell ... 
shar**      -- shell archiver 
tex         -- text processing language 
uudecode    -- decryption of binary files made by uuencode 
uncompress  -- file compression utility 
uuencode**  -- encryption of binary files into ASCII

* NOTE: you cannot install** CARS if one of the above programs is not available.
        you cannot install** CARS if the name of one of the above was changed in
        your system; you will need to alias the command to the standard name.
  One way to check that a program, say awk, is available is by typing
        which awk
  or
        path awk
  If the program is available, the response will be its location.
  Otherwise, the response will be something like
        no hunt in . ./bin /paw/adam .... etc
  but don't give up---consult your local guru!

**The programs  shar  and uuencode are needed ONLY if you want to make a
  distribution file (the type you received) to be sent back to us.
 
INSTALLATION NOTES:

The system is distributed as a "shar" file (you know this
or you wouldn't be reading this file!). 

The steps in installation are given below:  "csh>" represents the computer
    prompt, and what follows - the commands you should give.

1) csh> CARS.shar   # YOU SHOULD HAVE ALREADY DONE THIS - NO NEED TO REPEAT.
   This command extract the basic files that are used in the installation.
   If you have not executed it yet:
   Usually one cuts the top off of CARS.mail and calls the resulting file 
   CARS.shar.  Then make the file CARS.shar executable using the command: 
	csh> chmod +x CARS.shar
   Then extract the shar format files by giving the command CARS.shar

2) Add the following line to your .cshrc file (in your root directory):
   source $home/.ieeerc
   (don't hesitate to ask a systems person about items 2 and 3
   if you are unsure of what they do -- you can even call us!)
   *******
   Make sure this line is added AFTER the definitions of "path" and
   "cdpath", if any.
   *******

3) Edit the file   ieeerc    in your this directory.
   When you are done, save the file as ~/.ieeerc.
   This puts the ieee definitions together, and places them
   in your home directory as an "invisible" file. 

   Here is an explanation of the commands in that file, and of the
   things you need to do yourself.

   A)
   Replace the string  "ieee"  in

   setenv ieee_path $home/ieee/

   with the name of the path of the installation,
   starting at your home directory.
   This is the path to the README file, to the various directories such as
   bin, papers, datafiles, doc and tmp.   The path SHOULD INCLUDE THE
   TERMINAL SLASH.  
   This way the variable "ieee_path" will be definded, for 
   use in the "set path" statment.  

   You can replace  $home/ieeepath/ with  /fullIeeePath/
   where "fullIeeeePath" is the full name of the path to the installation.
   You find this path by typing the command "pwd"  while in that directory.
   If you use the full path it should begin with a slash. You can usually
   use the "~" abbreviation.

   If you're running ULTIX and it complains (after step E below), try instead
   set ieee_path="$home/ieeepath/"  or
   set ieee_path="fullIeeePath/"
   and/or consult your local guru.
    
   B)
   Replace the string "edit" in

   setenv  EDITOR  "edit"
  
   with the name of your preferred editor, hopefully emacs, but vi and any
   other reasonable editor should work just as well.
   If this variable is not set then vi is used as a default.  
   If this variable is already set in  .cshrc, you may omit it from .ieeerc

   If you're running ULTIX, see last comment in A) above.
 
   C) 
   add ${ieee_path}papers to the cdpath by choosing the appropriate line:

   set    cdpath    	= ($cdpath ${ieee_path}papers ) 
   if  cdpath   was previously defined, or
   set    cdpath    	= (. ${ieee_path}papers ) 
   if it was not.
   
   (comment out the wrong line, by inserting a # at the beginning of the line).
   This will make it easier to change directory to the papers/ 
   directory -- it causes the papers directory to be searched
   as if its contents are in the current directory. 
   This is an optional modification.  For example, the command
   cd 90-001
   will put you at the directory papers/90-001, NO MATTER WHERE YOU ARE.
   This is useful for printing, as experience will show you.

   D)
   set    path		= ($path ${ieee_path}bin)

   This adds the path to the new /bin directory to the path variable list;
   this  will allow you to execute the CARS commands from anywhere.
 
   e)
   Now leave the editor and give the command "csh> source .cshrc"
   (from your home directory!).
   This will bring the changes into effect (if you are using a multi-window
   terminal you need to either do this in every window or exit and login anew).
   You may also need to use the command "csh> rehash" to get the 
   shell to recognize the path and new commands. 

4) csh> make
   This will construct the files, templates, etc.

5) Modify the file ${ieee_path}bin/LocalTeX to run and print TeX on 
   your system, starting at line 109.  At line 114 you can add your 
   favorite spell check program, the command for ispell is commented out. 
   As delivered this procedure runs TeX on the files in a "standard" way, 
   If the proceedure for running TeX is different at you site, you
   should modify it here.  The lines 118-122 are where the commands to 
   print the dvi files go, there are several examples in the comments. 

6) Modify the file ./bin/TeX/AEData.tex to reflect information
   about yourself (the Associate Editor). The maximum number of 
   characters is about 39 per line (we used numerals).  If you
   exceed this TeX will produce a black dot at the end of the line. 
   To overcome this you will need to hack with LetterForm.tex (carefully!)
   To modify the system for non-AC Transactions, edit the file
   ieeepath/bin/TeX/Defs.tex
   and change the definitions of CS and tac.

7) Return to the directory ${ieee_path} and give the command
   csh> make documentation    
   This command will LaTeX the users manual, and run example letters. 

   NOTE: 
   A)
   This installation procedure runs LaTeX on the users guide.
   LaTeX makes lots of warning messages, when it produces 
   the manual, most of these are warnings that can be ignored. 
   If there are errors, (you will see a ? from \TeX), then 
   there is a problem.
 
   B)
   The file UsersGuide.tex and the .dvi file are in the doc/
   directory.  The main file is UsersGuide.tex, it is a LaTeX 
   file.  There are several example letters in ./doc/Examples, 
   which are TeX, so they are processed separately and YOU have 
   to collate them. Sorry.

   The procedure is set up to be automatic and it uses temporary 
   versions of the major data structures -- if you interrupt it
   you may have to manually restore the ``papersDB'' and 
   ``reviewerDB'' files. Examine the procedure, to see
   what to do -- if you need help, see your system administrator! 
   The files are left as a ``.tar'' file in the ./papers directory.
   You can look at it or delete it as you please.  You can always 
   recreate the files using the procedure.  
  
8) Try the CARS system, get a pen and pick up the documentation, read it,
   correct it, send corrections to us! RTFM!! (Read The ?Fine? Manual) 
   Let us know what is good and 
   bad.  Please pay special attention to the TBD section.
   Please feel free to hack around and make this package better.
   You can remove the CARS.shar file, its just the distribution files.  
 
9) Please check the ./tmp directory to make sure we are deleting all 
    of the temporary files  -- if nothing is running this directory
    should be empty.  The way we have debugged is to keep the temporary
    files around, so we may not be deleting them as we should.  
    Don't let these files build up.

10) In the directory ${ieee_path}papers there is a directory called 89-test.
    This is directory used by the "Example" program in the directory 
    ${ieee_path}/doc/Examples.  It is there for you to examine and delete.
    It has no use beyond verifying that the system is installed correctly 
    and generating the example letters.    

11) We are:  
     Jim Gillis
     M4 / 971 
     The Aerospace Corp. 
     P. O. Box 92957    
     Los Angeles, CA 90009-2957 
     
     wk. (213) 336 8770         
     [email-masked]  
 and  
     Adam Shwartz   (really no c's!) 
     Electrical Engineering
     Technion---Israel Institute of Technology
     Haifa 32000, Israel
     
     [email-masked]

12) In order to preserve our rights, and until we figure out what to do--
    we shall reserve all our rights.  Please don't distribute without our 
    consent. This software is in beta test and is for your amusement. 
    We specifically disavow any responsibility of any kind to anyone 
    other than to our friends -- who will forgive us.

NEW STUFF  -- NOT OTHERWISE DOCUMENTED. 

    The file bin/fingerReviewer  allows for a "master reviewers database," 
    to be searched in additon to the usual file.  This is a file of reviewers 
    (i.e. the same format as the reviewers database), that is to be searched 
    in addition to the usual database.  At line 53 of "bin/fingerReviewer" the 
    second reviewer file is set.  This file can be anywhere, just adjust the 
    path appropoiately.  Currently, the logic looks for a nonexistant file 
    and proceeds on without the second file. 

    In the "bin/TeX" directory is the TeX file  SR.tex. 
    This file is a templates for reports on the papers which are sent to the 
    Transactions editor. Use it or not, it is the next 
    phase in our development.  Comments and suggestions are welcome. 

TO CREATE A DISTRIBUTION

1) Edit the file MailMsg, by adding a message about the distribution .
   Don't forget to tell us what you have changed! 
   If you would like us to have your papers and datafiles directories
   please add these to the list of directories in the Makefile.
   PLEASE TELL US THAT YOU HAVE DONE SO.  IF THE EXAMPLES ARE
   REAL PAPERS CALL US FIRST.  ACTUAL DATA MUST BE ENCRYPTED,
   RATHER THAN ENCODED. THIS IS TO PROTECT THE REVIEW PROCESS. 
   THIS POINT IS REALLY IMPORTANT.

2) Move CARS.shar to CARS.shar_old (to preserve the last version).
   Move CARS.dist to CARS.dist_old (to preserve the last version). 

3) Type:

    csh> make redistribution
   
   and the make file will package the system up into CARS.shar
   and CARS.dist.  The redistribution command picks up all of 
   your changes and your data files. If you use the command 
   "make distribution" your data files will not be transported.
   This will make a much smaller distribution; however if you 
   are reporting problems, we won't have any of your data.   
   See 1). 

4) Get the program to us!!  

   csh> mail [email-masked] < CARS.dist 

  or use US Mail (smail? :-} ), We can read DOS 3.5in Floppy disks.  

jg & as 
SHAR_EOF
fi # end of overwriting check
if test -f 'Makefile'
then
	echo shar: will not over-write existing file "'Makefile'"
else
cat << \SHAR_EOF > 'Makefile'
#     This is the make file for CARS --
#           Computer Automated Review System
#     The system was conceived and initially developed at the 
#     University of Maryland's System Research Center 
#     in Academic Year 1990- 1991.   
#     The initial design is due to Adam Shwartz and Andre' Tits
#     The initial programing and documentation was done by Jim Gillis.   
#     Eyad Abed, Bill Levine made substantial contributions from
#     The users point of view.  We thank them. 
#     Please see the Readme file for more information.  
#     The documentation, which is in LaTeX also explains the
#     goals and usage of the system.
#
#
# .IGNORE: 
.SILENT:  
#
#
pkgNme      = CARS#   
#
#   traling blanks are a no-no here ... 
#
usersGuideDir    = doc/#
#
#  distribution and unpack definitions 
#   traling blanks are a no-no here ... 
#
distTar     = ${pkgNme}.tar#    
distTarZ    = ${distTar}.Z#   
distTarZuu  = ${distTarZ}.uu#   
distShar    = ${pkgNme}.shar#         
distMail    = ${pkgNme}.mail#
#
#  
mailNotes = MailMsg     
files = README Makefile QuikRef ieeerc  ${mailNotes} 
#                     files for distribution in the top directory .. 
#
dirs  = bin doc tmp
#                    papers datafiles -- may already exist 
#                                        so we don't want to 
#                                        destroy them 
redirs  = bin doc tmp papers datafiles 
#                    papers datafiles -- we want to ship these  
#					in a redistribution.  
# 
#  Basic installation target 
#   -- unpack the distribution tape 
#
install:  
	echo ' ' 
	echo 'Unpacking the ${pkgNme} system. '
	echo '    -- after verification you can delete ${distShar}.'
	echo ' '  
	chmod o+rwx . ; uudecode ${distTarZuu} ; chmod o-rwx . ; 
	uncompress ${distTarZ} 
	tar -xof ${distTar}  
	/bin/rm -f ${distTar}
	/bin/rm -f ${distTarZ}
	/bin/rm -f ${distTarZuu}
	find . -name "*" -exec chmod go-rwx \{\} \;  
#
#          create the papers and datafiles directories if need be ..
#             they are readable only by the owner as a default.
#
	chmod +x ./bin/make_dirs 
	./bin/make_dirs `pwd` 
#
#         edit the file ../bin/TeX/Defs.tex to have the 
#           correct path for TeX      
#
	chmod +x ./bin/edit_DefsTeX  
	./bin/edit_DefsTeX `pwd`
#
#
documentation:  
	cd ${usersGuideDir}; make usersGuide 
#
#
#  create the distribution tape 
#
distribution:
	echo ' ' 
	echo ' The CAR distribution file -- ${distShar} & ${distMail} '
	echo ' ' 
	/bin/rm -f ${distShar} 
	/bin/rm -f tmp/*                 # housekeeping ... 
	/bin/rm -f doc/*.aux
	/bin/rm -f doc/*.dvi
	/bin/rm -f doc/*.log
	/bin/rm -f doc/*~
	/bin/rm -f doc/*.bak
	/bin/rm -f bin/*~
	/bin/rm -f bin/*.bak 
	tar -cf -  ${dirs} | compress  > ${distTarZ} 
	uuencode  ${distTarZ} ${distTarZ}  > ${distTarZuu} 
	shar ${files} ${distTarZuu} > ${distShar}    
	chmod +x ${distShar}
	cat ${mailNotes} ${distShar} > ${distMail}
	/bin/rm -f ${distTarZ} 
	/bin/rm -f ${distTarZuu} 
#
#
#  create a re-distribution tape 
#   You can use this to move you file from one spot to another
#   and transmit problems to jim or adam ... 
#   It is just like a distribution except that it also collects 
#   the papers and datafiles directories in the distribution.  
#
redistribution:
	echo ' ' 
	echo ' A CAR's re-distribution file -- ${distShar} & ${distMail} '
	echo ' ' 
	/bin/rm -f ${distShar} 
	/bin/rm -f tmp/*                 # housekeeping ... 
	/bin/rm -f doc/*.aux
	/bin/rm -f doc/*.dvi
	/bin/rm -f doc/*.log
	/bin/rm -f doc/*~
	/bin/rm -f doc/*.bak
	/bin/rm -f bin/*~
	/bin/rm -f bin/*.bak 
	tar -cf -  ${redirs} | compress  > ${distTarZ} 
	uuencode  ${distTarZ} ${distTarZ}  > ${distTarZuu} 
	shar ${files} ${distTarZuu} > ${distShar}    
	chmod +x ${distShar}
	cat ${mailNotes} ${distShar} > ${distMail}
	/bin/rm -f ${distTarZ} 
	/bin/rm -f ${distTarZuu} 
#
SHAR_EOF
fi # end of overwriting check
if test -f 'QuikRef'
then
	echo shar: will not over-write existing file "'QuikRef'"
else
cat << \SHAR_EOF > 'QuikRef'
Quick Reference Guide: CARS version  beta  1.2.

The programs are available in interactive mode only.
That is - give the command and wait for questions.

All programs are case-sensitive; search patterns depend on case of letters.
Be consistent!

The programs can be executed from any directory, and will leave you in the
directory you started in.

No-no's:  do not tamper with the structure of the data files.  In particular,
do not break long lines!

Commands:

newPaper: enters information about a new paper into papersDB.
Creates a directory whose name is the paper number, and a file PaperData.tex
in that directory, with information about the paper.

newReviewer: enters information about a reviewer into reviewerDB.
Can be used to enter information about other people-is not connected to
a paper.

writeLetter: write a letter, usually associated with a paper. 
Can only be used after newPaper created an entry about that paper. 
Program will ask for the name of the reviewer. Creates a TeX file 
called Name-xx.tex if the given name is Name (see below for file 
extension definitions). Pulls the address of the reviewer from 
reviewerDB, unless you use the option to enter a new reviewer, 
See the manual to see how to write a misc. letter.              

xx = rr (review request), r1 (reminder), d (delay), t (thanks), 
     rcdc (review CDC paper), racc (Review ACC paper), 2p, 2c, 3p, 3c,
     (various decision letters). 

fingerReviewer: looks for a person in the reviewerDB file and extracts
by keywords.  This program is a preliminary version.
A database containing useful addresses is being assembled.
The search tries to match a complete string.  All hits are displayed.

fingerPaper: looks for a paper in the papersDB file and extracts
by keywords.  This program is a preliminary version.
The search tries to match a complete string.  All hits are displayed.

LocalTeX: edit this file to define the defaults; should every file you
edit be TeX'ed, TeX'ed and printed, etc.

To change the texts of letters, edit the file bin/TeX/Texts.tex

For complaints:
     Jim Gillis
     Systems Research Center
     A. V. Williams Bld.
     University of Maryland
     College park, MD. 20742

     wk. (301) 405 7062
     wk. (213) 336 5358         (after sept. 91)
     [email-masked]
     [email-masked]  (after sept. 91)
 and
     Adam Shwartz   (really no c's!)
     Systems Research Center
     A. V. Williams bld.
     University of Maryland
     College Park, MD. 20742

     [email-masked] 

Note: the next distribution will overwrite every file, EXCEPT the
data files and sub-directories of papers/
Thus, if you make changes, save them before installing the next distribution.

Command line options

  newPaper 
        -ne                     =   Don't invoke the editor.
        -p string               =   Here "string" is the paper number. 
        -recvd mm/dd/yy         =   The date the paper was received. 
        -promised mm/dd/yy      =   The date the paper was received. 
        -aeal string            =   Here "string" is the associate editor at large.
        -title file             =   Here "file" is a file  containing the paper title.
        -authors file           =   Here "file" is a file containing the authors,
                                      one per line.  
        -mail2 "string"        =   The corresponding author.
        -rem file              =   Here "file" is a file containing remarks 
                                     about the paper.
 newReviewer
        -ne                    = Don't invoke the editor.
        -sal "string"          = Here string is the salutation used for the reviewer,
                                     things like Dr., Professor, Mr., Ms., etc. 
        -fn "string"           = Here "string" is the first name and middle initial
                                     of the reviewer. 
        -ln "string"           = Here "string" is the last name of the reviewer. 
        -t "string"            = Here "string" is the title of the reviewer,
                                      for things like FRS, etc. 
        -wa file               = Here file contains the work address of the 
                                      reviewer. 
        -ha file               = Here file contains the home address of the 
                                reviewer. 
        -dp "string"           = Here "string" is the daytime phone of the reviewer. 
        -np "string"           = Here "string" is the night-time phone of the
                                      reviewer. 
        -fax  "string"         = Here "string" is the fax number for the reviewer. 
        -email "string"        = Here "string" contains the electronic mail 
                                      address of the reviewer. 
        -rem "string"          = Here "string" contains a remark about the reviewer.  

 writeLetter
        -ne                    = Don't invoke the editor.
        -t "string"            = Here "string" is the type of letter being requested. 
        -r "string"            = Here "string" is a search string used to identify 
                                    the reviewer.  
        -p "string"            = Here "string" is a search string used to identify 
                                    the paper.  
        -dvi [yn]              = This is a flag passed as the -d option to LocalTeX
                                   the values are 'y' or 'n' 
                                   (y= print, n = no print).
        -d mm/dd/yy            =   The date the revised paper is due. 
 
 fingerReviewer 
        "string"
  <or>  -s "string"            = "string" is a search string,  
                                   records are searched using the pattern:
                                        /string/ 
                                   each record is treated like one line, allowing
                                   complicated searches for reviewers. 
        -f file               =  the output is written to a file (default is stdout)
 
 fingerPaper 
        "string"
  <or>  -s "string"         = "string" is a search string,  
                               records are searched using the patterns:
                               /^%[Aa]*string*/ /^%[Tt]*string*/ /^[Pp]*string*/
                               /^string/ 
        -f file             =  the output is written to a file (default is stdout)
SHAR_EOF
fi # end of overwriting check
if test -f 'ieeerc'
then
	echo shar: will not over-write existing file "'ieeerc'"
else
cat << \SHAR_EOF > 'ieeerc'
#
setenv ieee_path 	$home/ieee/  # put the correct path here 
#
#  Pick on of the next to lines, and uncomment it.  
#
# set    cdpath    	= ($cdpath ${ieee_path}papers ) 
# set    cdpath    	= (. ${ieee_path}papers ) 
#
set    path		= ($path ${ieee_path}bin)
#
setenv EDITOR 		"vi"         # put you favorite editor here ...  
SHAR_EOF
chmod +x 'ieeerc'
fi # end of overwriting check
if test -f 'MailMsg'
then
	echo shar: will not over-write existing file "'MailMsg'"
else
cat << \SHAR_EOF > 'MailMsg'

Gentle maybe-would-be user,

The following contains the Computer Aided Review System--CARS
  (version beta 1.2--a shar "shell archive" format).
In case of trouble, refer to the README file (below), or contact one
  of us (Jim Gillis or Adam Shwartz, addresses below).

INSTALLATION  REQUIREMENTS*:

awk         -- pattern matching language
compress    -- file compression utility
csh         -- c-shell, currently most scripts are csh scripts.
latex       -- variant of tex used for documentation
sed         -- stream editor
sh          -- the bourne shell ...
tex         -- text processing language
uudecode    -- decryption of binary files made by uuencode
uncompress  -- file compression utility

* NOTE: you cannot install** CARS if one of the above programs is not available.
*       you cannot install** CARS if the name of one of the above was changed in
        your system; you will need to alias the command to the standard name.
  One way to check that a program, say awk, is available is by typing
        which awk
  or
        path awk
  If the program is available, the response will be its location.
  Otherwise, the response will be something like
        no hunt in . ./bin /paw/adam .... etc
  Don't give up - consult your local guru!

1)
 Create directory in which you wish to put the CARS system (e.g 
  "csh> mkdir IEEE" ). Then change to that directory (e.g. "csh> cd IEEE").

2)
 Copy the CARS.mail to the directory in which you wish to install the system
 and rename it CARS.shar (e.g. "csh> cp CARS.mail IEEE/CARS.shar").

3)
 Make the file CARS.shar executable (i.e. issue the command 
  "csh> chmod u+x CARS.shar"). 

 Cut the top off the file CARS.shar -- that is remove lines 1, through the
 line with "+++" across it (inclusive).  The first line of the new file 
 should be  "#! /bin/sh " -- since you did a cp these directions are 
 still in the top of the file CARS.mail.  It is fine to print the
 top of CARS.mail; however you must trim the bottom off before printing
 as it is a large encoded file.  The top of this file (CARS.mail) is 
 these instructions, the bottom is a shar format file containing the 
 CARS system.

4)
 Then execute it (by giving the command  "csh> CARS.shar"). 
     This will unpack the README file, the makefile and
     some encoded files for the system.
     These installation instructions are now available in the file MailMsg.

5) 
 Print the README file (it is a standard text file) for further instructions.

6)
 Now follow the rest of the installation notes (as given in the README file).

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SHAR_EOF
fi # end of overwriting check
if test -f 'CARS.tar.Z.uu'
then
	echo shar: will not over-write existing file "'CARS.tar.Z.uu'"
else
cat << \SHAR_EOF > 'CARS.tar.Z.uu'
SHAR_EOF
fi # end of overwriting check
#	End of shell archive
exit 0