%THE HELIOS FILE SERVER: INSTALLATION INFORMATION, NOVEMBER 1990.
%$Id: HEL91017.tex,v 1.1 1992/01/27 16:38:06 doc Exp $
\documentstyle[a5,times]{psl}

%\newcommand{\prim}[1]{{\bf #1}}
\title{{\Huge The Helios File Server: Installation Information}}

\author{}
\date{}
%\makeindex
\pagestyle{plain}
\begin{document}

\include{docinfo}

\docinfotitle{The Helios File Server: Installation Information}
\docinfoauthor{Perihelion Software Limited}
\docinfoproject{HEL}
\docinfoauthinit{PSL}
\docinfoyear{90}
\docinfodocno{017}
\docinforev{1}
\docinfooperator{ID}
\docinfostate{APPROVED}
\docinfosecurity{PUBLISHED 1990}
\docinforeader{PSL}

\maketitle
\input{HEL91019}
\setcounter{tocdepth}{4}
\pagenumbering{roman}
\tableofcontents
\cleardoublepage

\pagenumbering{arabic}


\chapter{Introduction}
These notes explain how to configure the file server for different disc
formats and hardware controllers. You should already have followed the
installation instructions in Chapter 2 of `The Helios File Server'.  
Helios supports most leading makes of transputer or SCSI interface TRAMs
and boards. It also runs on a PC hard disc partition. Several possible
configurations are currently available for the Helios File Server, and
their individual hardware requirements are described on the following pages.
\index{SCSI device support}\index{MSC}
\vfill
\vspace*{18cm}
\cleardoublepage
\chapter{Device support}

Helios provides a device driver support between the file server and the
controller hardware. Drivers are provided to support most of the
leading makes of interface. Device drivers are located in the {\tt
/helios/lib} directory. The conventional format for a Helios device
driver is: {\tt $<$name$>$.d} 
\index{Device drivers: format}

\section{The devinfo file}

Before you run the file server, make an appropriate entry in
the {\tt devinfo.src} file. The example file contains entries for
each of the currently supported devices. Find the discdevice which
corresponds to the device you want to use, and edit the drive parameters
to match your disc.
 You must also decide how much  cache memory the file
server should be allowed to use. The practical minimum is  100k,
and any value of over  1 Mbyte will allow most of your working
files to be cached. When you have edited the {\tt devinfo.src} file, you
should compile it again by using the following command:\begin{verbatim} 
 gdi /helios/etc/devinfo.src /helios/etc/devinfo
\end{verbatim} 

\noindent {\bf Note:} For a detailed description of the {\tt
devinfo.src} file,
see the Appendix.
\newpage
\section{The Parsytec MSC}

\noindent {\bf Device driver:} {\tt msc.d}
\vspace{0.25cm} 

\index{RAM}\index{Cache|prim}
\noindent This uses the Parsytec MSC SCSI interface board, which offers 4 Mbytes
of RAM, an SCSI interface and a T800 processor. The Helios File Server
runs under Helios on this processor, and it uses most of the RAM for its
own cache. A suitable SCSI drive with a capacity of up to 2 Gbytes
should be added.


\section{The Hunt HE1000}

\noindent {\bf Device driver:} {\tt he1000.d}
\vspace{0.25cm}

\index{HE1000}
\noindent This version uses the Hunt Engineering HE1000 SCSI interface TRAM. It
has a 16 bit transputer, and controller software from ROM. It uses a
link interface with which the Helios File Server communicates. HFS must
run on an adjacent 32 bit processor under Helios. The device driver can
communicate with the HE1000 by using any one of the four links which are
available. 

\section{The Transtech TTM11-2}

\noindent {\bf Device driver:} {\tt he1000.d}
\vspace{0.25cm}

\noindent The HE1000 is also supplied by Transtech, as the TTM11-2.

\section{The T2SL Systems Paradise-1}

\noindent {\bf Device driver:} {\tt paradise.d}
\vspace{0.25cm}

\index{T2 Systems: Paradise SCSI}
\noindent In this configuration, HFS runs under Helios on one of the existing
network transputers. This is connected through an Inmos serial link to a
T2 Systems Paradise-1 SCSI transputer module.
The Paradise-1 is based on a T222 transputer, controlled by firmware. It
can be coupled to any SCSI Winchester disc drive of up to 3 Gbytes. The
firmware manages the low level SCSI interface. This driver is supplied on
request from T2 Systems, Ltd.
\newpage

\section{The Inmos IMS B422}
\index{Inmos B422}

\noindent {\bf Device driver:} {\tt b422.d}
\vspace{0.25cm}

\noindent This version uses the Inmos B422 SCSI TRAM. It uses a 20 MHZ 16 bit
transputer with 64k of S-ram. Controller software is downloaded (file b422.btu)
from the host.

\section{The Paratech GM8504}

Details of this driver can be obtained directly from Paratech.





%\chapter{M212 Disc Controller Support}
\index{Disc controller support}

\section{Rawdisc support}
\index{Rawdisc support}
This version uses any spare partition on the hard disc of a PC host. The
Helios file server can run on any transputer which has sufficient memory
available for the cache, but the further the transputer is away from the
host, the longer the disc access delays will be. A spare partition needs
to contain a minimum of 20 Mbytes to be of use. A pseudo tape device is
supported. It uses the file {\tt /helios/tmp/tape} if the tape volume is
defined in the {\tt devinfo} file.


\section{The A.G. Electronics M200}
\index{A.G. Electronics M212 disc controller}

\noindent {\bf Device driver:} {\tt m212.d}
\vspace{0.25cm}

\noindent This controller uses the M212 disc controller by Inmos, which provides a 16
bit processor. The Helios File Server must be
run on an adjacent 32 bit processor under Helios.
The A.G. Electronics M200 hard disc system has a device interface which
can use the multi sector operations supported by the firmware for this device.


\section{The Transtech TMB05}
\index{Transtech TMB05}

\noindent {\bf Device driver:} {\tt m212.d}
\vspace{0.25cm}


\noindent The Transtech TMB05 is compatible with the A.G. Electronics M200 hard
disc system.

\section{PC disc partition}

The Helios file server can use a spare partition on a PC hard disc. This
allows the restrictions of filenames to be lifted, and introduces
performance benefits through the caching of the filing system.


%\cleardoublepage
\section{The contents of the release disc}
\index{Release disc: contents: table 2.1}
The files contained in the release disc are listed 
in table 2.1.
\vfill
\newpage


\begin{table}
\begin{tabular}{l@{\hspace{.25in}}l@{\hspace{.25in}}l}
lib&&-{}- {\bf Server and Drivers}\\
\\
&&-{}- the file server(fs)\\
&&-{}- device drivers for disc interface hardware\\
\\
etc&&-{}- {\bf Device Information}\\
\\
&&-{}- example devinfo source (devinfo.src)\\
&&-{}- compiled version (devinfo)\\
\\
bin&&-{}- {\bf Commands}\\
\\
&&-{}- display capabilities (access)\\
&&-{}- file protection (chmod)\\
&&-{}- disc editor (de)\\
&&-{}- format partition (fsformat)\\
&&-{}- alter sync mode (fsync)\\
&&-{}- devinfo compiler (gdi)\\
&&-{}- load M212 firmware (loadm2)\\
&&-{}- capability manipulation (refine)\\
&&-{}- flush cache to disc (sync)\\
&&-{}- terminate file server (termfs)\\
\\
devs&&-{}- {\bf Driver Sources}\\
\\
msdos&&-{}- {\bf MSDOS Partition Builder} (makedisk.exe)\\
\end{tabular}
\begin{center}
Table {\bf 2.1} The contents of the file server release disc.
\end{center}
\end{table}
\vfill
\newpage
\vspace*{18cm}

\chapter{Installation: hardware-specific entries}

\index{Device drivers}
Device drivers obtain disc characteristics from the {\tt devinfo} file.
(An example of this file is supplied with the release disc.) Before
using the file server, you should edit the {\tt devinfo.src} file to
match the characteristics of your disc, and then recompile it with the
{\tt gdi} command. (See Appendix A.1 for an example.)

\section{Raw disc}

The raw disc service is provided by a server within the Helios I/O
server, and uses a spare partition on the host machine. This provides you with a directory called {\tt /rawdisc},
containing a list of partitions which are available for the file server
to use. You will need to initialise the parameters in the fileserver and
 discdevice structures of the {\tt devinfo.src} file, to set up the
partitions you intend to use. Place the number of the partition to be
used in the controller field of the discdevice entry. Run the  makedisk
program with the partition letter as its only argument, and the
disc parameters, (such as sectorsize, and the number of sectors, tracks
and cylinders),will be displayed on your screen. Copy the entries into
the {\tt devinfo.src} file. If you have already run
the  makedisk program once, simply rerun it to obtain this information.

\index{Installation: hardware-specific entries}
\section{The Parsytec MSC}
\index{Parsytec: installation entries for MSC controller.}\index{Devinfo file}

The board should be marked as a system processor in the resource
map, and the cache should use about 75 percent of the available memory.
The file server MSC should contain entries for {\bf cgsize} (blocks per
cylinder group), and {\bf ncg} (number of cylinder groups) The {\bf ncg}
rating should be in the range 32 to 64. The product
of both values multiplied by the block size, (which is 4Kbytes), gives the capacity of the
disc, so the drive entry in the disc device MSC is not used.


\section{The A.G. Electronics M200}
\index{A.G. Electronics: installation entries for M212 controller}
\index{A.G. Electronics: firmware}
The M212 device requires the disc parameters to be defined {\em
exactly}, so that it can initialise the controller. You will also need
to give the number of the link which provides your access to M212. You
should place the link number in the {\bf controller} field of the disc device
entry. If you want to use the A.G. Electronics firmware, you should set
the disc device {\bf mode} to indicate the buffering that you intend to use.
The bottom 4 bits will indicate the `read' mode, and the next 4 bits
will indicate the `write' mode. The default value, which uses M212
commands only, is 0 (Zero). A value of 1 would use `buffered' mode, and a
value of 2 would use `unbuffered' mode. You can use different modes for
`read' and `write' operations. Remember that you will need to load the
A.G. Electronics board with its controlling software before you can run the file
server or the disc editor. You can load the software in two different
ways. (1) Use the software supplied by A.G. Electronics and load from
the board's PC link. (2) Load from Helios, by using the {\tt loadm2}
command. In either case, you will only need to load the software once,
unless the M212 is reset for some reason.
\index{loadm2 command}


\section{The Hunt HE1000}
\index{Hunt Engineering: installation entries for HE1000} 
The disc parameters for the HE1000 entry in the {\tt devinfo} file must
be updated to correspond with the disc you are using. You must also give
the number of the link you are using to access the device. You should
place the link number in the {\bf controller} field of the disc device entry.
The SCSI id of the disc should be placed in the {\bf id} field, and that of
the HE1000 should be placed in the {\bf mode} field. The drive fields
should also give the sectorsize, sectors, tracks and cylinder values for
your disc. (There is an
example in the {\tt devinfo.src} file under the name {\tt he1000} for
both the fileserver and discdevice entries.) These parameters will be
used by the {\tt fsformat} command and the HFS drivers. 
\index{Devinfo file: HE1000 installation}

\section{The Transtech TTM11-2}
\index{Transtech: installation entries for TTM11-2}

The HE1000 is supplied by Transtech as the TTM11-2, so the installation
entries are the same as those for the HE1000, as described in the previous
section.

\section{The T2SL Paradise-1}


\noindent The disc parameters for the Paradise-1 TRAM must be entered in the 
devinfo.src file. 
(There is an example in the devinfo.src file under the
name {\tt paradise} for both the fileserver and discdevice entries.) 
 The
fileserver must be run on a processor which is adjacent to the
Paradise-1 TRAM. The example devinfo entry for the Paradise-1 was
written for a 40 Mbyte disc drive. The user must update the cylinder
group size (cgsize), and the number of cylinder groups (ncg), parameters
to reflect the actual capacity of the user's disc drive. The total disc
capacity (in bytes), available to the file server will be {\tt 4096 x
cgsize x ncg}. This should be less than (or equal to) the actual disc
capacity. The controller field and the id field will also need to be
updated. The controller field defines which link of the HFS processor
connects to the Paradise-1, and the id field defines the SCSI id of the
disc drive.

\index{T2SL Systems: Entries for the Paradise-1}

\section{The Inmos IMS B422}
\index{Inmos: Entries for the IMS B422}

The disc parameters for the IMS B422 TRAM must be entered in the
devinfo.src file. The controlling link is specified in the controller
field, and the SCSI id of the disc is specified in the id field. The
sectorsize, sectors, tracks and cylinder fields must correspond to the disc.
\pagebreak
\vspace*{18cm}



















%\section{The ATW Raw Disc Service}
%\index{ATW raw disc: installation entries}
%\index{mscsifmt program: ATW installation}
%\index{Devinfo.src file: ATW installation}
%If you are using an ATW, the Rawdisc directory will contain the
%partitions ($0\ldots n$), which you will have defined as Helios partitions
%by using the {\tt mscsifmt} program. You can define each one of these
%programs as `for the use of the file server' by creating `fileserver' and
%`discdevice' entries for them in your {\tt devinfo.src} file. Each
%file server will be associated with a partition, and this should be
%shown in the controller field of the disc device.

\cleardoublepage

\chapter{Formatting and initialisation}
\index{Formatting}\index{Initialisation}

Before you can run the file server on a disc or on a partition, you must
first format the medium, and then initialise the medium with the
file server data structures. The steps you must take to do this will
vary according to the type of machine you are using.
\vspace{0.25cm}

\index{Formatting the Parsytec MSC disc}
\index{Formatting the Inmos M212 disc} 
\index{Formatting the Hunt SCSI disc}
\index{fsformat command}

\begin{enumerate}
\item The MSC disc is already formatted.
\item You can format an M212 disc, a Hunt SCSI disc or a T2SL Paradise-1 
by using {\tt fsformat}. Other manufacturers may supply their 
own formatting software. 


\item PC discs should already be formatted. (If not,
you can format them by using the relevant software on the host machine.)
You will also need to initialise
the partition as an MSDOS partition, and then you must run the program
{\tt makedisk.exe}, with the partition letter as its only argument.
\index{MSDOS: partitions}
This will make MSDOS think that the partition is full, so that it will
not try to use it.
\end{enumerate}
\vspace{0.25cm}
    
\noindent When you have formatted the drive or the partition, you must initialise
it with the data structures of the Helios file server. To do this, you
use the command:\index{Initialising a formatted drive or
partition: command}\begin{verbatim} 
/helios/lib/fs -m <name>
\end{verbatim}
(Remember that the {\tt$<$name$>$} on the end of that command must be
the same as the name of the `fileserver' entry in the {\tt devinfo.src}
file. It will also be the name you intend to associate with the drive or
the partition you have just formatted).
\index{Devinfo.src file: fileserver entry}
\vfill
\newpage
\vspace*{18cm}

%\cleardoublepage
%\printindex
%\cleardoublepage
\input{HEL91020}
%\cleardoublepage
%\input{com}

\end{document}




