\documentstyle[a4,12pt]{article}
\begin{document}
\author{APM Manual pages}
\title{SETUP}
\maketitle
\parskip .1 in
\setcounter{secnumdepth}{10}
\parindent 0in
\section{Preamble}
The SETUP command has been provided (as on Vax) to make available packages.

Example: \hspace{ 0.7 in} setup edwin

In fact, the command SETUP $<$X$>$ transfers control to command file $<$X$>$:SETUP.COM.

\section{Available SETUPs}
The following is a list of packages which may be made available in this way.

\small\tt \begin{verbatim}EDWIN   :  Edinburgh Graphics library
ESDL    :  Edinburgh Circuit Design package
GKS     :
ILAP    :
IPLOG   :
OFFICE  :  Electronic Office utilities
USEFUL  :  Utilities provided by CS4 for general use. See HELP USEFUL
VLSI    :
\end{verbatim}\rm  \normalsize 
There are others and any user may make a SETUP file simply editing up SETUP.COM.


\section{Important Note}
On the current 1-process operating system SETUP $<$X$>$ is implemented by
switching input to a command file $<$X$>$:SETUP.COM. This means that SETUPs buried
in command files will cause control to be switched out from the command file -
it may not be switched back. Command files may therefore only contain one SETUP
command which should be the last command in the file.

\vspace{.75in} view:setup printed on 16/02/89 at 16.08

\newpage
\tableofcontents
\end{document}