-\versionid $Id: faq.but,v 1.13 2001/12/04 19:12:04 simon Exp $
+\versionid $Id: faq.but,v 1.17 2002/01/02 15:44:06 simon Exp $
\A{faq} PuTTY FAQ
Not in the 0.51 release, but it has been added since then.
-\S{faq-password}{Question} Does PuTTY have the ability to remember
-my password so I don't have to type it every time?
+\S{faq-password-remember}{Question} Does PuTTY have the ability to
+remember my password so I don't have to type it every time?
No, it doesn't.
However, PuTTY on portable devices would clearly be a useful thing,
so in the long term I hope there will be a WinCE port.
-\S{faq-mac}{Question} Will there be a port to the Mac?
+\S{faq-win31}{Question} Is there a port to Windows 3.1?
+
+PuTTY is a 32-bit application from the ground up, so it won't run on
+Windows 3.1 as a native 16-bit program; and it would be \e{very}
+hard to port it to do so, because of Windows 3.1's vile memory
+allocation mechanisms.
+
+However, it is possible in theory to compile the existing PuTTY
+source in such a way that it will run under Win32s (an extension to
+Windows 3.1 to let you run 32-bit programs). In order to do this
+you'll need the right kind of C compiler - modern versions of Visual
+C at least have stopped being backwards compatible to Win32s. Also,
+the last time we tried this it didn't work very well.
+
+If you're interested in running PuTTY under Windows 3.1, help and
+testing in this area would be very welcome!
+
+\S{faq-mac-port}{Question} Will there be a port to the Mac?
A Mac port was started once and is half-finished, but development
has been static for some time and the main PuTTY code has moved on,
\H{faq-trouble} Troubleshooting
-\S{faq-mac}{Question} Why do I see \q{Incorrect MAC received on
-packet}?
+\S{faq-incorrect-mac}{Question} Why do I see \q{Incorrect MAC
+received on packet}?
This is due to a bug in old SSH 2 servers distributed by
\cw{ssh.com}. Version 2.3.0 and below of their SSH 2 server
your terminal is likely to cause various other unpleasant behaviour,
so this is only a small remedy.
-\S{faq-puttyputty}{Question} When I \cw{cat} a binary file, my
-window title changes to a nonsense string.
+\S{faq-wintitle}{Question} When I \cw{cat} a binary file, my window
+title changes to a nonsense string.
Don't do that, then.
accident, and cause unexpected changes in the window title. Don't do
it.
-\S{faq-password}{Question} My keyboard stops working once PuTTY
-displays the password prompt.
+\S{faq-password-fails}{Question} My keyboard stops working once
+PuTTY displays the 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.
+
+If you've already tried all the relevant options in the PuTTY
+Keyboard panel, you may need to mail the PuTTY maintainers and ask.
+
+It is \e{not} usually helpful just to tell us which application,
+which server operating system, and which key isn't working; in order
+to replicate the problem we would need to have a copy of every
+operating system, and every application, that anyone has ever
+complained about.
+
+PuTTY responds to function key presses by sending a sequence of
+control characters to the server. If a function key isn't doing what
+you expect, it's likely that the character sequence your application
+is expecting to receive is not the same as the one PuTTY is sending.
+Therefore what we really need to know is \e{what} sequence the
+application is expecting.
+
+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
+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
+us \q{I wanted the F1 key to send \c{^[[11~}, but instead it's
+sending \c{^[OP}, can this be done?}, or something similar.
+
+You should still read the
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html}{Feedback
+page} on the PuTTY website (also provided as \k{feedback} in the
+manual), and follow the guidelines contained in that.
+
\H{faq-secure} Security questions
\S{faq-publicpc}{Question} Is it safe for me to download PuTTY and
something worthwhile, ask us first. If you don't like these terms,
feel perfectly free not to donate. We don't mind.
+\S{faq-sillyputty}{Question} Where can I buy silly putty?
+
+You're looking at the wrong web site; the only PuTTY we know about
+here is the name of a computer program.
+
+If you want the kind of putty you can buy as an executive toy, the
+PuTTY team can personally recommend Thinking Putty, which you can
+buy from Crazy Aaron's Putty World, at
+\W{http://www.puttyworld.com}\cw{www.puttyworld.com}.
+
\S{faq-pronounce}{Question} How do I pronounce PuTTY?
Exactly like the normal word \q{putty}. Just like the stuff you put
projects / PuTTY.git / blobdiff