--- gforth/INSTALL.DOS	1995/12/11 13:15:18	1.1
+++ gforth/INSTALL.DOS	1996/11/07 22:31:32	1.4
@@ -1,46 +1,42 @@
-You need DJ Delorie's port of GCC to DOS (DJGPP) to compile Gforth. DJGPP
-provides a DOS extender (GO32) that allows to use the 32-bit features of
-the 80386, but on the other hand it requires at least an 386.
-
-Gforth hasn't been tested with EMX, using EMX will require some changes in
-the console IO part. If you don't want to install this package (quite
-large), look for a binary distribution of Gforth for DOS. You must have a
-version of GNU make, because DOS make programs are likely to have problems
-with the Makefile. If you want to change Gforth, you may need GNU m4, too.
+You need DJ Delorie's port of GCC to DOS (DJGPP 2.0) to compile
+Gforth. DJGPP provides a DPMI client that allows to use the 32-bit
+features of the 80386, but on the other hand it requires at least a
+386. A DPMI host is also part of the DJGPP 2.0 package, this is
+required if you don't have a DPMI host yourself (Windows/OS/2/Linux
+DOS-box, Quemm or others).
+
+Gforth hasn't been tested with EMX, using EMX will require some
+changes in the console IO part. For OS/2 EMX supports POSIX-style tty,
+so it might just compile out of the box. If you don't want to install
+the DJGPP package (quite large), look for a binary distribution of
+Gforth for DOS. You also must have a version of GNU make, because DOS
+make programs are likely to have problems with the Makefile. If you
+want to change Gforth, you may need GNU m4, too. Because DJGPP
+provides use of long filenames under Windows 95, you should unpack the
+gforth package with a Windows-95-aware archiver (those from DJGPP come
+in mind), because otherwise gforth will not find the necessary
+files. There is no such problem when using MS-DOS prior 7.x.
 
 If you don't bother and want to make it yourself, type
 
 configure
 
-There are no options for configure, because DOS can't execute a real
-configure script, all the configuring stuff is done on a real operating
-system. If you want to change something (e.g. use FORCE_REG or
-DIRECT_THREADED), you have to change the makefile yourself. Be careful! DOS
-command line arguments are limited to an overall size of 126 bytes, so
-adding a new define in the makefile will make it too long. In this case add
-the define at the beginning of machine.h instead, or create a file
-containing all extra options, and add @<filename> to the defines (move the
--DDEFAULTPATH-define into this file, and it will fit into the command line).
+configure has the following useful parameters:
+  --enable-force-reg      Use explicit register declarations if they appear in
+                          the machine.h file. This can cause a good speedup,
+                          but also incorrect code with some gcc versions on
+                          some processors (default disabled).
+  --enable-direct-threaded      Force direct threading. This may not work on
+                                some machines and may cause slowdown on others.
+                                (default disabled)
+  --enable-indirect-threaded    Force indirect threading. This can cause a
+                                slowdown on some machines.
+                                (default enabled)
 
 After covering all inconveniences, type
 
-make gforth
-
-and after this finishes, type
-
 make
 
-We apologize for the inconveniences, we did not invent the 640k limit
-that prevents doing make straight forward. You may run out of memory
-anyway, because GCC eats up lots of it while compiling engine.c. Keep
-enough space free on your harddisk to allow GCC to swap.
-
-If you want to add some defines like -DFORCE_REG, type
-
-make gforth XDEFINES=-DFORCE_REG
-
-instead.
-
 Now you can check whether your shiny new Forth system works. Say
 
 make test
@@ -57,11 +53,11 @@ command lines.
 
 Add the following entry to your Autoexec.bat:
 
-SET GFORTHPATH=<your gforth source directory>:.
+SET GFORTHPATH=<your gforth source directory>;.
 
-Use / instead of \ in your gforth source directory.  Another problem
-is, that Gforth uses : as path separator, and DOS pathes may look like
-D:/gforth.  Sorry, there is no workaround for this now.
+Use / instead of \ in your gforth source directory. Gforth now uses
+';' as path separator, so you won't have problems with DOS pathes that
+may contain ':', which is the default path separator in Unix.
 
 For paper documentation, print gforth.ps (a Postscript file (300dpi
 fonts, i.e., it works, but does not produce best quality on better