--- a/man/xemacs-faq.texi	Mon Aug 13 10:57:57 2007 +0200
+++ b/man/xemacs-faq.texi	Mon Aug 13 10:58:40 2007 +0200
@@ -1,4 +1,4 @@
-\input texinfo.tex      @c -*-texinfo-*-
+\input texinfo.tex      @c -*- mode: texinfo; coding: iso-2022-8 -*-
 @c %**start of header
 @setfilename ../info/xemacs-faq.info
 @settitle Frequently asked questions about XEmacs
@@ -7,7 +7,7 @@
 @finalout
 @titlepage
 @title XEmacs FAQ
-@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 1999/12/08 01:33:17 $
+@subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2000/03/04 17:13:15 $
 @sp 1
 @author Tony Rossini <arossini@@stat.sc.edu>
 @author Ben Wing <ben@@xemacs.org>
@@ -405,6 +405,9 @@
 * Q6.3.2::	What are the differences between the various MS Windows emacsen?
 * Q6.3.3::	What is the porting team doing at the moment?
 
+Troubleshooting:
+* Q6.4.1::      XEmacs won't start on Windows. (NEW)
+
 Current Events:
 
 * Q7.0.1::      What is new in 20.2?
@@ -6225,6 +6228,9 @@
 * Q6.3.2::	What are the differences between the various MS Windows emacsen?
 * Q6.3.3::	What is the porting team doing at the moment?
 
+Troubleshooting:
+* Q6.4.1::      XEmacs won't start on Windows. (NEW)
+
 @end menu
 
 @node Q6.0.1, Q6.0.2, MS Windows, MS Windows
@@ -6555,11 +6561,31 @@
 @end itemize
 
 
-@node Q6.3.3, , Q6.3.2, MS Windows
+@node Q6.3.3, Q6.4.1, Q6.3.2, MS Windows
 @unnumberedsubsec Q6.3.3: What is the porting team doing at the moment?
 
 The porting team is continuing work on the MS Windows-specific code.
 
+@node Q6.4.1, ,Q6.3.3, MS Windows
+@unnumberedsec 6.3: Troubleshooting
+@unnumberedsubsec Q6.4.1 XEmacs won't start on Windows. (NEW)
+
+XEmacs relies on a process called "dumping" to generate a working
+executable. Under MS-Windows this process effectively fixes the memory
+addresses of information in the executable. When XEmacs starts up it tries
+to reserve these memory addresses so that the dumping process can be
+reversed - putting the information back at the correct addresses.
+Unfortunately some .dlls (For instance the soundblaster driver) occupy
+memory addresses that can conflict with those needed by the dumped XEmacs
+executable. In this instance XEmacs will fail to start without any
+explanation. Note that this is extremely machine specific.
+
+Work is being done on fixes for 21.1.* that will make more intelligent
+guesses about which memory addresses will be free and so this should
+cure the problem for most people.
+
+21.2 implements "portable dumping" which will eliminate the problem
+altogether.
 
 @node Current Events,  , MS Windows, Top
 @unnumbered 7 What the Future Holds