\documentstyle{article}
% Local definitions
% -----------------

\def\itemitemb{\itemitem{$\bullet$}}                  % Bulleted subitem
\def\newline{\hfil\break}                             % Force new line

%----- Display example text (#1) in typewriter font

\def\example#1{\nobreak\smallskip\hbox{\hbox to 1.in{ \hfil}{\tt #1}\hfil}
               \nobreak\smallskip\noindent\ignorespaces}

%----- Enclose text (#2) in ruled box of given thickness (#1)

\def\boxit#1#2{\vbox{\hrule height #1pt\hbox{\vrule width #1pt\hskip 5pt
                   \vbox{\vskip 5pt #2 \vskip 5pt}\hskip 5pt
                   \vrule width #1pt}\hrule height #1pt}}

%----- Display boxed warning text (#1)

\def\warning#1{\bigskip
               \setbox1=\vbox{\tolerance=5000\parfillskip=0pt
               \hsize=3in\noindent#1}
               \centerline{\boxit{1.0}{\box1}}
               \bigskip}

\def\spot{\newline\ \ $\bullet$\ \ }

% Source text
% -----------
\begin{document}
\begin{center}

{\Large {\bf Isaac Newton Telescope}}
\vskip 0.5in
{\large {\bf ``USER BEWARE'' LIST}}
\vskip 0.5in
\warning{ALWAYS READ LIST BEFORE STARTING UP}
\bigskip
{\bf Last update on:} \today
\bigskip\bigskip
\end{center}

\parindent 0pt
\parskip 0.2cm
\newpage
This section documents known faults that can occur, and for which at the
moment no permanent cure is made.

\begin{itemize}
\item Pointing Problems:

{\bf Symptoms:} 
Bad pointing, even after a repeated SNAFU procedure.

{\bf Diagnosis:}
Most likely cause a fault on one of the Ferranti encoders. In order to check
this run the task ENCODER from the Telescope Control System VDU by typing:

%\INPSCF{ENCODERS}
$*${\tt ENCODERS}

This will produce a status report on the three Ferranti encoders. If one of them
ia baulking, it will show up in the form of deviant encoder readings.

{\bf Remedie}
Disable the faulty encoder by setting its weight to zero. Refer to section
11.1.6 for full details.

\item Error Messages after CCD exposure

{\bf Symptoms:} one or more of the following messages appear:

OBSNPACK: BDP error: Specified version different from actual version \\
AGBXPACK: BDP error: F (Error code not found on file SYS:bdp.err/G)  \\
SPECPACK: BDP error: F (Error code not found on file SYS:bdp.err/G)  \\
Error writing archive packets to disc

{\bf Possible Solution:}
Look to see if files PKTTYPES.DAT and PKTTYPES.BCK exist on account 180.
If not, ask the Duty Technician to restore the PACKETS tape.

\item ``Funny Images''

{\bf Symptoms:}
Image with bars accross it, or one part slipped with respect to another, or
some other obvious fault.

{\bf Diagnosis:}
Either a DMA transfer problem, 
which should produce a message on the ADAM terminal, {\bf or}
the data were written onto a corrupted part of the EGLE disc.

{\bf Remedie:}
None! These errors are irrecoverable. Refer to section 9.5 to read about 
what to do or NOT to do with the data.

\item Errors on the MIMIC display.

{\bf Symptoms:}
The MIMIC display signals errors or flash remarks which you
can scarcely credit.

{\bf Diagnosis:}
There may be a real error, but often the error messages are the result
of a minor corruption of the A\&G box micro processor.

{\bf Remedie:}
\begin{enumerate}
\item Press the red ``PANIC'' button on the IPCS desk, which resets the
      A\&G box micro.
\item Type at the ADAM terminal:

      ADAM\,:$>$ {\tt IDS OPEN}
\end{enumerate}
If this does not cure the problem then you probably have a real fault so
call the Duty Technician.
\end{itemize}
\end{document}
