OK, let's get started.  First you need to edit FXUUCP.CFG which you will find
in your WILDCAT\GATEWAY directory.  For complete reference to commands you
should consult your wcGate manual or FXUUCP.DOC that you will find in your
\WILDCAT\GATEWAY\ directory.

---FXUUCP.CFG---
device        : 1
speed         : 57600
node          : jamesbbs
uucpname      : jamesbbs
spool         : C:\WILDCAT\GATEWAY\
uu.retries    : 10
uu.handshake  : 60
uu.time       : 60
uu.windows    : 3
uu.driver     : NATIVE
fx.share      : 1

Device -> The PORT number of your serial/modem.  If you use a DigiBoard this
number is the port number that corresponds to the DOS name, not the Digi 
channel number.  Normally it is just the com port number that your modem is
connected to.

Speed ->  The speed which you lock the port at.

Node  & UucpName ->  My sight (Machine) name works fine here, you may want
to refer to the wcGate manual for a more complete description if you need
something different.  

Spool ->  This is the directory where received files will be placed.  Do not
put the directory name of your host here, the program will automatically 
place the name of the host at the end of this path.  This path is usually 
\WILDCAT\GATEWAY and when mail is received it will be placed in 
\WILDCAT\GATEWAY\[HOSTNAME], for my system the path would end up being 
\WILDCAT\GATEWAY\ERI. The \ERI is automatically added by FX UUCICO during
the download and the files are placed there.

uu.Retries ->  Number of times to attempt to call your host if you can't
get connected.

uu.Handshake ->  MaxTime to wait for the connection, 60 seconds should be
plenty.

uu.Time ->  Time out in seconds for the script.  If no response is received 
within this amount of time the script is aborted and the session recycled

uu.Windows -> Number of windows for your download protocol.  Your host will
tell you which protocol to use along with the packet size and number of 
windows.

uu.Driver -> Your choices are Native, Digi and Fossil.  Native will usually
give the best results, for some reason Fossil support slows things down
a little.

fx.Share -> controls the networking features, 1 is on and 0 is off.


You must now define several files which will be used to control the operation
of the FX UUCICO.  The first is the DIALERS file which you will find in
your \WILDCAT\GATEWAY directory


---DIALERS---
# Dialer-name   device  speed      dialer-script
Supra288    default   default "" \d+++\d "" atz OK ATDT99999999 CONNECT 

The dialers is a file with one line for each of the devices you will be 
dialing out with.  If will only be dialing out with one modem you should
only have one line here.  The dialer name is the name which FX UUCICO will 
search for as specified in the SYSTEMS "dialer" field.

The device line overrides the default port specified in the FXUUCP.CFG file.

The speed line overrides the default port speed from FXUUCP.CFG.

The last part of the line is the actual dialing script.  You would be well 
advised to keep this as simple as possible to make life easier on you.  The
script is made up of pairs of send-expect statements.  The first part is
expect, then send, then expect and so on.  

"" \d+++\d "" atz OK ATDT99999999 CONNECT

[<EXPECT "">] [<SEND \d+++\d> <EXPECT "">] [<SEND atz> <EXPECT OK >] 

[<SEND ATDT9999999> <EXPECT CONNECT>]

In my script is an "", which is an "empty token" (the script doesn't expect 
anything), then comes \d+++\d, which delays for 2 seconds, sends the escape 
code and delays another 2 seconds.   After that is another empty token (the 
script doesn't look for anything).  Then there is a send where the scripts 
sends atz and then expects OK.  Then the script sends atdt9999999 
(where 9999999 is your hosts' phone number) and expects CONNECT.  After 
connect is received, the dialer script ends and the SCRIPTS script starts.  
For complete syntax of the scripts refer to your wcGate manual.


---SYSTEMS---
#host  time protocol  dialer     script  phone-number  login password
#
eri Any   g     supra288  toerinet 9999999  jamesbbs password

The SYSTEMS file contains all the information needed to control the session 
with your host.  The first element is the host name, this will have to match
your hosts' name when you log on or the session will fail.  

The next entry is the times allowed for calling, leave this to "Any" since
you will decide when to call out through your events.  

Next is your transfer protocol, there are different ones so ask your host 
which one will be best for you.

The next two entries are the dialer and script names, these are the names 
that appear in the DIALERS and SCRIPTS files as dialer-name and script name
respectively.  These names all must correspond to the lines in SCRIPTS or  
DIALERS or the session will fail.

Next is your hosts' phone number, your log-in name and finally your password.
These last two will be used to replace any /L or /P in your scripts. 

The next step is to call your host and record the log-on session.  Use your
regular terminal software (I used Qmodem) and record your log-on session.  
You may have to change your video emulation to VT100 or VT102, your host 
should tell you what to use.  You will refer to this capture session later 
to write your log-on scripts.  Here is an example of mine.

---Session Capture---
Connect 28800
Connected to port ttyS22
EriNet On-Line Communications (513)XXX-XXXX, New users log in as 'new'
eri login:
Password:

---SCRIPTS---
# SCRIPTS file
#
toerinet login: \L Password: \P 

The scripts is your actual script that logs you on to your hosts' system. 
The first part of the line is the name of the script, after that is the
actual script.  In my session capture you can see that there are two places
that I have to send information, the login name and the password.  My script
is very simple and all it does is look for "login:" and send /L (which will
be replaced with your login name as defined in SYSTEMS) and then look for 
"Password:" and send /P (which will be replaced with your password from 
SYSTEMS).  At this point the actual mail transfer program starts and the mail
transfer is automatic from there.   There are some systems where you will
have to change directories and perform other functions in order to start your
mail transfer.  Use your recorded session to write the appropriate scripts 
and be sure to contact your host if you are having problems.


---PERMITS---
default   /system=known

PERMITS controls the security of your mail sessions.  You can make this as
simple or as complicated as you feel necessary.  I have found that the sample
above works fine for me.


You will now need to automate your mail sessions through batch files.  There
will be three parts to your batch file; the first is to scan and export any
new mail to be sent to your host.  The second is to call your host and the 
third is to toss the received mail into Wildcat!.  On my system, I toss the
messages through a separate batch file on a local node, this way I don't tie
up my phone line while tossing.  You can just as easily add the toss line
to the same batch file you scan and dial out with and do it all in one 
session.  


---UUCP.BAT---
cd \wildcat
wcGate Export UUCP Host:Eri
cd \wildcat\gateway
uucico -seri

---TossUUCP.BAT---
cd \wildcat
wcGate Import UUCP Host:Eri Flag Check

That's it!  Don't be surprised if things don't work right the first few times,
there are a lot of parts to this puzzle and it will take some "tweaking" to
get them all to work together.  Be systematic about your setup and keep good
notes on all your settings to make debugging easier.

If you have and questions you can't seem to resolve there are quite a few 
places to go for help.  First and foremost is Mustang's tech support, either 
via phone or E-Mail.  You can also get answers on the Fido Wildcat echo or on
the Internet in alt.bbs.wildcat.  Finally you can reach me at my BBS,
(513) 323-6009, on FidoNet (1:110/940 or the Wildcat echo), on TechNet 
(87:1001/40) or finally on the Internet (E-Mail: james@jamesbbs.com or 
alt.bbs.wildcat).  See, this really does work!
