(Boca comments are prepended with "###"...Also, read README.BCR for 
 additional Boca-site suggestions) -djc 05/30/95

To use the socksified telnet and ftp clients:

  (1) Install a socks.cfg file at the %ETC% directory, e.g.,
      direct              9.0.0.0    255.0.0.0
      sockd @=9.14.1.100  0.0.0.0      0.0.0.0
      #change 9.14.1.100 to your sockd gateway address

###
### This will probably be the C:\TCPIP\ETC directory, unless
### you specified another directory structure when you installed
### TCP/IP for OS/2.
###
### Boca's sockd gateway address is 9.83.11.95. The 
### SOCKS.CFG included in this distribution is already
### set for this address. Just copy it over...
###

      Copy DBCSCONV.INI to %ETC% directory.
###
### As before, this is likely to be C:\TCPIP\ETC unless you
### intended otherwise...
###

  (2) Set environment variables:
      Set the SOCKS_DOMAIN for domain(s) considered internal, e.g.,
      SET SOCKS_DOMAIN=ibm.com,advantis.com
###
### OK.
###
      Set SOCKS_NS for external name server(s), e.g.,
      SET SOCKS_NS=9.14.1.100
###
### Again, Boca's is 9.83.11.95
###
      You may want to set them in config.sys
###
### Definitely. Make sure to include the keyword "SET" in front
### of each variable when placing them in the CONFIG.SYS. By the
### way, location of these variables at a particular place in the
### CONFIG.SYS file isn't important - most people will just tag
### them onto the bottom.
###

  (3) Copy SOCKSDLL.DLL to a LIBPATH directory (check config.sys
      to verify LIBPATH setting)
###
### The C:\TCPIP\DLL directory would be the usual choice, unless
### you installed OS/2 TCP/IP in another location.
### 

  (4) If you have an older version of SO32DLL.DLL and TCP32DLL.DLL,
      rename them to something else.  Replace them with the new version
      you just got.
### 
### This part may be tricky. Despite the recent dates on the copies in
### this distribution, these 2 files are believed to be dated at the same
### time as this author's README file (9/30/94). If you have the most
### recent OS/2 TCP/IP patches, you probably already have these.
### Also, if you do need to copy these over to the C:\TCPIP\DLL 
### directory, you may have to do it with a bootable DOS or OS/2
### diskette. The reason is that these two files are frequently LOCKED
### when OS/2 TCP/IP is running, and you will not be allowed to
### copy over them when you are running from a "normal" hard-disk bootup.
###

  (5) Now you are ready to try the socksified clients.

###
### We suggest a full reboot before trying them...
###
### There are additional tips in the README.BCR file included with
### this distribution, including a method to integrate RTELNET into
### the WebExplorer code so you can do remote telnet sessions while
### in WebExplorer. 
###
      
###
### You can ignore the following steps unless you are interested in
### knowing how to *develop* programs with SOCKSified code...
###

To use SOCKSDLL.DLL and SOCKSDLL.LIB to socksify other clients
(assuming you have access to the client source)
 
  (a) Copy SOCKSDLL.LIB to a %LIB% directory
 
  (b) Change the make file to
      Compile the client with compiler options
        /Dconnect=Rconnect  /Dgethostbyname=Rgethostbyname
      Link the client with the addition socksdll.lib

  (c) Follow the instructions (1)-(4) above to run the client
 
  Note: This instruction is for clients with only blocking TCP
        connect() calls.  If you need non-blocking connect()
        or inbound connection setup, please contact me.
        The SOCKSDLL.DLL is built for 32-bit applications.

###
### The original author and owner of the code is this gentleman...
###

Please direct your questions, problems and comments to
 
      Winston Chung
      CHUNG at RALVM12  (wchung@vnet.ibm.com)

9/30/94