Install.doc
-----------

Floppy disk install
-------------------
   The following procedure works equally well for versions 1.2 and 1.3 of
Workbench and for single and multiple floppy disk systems.  It is aimed at
being straightforward enough so that even a novice Amiga user should have
little, if any trouble completing it.

   First boot your system from a copy of your original Workbench disk, do
NOT use the original, the WBStrip script will delete several files from
it in order to make room for JR-Comm and the font files it uses.

   Next, you will have to copy the following files over to ram:

               LHARC (at least version 1.10 is recommended)
               JR-Comm
               JR-Comm.info
               JR-Edit
               JR-Edit.info
               fonts.lzh
               WBStrip

   
   From the CLI type the following command exactly as shown:

                     Execute ram:WBStrip df0:

   After the script completes you may want to customize the Startup-Sequence
file in the S: directory.  This script will have renamed the original
Startup-Seuqence to Startup-Sequence.bak since it will have created its
own file that just loads Workbench and deletes the initial CLI.


Hard disk installation
----------------------
   First thing to do is to install the font files.  The LHARC 1.10 command
line to accomplish this is:

                  LHARC -m -x e <fonts.lzh> fonts:

   The fonts.lzh filename is in angle brackets to indicate that you have to
prefix it with the path to where it's located.

   Although the JRCOMM: assignment isn't strictly necessary, it is suggested
that you create a subdirectory somewhere in your environment and then modify
your Startup-Sequence to make this assignment to this subdirectory every
time you boot your system.

   If the assignment isn't made, JR-Comm will default it's file path to the
S: assignment instead.  If you don't mind the clutter that this can produce
then leave it be.

   If you're mostly a Workbench type person, then copying JR-Comm and the
icon for it to the directory you're going to launch it from is all that
is needed and you can forget about the rest of the discussion here.


Redirection facility
--------------------
   For CLI bangers you'd probably do best by copying the JR-Comm file over
to a subdirectory that is included in your path so that it can be started
from anywhere in your environment.  The following hard disk directory
structure will be used as an example for explaining how the redirection
facility works.

      SYS:---------------------------------------------+
         |                                             |
         jrcomm/---------+                             word/---------+
               |         |                             |             |
         jrcomm.def      |                             |       jrcomm.def
         jrcomm.phones   |                             |
         jrcomm.macros   |                             paint/--------+
                         |                             |             |
          +--------------+--------------+              |       jrcomm.def
          |              |              |              |
          env1/          env2/          env3/          games/
              |              |              |
        jrcomm.phones  jrcomm.phones  jrcomm.phones
        jrcomm.macros  jrcomm.macros  jrcomm.macros

   By assigning JRCOMM: to SYS:jrcomm, and having the "JR-Comm files"
pathname in the general requester set to "JRCOMM:", JR-Comm will load
its defaults files directly from this path, but only if there isn't a
jrcomm.def file in the current directory from where you start JR-Comm.

   Confused?  Ok, let's try this:

   Say that our current directory is SYS:games.  When starting JR-Comm, it
will load its defaults from JRCOMM: since there isn't a jrcomm.def file in
the games subdirectory.

   But, say we're in SYS:word, since there's a jrcomm.def file there,
JR-Comm will load that file instead of the jrcomm.def in JRCOMM:

   And this is where it gets interesting.

   Remember the "JR-Comm files" pathname in the general parameters
requester?  This pathname is saved in the jrcomm.def file and when JR-Comm
is loaded, it will then look in the path that it is set to for any other
files that JR-Comm will use.

   The two other default files are jrcomm.phones and jrcomm.macros.  These
files are loaded after jrcomm.def is loaded, and that's where the
redirection comes from, the ability to redirect JR-Comm to another place so
that a completey different configuration can be setup and used automatically
as needed.

   So, let's say that the jrcomm.def file in SYS:word points to JRCOMM:env1.
When JR-Comm is started from the word subdirectory, it will load jrcomm.def
from there and then load jrcomm.phones and jrcomm.macros from JRCOMM:env1.

   Pretty nifty, eh?  Well, I hope you at least understand it...

   Good luck!