
How I installed emtex, mf, dvips, and NFSS2 on a 386 w/ postscript or hplaser
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                   John Refling,  University of California
                         jrefling@balboa.eng.uci.edu
                  date: 18 October 1993,  Version: 1.1

Archivists
~~~~~~~~~~
This file should be stored on your machine with a base name of 'jrhelp11'.
in a place related to tex.  A one line description of this guide might be:
"Describes install of emtex, nfss2, postscript, hplaser on 386. No windows"

How to get latest
~~~~~~~~~~~~~~~~~
The latest version of this may be obtained by sending mail to:
refling@sloth.eng.uci.edu.  The vactaion program will send this to you
automatically.  This address is different from where I receive regular
e-mail.  This service may not last much past December, 1993.  This will
also soon be available at simtel mirrors such as wuarchive.wustl.edu
and oak.oakland.edu in/or near the /pub/msdos/tex directory.

What's changed from version 1.0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a few minor details, unless you got to the very last section, which has
some important changes.
ALL REVISIONS ARE MARKED AS FOLLOWS:
new text new text new text new text new text new text new text
[*1.0 original text original text original text original text original text]

so just search through for [*.
The number following the [* is the version from which it was changed.

What's changed from version 0.1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ability for more logical organization of files on drive
multiple printers
hp laserjet iv pcl installation
hp laserjet plus pcl installtion
updated some of the source distribution sites

What is this
~~~~~~~~~~~~
This is a short account of my experiences installing emtex on a few different
computers, with a few different printers.

Hardware you NEED to follow this guide
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a 386 or greater computer with reasonable (4MB) ram about 10 meg free space
    peak for the install, reduced to a few megs disk space permanently.
a reasonable dos version (I don't use windows or os/2, so that's not covered).
a laser printer (postscript or pcl hplaserjet or hplaserjet iv, are tested).

Note: I don't do ANYTHING with windows, so can't answer ANY questions on that.
Note: I don't do ANYTHING with OS/2, so can't answer ANY questions on that.

What you get
~~~~~~~~~~~~
emtex system (tex, latex, mf, screen previewers, mainz macros, nfss2)
dynamically generated fonts (that's right, I don't generate them until the
   first time I use them.
your choice of emtex's directory structure or your own custom structure.

Note: I don't do ANYTHING with windows, so can't answer ANY questions on that.

How to do it
~~~~~~~~~~~~
Print out a copy of this file, and follow along with it.   You need either
ftp access from your pc, or disks with the files on them.  Also, there is
stuff in this file you need to save in other files, so know how to use
an editor to cut things out.  You also need unzip, and know how to use it.

What you don't get
~~~~~~~~~~~~~~~~~~
This worked for me, but I can't guarantee it for you.  You take all
responsibility for implementing this.  You are assumed to know enough
about what is going on to not do something dangerous even if it says to
do so here.  Besides, someone could have changed this before you got it.

Note: I don't do ANYTHING with windows, so can't answer ANY questions on that.
Note: I don't do ANYTHING with OS/2, so can't answer ANY questions on that.

Introduction
~~~~~~~~~~~~
The emtex distribution was a little confusing to me at first, since I am
used to obtaining one compressed distribution archive file and working with
that.  When a new version is distributed, one goes back to the ftp site and
gets the compressed file with the next higher version number.

With emtex, things are spread across directories, not only in terms of package
components, but also in terms of revision levels.  The most serious drawback
of this method is that it is difficult to determine the revision level of
programs, or where a particular revision level is.  The simpliest way to
install it this is just to install ALL of the archives in in order, and let
them overwrite [hopefully] older versions.  Then, you will have the latest
versions, and you delete what you don't want.  Some of the installation could
be skipped, since it will be deleted.

All files will be put in .\emtex.  If you don't like this, look at the command
line options of unzip.  I will start at the root directory \ and change it
later.  Note: if you change the directory stucture, you need to set a LOT of
environment variables.  I do this at the end of this guide.

Note:  your results may vary depending on if you miss a step, or if I missed
a step in this document.  This is still a draft document, although it has been
tested several times.  Network information changes, as well as the files
network archivists choose to put on their archives.  You may have to look
around a bit.  Be creative!


OBTAIN THE DISTRIBUTION AND EXTRACT IT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.  mkdir \emdist                          [make a directory called \emdist]
    chdir \emdist

2.  use ftp to connect to a distribution machine, ftp.uni-stuttgart.de,
    ftp.shsu.edu, wuarchive.wustl.edu, etc, and get to the emtex directory
    something like pub/soft/tex/systems/msdos/emtex, etc.  Grab all the files
    in the disk1, disk2, disk3, disk4, disk5, betatest subdirs.  MAKE SURE YOU
    SET BINARY MODE BEFORE THE TRANSFER OF BINARY FILES (zip, exe, com, etc),
    and ascii mode before the transfer of text files (ger, eng, doc, txt, etc)
    I don't use all the programs, if you know what you are doing, you don't
    have to transfer everything.  You might want to archive it on floppy.
    Compare dates and sized with below.  If they are the same, installation
    should go smoothly.  The files listed below are the ones absolutely
    necessary.  [Note: when I tried connecting today, {oct 17}, uni-stuttgart
    was being changed to another computer: info2.rus.uni-stuttgart.de
    and the file structure appeared to be: pub/tex/systems/msdos/emtex/.]

    If you are starting from floppy which you made earlier, just proceed
    below, substituting A: or B: and the appropriate floppy disk for \emdist.
    Do the following in order.

3.  cd \                         [or wherever you want the emtex root to be]
4.  unzip -d \emdist\tex1.zip                   [disk1, 375854, oct 07 1991]
    unzip -d \emdist\tex2.zip                   [disk1, 268240, oct 11 1992]
    unzip -d \emdist\latex1.zip                 [disk2, 248823, jun 11 1992]
    unzip -d \emdist\latex2.zip                 [disk2, 238131, jun 25 1992]
    unzip -d \emdist\blatex.zip                 [disk2, 231677, jun 25 1992]
    unzip -d \emdist\makeindx.zip               [disk2,  52717, jun 25 1992]
    unzip -d \emdist\bmf1.zip                   [disk3, 266527, oct 04 1990]
    unzip -d \emdist\texcad.zip                 [disk3, 120547, mar 22 1991]
    unzip -d \emdist\mf1.zip                    [disk4, 249916, oct 04 1990]
    unzip -d \emdist\mf2.zip                    [disk4, 344463, oct 04 1990]
    unzip -d \emdist\mf3.zip                    [disk4, 278545, oct 04 1990]
    unzip -d \emdist\mfware1.zip                [disk4, 327215, oct 04 1990]
    unzip -d \emdist\bibtex.zip                 [disk5, 119155, oct 04 1990]
    unzip -d \emdist\bmf2.zip                   [disk5, 271791, oct 04 1990]
    unzip -d \emdist\btex1.zip                  [disk5, 265159, oct 04 1990]
    unzip -d \emdist\btex2.zip                  [disk5, 274600, jun 11 1992]
    unzip -d \emdist\mfware2.zip                [disk5, 140361, oct 04 1990]
    unzip -d \emdist\misc_mf.zip                [disk5,  36349, oct 04 1990]
    unzip -d -o \emdist\tex386b8.zip         [betatest, 219721, apr 13 1992]
    unzip -d -o \emdist\mfb1.zip             [betatest, 957225, jun 04 1992]
    unzip -d -o \emdist\mfjob11l.zip         [betatest,  99304, jun 09 1992]
    unzip -d -o \emdist\maketcp.zip          [betatest,  26335, nov 30 1992]
    copy \emdist\*.eng emtex\doc             [disk1, various, jun 25 1992]
    copy \emdist\readme.tst emtex\doc        [betatest, 3937, feb 08 1993]

5.  Get rid of stuff:
    cd emtex
    del *.cmd                                                   [os/2 stuff?]
    del bmf*.exe                                                [small mf]
    del blatex.bat                                              [small latex]
    del btex*.exe                                               [small tex]
    del mf.exe                                                  [small mf]
    del mf186.exe                                               [small mf]
    del mf286.exe                                               [small mf]
    del tex.exe                                                 [small tex]
    del tex286.exe                                              [small tex]
    del texp.exe                                                [win stuff?]
    del dll                                                     [win stuff?]
    rmdir dll                                                   [win stuff?]
    del texfmts                                                 [small tex]
    rmdir texfmts                                               [small tex]
    del mfbases                                                 [small tex]
    rmdir mfbases                                               [small tex]
    del remove                                                  [intnl files]
    rmdir remove                                                [intnl files]
    del mfp.exe                                                 [win stuff?]
    del mfpm.ovl                                                [win stuff?]
    del mfjob1.ovl                                              [small mfjob]
    del mfjob2.ovl                                              [small mfjob]
    ren tex386.exe tex.exe
    ren mf386.exe mf.exe

This will give you the following software and versions:

bibtex.exe        0.99c [3c]
chtopx.exe        1 [1f]
gftodvi.exe       3.0 [1g]
gftopk.exe        2.2 [1h]
gftopxl.exe       no version
gftype.exe        3 [1e]
makeindx.exe      2.11
maketcp.exe       1.1c
mf386.exe         2.71 [3c-beta1] (renamed to tex.exe)
mfjob.exe         1.1l
mft.exe           2.0 [1e]
pktogf.exe        1.0 [1c]
pktopx.exe        2.2 [1e]
pktype.exe        2.3 [1c]
pxtoch.exe        1 [1f]
pxtopk.exe        2.2 [1f]
tex386.exe        3.141 [3c-beta8] (ranamed to tex.exe)
texcad.exe        2.8

of which I delete ALL except tex.exe, mf.exe, bibtex.exe, mfjob.exe and
makeindx.exe, gftopk.exe, and texcad.exe.  This is a non-standard,
personal decision.  You should wait on this until the end of the
installation after deciding what you want to keep.

I would perfer to not rename tex386.exe and mf386.exe to tex.exe and mf.exe
but it seems to be necessary in the latter case since I can't see how to
control the running of mf.exe mf186.exe mf286.exe or mf386.exe from 
inside mfjob when it is called by dviscr.exe.

Set Environment variables (see \emtex\set-tex.bat)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Make sure that the following is in \config.sys: (the numbers can be larger)

shell=command.com /e:1024 /p
buffers=20
files=20

if tex complains that it can't open an output file, increase the files.
if you will be using tex and latex only put these in your autoexec.bat:

set texinput=\emtex\texinput
set btexfmt=\emtex\btexfmts
set textfm=\emtex\tfm
set mfinput=\emtex\mfinput
set bmfbas=\emtex\bmfbases
set mfjob=\emtex\mfjob

you may keep the executibles in the \emtex directory and:
edit \autoexec.bat and append the following to the path statement:
;\emtex

Use batch files or aliases to call tex and slitex with appropriate base
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
create \emtex\latex.bat in path:   or:     add the following aliases to ced:
tex &lplain %1 %2 %3 %4 %5 %6              alias latex = tex &lplain %1 %2

create \emtex\slitex.bat in path:          alias slitex = tex &splain %1 %2
tex &splain %1 %2 %3 %4 %5 %6

reboot your computer now so the changes will take effect.

Snatch latest version of modes.mf (only necessary if using hplaser iv pcl) 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ftp ftp.cs.umb.edu      get pub/tex/modes.mf
mkdir \emtex\mflocal
and put it in \emtex\mflocal as modes.mf
edit \emtex\mfinput\plain.ini and \emtex\mfinput\cm.ini so that the following:
input modes;
comes after input local;
append ;\emtex\mflocal to the set mfinput in autoexec.bat
reboot now

Build mf now (INITMF)
~~~~~~~~~~~~~~~~~~~~~
cd \emtex\bmfbases
edit bas.bat and change "bmf" to "mf" in all cases (2)
bas

Build latex now (INITEX)
~~~~~~~~~~~~~~~~~~~~~~~~
cd \emtex\btexfmts
edit fmt.bat and change "btex" to "tex" in all cases (2)
edit slifmt.bat and change "btex" to "tex" in all cases (1)
fmt
slifmt

Build the Mainz optional macro distribution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Many needed for nfss documentation and useful for latex later.
This includes: array, doc, ftnright, multicol, theorem, verbatim, nfss2.

cd \emtex       [or wherever your btexfmts, doc, texinput, tfm, etc are]
mkdir mainz
edit \autoexec.bat and append your complete mainz path to the texinput
eg, mine looks like: set texinput=\emtex\texinput;\emtex\mainz
save and reboot the computer now.
make some temporary directories: [IF ALL YOU WANT IS NFSS2, DO *** ITEMS]

mkdir \array                                    [oct 12 1992]
mkdir \doc                                      [sept 8 1992]
mkdir \multicol                                 [sept 7 1992]
mkdir \theorem                                  [sept 7 1992]
mkdir \verbatim                                 [jan 20 1992]
mkdir \ftnright                                 [may 17 1993]
mkdir \nfss2               ***                  [oct 5 1993] (yes, today!)
mkdir \psmetrics           ***      [many binary, under nfss2, oct 5 1993]

The date is the latest revision I saw.  Get the files from the
pub/soft/tex/macros/latex/distribs/* distribution on the site you
used in step 2 above, and put them in the appropriate just made
temporary directories.  This should have a tree structure but since I
use it only briefly, and the nfss2 and psmetrics have been changing,
it would be a pain to combine all of them for archival on floppy.

This takes forever!  HINT HINT HINT: It would be really nice if the
people who archive this stuff would bundle it together better.  For
several reasons: 1. mget doesn't always work with so many files.  2.
It doesn't work with directories.  3.  It is hard to make sure you
get all of them.  4. ascii and binary files are mixed together.  HINT
HINT HINT.  

All should be transfered in ascii mode, except for the files in
psmetrics, *.vf and *.tfm must be binary mode.  The ascii ones in
psmetrics are: ec.enc, makefile, psfonts.new, texchars.pro,
vpltovpl.* (zip and save to floppy NOW if you want)

[IF ALL YOU WANT IS NFSS2, SKIP TO 'INSTALL NFSS2' BELOW]

process doc (mz0):
cd \doc
tex install.mz0
answer: unix: n
        multicol: y
copy *.drv \emtex\doc
copy *.sty \emtex\mainz
copy docstrip.tex \emtex\mainz
copy *.ist \emtex\mainz

process multicol (mz1):
cd \multicol
tex install.mz1
copy multicol.sty \emtex\mainz
copy multicol.drv \emtex\doc

process theorem (mz2):
cd \theorem
tex install.mz2
copy *.sty \emtex\mainz
copy *.drv \emtex\doc

(skip mz3, nfss[1] is obsolete)

process verbatim (mz4):
cd \verbatim
tex docstrip
answer: use.. : y
copy *.sty \emtex\mainz
copy verbatim.tex \emtex\doc
copy verbtest.* \emtex\doc

process array (mz5):
cd \array
tex install.mz5
copy *.sty \emtex\mainz
copy *.drv \emtex\doc

process ftnright (mz6):
cd \ftnright
tex install.mz6
copy *.sty \emtex\mainz
copy *.drv \emtex\doc

You may want to produce all the documentation for the package so far.
To do so, print out all text files in \emtex\doc.  run tex or latex on
.tex files. run latex on all .drv files to produce .dvi files which
may be converted into your printer's format.  You may not be able to do
that yet because we have not yet installed that software.  Or you may
want to wait until we have installed NFSS2 (below) before printing.  If
I recall correctly, some of the documentation may be formatted for A4
size paper, and may need to be reformatted for 8 1/2 x 11 paper.  In any
event, at least you now know where all the documentation is.

get rid of the original stuff after archiving it on floppy:

del \array\*.*
rmdir \array
del \doc\*.*
rmdir \doc
del \multicol\*.*
rmdir \multicol
del \theorem\*.*
rmdir \theorem
del \verbatim\*.*
rmdir \verbatim
del \ftnright\*.*
rmdir \ftnright

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

INSTALL NFSS2 (mz8) [no mz7]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
un/Fortunately, the NFSS2 distribution has been changing since it was
released.  Therefore, your results may vary.

Now,
cd \nfss2
copy doc.sty \emtex\mainz
copy docstrip.tex \emtex\mainz
latex nfssinst.ltx                  [for the docs]
latex nfssinst.ltx
copy nfssinst.dvi \emtex\doc        [and print and read it]
tex main.ins
    answer: large? y, ams? n, 35 ps? y, cork? c, german? n, pandora n.
copy *.fd \emtex\mainz
copy *.sty \emtex\mainz
copy nfssfont.tex \emtex\mainz
copy nfslides.tex \emtex\mainz
copy sfontdef.tex \emtex\mainz
tex -i -8 nfss2ltx.tex \dump
copy nfss2ltx.fmt \emtex\btexfmts
copy nfss2ltx.tex \emtex\mainz
copy nfsscode.tex \emtex\mainz
copy fdprefix.tex \emtex\mainz
copy fontdef.tex \emtex\mainz
copy preload.tex \emtex\mainz
copy cmpreloa.xpt \emtex\mainz
***** the following may have been left out from the documentation   ****
copy *.def \emtex\mainz

now alias latex to use nfss2ltx, ie, change your .bat file or ced definition,
ie, for my setup, alias latex = tex &nfss2ltx or change \emtex\latex.bat

Do the docs (trouble printing now --- may want to come back here later)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
most will have problems:  may have to add \defaultencoding and
\fontencoding{T1} to print out on postscript as is.

latex main.drv                    [some errors due to missing fonts]
latex main.drv                    [some errors due to missing fonts]
latex interfac.ltx
latex psnfss2.tex
latex essnfss2.tex                   [wont work --- needs ltugboat.sty]
latex lozguide.tex                   [" --- needs nflucbrb.sty and nfloz.sty]

copy *.dvi to \emtex\doc (print and read)

Copy the above source files to \emtex\doc for future latexing

Get rid of original sources after achiving to floppy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
del \nfss2\*.*
rmdir \nfss2

Test
~~~~
mkdir \test
cd \test

if you want to use the old cm fonts, make a small file called cmr.tex:
\documentstyle{article}
\begin{document}
Hello world...........$\sum$
\end{document}

and latex it.  It should work.

If you want to use the native postscript fonts in your printer, make a small
file called post.tex: (postscript printers only!)
\documentstyle[nftimes]{article}
\fontencoding{T1}
\def\encodingdefault{T1}
\begin{document}
Hello world...........$\sum$
\end{document}

and latex it.  This is the sequence you will use in the future.
This will probably die due to lack of the postscript font tfms.  Fix that:
copy \psmetric\*.tfm \emtex\tfm

and latex the document.  It should work.

remember, the tfm files are BINARY! and must be transferred accordingly.
If you get an 'improper tfm error' you didn't do it right.

INSTALL DVIPS (for postscript printer only)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ftp monu1.cc.monash.edu.au [original source]  or   wuarchive.wustl.edu
cd /pub                                            /mirrors/msdos/postscript
get dvips5518.zip        [binary, 546043]

then:
cd \
unzip -d dvips5518.zip *.exe
unzip -d dvips5518.zip *.pro
unzip -d dvips5518.zip *.ps
unzip -d dvips5518.zip *.doc
unzip -d dvips5518.zip *.bat
unzip -d dvips5518.zip *.tex
unzip -d dvips5518.zip *.sty
unzip -d dvips5518.zip *.pc

I did this in a round-about way to prevent the .tfm files from being
uncompressed.  NFSS2 uses it own set of .tfm files, which were obtained
from the psmetrics distribution directory (we copied them to the correct
place in the previous step).

edit \emtex\ps\config.ps and uncomment the default V path and chenge it to:
V c:\emtex\vf

copy \psmetric\psfonts.new \emtex\ps\psfonts.map    [notice the rename]
copy \psmetric\ec.enc \emtex\ps\
delete the zip files and temporary directories.

Dvips supplies a maketexp.bat which uses command.com, which must be
executable.  Type command.  If you get a new layer of DOS, you are ok.
If you get 'bad-command or filename' you need to change the mode of
command.com so it is not hidden and/or system.  Play.
[*1.0 (insert above paragraph)]

Install virtual fonts (postscript only)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We also needed to prevent the .vf files in dvips5518 from uncompressing.
NFSS2 uses it own set of .vf files.

mkdir \emtex\vf
copy \psmetric\*.vf \emtex\vf                              [binary files!]

[note: you may wish to keep the .vf and .tfm and their psfonts.map file
from dvips5518.zip around for other applications]

now:
cd \test
dvips post

this should work.  copy post.ps to lpt1: (or whatever your printer is)
It should have the text but no math.  The math needs to use the old
cmr fonts.

dvips should have created an instruction file for mfjob to create the
missing math fonts.  If all is well, run
mfjob dvips
dvips post
copy post.ps to lpt1:

and you should have math.


Building missing fonts
~~~~~~~~~~~~~~~~~~~~~~
you can either do this on demand for the fonts needed, or all at once.
for the latter, run mfjob with one of the .mfj files in \emtex\mfjob.
I don't do it that way.

I create everything on demand, when dvips complains, using mfjob dvips
as above.

Screen previewer and hplaserjet driver
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
get the following files from the standard distribution sites (binary!)
and unzip them:

cd \
unzip -d \emdist\dvidrv_14s.zip       [betatest,1033814, nov 05 1992]

if you have a machine with a coprocessor,
unzip -d \emdist\dvidrv87_14s.zip     [betatest, 448181, nov 05 1992]

cd \emtex
del *.cmd
del *.dot

all that is of interest here is the following:
dvidrv.exe   and dvidrv.err         (main programs)
dvihplj.exe  or  dvihplj7.exe       (choose one depending on coprocessor)
dviscr.exe   or  dviscr7.exe        (choose one depending on coprocessor)
lj.cnf                              (configuration for both dviscr dvihplj)
prthplj.bat     (edit this \emtex\prthplj.bat to choose dvihplj or dvihplj7)
v.bat           (edit this \emtex\v.bat to choose dviscr or dviscr7)
vs.bat and dviscrs are for limited memory dos machines.

The previewer and hplj need fonts on your pc, so you will have to make
them, either all at once or on demand, as above.  OR you can use the 
font libraries which have all the fonts stored in them already.  They
are on the ftp distribution site.  They have names similar to lj_1.fli,
etc and are binary files.  This is true for postscript also, you need
some fonts on your pc to view the document, even if you print in post-
script!

This is were I decided to say with the cmr fonts, even though I have a
postscript printer.  In my opinion, the cmr fonts look better, and I do
a lot of mathematical typesetting, so I need some of the cmr stuff anyway.
Besides, mixing postscript and cmr on the same page looks really bad on
my printer.  Since I generate the fonts on demand, I essentially have all
the scaleable fonts I need anyway.  Font generation is under a minute on
a 486-33.  And, like I said before, you need the fonts to preview the
document on the screen.  This is a personal choice, you are free to choose
differently.

Now, continuing with the installation using my choice,

edit the \emtex\lj.cnf to reflect where the fonts are (rename the orignl):

% lj.cnf (300x300 DPI using LJ fonts)
/pf=\texfonts\pixel.lj\@Rrdpi\@f.pk
/r=300
/rf=300
/fs=1
/fm=hplaser
/fd=2
/fb

Note: only if you used the new modes.mf way above and an odd printer:
If you are using an hplaserjet iv, change hplaser to ljfour, change the
300 to 600.  I understand that this driver does not work properly
with the hplaserjet iv yet.
If you are using another engine, search through the modes.mf file
to find something appropriate.

The /fb sets it into batch mode so missing fonts are generated
automatically.

to view the .dvi file, use v.bat
to print the .dvi file to a hplaserjet use prthplj.bat

both can be customized.

for example,
cd \test
v cmr
or 
v post

Note, as I mentioned before, you can't view postscript on your screen,
unless you install those fonts (they too are on the net near the emtex
distribution.)  The missing fonts appear as boxes on the screen, but
print fine on a postscript printer.

I add a /s3 to the parameter list in v.bat.
The /s3 scales the page down so more of the page fits on the screen.
The number to use varies depending on the video adapter you use.
You could also add it to the environment variable: set dviscr=-s3
instead.

to print:

prthplj cmr

will send output to prn:. You may want to customize dvihplj.bat to specify
the output file, then copy the file to the printer. (/po).
[*1.0: the output file, then copy the file to the printer. (/op).]

If you copy the file to the printer, you must specify binary mode (copy/b):

hplaserjet iv
~~~~~~~~~~~~~
There is another driver for the laser jet iv which I have tried, while
the emtex one is being repaired.  It is at

ftp.uni-bielefeld.de
/tex/dviware/dvilj4

and needs go32.exe from the djcpp gnu c distribution.
The version I tested worked fine except for messing up a few characters
in a few point sizes in landscape mode.  That was version 0.51alpha6.
To use it, you need to change the font subdirectory from 300dpi to
600.  I don't think it can run mfjob, so use dvips to do so.  Change
the default resolution from 300 to 600 in config.ps.  Change the mode
for metafont to ljfour.  Use a -a to specify the font directory.  There
may be other changes, too.

custom fonts
~~~~~~~~~~~~
to use a custom font, say APL, get the .mf file off the net, and
put it in the \emtex\mflocal subdirectory.  Make sure mfinput
[*1.0: put it in the \emtex\mflocal subdirectory.  Make sure mfinputs]
points there too.  As an example, use cmapl10.mf from the net:

mf \mode=hplaser; \nonstopmode; mag=1.0; input cmapl10
you will then get a cmapl10.tfm which you move to your tfm subdirectory.
then, for example, do tex testfont
and reply cmapl10
then v testfont
and let it generate the fonts and look at them!  To use them, read the
texbook.

As before, use a \mode= appropriate for your printer engine.  Apple laser
and hplaserjet are hplaser, hplaserjet iv is ljfour.  These are defined
in modes.mf

Get rid of the original downloaded zip files (or archive to floppy)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
del \emdist\*.*
rmdir \emdist

and any other temporary directories

Customize (Advanced users only - 99% of people should skip this)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Most people should stop now, while it is working!
I customize everything so it fits my directory structure.
This is totally non-standard.

move all the files:
\emtex\dvips    --->   \lib\dvips
\emtex\vf       --->   \lib\dvips\vf
\emtex\tfm      --->   \lib\tex\tfm
\emtex\texinput --->   \lib\tex\inputs
\emtex\btexfmts --->   \lib\tex\formats
\emtex\mainz    --->   \lib\tex\mainz
                --->   \lib\tex\local
\emtex\bmfbases --->   \lib\mf\bases
\emtex\mfinput  --->   \lib\mf\inputs
\emtex\mflocal  --->   \lib\mf\local
\emtex\mfjob    --->   \lib\mfjob
\emtex\bibinput --->   \lib\bibinput
fonts:          --->   \lib\hplaser\300\*
[*1.0: fonts:          --->   \lib\fonts\hplaser\300\*]

set texinput=\lib\tex\inputs;\lib\tex\mainz;\lib\tex\local
set btexfmt=\lib\tex\formats
set textfm=\lib\tex\tfm
set bmfbas=\lib\mf\bases
set mfinput=\lib\mf\inputs;\lib\mf\local
set mfjob=\lib\mfjob
set dvipsheaders=\lib\dvips
set texfonts=\lib\tex\tfm
set texconfig=\lib\dvips
set dviscr=-s3

edit \lib\dvips\config.ps and change the paths and uncomment them.
T \lib\tex\tfm
V \lib\dvips\vf
P \lib\hplaser\%d\%f.%p
H \lib\dvips

edit lj.cnf:
/pf=\lib\hplaser\@Rr\@f.pk
/r=300
/rf=300
/fs=1
/fm=hplaser
/fd=2
/fb

edit maketexp.bat:
change first path c:\texfonts --->  c:\lib
change second path c:\texfonts\pixel.lj ---> c:\lib\hplaser
change both @Rrdpi  --->   @Rr
[*1.0 (added above paragraph)]

If you are using dvilj4, this scheme seems to work,
since the font paths appear to be unflexible, ie, fixed to *\600\*, not
*\600dpi\*.  You will need to change the font path for dvilj4 in the
command line (-a).

Have fun
~~~~~~~~
Note: I don't do ANYTHING with windows, so can't answer ANY questions on that.
Note: I don't do ANYTHING with OS/2, so can't answer ANY questions on that.

[end]

(c) 1993 John P. Refling, All rights reserved.
