X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Ffaq.but;h=8467384321fc8c8c0d20c99ea21d4b92c3ce2129;hb=182a511ec3dce0b726be5df4e8e16af605ec4f6a;hp=fea60ffaabd2f47af97eeb32f45da76503b62ead;hpb=71228b9c45daefaeab03714cfcf24fc418eb90a9;p=PuTTY.git diff --git a/doc/faq.but b/doc/faq.but index fea60ffa..84673843 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -1,4 +1,4 @@ -\versionid $Id$ +\define{versionidfaq} \versionid $Id$ \A{faq} PuTTY FAQ @@ -292,11 +292,17 @@ testing in this area would be very welcome! \S{faq-mac-port}{Question} Will there be a port to the Mac? -There is a port to the Mac OS in progress. It's just about usable, but -has an awful lot of gaps and rough edges that will need cleaning up -before release (such as useful random numbers). +There are several answers to this question: -A separate port to Mac OS X is also underway. +\b The Unix/Gtk port is already fully working under Mac OS X as an X11 +application. + +\b A native (Cocoa) Mac OS X port is in progress. It's just about +usable, but is of nowhere near release quality yet, and is likely to +behave in unexpected ways. + +\b A separate port to the classic Mac OS (pre-OSX) is also in +progress; it too is not ready yet. \S{faq-epoc}{Question} Will there be a port to EPOC? @@ -623,12 +629,17 @@ SCP backend did not suffer from this performance issue because SCP is a much simpler protocol.) \S{faq-bce}{Question} When I run full-colour applications, I see -areas of black space where colour ought to be. +areas of black space where colour ought to be, or vice versa. + +You almost certainly need to change the \q{Use background colour to +erase screen} setting in the Terminal panel. If there is too much +black space (the commoner situation), you should enable it, while if +there is too much colour, you should disable it. (See \k{config-erase}.) -You almost certainly need to enable the \q{Use background colour to -erase screen} setting in the Terminal panel. Note that if you do -this in mid-session, in versions before 0.54, it may not take effect -until you reset the terminal (see \k{faq-resetterm}). +In old versions of PuTTY, this was disabled by default, and would not +take effect until you reset the terminal (see \k{faq-resetterm}). +Since 0.54, it is enabled by default, and changes take effect +immediately. \S{faq-resetterm}{Question} When I change some terminal settings, nothing happens. @@ -700,7 +711,7 @@ Set the key's value to something like 10. This will cause Windows to try harder to keep connections alive instead of abandoning them. \S{faq-puttyputty}{Question} When I \cw{cat} a binary file, I get -`PuTTYPuTTYPuTTY' on my command line. +\q{PuTTYPuTTYPuTTY} on my command line. Don't do that, then. @@ -907,6 +918,16 @@ reported to us). There is a patch for OpenSSH attached to that bug; it's also fixed in recent versions of portable OpenSSH (from around 3.8). +\S{faq-connaborted}{Question} Do you want to hear about \q{Software +caused connection abort}? + +In the documentation for PuTTY 0.53 and 0.53b, we mentioned that we'd +like to hear about any occurrences of this error. Since the release +of PuTTY 0.54, however, we've been convinced that this error doesn't +indicate that PuTTY's doing anything wrong, and we don't need to hear +about further occurrences. See \k{errors-connaborted} for our current +documentation of this error. + \H{faq-secure} Security questions \S{faq-publicpc}{Question} Is it safe for me to download PuTTY and