Replace outdated information.

1 files changed, 58 insertions, 42 deletions

diff --git a/nt/README b/nt/README
index 4db11487553..ce04b839f43 100644
--- a/nt/README
+++ b/nt/README
@@ -1,60 +1,76 @@
-                 Emacs for Windows NT and Windows 95
+             Emacs for Windows NT/2000 and Windows 95/98/ME
 
-This directory contains support for compiling and running GNU Emacs on
-Windows NT and Windows 95.  This port supports all of the major
-functionality of the Unix version, including subprocesses, windowing
-features (fonts, colors, scroll bars, multiple frames, etc.), and
-networking support.
+  This directory contains support for compiling and running GNU Emacs on
+  Windows NT, Windows 95, and their successors.  This port supports all
+  of the major functionality of the Unix version, including
+  subprocesses, windowing features (fonts, colors, scroll bars, multiple
+  frames, etc.), and networking support.
 
-Precompiled distributions are also available; ftp to
+  Precompiled distributions are also available; ftp to
 
-        ftp://ftp.cs.washington.edu/pub/ntemacs/latest
+        ftp://ftp.gnu.org/gnu/windows/emacs/latest/
 
-for the latest precompiled distributions.
-
-* Preliminaries
-
-To compile Emacs, you will need either Microsoft Visual C++ 2.0 or
-later, or a Windows port of GCC 2.95 or later with Mingw and W32 API
-support and a port of GNU make.  You can use the Cygwin ports of GCC,
-but Emacs requires the Mingw headers and libraries to build.
+  for the latest precompiled distributions.
 
 * Building and installing
 
-See the INSTALL file in this directory for detailed instructions on
-building and installing Emacs on your system.
+  See the INSTALL file in this directory for detailed instructions on
+  building and installing Emacs on your system.
 
 * Further information
 
-If you have access to the World Wide Web, I would recommend pointing
-your favorite web browser to the document (if you haven't already):
+  There is a web page that serves as a FAQ at:
 
-        http://www.cs.washington.edu/homes/voelker/ntemacs.html
+        http://www.gnu.org/software/emacs/windows/ntemacs.html
 
-This web document serves as a FAQ and a source for further information
-about the port and related software packages.
+  There is also a mailing list for discussing issues related to this
+  port of Emacs.  For information about the list, send a message to
+  ntemacs-users-request@cs.washington.edu with the word "info" in the
+  *body* of the message.  To subscribe to the list, send a message to
+  the same address with the word "subscribe" in the body of the message;
+  similarly, to unsubscribe from the list, send a message with the word
+  "unsubscribe" in the message body.
 
-There is also a mailing list for discussing issues related to this
-port of Emacs.  For information about the list, send a message to
-ntemacs-users-request@cs.washington.edu with the word "info" in the
-*body* of the message.  To subscribe to the list, send a message to
-the same address with the word "subscribe" in the body of the message;
-similarly, to unsubscribe from the list, send a message with the word
-"unsubscribe" in the message body.
+  Another valuable source of information and help which should not be
+  overlooked is the various Usenet news groups dedicated to Emacs.
+  These are particuarly good for help with general issues which aren't
+  specific to the Windows port of Emacs.  The main news groups to use
+  for seeking help are:
 
-You are also always welcome to send me mail directly.  If you don't
-hear from me immediately, however, don't worry; it sometimes takes me
-a few days (or longer) to get to all of my mail regarding Emacs.
+        gnu.emacs.help
+        comp.emacs
 
-* Reporting bugs
+  There are also fairly regular postings and announcements of new or
+  updated Emacs packages on this group:
 
-If you encounter bugs in this port of Emacs, first check the FAQ on
-the web page above to see if the bug is already known and if there are
-any workarounds.  If not, then I would like to hear about it; either
-send a bug report to the mailing list, or to me directly (I would
-recommend sending to the list first).
+        gnu.emacs.sources
 
-Enjoy.
+  You are also always welcome to send me mail directly.  If you don't
+  hear from me immediately, however, don't worry; it sometimes takes me
+  a few days (or longer) to get to all of my mail regarding Emacs.
+
+* Reporting bugs
 
--geoff
-(voelker@cs.washington.edu)
+  If you encounter a bug in this port of Emacs, we would like to hear
+  about it.  First check the file etc/PROBLEMS and the FAQ on the web
+  page above to see if the bug is already known and if there are any
+  workarounds.  If not, then check whether the bug has something to do
+  with code in your .emacs file, e.g. by invoking Emacs with the "-q
+  --no-site-file" options.
+
+  If you decide that it is a bug in Emacs that might be specific to the
+  Windows port, send a message to the ntemacs-users@cs.washington.edu
+  mailing list describing the bug, the version of Emacs that you are
+  using, and the operating system that you are running on (Windows NT,
+  95 or 98 including service pack level if known).  If the bug is
+  related to subprocesses, also specify which shell you are using (e.g.,
+  include the values of `shell-file-name' and `shell-explicit-file-name'
+  in your message).
+
+  If you think the bug is not specific to the Windows port of Emacs,
+  then it is better to mail the bug report to bug-gnu-emacs@gnu.org so
+  that it will be seen by the right people.  If Emacs has been set up to
+  send mail, you can use the command M-x report-emacs-bug to create and
+  send the bug report, but in some cases there is a function to report
+  bugs in a specific package; e.g. M-x gnus-bug for Gnus, M-x
+  c-submit-bug-report for C/C++/Java mode, etc.