X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/fa58cf815a60282a9bb2b1ebe7ccf1dda2748553..4c48c989a62fba2809d684b30963b4411038fe96:/doc/faq.but

diff --git a/doc/faq.but b/doc/faq.but
index d3253591..2068bee5 100644
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -1,4 +1,4 @@
-\versionid $Id: faq.but,v 1.45 2003/03/04 14:14:17 ben Exp $
+\versionid $Id: faq.but,v 1.47 2003/05/22 08:43:50 simon Exp $
 
 \A{faq} PuTTY FAQ
 
@@ -28,11 +28,6 @@ implemented.
 \S{faq-ssh2}{Question} Does PuTTY support SSH v2?
 
 Yes. SSH v2 support has been available in PuTTY since version 0.50.
-However, currently the \e{default} SSH protocol is v1; to select SSH
-v2 if your server supports both, go to the SSH panel and change the
-\e{Preferred SSH protocol version} option. (The factory default will
-\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/ssh2-default.html}{change to v2}
-in the next full release.)
 
 Public key authentication (both RSA and DSA) in SSH v2 is new in
 version 0.52.
@@ -194,26 +189,17 @@ or any other port of PuTTY, they were mistaken. We don't.
 
 It's currently being worked on. If you look at the nightly source
 snapshots, you should find a \c{unix} subdirectory, which should
-build you a Unix port of Plink, and also \c{pterm} - an
+build you Unix ports of Plink, PuTTY itself, and also \c{pterm} - an
 \cw{xterm}-type program which supports the same terminal emulation
-as PuTTY.
-
-It isn't yet clear whether we will bother combining the terminal
-emulator and network back end into the same process, to provide a
-Unix port of the full GUI form of PuTTY. It wouldn't be as useful a
-thing on Unix as it would be on Windows; its major value would
-probably be as a pathfinding effort for other ports. If anyone
-really wants it, we'd be interested to know why :-)
+as PuTTY. We do not yet have Unix ports of PSCP, PSFTP, Pageant or
+PuTTYgen.
 
 \S{faq-wince}{Question} Will there be a port to Windows CE or PocketPC?
 
-Probably not in the particularly near future. Despite sharing large
-parts of the Windows API, in practice WinCE doesn't appear to be
-significantly easier to port to than a totally different operating
-system.
-
-However, PuTTY on portable devices would clearly be a useful thing,
-so in the long term I hope there will be a WinCE port.
+It's currently being worked on, but it's only in its early stages yet,
+and certainly isn't yet useful.  PuTTY on portable devices would
+clearly be a useful thing, so in the long term I hope it can be
+brought up to release quality.
 
 \S{faq-win31}{Question} Is there a port to Windows 3.1?
 
@@ -234,9 +220,9 @@ testing in this area would be very welcome!
 
 \S{faq-mac-port}{Question} Will there be a port to the Mac?
 
-Eventually.  The terminal emulation code has been ported, as has the
-saved-settings infrastructure, but networking and a configuration GUI
-still need to be done before the port will be of any use.
+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.
 
 \S{faq-epoc}{Question} Will there be a port to EPOC?
 
@@ -245,6 +231,10 @@ even on systems the developers \e{do} already know how to program
 for, it might be a long time before any of us get round to learning
 a new system and doing the port for that.
 
+However, some of the work has been done by other people, and a beta
+port of PuTTY for the Nokia 9200 Communicator series is available
+from \W{http://www.s2.org/putty/}\cw{http://www.s2.org/putty/}
+
 \H{faq-embedding} Embedding PuTTY in other programs
 
 \S{faq-dll}{Question} Is the SSH or Telnet code available as a DLL?