Currently, release versions of PuTTY tools only run on full Win32
systems and Unix. \q{Win32} includes Windows 95, 98, and ME, and it
-includes Windows NT, Windows 2000 and Windows XP.
+includes Windows NT, 2000, XP, and Vista.
In the development code, a partial port to the Mac OS (see
\k{faq-mac-port}) is under way.
Most of the code cleanup work would be a good thing to happen in
general, so if anyone feels like helping, we wouldn't say no.
+See also
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/dll-frontend.html}{the wishlist entry}.
+
\S{faq-vb}{Question} Is the SSH or Telnet code available as a Visual
Basic component?
PuTTY also requires a random number seed file, to improve the
unpredictability of randomly chosen data needed as part of the SSH
-cryptography. This is stored by default in a file called \i\c{PUTTY.RND}
-in your Windows home directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in
-the actual Windows directory (such as \c{C:\\WINDOWS}) if the home
-directory doesn't exist, for example if you're using Win95. If you
+cryptography. This is stored by default in a file called \i\c{PUTTY.RND};
+this is stored by default in the \q{Application Data} directory,
+or failing that, one of a number of fallback locations. If you
want to change the location of the random number seed file, you can
put your chosen pathname in the Registry, at
\H{faq-misc} Miscellaneous questions
\S{faq-openssh}{Question} Is PuTTY a port of \i{OpenSSH}, or based on
-OpenSSH?
+OpenSSH or OpenSSL?
No, it isn't. PuTTY is almost completely composed of code written
from scratch for PuTTY. The only code we share with OpenSSH is the
-detector for SSH-1 CRC compensation attacks, written by CORE SDI S.A.
+detector for SSH-1 CRC compensation attacks, written by CORE SDI
+S.A; we share no code at all with OpenSSL.
\S{faq-sillyputty}{Question} Where can I buy silly putty?