               INSTALLING THE OS9/TeX SYSTEM

   Installing the OS9/TeX system consists primarily of correctly
unpacking the archives, which will build the directories and many of the
files, and running some shell scripts which will build a number of other
files.  The archives were all created with LHa version 2.01 for OSK,
ported by Mike Haaland.  You'll need this or a compatible program
to dearchive.
   The installation requires at least 10 megabytes of free space on your
hard disk (in addition to the 3 meg required to hold the archives), and
"mfree -e" should show a free block of at least 1500k to carry out some
of the steps in the installation. You may need to reboot, terminate some
programs, and unload some things from memory.  This memory requirement
is primarily for initex and virtex. If you can't get this much free
memory, you may need to find an older version of initex and virtex (and
the accompanying tex.pool file) which requires less memory.

------------------------------------------------------------------------------

Step 0: Print out this file, and check off each step as you do it.

------------------------------------------------------------------------------

Step 1: Install the executables.

   a. Choose an appropriate directory on your system.  I use
/DD/CMDS/TEXCMDS, but there may be something more appropriate for your
system.  Then chd to that directory, and unpack the executable archives
with:
        lha -x <full path of texcmds.lzh>
        lha -x <full path of dvitranslators.lzh>
If you downloaded the tangle and weave program archive, you can also
        lha -x <full path of tangleweave.lzh>

   b. Check the attributes.  All the executable files should have an
appropriate ownership, and have public and private read and execute
privileges.

   c. Set your PATH variable(s) accordingly.  If you created a new
directory for these commands, you'll need to add this to the PATH
variable in the .login files for each user that will want to
access these programs.

------------------------------------------------------------------------------

Step 2: Install the data files.

   a. Choose and create an appropriate directory.  I _STRONGLY_
recommend you use /DD/SYS/TEX.  The executables currently look by
default in /DD/SYS/TEX and then /DD/USR/TEX.  These can be overridden by
appropriate environment variables, but this can be complicated to get
right.  I've not tried installing the system in /DD/USR/TEX, though it
should work.

   b. Unpack the archive.  As above, first chd to /DD/SYS/TEX, then
         lha -x <full path of texdir.lzh>
This will take several hours to unpack, so be patient.

------------------------------------------------------------------------------

Step 3: Select a printer, and edit some configuration files.

   a. Choose a DVI translator program.  Included in the package
are DVI translators for a number of popular printers.  These
are the executables named dvi___.  This is a list of the
ones included:
        dvialw  - Apple LaserWriter and other 300dpi Postscript printers
        dvidjp  - Hewlett Packard Deskjet Plus
        dvieps  - Epson MX/FX and compatible 9-pin printers
        dviimp  - imPRESS/Imagen laser printer family
        dvijet  - Hewlett Packard LaserJet
        dvijep  - Hewlett Packard LaserJet Plus
        dvilj2  - Hewlett Packard LaserJet II
        dvimac  - Apple ImageWriter 144dpi printer
        dvioki  - Okidata 192 144dpi printer (should work with Oki 92?)
        dvitos  - Toshiba P-1351 180dpi printer
   Four have been carefully tested under OS9/68k: dvialw, dvieps,
dvilj2, and dvioki.  If you have trouble with one of the others, please
tell me and I'll try to fix the problem.
   If your printer is not on this list, you'll need to find,
write, or buy a DVI translator program for it.

   b. MetaFont has a "modes" file which tells it the resolution
and other properties of various printers.  This information is used
whenever MetaFont creates a font.  You should look through the
file /DD/SYS/TEX/MFINPUTS/modes.mf to select the printer description
that's appropriate for your printer.  You should then edit the
line (about 6 lines from the bottom of the file) which reads
	localfont := CanonCX;
to include the name of the appropriate printer description.
If in doubt, CanonCX is a good choice for any 300dpi laser printer,
and you should use EpsonMXFX for 9-pin Epson-compatible printers.
For other printers, read the file carefully and choose the best
one.  If you must create your own, start by copying and modifying
another one, and proceed carefully.  It will help to consult
the METAFONTBook.

   c. Edit the "makefont" program.
      Since running MetaFont to build a new font involves a somewhat
