--- gforth/INSTALL	1997/02/01 14:59:27	1.26
+++ gforth/INSTALL	1997/03/20 14:39:48	1.27
@@ -154,74 +154,3 @@ keep the old version for some time after
 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
-
-You need to read this only if you see a message like
-
-...
-The Gforth installer should look into the INSTALL file
-
-1) "gforth: Cannot load nonrelocatable image (compiled for address $1234) at address $5678
-The Gforth installer should look into the INSTALL file"
-
-Gforth supports both relocatable and fixed-address images. If you load
-normal Forth code and save the image, you get a fixed-address
-image. Producing a relocatable image is more difficult.
-
-Therefore, Gforth has only a relocatable image of the kernel
-(kernel.fi), which is powerful enough to load the rest of
-Gforth. However, loading the rest takes a noticable amount of time. To
-avoid this delay (which would occur on every startup), the
-installation procedure produces an image fixed at an address
-determined at the Gforth run that produced the image. This
-fixed-address image is loaded by default. On most OSs this works,
-because the first chunk of memory is always allocated at the same
-address. If the address changes, you get the message above.
-
-An image address change can be caused by a change of the gforth
-executable, or by a change (upgrade) of the OS; in these cases you
-just have to rebuild and reinstall the fixed address image with
-
-rm gforth.fi; make gforth.fi; make install
-
-If you get such a message with a different address in place of the
-$5678 each time you try to start gforth, you cannot use fixed-address
-images on your OS. In this case, send us a message so that we start
-searching for a comfortable solution to this problem. In the
-meantime, start gforth with
-
-gforth -i kernel.fi startup.fs
-
-If the addresses changes by only a small amount (e.g. by one or two
-pages), you can fix it by defining FUZZ (in config.h) to a number at
-least two times the changes you observe (0x4000 is a good idea, this
-is four 4k pages) and recompile. We do this for the DJGPP port for
-DOS, because the start address there changes by one or two pages, and
-it helps us to keep the DOS people happy without investing too much
-work in a braindead environment.
-
-
-2) "%s: Checksum of image ($13579b) does not match the executable ($2468a)
-The Gforth installer should look into the INSTALL file"
-
-A fixed-address image is not only fixed with respect to its base
-address, but also with respect to certain addresses in the gforth
-executable and the threading method. These things are encoded in a
-checksum.
-
-If the checksum of the executable and the checksum of the image are
-not equal, you get the message above. This can be caused, e.g., by
-trying to run an image produced for a direct threading system on an
-indirect threaded system.
-
-Chances are that you unintentionally tried to execute an image from
-the wrong directory. As a remedy, you can specify Gforth's search
-path with the "-p" command line option and with the GFORTHPATH
-environment variable.
-
-On the other hand, if you need to solve the problem by creating a new
-fixed-address image, you can use the steps described above.
-
-