VTECO is distributed as sources on DOS format magtape. To install it on a new system, first log in to a privileged account. On VAX/VMS systems, log in with CLI=MCR. To load the tape onto your disk, enter: .lit &>FLX SY:=MM:[*,*]*.* .eli .nt It is important that the VTECO distribution be loaded into an otherwise empty diectory. Because the command file performs substantial clean-up operations, user files other than those included in the distribution may be lost. .en Once the tape is loaded, VTECO is built and installed on the target system with the command: .lit &>@VTEC .eli The command file asks several questions while generating VTECO. These questions deal with the configuration on which it will be built and run. Following is all the questions asked by the command files and explanations of them. .ls .tp 3 .le;Are you installing VTEC on a VAX-11 [Y/N]? .s This question is asked to determine how to proceed with the generation. Many of the later commands issued by the generation command file require knowledge of whether the host operating system is VMS or RSX. .tp 3 .le;Does your system include the SOB instruction [Y/N]? .s Asked only on RSX-11M systems, this question affects the conditional assembly of VTECO. Many of the modules use the hardware SOB instruction if it is available to increase efficiency of the code. This instruction is available on all machines except the PDP-11/04, /05, /10, /15, and /20. .tp 3 .le;Does your system include hardware multiply (EIS) support [Y/N]? .s Asked only on RSX-11M systems, this question affects the conditional assembly of VTECO. Some of the modules use hardware multiply if it is available to increase the efficiency of the code. Hardware multiply is an option on most PDP-11 processors. .tp 3 .le;Do you want the multi-user version of VTECO [Y/N]? .s Asked only on RSX-11M systems, this question causes VTECO to be configured as a multi-user program. As a multi-user program, TECO's pure code resides in a dynamic common area, and each user's program contains only his data and impure code. .tp 3 .le;Delete temporary files after use [Y/N]? .s The sophisticated user may want to modify the VTECO package, or rebuild it at a future date without respecifying all the parameters of the build file. Answering this question in the affirmative allows him/her to do this by preserving the temporary command, prefix, and library files which are otherwise automatically deleted as part of the VTECO build procedure. .tp 3 .le;Assembly listing files desired [Y/N]? .s Part of the VTECO build procedure consists of assembling the various modules which comprise the editor. This question determines whether or not listings will be generated by the assembler. .tp 3 .le;What is to be the listing device? [DDU] [S] .s If the answer to the previous question was affirmative, this question is asked. The proper response to this question is the name of the device where assembly listings are to be sent. Appropriate answers may be: "TI:", "SY:", "DK1", etc. A null answer to this question defaults the answer to "SY:". Note that for output to be printed via the print spooler, the appropriate response is "SY:", ^¬\& "LP:" .tp 3 .le;Spool listing files [Y/N]? .s If the assembly listing files are to be printed on the line printer, and the host system includes a print spooler, this question should invoke a positive response. Note that to use this option, the answer to the previous question should have been the name of a valid mass storage device, such as "SY". .tp 3 .le;Do you need narrow (80 column) output [Y/N]? .s This question, when answered in the affirmative, causes the assembler to output its listings in 80 column, rather than 132 column, format. This is useful when printing on terminals and printers which only support 80 columns of printout. .tp 3 .le;Does your system include a resident FCS library [Y/N]? .s Some memory savings (about 2 KW per copy) may be achieved through the use of a resident library. If the host system includes such a library, answer "YES" to this question. .tp 3 .le;What is the name of the resident library? [S] .s This question is asked only if a positive response was given to the previous question. The appropriate response is the name (6 characters or less) of the resident FCS library on the host system. .tp 3 .le;Is it a memory resident overlayed library [Y/N]? .s This question is asked only on RSX-11M systems where an FCS resident library is specified and multi-user support is requested. The build procedure generates the smallest possible copy of VTECO, and this question helps insure that the build is performed correctly. .tp 3 .le;Is it a supervisor mode library [Y/N]? .s This question is asked only on RSX-11M PLUS systems, and selects the proper overlay structure and taskbuild command file to generate a version of VTECO which uses the FCS supervisor mode library. .tp 3 .le;Task builder map desired [Y/N]? .s The answer to this question determines whether or not a memory map will be generated by the task builder. Since diagnosing failures requires the use of this map, it is useful to answer "YES" here. .tp 3 .le;What is to be the map device [DDU] [S] .s Like the similar question regarding assembly listings above, this question determines the device on which the map will be output. Appropriate answers may be: "TI:", "SY:", "DK1", etc. A null answer to this question defaults the answer to "SY:". Note that for output to be printed via the print spooler, the appropriate response is "SY:", ^¬\& "LP:" .tp 3 .le;Spool map file [Y/N]? .s If the map file is to be printed on the line printer, and the host system includes a print spooler, this question should invoke a positive response. Note that to use this option, the answer to the previous question should have been the name of a valid mass storage device, such as "SY". .tp 3 .le;Do you need narrow (80 column) output [Y/N]? .s This question is asked only if assembly listing files were not requested and a map file is required. If assembly listing files were requested, the answer to this question is taken to be the same as that given in the corresponding question above. This question, when answered in the affirmative, causes the assembler to output its listings in 80 column, rather than 132 column, format. This is useful when printing on terminals and printers which only support 80 columns of printout. .le;DCL EDIT command rather than traditional TECO commands [Y/N]? .s The VTECO distribution allows VTECO to be installed with the taskname "...EDI", allowing it to be called with the EDIT command. The remainder of the command is parsed by VTECO, and any editor specified via a qualifier is spawned from there. This feature is only available under RSX-11M V3.2 or later. .nt In order to use the "EDIT/EDI" command, the DEC EDI editor must be reinstalled using the task name "...EDL". The installation procedure does &n&o&t do this automatically. .en .tp 3 .le;Do you want to install TECO's library macros [Y/N]? .s This question must be answered "Y" on the first installation of VTECO on a new system. The library macros which are installed give VTECO its operational characteristics. On a subsequent installation (for instance if VTECO is rebuilt for a new library) the macros need not be reinstalled. .els The installation procedure leaves VTECO installed on RSX-11M systems, and "installed" for MCR users on VAX/VMS systems. To make the installation permanent on RSX-11M systems, VTECO should be installed with VMR. To do this, the following commands should be issued: .tp 8 .lit &>SET /UIC=[1,54] &>RUN VMR ^&ENTER FILENAME:\&RSX11M ^&VMR>\&@[uic]TECINS ^&VMR>\&_^Z &> .eli where [uic] is the directory under which the sources were loaded onto the disk. To make VTEC easily available to DCL users under VAX/VMS, the following global definitions should be included in the system login command file: .tp 6 .lit &$ TEC :== MCR TEC &$ MAK :== MCR MAK &$ MUN :== MCR MUN &$ OLD :== MCR OLD &$ NEW :== MCR NEW .eli Note that the "EDI" form of TECO commands may also be made available under VAX/VMS, but this is not recommended due to conflicts with the existing EDIT command.