--- gforth/INSTALL.DOS	1996/10/06 22:24:13	1.3
+++ gforth/INSTALL.DOS	1996/12/06 20:23:03	1.5
@@ -1,3 +1,5 @@
+MS-DOS:
+
 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
@@ -5,11 +7,28 @@ features of the 80386, but on the other
 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. If you don't want to install the DJGPP 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.
+OS/2:
+
+You need EMX 0.9c to compile Gforth. The EMX package provides all
+necessary Unix-like tools, tty and signal handling.
+
+If you don't want to install the DJGPP or EMX package (quite large),
+look for a binary distribution of Gforth for DOS or OS/2. You also
+must have a version of GNU make, because DOS/OS/2 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 or the Cygnus
+Win32-package come in mind), because otherwise gforth will not find
+the necessary files. With MS-DOS versions prior 7.0 or DR-DOS, these
+names are cut due to the 8.3 rule. This might confuse DJGPP 2.0's
+make, you could use DJGPP 1.x's make instead. Gforth 0.2.0 hasn't been
+compiled with a MS-DOS prior 7.0.
+
+Compiling under DOS or OS/2 has a number of quirks, and if it doesn't
+compile out of the box, you should know what you do. I therefore
+discourage unexperienced users to compile gforth themselfes. There's a
+binary package for it anyway.
 
 If you don't bother and want to make it yourself, type
 
@@ -22,10 +41,10 @@ configure has the following useful param
                           some processors (default disabled).
   --enable-direct-threaded      Force direct threading. This may not work on
                                 some machines and may cause slowdown on others.
-                                (default processor-dependent)
+                                (default disabled)
   --enable-indirect-threaded    Force indirect threading. This can cause a
                                 slowdown on some machines.
-                                (default processor-dependent)
+                                (default enabled)
 
 After covering all inconveniences, type
 
@@ -50,8 +69,8 @@ Add the following entry to your Autoexec
 SET GFORTHPATH=<your gforth source directory>;.
 
 Use / instead of \ in your gforth source directory. Gforth now uses
-';' as path separator, so you won't have problems DOS pathes that may
-contain ':', which is the default path separator in Unix.
+';' 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
@@ -61,6 +80,6 @@ make gforth.dvi
 
 and print the resulting file gforth.dvi (you need TeX for that! But
 with TeX you can print it even if you don't have a Postscript printer
-nor Ghostscript).  You could be able to make a html version of the
+nor Ghostscript).  You could be able to make a HTML version of the
 document, but AFAIK there is no texi2html for DOS available, as there
 is no perl available.