create a Windows shortcut that invokes PuTTY with a command line
like
-\c \path\name\to\putty.exe -load mysession
+\c \path\name\to\putty.exe -load "mysession"
(Note: prior to 0.53, the syntax was \c{@session}. This is now
deprecated and may be removed at some point.)
accident, and cause unexpected changes in the window title. Don't do
it.
-\S{faq-password-fails}{Question} My keyboard stops working once
-PuTTY displays the password prompt.
+\S{faq-password-fails}{Question} My \i{keyboard} stops working once
+PuTTY displays the \i{password prompt}.
No, it doesn't. PuTTY just doesn't display the password you type, so
that someone looking at your screen can't see what it is.
your screen can't even tell how \e{long} your password is, which
might be valuable information.
-\S{faq-keyboard}{Question} One or more function keys don't do what I
-expected in a server-side application.
+\S{faq-keyboard}{Question} One or more \I{keyboard}\i{function keys}
+don't do what I expected in a server-side application.
If you've already tried all the relevant options in the PuTTY
Keyboard panel, you may need to mail the PuTTY maintainers and ask.
The simplest way to investigate this is to find some other terminal
environment, in which that function key \e{does} work; and then
investigate what sequence the function key is sending in that
-situation. One reasonably easy way to do this on a Unix system is to
-type the command \c{cat}, and then press the function key. This is
+situation. One reasonably easy way to do this on a \i{Unix} system is to
+type the command \i\c{cat}, and then press the function key. This is
likely to produce output of the form \c{^[[11~}. You can also do
this in PuTTY, to find out what sequence the function key is
producing in that. Then you can mail the PuTTY maintainers and tell
also remove the delays, but would lose a \e{lot} more security
still. We do not recommend it.)
+\S{faq-xpwontrun}{Question} PuTTY fails to start up. Windows claims that
+\q{the application configuration is incorrect}.
+
+This is caused by a bug in certain versions of \i{Windows XP} which is
+triggered by PuTTY 0.58. It can be avoided by installing
+Service Pack 2, by using a different version of PuTTY, or by installing
+a special \i{manifest file} alongside the PuTTY executable.
+The
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/xp-wont-run}{\q{xp-wont-run}}
+entry in PuTTY's wishlist has more details.
+
\H{faq-secure} Security questions
\S{faq-publicpc}{Question} Is it safe for me to download PuTTY and