--- gforth/INSTALL	1995/11/07 18:06:29	1.11
+++ gforth/INSTALL	1995/11/29 20:20:32	1.15
@@ -28,39 +28,81 @@ configure has the following useful param
 If you don't like the defaults for the installation directories, you
 should override them already during configure.  E.g., if you want to
 install in the /gnu hierarchy instead of in the default /usr/local
-hirarchy, say
+hierarchy, say
 
 ./configure --prefix=/gnu
 
+Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you
+should say so during configuration:
+
+env GCC=gcc-2.7.1 ./configure
+
 After, configuration, type
 
 make
 
-If your make has trouble with the Makefile, "make gforth" might work.
+Now you can check whether your shiny new Forth system works. Say
 
-If your installed gcc isn't called "gcc" (e.g., called "gcc-2.6.1"), type
+make test
 
-make GCC=<whatever you call your gcc>
+You can run some benchmarks with
 
-instead.
+make bench
 
-Now you can check whether your shiny new Forth system works. Say
+and compare them with the results in Benchres and in the manual.
 
-make test
+If everything is all right, you may want to install gforth. Type
+
+make install
 
-To make the documentation, type
+You have to make an entry in the info directory file manually.
 
-make -k gforth.info gforth.ps html
+For paper documentation, print gforth.ps (a Postscript file (300dpi
+fonts, i.e., it works, but does not produce best quality on better
+printers)), or say
 
-If everything is allright, you may want to install gforth. Type
+make gforth.dvi
 
-make install
+and print the resulting file gforth.dvi. You can also get the
+documentation in HTML format by typing
+
+make html
+
+
+		Preloading installation-specific code
+
+If you want to have some installation-specific files loaded when
+Gforth starts (e.g., an assembler for your processor), put commands
+for loading them into /usr/local/share/gforth/site-forth/site-init.fs
+(if the commands work for all architectures) or
+/usr/local/lib/gforth/site-forth/site-init.fs (for
+architecture-specific commands);
+/usr/local/lib/gforth/site-forth/site-init.fs takes precedence if both
+files are present (unless you change the search path). The file names
+given above are the defaults; if you have changed the prefix, you have
+to replace "/usr/local" in these names with your prefix.
+
+By default, the installation procedure creates an empty
+/usr/local/share/gforth/site-forth/site-init.fs if there is no such
+file.
+
+If you change the site-init.fs file, you should run "make install"
+again for the changes to take effect (Actually, the part of "make
+install" starting with "rm gforth.fi" is sufficient).
+
+
+		Multiple Versions and Deinstallation
+
+Several versions of Gforth can be installed and used at the same
+time. Version `foo' can be invoked with `gforth-foo'. We recommend to
+keep the old version for some time after a new one has been installed.
 
-You have to make an entry in the info directory file manually. Also,
-you have to install gforth.ps and html yourself.
+You can deinstall this version of Gforth with 'make uninstall' and
+version foo with 'make uninstall VERSION=foo'. 'make uninstall' also
+tells you how to uninstall Gforth completely.
 
 
-A possible problem:
+			A Possible Problem
 
 You need to read this only if you see a message like