putty/windows
Simon Tatham 19fba3fe55 Replace the hacky 'OSSocket' type with a closure.
The mechanism for constructing a new connection-type Socket when a
listening one receives an incoming connection previously worked by
passing a platform-specific 'OSSocket' type to the plug_accepting
function, which would then call sk_register to wrap it with a proper
Socket instance. This is less flexible than ideal, because it presumes
that only one kind of OS object might ever need to be turned into a
Socket. So I've replaced OSSocket throughout the code base with a pair
of parameters consisting of a function pointer and a context such that
passing the latter to the former returns the appropriate Socket; this
will permit different classes of listening Socket to pass different
function pointers.

In deference to the reality that OSSockets tend to be small integers
or pointer-sized OS handles, I've made the context parameter an
int/pointer union that can hold either of those directly, rather than
the usual approach of making it a plain 'void *' and requiring a
context structure to be dynamically allocated every time.

[originally from svn r10068]
2013-11-17 14:03:55 +00:00
..
README.txt Mention the potential networked-CHM problem in the post-installer 2007-01-23 11:38:11 +00:00
pageant.ico Tweak the icon script, and the generated icons, to more closely 2007-01-07 10:17:12 +00:00
pageant.mft Change manifest files to declare Windows GUI apps to be "DPI-aware", that is, 2009-09-25 23:32:14 +00:00
pageant.rc Belatedly update the copyright year to 2013. 2013-08-05 15:15:17 +00:00
pageants.ico Tweak the icon script, and the generated icons, to more closely 2007-01-07 10:17:12 +00:00
plink.rc `win-versioninfo': all builds of all Windows binaries now contain 2005-10-04 14:13:28 +00:00
pscp.ico Tweak the icon script, and the generated icons, to more closely 2007-01-07 10:17:12 +00:00
pscp.rc `win-versioninfo': all builds of all Windows binaries now contain 2005-10-04 14:13:28 +00:00
psftp.rc `win-versioninfo': all builds of all Windows binaries now contain 2005-10-04 14:13:28 +00:00
putty.ico Tweak the icon script, and the generated icons, to more closely 2007-01-07 10:17:12 +00:00
putty.iss Bump version number prior to tagging 0.63. 2013-08-06 17:09:07 +00:00
putty.mft Change manifest files to declare Windows GUI apps to be "DPI-aware", that is, 2009-09-25 23:32:14 +00:00
putty.rc `win-versioninfo': all builds of all Windows binaries now contain 2005-10-04 14:13:28 +00:00
puttycfg.ico Tweak the icon script, and the generated icons, to more closely 2007-01-07 10:17:12 +00:00
puttygen.ico Tweak the icon script, and the generated icons, to more closely 2007-01-07 10:17:12 +00:00
puttygen.mft Change manifest files to declare Windows GUI apps to be "DPI-aware", that is, 2009-09-25 23:32:14 +00:00
puttygen.rc Belatedly update the copyright year to 2013. 2013-08-05 15:15:17 +00:00
puttyins.ico `installer.ico' doesn't fit into 8.3, so gets truncated to INSTALLE.ICO in 2007-02-06 22:39:15 +00:00
puttytel.rc `win-versioninfo': all builds of all Windows binaries now contain 2005-10-04 14:13:28 +00:00
rcstuff.h `win-versioninfo': all builds of all Windows binaries now contain 2005-10-04 14:13:28 +00:00
sizetip.c Sprinkle some header comments in various files in an attempt to explain what 2006-04-23 18:26:03 +00:00
version.rc2 Bump version number prior to tagging 0.63. 2013-08-06 17:09:07 +00:00
website.url
win_res.h Sprinkle some header comments in various files in an attempt to explain what 2006-04-23 18:26:03 +00:00
win_res.rc2 Belatedly update the copyright year to 2013. 2013-08-05 15:15:17 +00:00
wincfg.c Post-release destabilisation! Completely remove the struct type 2011-07-14 18:52:21 +00:00
wincons.c Two related changes to timing code: 2012-09-18 21:42:48 +00:00
winctrls.c Back out r9964. I wasn't paying attention: every control is in the 2013-07-22 19:56:04 +00:00
windefs.c Turn 'Filename' into a dynamically allocated type with no arbitrary 2011-10-02 11:01:57 +00:00
windlg.c Turn 'Filename' into a dynamically allocated type with no arbitrary 2011-10-02 11:01:57 +00:00
window.c Find ToUnicodeEx() at run time, not load time. 2013-11-17 14:03:20 +00:00
wingss.c Post-release destabilisation! Completely remove the struct type 2011-07-14 18:52:21 +00:00
winhandl.c Revamp of EOF handling in all network connections, pipes and other 2011-09-13 11:44:03 +00:00
winhelp.c Quell a (correct) GCC warning in the NO_HTMLHELP case. 2012-09-17 22:28:07 +00:00
winhelp.h Add a bug-compatibility flag to disable the 2012-07-28 19:30:12 +00:00
winhsock.c Implement freezing on Windows handle sockets. 2013-11-17 14:03:48 +00:00
winjump.c Replace the type-checking COMPTR macro with my current idea of best 2013-07-22 07:12:15 +00:00
winmisc.c Remove the variable 'bufused', which came over from winnet.c in 2013-07-22 19:55:53 +00:00
winnet.c Replace the hacky 'OSSocket' type with a closure. 2013-11-17 14:03:55 +00:00
winnoise.c Been meaning to get round to this for a while: use CryptGenRandom to 2013-07-20 08:34:54 +00:00
winnojmp.c Fix up svn:eol-style and svn:keywords on new files. 2010-12-27 00:24:48 +00:00
winpgen.c Fix a few more memory and resource leaks. 2013-07-22 19:55:55 +00:00
winpgnt.c Get rid of the variable 'advapi' in Pageant's WinMain, which was never 2013-07-24 19:18:06 +00:00
winpgntc.c Another big batch of memory leak fixes, again mostly on error paths. 2013-07-22 07:11:54 +00:00
winplink.c Fix cut-and-paste errors in nonfatal() implementations. 2013-09-23 14:35:08 +00:00
winprint.c Another big batch of memory leak fixes, again mostly on error paths. 2013-07-22 07:11:54 +00:00
winproxy.c Factor out the HANDLE-to-Socket adapter from winproxy.c. 2013-11-17 14:03:44 +00:00
winser.c Two related changes to timing code: 2012-09-18 21:42:48 +00:00
winsftp.c Only run one toplevel callback per event loop iteration. 2013-09-15 14:05:31 +00:00
winstore.c Fix a double error handling goof in the winstore side of the jump list 2013-07-22 07:11:58 +00:00
winstuff.h Revamp Windows pending_netevent using toplevel callbacks. 2013-08-17 16:06:35 +00:00
wintime.c Sprinkle some header comments in various files in an attempt to explain what 2006-04-23 18:26:03 +00:00
winucs.c Add missing casts in arguments to ctype functions. 2013-07-22 07:12:10 +00:00
winutils.c Adjust comments around split_into_argv() to clarify that it's not 2013-01-19 17:17:44 +00:00
winx11.c Post-release destabilisation! Completely remove the struct type 2011-07-14 18:52:21 +00:00

README.txt

Этот файл содержит невидимые символы Юникода!

Этот файл содержит невидимые символы Юникода, которые могут быть отображены не так, как показано ниже. Если это намеренно, можете спокойно проигнорировать это предупреждение. Используйте кнопку Экранировать, чтобы показать скрытые символы.

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 on
your PATH. How you do this depends on your version of Windows. On
Windows NT, 2000, and XP, you can set it using Control Panel > System;
on Windows 95, 98, and Me, you will need to edit AUTOEXEC.BAT. Consult
your Windows manuals for details.

Some versions of Windows will refuse to run HTML Help files (.CHM)
if they are installed on a network drive. If you have installed
PuTTY on a network drive, you might want to check that the help file
works properly. If not, see http://support.microsoft.com/kb/896054
for information on how to solve this problem.

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'.