1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-05-28 23:34:49 -05:00
Simon Tatham 72ff571148 Major destabilisation, phase 2. This time it's the backends' turn:
each backend now stores all its internal variables in a big struct,
and each backend function gets a pointer to this struct passed to
it. This still isn't the end of the work - lots of subsidiary things
still use globals, notably all the cipher and compressor modules and
the X11 forwarding authentication stuff. But ssh.c itself has now
been transformed, and that was the really painful bit, so from here
on it all ought to be a sequence of much smaller and simpler pieces
of work.

[originally from svn r2127]
2002-10-25 11:30:33 +00:00
2002-03-16 18:19:31 +00:00
2000-03-17 11:23:33 +00:00
2001-05-13 14:02:28 +00:00
2002-10-23 14:24:40 +00:00
1999-01-08 13:02:13 +00:00
2000-10-20 09:50:56 +00:00
1999-01-08 13:02:13 +00:00
1999-08-31 09:20:48 +00:00
1999-08-31 09:20:48 +00:00
2001-09-25 19:59:14 +00:00
2001-05-13 14:02:28 +00:00
2001-12-11 18:47:35 +00:00

PuTTY README
============

This is the README file for the PuTTY installer distribution. If
you're reading this, you've probably just run our installer and
installed PuTTY on your system.

What should I do next?
----------------------

If you want to use PuTTY to connect to other computers, or use PSFTP
to transfer files, you should just be able to run them from the
Start menu.

If you want to use the command-line-only file transfer utility PSCP,
you will probably want to put the PuTTY installation directory to be
on your PATH. How you do this depends on your version of Windows. On
Windows NT and 2000, you can set it using Control Panel > System; on
Windows 95 you will need to edit AUTOEXEC.BAT. Consult your Windows
manuals for details.

What do I do if it doesn't work?
--------------------------------

The PuTTY home web site is

    http://www.chiark.greenend.org.uk/~sgtatham/putty/

Here you will find our list of known bugs and pending feature
requests. If your problem is not listed in there, or in the FAQ, or
in the manuals, read the Feedback page to find out how to report
bugs to us. PLEASE read the Feedback page carefully: it is there to
save you time as well as us. Do not send us one-line bug reports
telling us `it doesn't work'.
Description
No description provided
Readme 340 MiB
Languages
C 89.7%
Python 8%
Perl 0.9%
CMake 0.8%
Shell 0.4%
Other 0.1%