they contain their own method for the user to scroll back to the bit they were interested in. We have generally found this policy to do the Right Thing in almost all situations.
Unfortunately, screen is one exception: it uses the alternate screen, but it's still usually helpful to have PuTTY's scrollback continue working. The simplest solution is to go to the Features control panel and tick ‘Disable switching to alternate terminal screen’. (See
section 4.6.4
for more details.) Alternatively, you can tell screen itself not to use the alternate screen: the
screen FAQ
suggests
adding the line ‘termcapinfo xterm ti@:te@’ to your .screenrc file.
The reason why this only started to be a problem in 0.54 is because screen typically uses an unusual control sequence to switch to the alternate screen, and previous versions of PuTTY did not support this sequence.
A.7.20 Since I upgraded Windows XP to Service Pack 2, I can't use addresses like 127.0.0.2.
Some people who ask PuTTY to listen on localhost addresses other than 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
884020
. The article links to a
fix you can download.
(However, we've been told that SP2 also fixes the bug that means you need to use non-127.0.0.1 addresses to forward Terminal Services in the first place.)
A.7.21 PSFTP commands seem to be missing a directory separator (slash).
Some people have reported the following incorrect behaviour with PSFTP:
psftp> pwd
Remote directory is /dir1/dir2
psftp> get filename.ext
/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 (
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).
A.7.22 Do you want to hear about ‘Software caused connection abort’?
In the documentation for PuTTY 0.53 and 0.53b, we mentioned that we'd like to hear about any occurrences of this error. Since the release of PuTTY 0.54, however, we've been convinced that this error doesn't indicate that PuTTY's doing anything wrong, and we don't need to hear about further occurrences. See
section 10.14
for our current documentation of this error.
A.7.23 My SSH-2 session locks up for a few seconds every so often.
Recent versions of PuTTY automatically initiate repeat key exchange once per hour, to improve session security. If your client or server machine is slow, you may experience this as a delay of anything up to thirty seconds or so.
These delays are inconvenient, but they are there for your protection. If they really cause you a problem, you can choose to turn off periodic rekeying using the ‘Kex’ configuration panel (see
section 4.19
), but be aware that you will be sacrificing security for this.
(Falling back to SSH-1 would also remove the delays, but would lose a lot more security still. We do not recommend it.)
A.7.24 PuTTY fails to start up. Windows claims that ‘the application configuration is incorrect’.
This is caused by a bug in certain versions of Windows XP which is triggered by PuTTY 0.58. This was fixed in 0.59. The
‘xp-wont-
run’
entry in PuTTY's wishlist has more details.