
By now, you're probably either thoroughly confused or you're
doing okay with all of this stuff.  If you're confused, I
suggest you just go to bed and take it up again tomorrow.
If you're okay with all of this stuff, then it might be time
to try manually running through the processes as I've
described them.

I'm going to list my "INTERNET" event batch file now so that
you can see what I do every two hours to upload and download
my newsgroup and email messages.  Here it is:

INTERNET.

IF EXIST C:\TRITEL\MWORK\WHOSON.4 DEL C:\TRITEL\MWORK\WHOSON.4
COPY C:\TRITEL3\WHOSON.INT C:\TRITEL\MWORK\WHOSON.4
C:
CD\TRIDOG
TRIDOG
CD\GIGO\MANAGER
NETMGR
CD\GIGO
MAILSCAN
CD\TRITOSS
TRITOSS
CD\GIGO
SRCH C:\GIGO\OUTBOUND /nr /!n *.pkt /c C:\GIGO\OUTBOUND\ZIP_TEMP /rm
PKUNZIP C:\GIGO\OUTBOUND\ZIP_TEMP\*.* C:\GIGO\OUTBOUND
ECHO Y|DEL C:\GIGO\OUTBOUND\ZIP_TEMP\*.*
GATEWAY /NOLOGO /NOVIDEO
CD\FX
ECHO ATZ >COM3
DELAY 2
uucico -s nuchat -t360
CD\GIGO
GATEWAY /NOLOGO /NOVIDEO
DELAY 2
IF EXIST C:\TRITEL\MWORK\WHOSON.4 DEL C:\TRITEL\MWORK\WHOSON.4
COPY C:\TRITEL3\WHOSON.TOS C:\TRITEL\MWORK\WHOSON.4
CD\TRITOSS
TRITOSS
CD\TRIDOG
TRIDOG
DEL C:\TRITOSS\ARCMAIL\*.MSG
CD\GIGO\MANAGER
NETMGR
CD\GIGO
MAILSCAN
CD\TRITEL\UTILS\TRISTAT
TRISTAT C:\TRITEL\MWORK\CALLERS.LOG
IF EXIST C:\TRITEL\MWORK\WHOSON.4 DEL C:\TRITEL\MWORK\WHOSON.4
CD\TRITEL3
BOARD


Lines 13 through 15 may appear to be pretty strange but trust
me, you'll need them.  If you get a chance, take a look at
the file that TriToss creates in your C:\GIGO\OUTBOUND directory
during the outbound process.  That's right, it's not a .PKT
file.  It is actually a differently-named zip file that has
the .PKT nested down several subdirectories within the zip file.
My lines 13 through 15 take care of that so that the only thing
that remains in the C:\GIGO\OUTBOUND directory is a true .PKT
file.

You'll also note the use of some "whoson" files.  Well, I got
tired of my users not being able to see that there was an
event running on Node 4 so I creatively "edited" a whoson file
that TriBBS puts out and I copy them in and out during all of
my events so that my users can see what is happening on Node 4
when they desire.  I've even included my copies of them for
you to use if you would like.

Also, we didn't talk about the NETMGR utility.  It comes with
Gigo and I've included my NETMGR.CFG file for you to look at.
This gets rid of "junk" messages left over when you're not
actually running Fido.  If you read the doc file for netmgr
you'll see what it is capable of doing.  Actually, it's a real
powerful little utility - I plan on putting it to some different
uses later on.

Starting at the beginning, take a look at every line of the
batch file and see how it relates to the graphic we looked at
way back in one of the earlier readme files.  If you've set
things up the way I've suggested and you've gone through the
GIGO configuration files with a fine toothed comb, you should
literally be able to make some test runs by running all of these
batch file lines manually at the command line and seeing how
they all work.  I use OS/2 so it was easy to run each line and
have an open XTreeGold window to look at the results during
each step.


Final thought......

I've tried my best, with this collection of readme and config
files, to give back some of the help that was given to me when
I was about to pull my hair out during my attempt to set up
my Internet message conferences.  I sincerely hope all of this
has been helpful to you and that you are successful in getting
your own Internet stuff rolling.  I'd love to hear from you if
this little mini-novel has helped.  I can be reached in the
TriBBS Support Conference on TriBBSNet or you can email me
at ben.askew@bhabbs.com.
