Notes on Wattcp FTP
-------------------

Wattcp FTP is a command-line ftp client for DOS.  It has a scripting
capability and displays the amount of data that has been transmitted during
a transfer.  Unlike NCSA FTP, Wattcp FTP can resolve domain names.  It
handles multiline messages from the ftp server better than CUTCP ftp does.

To configure this program, you must create a WATTCP.CFG file for it; you do
not need to be connected to do this (however, see below if you are using
Wattcp FTP for testing purposes).  If you've already installed another
WATTCP application, you can just make a one-line WATTCP.CFG that points to
the WATTCP.CFG you already have, like so:

   include=e:\internet\wattcp.cfg

Otherwise, see FTP.DOC in the package for an example WATTCP.CFG.  You need
to set 5 things:  my_ip, netmask, nameserver, gateway, and domainslist.  Two
more can optionally be set and may help you connect:  sockdelay and
domainto.

If you have static IP, set my_ip to your static IP address:

   my_ip=204.117.9.33

(For me.)  If you have dynamic IP, comment out that line and put this
instead:

   include=e:\internet\ipaddr.cfg

You will need to create IPADDR.CFG at connect time and give its full
pathname here; see the README file on my site.

Set netmask like this (do *not* use your real netmask):

   netmask=0.0.0.0

Set nameserver to your nameserver's IP address:

   nameserver=199.191.1.80

If you have more than one nameserver, just give your primary nameserver;
don't use more than one nameserver line.

If you have a static gateway, give its IP address for gateway:

   gateway=199.191.1.70

If your gateway is dynamic, either give the gateway you *usually* get (it
will probably still work), or comment out the gateway line and put this
instead:

   include=e:\internet\gateway.cfg

As above, you need to create GATEWAY.CFG at connect time and give its path
here; see file README on my site.

Set domainslist to the empty string:

   domainslist=""

Giving your real domain here only slows down DNS queries.

It is probably a good idea to increase sockdelay (the amount of time Wattcp
FTP will wait to connect to a site before giving up).  Here is what I use:

   sockdelay=60

Finally, adding a line like this may help with domain name lookups:

   domainto=20

Wattcp FTP is relatively easy to set up and use and works quite well, so it
is a good application to begin with as you try to get things working.  If
you are just using it as a first application for testing purposes with your
packet driver, just edit this little WATTCP.CFG file.  Worry about dynamic
IP later; just fill in the values for your current session while you are
online (after your packet driver is loaded) and see if it works:

----- temporary WATTCP.CFG for testing begins -----
my_ip=127.0.0.1                  # put your IP address here
netmask=0.0.0.0                  # do not change this line
nameserver=127.0.0.2             # put your nameserver here
gateway=127.0.0.3                # put your gateway here
domainslist=""                   # do not change this line
sockdelay=60                     # do not change this line
domainto=60                      # do not change this line
mss=512                          # do not change this line
----- temporary WATTCP.CFG for testing ends -----

As I said, if you have dynamic IP and your IP address and gateway are not
constants, just fill in the ones you have *right now* (hopefully they were
printed on the screen when you logged in, and maybe your gateway is a
constant) and see if you can ftp to a site.  You can worry about making
batch files to create IPADDR.CFG and GATEWAY.CFG later, when you have
confirmed that your packet driver works.

If your provider has an ftp site, you can use that one to test.  If you
don't know of any ftp sites, you can try these:

   oak.oakland.edu
   garbo.uwasa.fi
   wuarchive.wustl.edu

Or even:

   ftp.oldskool.org

:-)  For example, type:

   ftp oak.oakland.edu

from the DOS prompt while you are in the directory where you installed
Wattcp FTP and where WATTCP.CFG is located.

When you are asked for your userid, type "ftp" or "anonymous" (either should
work, though there may be some sites with really old server software that
only accept "anonymous").  For your password, type your email address.  If
they tell you there are too many anonymous users, that is OK, and you should
consider that a success.  You are just trying to see if you can get
somewhere on the Internet.  You did, they don't want you, and that's good
enough for a test ;-).

For a more thorough test, list some directories and try to download a small
file.  Type "help" at the ftp> prompt to see the commands.