Mention the dangers of the "-pw" option.

[u/mdw/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 154fefb..752ac4b 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -1,4 +1,4 @@
-\versionid $Id: faq.but,v 1.68 2004/04/28 17:16:32 jacob Exp $
+\versionid $Id: faq.but,v 1.71 2004/05/26 09:19:48 jacob Exp $

 
 \A{faq} PuTTY FAQ
 
 
 \A{faq} PuTTY FAQ
 


@@ -80,6 +80,12 @@ option to be enabled or disabled as you choose. The controls are in
 the Terminal panel, in the section marked \q{Line discipline
 options}.
 
 the Terminal panel, in the section marked \q{Line discipline
 options}.
 

+\S{faq-savedsettings}{Question} Does PuTTY support storing settings,
+so I don't have to change them every time?
+
+Yes, all of PuTTY's settings can be saved in named session profiles.
+See \k{config-saving} in the documentation for how to do this.
+

 \S{faq-disksettings}{Question} Does PuTTY support storing its
 settings in a disk file?
 
 \S{faq-disksettings}{Question} Does PuTTY support storing its
 settings in a disk file?
 


@@ -559,8 +565,8 @@ In order to use Plink on these systems, you will need to download
 the
 \W{http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/}{WinSock 2 upgrade}:
 
 the
 \W{http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/}{WinSock 2 upgrade}:
 

-\c http://www.microsoft.com/windows95/downloads/contents/wuadmintools/
-\c   s_wunetworkingtools/w95sockets2/
+\c http://www.microsoft.com/windows95/downloads/contents/
+\c   wuadmintools/s_wunetworkingtools/w95sockets2/

 
 \S{faq-outofmem}{Question} After trying to establish an SSH 2
 connection, PuTTY says \q{Out of memory} and dies.
 
 \S{faq-outofmem}{Question} After trying to establish an SSH 2
 connection, PuTTY says \q{Out of memory} and dies.


@@ -667,12 +673,16 @@ This is a Windows problem, not a PuTTY problem. The timeout value
 can't be set on per application or per session basis. To increase
 the TCP timeout globally, you need to tinker with the Registry.
 
 can't be set on per application or per session basis. To increase
 the TCP timeout globally, you need to tinker with the Registry.
 

-On Windows 95, 98 or ME, the registry key you need to change is
+On Windows 95, 98 or ME, the registry key you need to create or
+change is

 
 \c HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\
 \c   MSTCP\MaxDataRetries
 
 (it must be of type DWORD in Win95, or String in Win98/ME).
 
 \c HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\
 \c   MSTCP\MaxDataRetries
 
 (it must be of type DWORD in Win95, or String in Win98/ME).

+(See MS Knowledge Base article
+\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;158474}{158474}
+for more information.)

 
 On Windows NT or 2000, the registry key is
 
 
 On Windows NT or 2000, the registry key is
 


@@ -680,6 +690,9 @@ On Windows NT or 2000, the registry key is
 \c   Parameters\TcpMaxDataRetransmissions
 
 and it must be of type DWORD.
 \c   Parameters\TcpMaxDataRetransmissions
 
 and it must be of type DWORD.

+(See MS Knowledge Base article
+\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;120642}{120642}
+for more information.)

 
 Set the key's value to something like 10. This will cause Windows to
 try harder to keep connections alive instead of abandoning them.
 
 Set the key's value to something like 10. This will cause Windows to
 try harder to keep connections alive instead of abandoning them.