\b The Unix/Gtk port is already fully working under Mac OS X as an X11
application.
-\b A native (Cocoa) Mac OS X port is in progress. It's just about
+\b A native (Cocoa) Mac OS X port has been started. It's just about
usable, but is of nowhere near release quality yet, and is likely to
-behave in unexpected ways.
+behave in unexpected ways. Currently it's unlikely to be completed
+unless someone steps in to help.
\b A separate port to the classic Mac OS (pre-OSX) is also in
progress; it too is not ready yet.
\H{faq-howto} HOWTO questions
+\S{faq-login}{Question} What login name / password should I use?
+
+This is not a question you should be asking \e{us}.
+
+PuTTY is a communications tool, for making connections to other
+computers. We maintain the tool; we \e{don't} administer any computers
+that you're likely to be able to use, in the same way that the people
+who make web browsers aren't responsible for most of the content you can
+view in them. \#{FIXME: less technical analogy?} We cannot help with
+questions of this sort.
+
+If you know the name of the computer you want to connect to, but don't
+know what login name or password to use, you should talk to whoever
+administers that computer. If you don't know who that is, see the next
+question for some possible ways to find out.
+
+\# FIXME: some people ask us to provide them with a login name
+apparently as random members of the public rather than in the
+belief that we run a server belonging to an organisation they already
+have some relationship with. Not sure what to say to such people.
+
\S{faq-commands}{Question} \I{commands on the server}What commands
can I type into my PuTTY terminal window?
-This is not a question you should be asking \e{us}. You need to read
-the manuals, or ask the administrator, of \e{the computer you have
-connected to}.
+Again, this is not a question you should be asking \e{us}. You need
+to read the manuals, or ask the administrator, of \e{the computer
+you have connected to}.
PuTTY does not process the commands you type into it. It's only a
communications tool. It makes a connection to another computer; it
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
the currently logged-in user on \i{multi-user systems}.)
If PuTTY was installed from the installer package, it will also
-appear in \q{Add/Remove Programs}.
-\#{XXX-REMOVE-BEFORE-RELEASE - replace with: Older versions of the uninstaller do not}
-Uninstallation does not currently
-remove the above-mentioned registry entries and file.
+appear in \q{Add/Remove Programs}. Older versions of the uninstaller
+do not remove the above-mentioned registry entries and file.
\S{faq-dsa}{Question} How come PuTTY now supports \i{DSA}, when the
website used to say how insecure it was?
\S{faq-pronounce}{Question} How do I pronounce \q{PuTTY}?
Exactly like the English word \q{putty}, which we pronounce
-/\u02C8{'}p\u028C{V}t\u026A{I}/.
+/\u02C8{'}p\u028C{V}ti/.
~mdw / sgt / putty / blobdiff