diff --git a/twander.1 b/twander.1
index f486828..ebea098 100644
--- a/twander.1
+++ b/twander.1
@@ -1474,7 +1474,39 @@
 There are several tricky corners of \'twander\' which need
 further explanation:
 
-.B 1) Getting Command Results Displayed In A New Window
+.B \'twander\' Will Not Enter Certain Directories On Win32
+
+Win32 allows file/directory names to contain non-ASCII
+characters.  Python, as shipped, defaults to ASCII only
+and grumbles mightily when it is asked to deal with a string
+containing characters with ordinal values greater than
+127 (i.e., 8-Bit "extended" ASCII).  The solution to this
+problem is to enable Python to handle non-ASCII strings.
+This is done by editing a file called "site.py".  This
+file is normally found in:
+
+.nf
+C:\\Program Files\\PythonXX\\Lib
+.fi
+
+Where "XX" is the actual version of Python you're running.
+
+Open this file with an editor and look for the following
+text:
+
+.nf
+encoding = "ascii" # Default value set by _PyUnicode_Init()
+
+if 0:
+    # Enable to support locale aware default string encodings.
+    import locale
+.fi
+
+Change the "if 0:" statement to "if 1:" and the problem
+will disappear.
+
+
+.B Getting Command Results Displayed In A New Window
 
 When you invoke a command via \'twander\', whether via a command
 definition in the Configuration File or the keyboard shortcut, you
@@ -1514,7 +1546,7 @@
 This is not so much of an issue on Win32 systems where the first
 form of the command above works fine.
 
-.B 2) Modal Operation Of New Windows
+.B Modal Operation Of New Windows
 
 Notice our example commands above do not end with "&". 
 These should not be needed on either Unix-like or Win32
@@ -1524,17 +1556,21 @@
 continue using \'twander\' while the new command executes.
 If not (\'twander\' is locked out while the new command runs -
 so-called "modal" operation), it means your system does not
-completely or correctly implement threading.  In that case,
-if you want non-modal command operation, try adding a "&" at
-the end of your Command Definition.
+completely or correctly implement threading.  In this case,
+try adding this statement to your Configuration File:
+"USETHREADS=False" which will force \'twander\' to 
+invoke new commands using conventional (heavyweight) process
+spawning.
 
-.B 3) Windows That Don't Disappear On Command Completion
+.B Windows That Don't Disappear On Command Completion
 
 It appears that some X Windows implementations (noted on XFree86 /
 FreeBSD) do not correctly destroy an \'xterm\' window after a command
 initiated with -e terminates.  This is not a \'twander\' problem.  The
-workaround is to manually kill the window or press enter once when
-the command is complete and the window has input focus.
+workaround is to add the following statement to your Configuration
+File: "USETHREADS=False" This forces conventional (heavyweight)
+process spawning when a command is run.  This mechanism correctly
+destroys the window upon command completion.
 
 
 .SH OTHER