-\versionid $Id: using.but,v 1.23 2004/06/15 10:17:03 jacob Exp $
+\versionid $Id: using.but,v 1.29 2004/09/16 15:44:58 jacob Exp $
\C{using} Using PuTTY
\S{using-sysmenu} The \i{System menu}
If you click the left mouse button on the icon in the top left
-corner of PuTTY's window, or click the right mouse button on the
-title bar, you will see the standard Windows system menu containing
-items like Minimise, Move, Size and Close.
+corner of PuTTY's terminal window, or click the right mouse button
+on the title bar, you will see the standard Windows system menu
+containing items like Minimise, Move, Size and Close.
PuTTY's system menu contains extra program features in addition to
the Windows standard options. These extra menu commands are
you, you should mail the PuTTY authors \#{FIXME} and give details
(see \k{feedback}).
+For more options relating to X11 forwarding, see \k{config-ssh-x11}.
+
\H{using-port-forwarding} Using \i{port forwarding} in SSH
The SSH protocol has the ability to forward arbitrary network
remote-to-local port forwardings (so that machines other than the
SSH server machine can connect to the forwarded port.) Note that
this feature is only available in the SSH 2 protocol, and not all
-SSH 2 servers support it (OpenSSH 3.0 does not, for example).
+SSH 2 servers honour it (in OpenSSH, for example, it's usually
+disabled by default).
You can also specify an \i{IP address} to listen on. Typically a
Windows machine can be asked to listen on any single IP address in
support it for remote-to-local ports, while SSH2 can support it in
theory but servers will not necessarily cooperate.
+(Note that if you're using Windows XP Service Pack 2, you may need
+to obtain a fix from Microsoft in order to use addresses like
+\cw{127.0.0.5} - see \k{faq-alternate-localhost}.)
+
\H{using-rawprot} Making \i{raw TCP connections}
A lot of \I{debugging Internet protocols}Internet protocols are
\I{saved sessions, loading from command line}The \c{-load} option
causes PuTTY to load configuration details out of a saved session.
If these details include a host name, then this option is all you
-need to make PuTTY start a session (although Plink still requires an
-explicitly specified host name).
+need to make PuTTY start a session.
You need double quotes around the session name if it contains spaces.
\k{config-command}). However, the \c{-m} option expects to be given
a local file name, and it will read a command from that file. On
most Unix systems, you can even put multiple lines in this file and
-execute more than one command in sequence, or a whole shell script.
+execute more than one command in sequence, or a whole shell script;
+but this will not work on all servers (and is known not to work
+with certain \q{embedded} servers such as routers).
This option is not available in the file transfer tools PSCP and
PSFTP.