====================
SocksCap for Windows
====================
File: FAQ (960812)

Frequently Asked Quesions about SocksCap
(last updated: 08-12-96)

------------------------------------------------------------------------

In this file:

Q: What is SocksCap?
Q: What is the current version?
Q: What is the difference between SocksCap, SocksCap16, and
   SocksCap32?
Q: Do I need to run SocksCap16, SocksCap32, or both?   
Q: Where do I get SocksCap?
Q: Is SocksCap free?  Source code available?
Q: Will it work with all stacks and applications?
Q: What about 32-bit versions?
Q: What happens if I start SocksCap16 AFTER a winsock application is
   already running?
Q: What if I close SocksCap16 before closing a winsock application?
Q: When I run SocksCap, the following message is displayed:
    	Couldn't find my own hostname: WSANO_DATA (errno=11004).
Q: Will I need to run ftp in PASV mode?
Q: Windows95 locks up during reboot if SocksCap16 is running.
Q: When I close SocksCap16 in Windows95 or Windows for Workgroups, it
   tells me "Exiting SocksCap may cause some network connections to
   become unstable."  But, I've closed all the client applications
   already.

------------------------------------------------------------------------

Q: What is SocksCap?
     
A: The purpose of SocksCap is to reside between non-SOCKSified Winsock
   applications and a non-SOCKSified Winsock stack, converting socket
   calls as needed to communicate through a Socks4 or Socks5 server.
   SocksCap can be configured to connect directly (not through the
   SOCKS server) to some addresses while using proxy connections
   (through the SOCKS server) to all others.


Q: What is the current version?

A: The current version of SocksCap16 (16-bit) is 0.53.  The current
   version of SocksCap32 (32-bit) is 0.12.
   

Q: What is the difference between SocksCap, SocksCap16, and
   SocksCap32?

A: "SocksCap" refers generally to both the 16- and 32-bit versions.
   "SocksCap16" is the 16-bit version.  "SocksCap32" is the 32-bit
   version.  Earlier 16-bit versions (beta 0.51 and prior) were called
   "SocksCap" and then the "16" was added to differentiate from the
   32-bit version.


Q: Do I need to run SocksCap16, SocksCap32, or both?   

A: For Windows 3.1 and Windows for Workgroups 3.11, run SocksCap16.
   For Win95, you'll need SocksCap32 for the 32-bit applications.  If
   you are running 16-bit applications under Win95, you'll need
   SocksCap16 for those.  You can run SocksCap16 and SocksCap32
   simultaneously under Win95 if you need to handle both 16- and
   32-bit applications.  Hopefully in the future, SocksCap16 and
   SocksCap32 will be more integrated with each other so you don't
   need to worry about which one (or both) to run under Win95.  Under
   WinNT, use SocksCap32 for 32-bit applications.  SocksCap16 does not
   run under WinNT.


Q: Where do I get SocksCap?

A: SocksCap is available through the SOCKS Web site at:
	http://www.socks.nec.com/
     or via anonymous ftp at:
	ftp://ftp.nec.com/pub/socks/


Q: Is SocksCap free?  Source code available?

A: The software is available freely via anonymous ftp and the SOCKS
   web site and is NOT in the public domain.  Use and distribution is
   restricted and subject to certain agreements.  The full copyright
   and restrictions can be found in the file named "COPYRIGH" in the
   distribution zip file.  Source code is not available.


Q: Will it work with all stacks and applications?

A: Since SocksCap functions independently from the applications and
   the stack, it needs to make many 'guesses' about the implementation
   of the applications and the stack.  Therefore, it will not be the
   'perfect' solution and will not work with every application and
   every stack. Hopefully though, it will work with a good number and
   will provide some much-needed connectivity for Windows clients
   behind firewalls.  (SocksCap32 has only been tested with
   Microsoft's 32-bit stack.)


Q: What about 32-bit versions?

A: SocksCap32 is currently available in alpha version and works with
   Microsoft's 32-bit stack.  SocksCap16 is still required under Win95
   for 16-bit Winsock applications to communicate through a Socks
   server.  SocksCap16 does not run under WinNT.


Q: What happens if I start SocksCap16 AFTER a winsock application is
   already running?
 
A: SocksCap16 needs to be started prior to other winsock applications.
   If SocksCap16 sees a request come from an application that was run
   prior to starting SocksCap16, it will attempt to make all
   connections directly for that application.  Beware that the
   application may become unstable.
 

Q: What if I close SocksCap16 before closing a winsock application?
 
A: SocksCap16 must remain running until all network applications are
   closed.  If SocksCap16 sees that there may still be active
   connections, it will display a warning that there may be active
   connections and give you a chance to cancel your exit
   request. (This does not apply to SocksCap32.)
 
 
Q: When I run SocksCap, the following message is displayed:
 	Couldn't find my own hostname: WSANO_DATA (errno=11004).
 
A: Your machine was not able to figure out its own hostname or IP
   address.  The current versions of SocksCap16 and SocksCap32 no
   longer strictly require that you be able to resolve your own
   address.  If it can't resolve itself, put your local PC's IP
   address in the list of Direct Connections if it needs to make
   connections to its own IP address.

   
Q: Will I need to run ftp in PASV mode?

A: Ftp is a tricky case to handle with this generic solution so it
   will probably suffer some quirkiness depending on the application
   and stack.  Probably best to try without PASV first and if that
   doesn't work, give PASV a try.


Q: Windows95 locks up during reboot if SocksCap16 is running.

A: This has been fixed in SocksCap16 version 0.50 and above.


Q: When I close SocksCap16 in Windows95 or Windows for Workgroups, it
   tells me "Exiting SocksCap may cause some network connections to
   become unstable."  But, I've closed all the client applications
   already.

A: This is because SocksCap16 sees the "WSASRV" process still running.
   You need to add "WSASRV" to the Direct Applications list in the
   SocksCap16 setup dialog.
