Remove obsolete information from Speed.sgml and move client-specific

info to Other-Clients.sgml
(This used to be commit b0d5e1b177808c3bd3494d0b2f6cf4c8c4bcfdd5)

1 files changed, 31 insertions, 1 deletions

diff --git a/docs/docbook/projdoc/Other-Clients.sgml b/docs/docbook/projdoc/Other-Clients.sgml
index 6177b4dcb6..73316927e0 100644
--- a/docs/docbook/projdoc/Other-Clients.sgml
+++ b/docs/docbook/projdoc/Other-Clients.sgml
@@ -168,7 +168,8 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 <title>Use latest TCP/IP stack from Microsoft</title>
 
 <para>Use the latest TCP/IP stack from microsoft if you use Windows
-for workgroups.</para>
+for workgroups. 
+</para>
 
 <para>The early TCP/IP stacks had lots of bugs.</para>
 
@@ -234,6 +235,24 @@ it may break the print queue reporting on some systems.
 It is presumably a WfWg bug.</para>
 
 </sect2>
+
+<sect2>
+<title>Speed improvement</title>
+
+<para>
+Note that some people have found that setting DefaultRcvWindow in
+the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
+big improvement. I don't know why.
+</para>
+
+<para>
+My own experience wth DefaultRcvWindow is that I get much better
+performance with a large value (16384 or larger). Other people have
+reported that anything over 3072 slows things down enourmously. One
+person even reported a speed drop of a factor of 30 when he went from
+3072 to 8192. I don't know why.
+</para>
+</sect2>
 </sect1>
 
 <sect1>
@@ -266,6 +285,17 @@ OutLook and you may also notice a significant speedup when accessing network
 neighborhood services.
 </para>
 
+<sect2>
+<title>Speed improvement</title>
+
+<para>
+Configure the win95 TCPIP registry settings to give better
+performance. I use a program called MTUSPEED.exe which I got off the
+net. There are various other utilities of this type freely available.
+</para>
+
+</sect2>
+
 </sect1>
 
 <sect1>