gregg@a.cs.okstate.edu@mandrill.CWRU.Edu (Gregg Wonderly) (10/13/87)
There are 13 parts to the distribution of VI written in TPU. The first, this file, is a plain text file. The remainder, are DCL command files. Files 2-13 should each be executed as DCL procedures in sequence. Below is a sequence of steps that should allow you to get VI up and running. 1) You should pick a directory to place VI under, and place all 13 files in that directory. Then, you can begin extracting. Three directories will be created, [.SRC], [.EXE], and [.DOC]. The directory names should reveal the purposes of these directories. 2) Place all 13 of the VI parts into the directory chosen in step 1. For each part, 2 through 13, execute the file as a command procedure using the command "@<filename>", where <filename> is the name of the file to execute (e.g. @VI_2.COM, followed by @VI_3.COM, etc). 3) After executing the 13th command file, you should set default to the [.SRC] directory, and use the commands "$ @make exe", and "$ @make tpusubs" to create the VI.EXE executable, and the CALL_USER routines for VI to use. 4) Next, set default to [-.DOC] (from the SRC directory), and execute the command "$ VIDOC", and "$ @VIDOC HELP" to create a printable version of the current documentation, as well as a HELP file that VI can use. When asked the question: Name of library to install HELP files in? you should probably answer with the full path to the current directory. VI.TPU contains the path VI$ROOT:[DOC]VI.HLB as the place where it will work from, so if you do not place the help file in this library (It will automatically be created for you), then you must edit VI.TPU to contain the proper path. 5) Here you have a decision to make. I have written a interface to callable TPU, [-.SRC]VI.MAR. If you wish to use this interface, then there must be a CLD definition for it installed in DCLTABLES. This is really only necessary for using VI as a SUB-process, but I find it conveinent to install the CLD so that I do not have to wait for SET COMMAND to complete when I log in. If do not wish to use the callable TPU interface then go to the next step NOW, otherwise hang tight. The CLD definition that needs to be installed is in [-.EXE]VI.CLD. If you do not have sufficient privileges to install a new DCLTABLES you should get prepared to do so, or find someone that will do it for you (now is not entirely necessary, as you can skip to step 6, and do this later). a) Take the time to examine the CLD, and make sure it is ok for your installation. If you are on a cluster, then there is some extra work that I won't describe here since I have never done it. Basically you need to do the following set of commands. (the dollar signs are provide by DCL in case it wasn't obvious). $ SET COMMAND [-.EXE]VI.CLD/TABLE=SYS$SHARE:DCLTABLES.EXE/OUT=- _$ SYS$SHARE:DCLTABLES.EXE $ MCR INSTALL INSTALL>SYS$SHARE:DCLTABLES/REPLACE INSTALL>EXIT b) This should be all that single CPU sites need to do. If you have a different arrangement at your sight that requires something different, then you would know that better than I. Remeber that you MUST logout and log back in to have the updated DCLTABLES available to your process. Step 8, below, can not be done unless you either 1) do not do (c) below, or 2) you logout and log back in after reinstalling DCLTABLES. c) [-.EXE]VI.COM, and [-.EXE]VISETUP.COM contain uses of the symbol, "VI". This symbol is normally equated to "EDIT/TPU". Once you have made the changes necessary to update DCLTABLES, then these references should be changed. In [-.EXE]VI.COM, change VI to be "VI", instead of "EDIT/TPU". In [-.EXE]VISETUP.COM, delete the assignment to the variable VI, as the comment there says to. 6) Next, set default to [-.EXE] (from [.DOC]), and edit the file VISETUP.COM. This file must be executed by each user wishing to use VI before they can use it. You should change the definition of VI$ROOT to be the parent directory of the directory you are in NOW. E.g. if you are in the directory DUA0:[PUBLIC.VI.DOC], then VI$ROOT should be defined to be DUA0:[PUBLIC.VI.]. Note that this file potentially defines 3 symbols. VI allows normal use of VI, VIS allows use of the VI.COM procedure to run VI in a subprocess, and VIEW allows READONLY editing of a file (as in UNIX). 7) The command file VI.COM is used to envoke VI in a sub-process so that a minimal amount of overhead for image activation will be incurred by the system. In the VI.COM that you have, there are invocations of a SUSPEND, and a RESUME command. I use these commands to suspend kept editors while they are not it use so that they will be swapped out or trimmed by the SWAPPER in a more timely manner. This will allow their memory to be put to use by other processes whenever possible. If you do not wish to do this and/or do not have these facilities available to you, then you should comment out these command lines. 8) Next, you should be ready to give VI a trial run. Execute the VISETUP.COM procedure in [.EXE]. Then type VI, and hit return. You should be off and running.