X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/270bd74191d1d681facc421907a1d0a928f3151d..811527db4fcb81534664f876beede7d84b6e307f:/doc/faq.but diff --git a/doc/faq.but b/doc/faq.but index b3409b3c..adf98151 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -1,4 +1,4 @@ -\versionid $Id: faq.but,v 1.69 2004/04/28 17:26:15 jacob Exp $ +\versionid $Id: faq.but,v 1.80 2004/09/22 14:07:35 jacob Exp $ \A{faq} PuTTY FAQ @@ -307,7 +307,7 @@ a new system and doing the port for that. However, some of the work has been done by other people, and a beta port of PuTTY for the Nokia 9200 Communicator series is available -from \W{http://www.s2.org/putty/}\cw{http://www.s2.org/putty/} +from \W{http://s2putty.sourceforge.net/}\cw{http://s2putty.sourceforge.net/} \H{faq-embedding} Embedding PuTTY in other programs @@ -364,8 +364,8 @@ to say something else; \c{vt220} might help if you have trouble. \S{faq-settings}{Question} Where does PuTTY store its data? -PuTTY stores most of its data (saved sessions, SSH host keys) in the -Registry. The precise location is +On Windows, PuTTY stores most of its data (saved sessions, SSH host +keys) in the Registry. The precise location is \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY @@ -383,6 +383,8 @@ pathname in the Registry, at \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile +On Unix, PuTTY stores all of this data in a directory \cw{~/.putty}. + \H{faq-howto} HOWTO questions \S{faq-startmax}{Question} How can I make PuTTY start up maximised? @@ -565,8 +567,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}: -\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. @@ -625,8 +627,8 @@ areas of black space where colour ought to be. You almost certainly need to enable the \q{Use background colour to erase screen} setting in the Terminal panel. Note that if you do -this in mid-session, it may not take effect until you reset the -terminal (see \k{faq-resetterm}). +this in mid-session, in versions before 0.54, it may not take effect +until you reset the terminal (see \k{faq-resetterm}). \S{faq-resetterm}{Question} When I change some terminal settings, nothing happens. @@ -673,12 +675,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. -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). +(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 @@ -686,6 +692,9 @@ On Windows NT or 2000, the registry key is \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. @@ -858,6 +867,50 @@ The reason why this only started to be a problem in 0.54 is because the alternate screen, and previous versions of PuTTY did not support this sequence. +\S{faq-alternate-localhost}{Question} Since I upgraded Windows XP +to Service Pack 2, I can't use addresses like \cw{127.0.0.2}. + +Some people who ask PuTTY to listen on localhost addresses other +than \cw{127.0.0.1} to forward services such as SMB and Windows +Terminal Services have found that doing so no longer works since +they upgraded to WinXP SP2. + +This is apparently an issue with SP2 that is acknowledged by Microsoft +in MS Knowledge Base article +\W{http://support.microsoft.com/default.aspx?scid=kb;en-us;884020}{884020}. + +For a fix, you'll need to contact Microsoft support, as mentioned in +the KB article. We've been told that the process is reasonably easy, +and is free of charge; and that the fix will be included in the next +Windows XP Service Pack (but probably not before). + +(\e{However}, we've been told that SP2 \e{also} fixes the bug that +means you need to use non-\cw{127.0.0.1} addresses to forward +Terminal Services in the first place.) + +\S{faq-missing-slash}{Question} PSFTP commands seem to be missing a +directory separator (slash). + +Some people have reported the following incorrect behaviour with +PSFTP: + +\c psftp> pwd +\e iii +\c Remote directory is /dir1/dir2 +\c psftp> get filename.ext +\e iiiiiiiiiiiiiiii +\c /dir1/dir2filename.ext: no such file or directory + +This is not a bug in PSFTP. There is a known bug in some versions of +portable OpenSSH +(\W{http://bugzilla.mindrot.org/show_bug.cgi?id=697}{bug 697}) that +causes these symptoms; it appears to have been introduced around +3.7.x. It manifests only on certain platforms (AIX is what has been +reported to us). + +There is a patch for OpenSSH attached to that bug; it's also fixed in +recent versions of portable OpenSSH (from around 3.8). + \H{faq-secure} Security questions \S{faq-publicpc}{Question} Is it safe for me to download PuTTY and