mirror of git://git.tartarus.org/simon/putty.git, used for client testing
Перейти к файлу
Simon Tatham 0e6c1fffd9 Introduce program category U, for non-GTK-requiring Unix apps. Plink
doesn't need to be linked with libgtk, libgdk, libX11 etc!

[originally from svn r2179]
2002-11-01 18:51:55 +00:00
contrib
doc .HLP files should be ignored as well. Oops. 2002-11-01 13:49:25 +00:00
unix Prevent another segfault. Oops. 2002-11-01 18:51:22 +00:00
.cvsignore
LATEST.VER
LICENCE
MODULE
README
README.txt
Recipe Introduce program category U, for non-GTK-requiring Unix apps. Plink 2002-11-01 18:51:55 +00:00
be_all.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
be_none.c
be_nossh.c
cmdline.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
console.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
import.c
int64.c
int64.h
ldisc.c Reorganised the Unicode layer somewhat: moved luni_send and 2002-10-26 11:08:59 +00:00
ldisc.h Richard points out that it would probably help if I committed 2002-10-26 12:42:07 +00:00
ldiscucs.c Arrgh! _Another_ missed commit. I really must do something about 2002-10-27 09:24:47 +00:00
logging.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
misc.c
misc.h
mkfiles.pl Introduce program category U, for non-GTK-requiring Unix apps. Plink 2002-11-01 18:51:55 +00:00
network.h More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
noise.c
pageant.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
pageant.ico
pageant.mft
pageant.rc
pageantc.c
pageants.ico
plink.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
plink.rc
portfwd.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
printing.c
proxy.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
proxy.h Fix proxy.c so that the static variables become const. 2002-10-26 11:12:24 +00:00
psftp.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
putty.h Further deglobalisation: settings.c now has a more sensible interface. 2002-10-30 18:12:46 +00:00
putty.ico
putty.iss
putty.mft
puttycfg.ico
puttygen.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
puttygen.ico
puttygen.mft
puttygen.rc
puttymem.h
puttyps.h
raw.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
resource.h
rlogin.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
scp.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
scp.ico
scp.rc
settings.c Further deglobalisation: settings.c now has a more sensible interface. 2002-10-30 18:12:46 +00:00
sftp.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
sftp.h
sizetip.c
ssh.c valgrind has caught two more uninitialised elements in the SSH 2002-11-01 12:59:09 +00:00
ssh.h Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
sshaes.c
sshblowf.c
sshbn.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
sshcrc.c
sshcrcda.c
sshdes.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
sshdh.c
sshdss.c
sshdssg.c
sshmd5.c
sshprime.c
sshpubk.c
sshrand.c
sshrsa.c
sshrsag.c
sshsh512.c
sshsha.c
sshzlib.c Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
storage.h
telnet.c Another valgrind-caught error. This one has apparently been there 2002-11-01 13:01:14 +00:00
terminal.c terminal.c should call the frontend beep() routine even with 2002-10-28 21:58:07 +00:00
terminal.h Yet more global-removal. The static variables in logging.c are now 2002-10-26 12:58:13 +00:00
tree234.c
tree234.h
unicode.c Fix some consts. 2002-10-30 18:12:22 +00:00
version.c
wcwidth.c
website.url
wildcard.c
win_res.h
win_res.rc
winctrls.c
windlg.c Further deglobalisation: settings.c now has a more sensible interface. 2002-10-30 18:12:46 +00:00
window.c Further deglobalisation: settings.c now has a more sensible interface. 2002-10-30 18:12:46 +00:00
winnet.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +00:00
winstore.c
winstuff.h Further deglobalisation: settings.c now has a more sensible interface. 2002-10-30 18:12:46 +00:00
winutils.c
x11fwd.c More preparatory work: remove the <windows.h> include from lots of 2002-10-30 17:57:31 +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 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'.