complicated command line, I've written a Microware Basic program to
help.  "Makefont.b" will prompt you for the name of the font to make,
and the size, and will then run METAFONT to build the font, and handle
some other housekeeping chores.  You'll first need to edit the
Makefont.b source code, contained in the FONTS directory, to reflect
your directories and preferred printer.  Once you've done this, you
should create the packed Makefont program using the following commands:
      basic
      load makefont.b
      chx /DD/CMDS/TEXCMDS
      pack makefont
      bye
Note that "makefont" will not work correctly for all fonts, since
it assumes some things about the naming.  For fonts that don't
match makefont's assumptions, you'll have to run MetaFont
by hand.  The file Usage.text should help.

------------------------------------------------------------------------------

Step 4: Create the format and base files

   a. TeX and MetaFont are macro languages, and for speed of operation,
they are designed to load pre-compiled macros.  The "initex" and "inimf"
programs are used to pre-compile macro sets which can be loaded by
"virmf".  First, make sure you have enough free memory, since initex is
especially memory hungry.  On my 3 meg MM/1, I sometimes have to reboot
in order to have sufficient free memory.  Then
         chd /dd/sys/tex
         install
The "install" shell script will build the "format" files, which are
precompiled macros for TeX, and the "base" files, which serve a similar
purpose for MetaFont.  It takes almost an hour to build the three format
files for Plain TeX, LaTeX, and SliTeX, and the two base files for
Plain METAFONT and the Computer Modern base.

------------------------------------------------------------------------------

Step 5: Test all the pieces

   a.  To make sure TeX works, go to the SAMPLES directory, and
         tex story.tex
After a few minutes, you should see
         This is TeX, C Version 3.14
         (story.tex [1])
         *
The number in brackets is a page number.  The open parentheses is
printed when TeX opens a file, followed by the file name.  The
close parenthese is printed when TeX closes the file.  So, this
output means that TeX has completely read the file story.tex, and
has generated one page of output.  Type "\end" at the prompt to
finish TeX (normally, the \end is part of the input file).  You
will then see
         Output written on story.dvi (1 page, 668 bytes).
         Transcript written on story.log.
  The dvi file is a DeVice Independent file that contains instructions
about where to put each character on the page.  The log file is a text
file with information about this run.  The byte size may vary.

   b.  Build some test fonts
   Before you can print it out, you'll need to create some fonts.
This particular document requires three fonts: cmr10, cmsl10, and
cmbx10.
       cmr10  - Computer Modern Roman 10 pt.
       cmsl10 - Computer Modern Roman Slanted 10pt
       cmbx10 - Computer Modern Bold Extended 10pt
To build them, use the "makefont" program
           makefont
           Name of font: cmr10
           Size to make font: <Return>
Makefont will run MetaFont to build the GF-format font file, then
run "gftopk" to convert it into a more compact PK format, and finally
delete some extraneous files.  Similarly, you should create the cmsl10
and cmbx10 fonts.

   c.  Print it out.
   If you're using one of the DVI translators supplied with the package,
you should be able to simply
          dvi___ story.dvi
Where dvi___ is one of the dvi translator programs.  This will
create a file suitable for sending to your printer.  For all but
Postscript printers, you should be careful to use "merge" to
print the file, since these are graphics files.  For example,
if you are using the LaserJet II translator, the commands are
          dvilj2 story.dvi
          merge story.dvi_lj2 >/p
If the translator program prints out any error messages, you'll
need to diagnose and fix the problem.  The most common problem
at first will be missing fonts, but as you create more and more
fonts, this problem will occur less frequently.

------------------------------------------------------------------------------

Step 6: Use it!

   a.  Read the file Usage.text for notes about operating the
various programs.

   b.  Buy a copy of "LaTeX: A Document Preparation System" and/or
"The TeXBook" for further details on how to use TeX.

   c.  Format and print out other documents.  There are several other
documents in the SAMPLES directory that you may want to look at.  Format
them with TeX or LaTeX, as appropriate (if one of the  first lines is a
"\documentstyle" command, then use LaTeX).  You can then print them as
above.  You will probably need to create more fonts in order to print
them successfully.  (You  may want to examine the Makefiles which appear
in subdirectories of the FONTS directory for ideas on building many
fonts at one time.)

------------------------------------------------------------------------------

