+ 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 help-emacs-windows@gnu.org
+ 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.