home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
TICIT2A.ZIP
/
TICIT.DOC
< prev
next >
Wrap
Text File
|
1994-12-27
|
21KB
|
884 lines
TicIt (tm) 2.00
Copyright 1994-1995 By ProSoft
COPYRIGHT NOTICE
TicIt is a copyrighted program being distributed under the shareware
concept. As such, you may use TicIt for a period of 30 days without
registering the software. After the 30 day evaluation period, you
must register your copy of TicIt or you will be in violation of
United States and International copyright laws.
As a shareware program, TicIt my be freely distributed through a
BBS. Shareware distributors may distribute copies of TicIt on disk
for a modest disk duplication charge not to exceed $6 per disk.
It is a violation of the TicIt license agreement to modify the EXE
file in anyway.
TicIt key files may not be transferred without the expression
written permission of ProSoft.
WARRANTY
TicIt is distributed without warranty. In no event will ProSoft be
liable to you for damages, including any loss of profits, lost
savings, or other incidental or consequential damages arising out of
your use of or inability to use the program, even if ProSoft or an
authorized representative has been advised of the possibility of such
damages. ProSoft will not be liable for any such claim by any other
party.
TRADEMARKS
TicIt is a trademark of ProSoft.
TriBBS is a registered trademark of TriSoft.
All other trademarks are the property of their respective owners.
AKNOWLEDGEMENTS
Special Thanks to Mark Goodwin for making TriBBS and his wonderful way
to make doc files, Mark I hope you don't mind me borrowing your format.
Thanks to Thomas Wagner for his great EXEC routines to minize memory
comsuption when running DOS programs from TicIt.
Thanks to Mark May for his wonderful Mythical Kingdom Package for
accessing various types of message base formats.
TABLE OF CONTENTS
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
SETTING UP TICIT . . . . . . . . . . . . . . . . . . . . . . . . . 2
THE TICIT CONFIGURATION FILE . . . . . . . . . . . . . . . . . 2
THE TICIT AREAS FILE . . . . . . . . . . . . . . . . . . . . . 4
RUNNING TICIT . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ADVANCED TICIT.CFG COMMANDS . . . . . . . . . . . . . . . . . . . . 6
ALLFIX COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . 8
ALLFIX MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . 10
OTHER TICIT COMMAND LINE COMMANDS . . . . . . . . . . . . . . . . . 11
MULTIPLE CONFIGURATION AND AREA FILES . . . . . . . . . . . . . . . 12
SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
i
INTRODUCTION
TicIt is a FidoNet TIC Processor written expressly for the TriBBS
Bulletin Board System. As such TicIt needs no other program to
import files into the TriBBS File Bases. TicIt Version 2.00+ will
only work with the 5.01+ Series of TriBBS, as the file lists are
now formatted.
REQUIREMENTS
TicIt requires an IBM PC or compatible computer with at least
460K of memory free to run. TicIt requires this large amount of
memory to speed its functions up. TicIt may be run off of a floppy
but is not recommended. TicIt also requires TriBBS 5.01+ series
to run correctly, any changes to TriBBS's FAREA.DAT will result in
data corruption, I will make every effort to update TicIt when
TriBBS changes. TicIt may be run on multinode systems *IF* only
one copy of TicIt is running at a time, however, people can be on the
board while TicIt is running, it shouldn't cause any problems.
1
SETTING UP TICIT
The first step in setting up TicIt is to create a directory for
TicIt. Use a DOS command similar to the following to create your
TicIt directory:
MD \TICIT
Next you must copy the file TicIt.EXE to the newly created TicIt
directory with a DOS command like the following:
COPY TICIT.EXE \TICIT
THE TICIT CONFIGURATION FILE
Now you must create a TicIt configuration file. This file must be
named TICIT.CFG and resides in your TicIt directory. You can
create a TicIt configuration file with any text editor. The
following in a sample TicIt configuration file:
----------------------------------------------------------------------
;
; TICIT.CFG for City Scape BBS
;
tribbs c:\tribbs
address 1:321/328
netmail c:\im\netmail
outecho c:\im\outbound
inecho c:\im\packets
----------------------------------------------------------------------
You should note that TicIt will treat anything after a line
beginning with a semicolon (;) as a comment. Comments are strictly
optional.
Now let's examine the TicIt configuration commands in the above
configuration file.
TRIBBS <node1's main directory>
The TRIBBS command is a required command and specifies where node
1's main directory is located.
ADDRESS <FidoNet address>
The ADDRESS command is a required command and tells TicIt the
FidoNet address that it should use in out-going TIC Packets.
2
NETMAIL <netmail directory>
The NETMAIL command is a required command and tells TicIt where
it is to place ARCMail and TicIt messages and where TicIt is
to look for incoming TicIt messages.
OUTBOUND <outgoing archive directory>
The OUTBOUND command is a required command and tells TicIt where
it is to place outgoing TIC files
TICPATH <incoming archive and packet directory>
The TICPATH command is a required command and tells TicIt where
it is to look for incoming TIC files.
There are a number of other optional configuration files command that
advanced users will want to take advantage too. They will be
discussed in detail in another section of this manual.
IMPORTANT: TicIt uses PKUNZIP.EXE, ARJ.EXE, and LHA.EXE to de-archive
the FILE_ID.DIZ or DESC.SDI. Therefore, all of these programs must
reside in a directory that is in your DOS PATH. If they are not
in your DOS PATH, TicIt will not be able to function correctly.
3
THE TICIT AREAS FILE
Next you must create a TicIt areas file. This file must be named
TICIT.BBS and resides in your TicIt directory. You can create a
TicIt configuration file with any text editor. The following is a
sample TicIt areas file:
----------------------------------------------------------------------
; TICIT.BBS for City Scape BBS
;
8 TRIBBS_SUPPORT 1:328/104 105 6:670/23 55:324/1
1 PROSOFT_FILES 1:321/102 103 105
----------------------------------------------------------------------
As with the TicIt configuration file, TicIt will treat anything
after a semicolon (;) as a comment in a TicIt areas file. Comments
are strictly optional.
The lines in the TicIt areas file use the following format:
<conference number> <echo name> <node address> <node address> <...>
Where:
<conference number> is the echo's conference number in your files
base. IMPORTANT: You need to specify a conference
number of 0 for passthru echoes. A passthru echo
is an echo that is echoed to your downlinks, but
is not carried on your board. (See also OTHER
COMMANDS for configuration setup for PassThru
echoes). TicIt now supports 30,000 conferences
per BBS file.
<echo name> is the echo's FidoNet File Dist. name,
up to 20 characters
<node address> is a node address that this echomail area is
echoed to. You must specify at least one echomail
address.
To keep the lines in TICIT.BBS as short as
possible, you can use a SEEN-BY like shorthand for
specifying node addresses. For example, if the
next node address has the same zone as the
previous node address you only have to specify the
next node's net and node address (net/node). If
the next node address has the same zone and net as
the previous node address you only have to specify
the next node's node address (node). You can
specify up to 30 nodes per echo name.
4
RUNNING TICIT
Running TicIt is a pretty simple matter. Simply add something like
the following to your frontend mailer's batch file where it processes
received TIC files:
cd \ticit
ticit
cd \im
Yes, it's that simple. TicIt both scans and tosses in a single
operation, as it keeps TicIt an extremely simple program to
use. However, to scan for new files in your own file bases, you'll
need to run TicIt with the HUB command-line parameter. TicIt when
it finds a ZIPped or ARJed files, will extract (if any) FILE_ID.DIZ
and format it for use in the TriBBS File List, thus eliminating any
running of FileMan(tm) for TriBBS to get them.
5
ADVANCED TICIT.CFG COMMANDS
TicIt offers a number of commands in its configuration file for
advanced setups. All of these commands are strictly optional. This
section explains these commands in detail.
HUBMODE < Yes or No >
The HUBMODE command tells TicIt wether or not it should
reprocess incoming TIC files for downlinks. It also is a
fail-safe switch incase the HUB command-line parameter is used
and the TICIT.IDX does not exist yet. HubMode is optional
and defaults to <No>
Example:
Hubmode yes
PASSTHRU <passthru file holding area path>
The PASSTHRU command tells TicIt where to move incoming files
which your downlinks want, but you do not carry on your board
yourself. CAUTION: Alot of passthru areas could take up harddrive
space on your board while holding the files for the mailer to
deliver!
Example:
passthru c:\im\passthru
FILE_LIST <echo list path & name of list>
The FILE_LIST command is used to specify what file TicIt will
send the a node that has included a %LIST in a message
line of an ALLFIX message.
Example:
file_list c:\fd\netfile\fidonet.na
6
PASSWORD <FidoNet address> <password>
The PASSWORD command is used to specify a node that has AllFix
access. You can have up to 100 PASSWORD commands in your
configuration file. A <password> can be up to 30 characters in
length and is case insensitive.
Example:
password 1:555/32 mypass
password 6/35/400 tribbs
password 1:328/104 lobster
BULLETIN <Path & name of bulletin to create>
The BULLETIN command is used to create a bulletin of the
last imported session of TIC files, much like the one TriNET
creates.
7
ALLFIX COMMANDS
TicIt offers a number of AllFix commands that can be used simply by
running TicIt using the following format at the DOS prompt:
TICIT ALLFIX <command>
This section will explain these AllFix commands in detail.
TICIT ALLFIX MGR
The MGR command instructs TicIt to scan and process any ALLFIX
messages in the netmail directory. Please note that it will base
its finding off the configuration files you specify, if you do not
run MGR for all the configuration files you have, any replies for
the unspecified configurations won't be generated.
TICIT ALLFIX FIND <FidoNet address>
The FIND command lists all of the active areas for a specified
node address.
Example:
TICIT allfix find 1:328/104
TICIT ALLFIX ADD <FidoNet address> <Echo> <Echo> <...>
The ADD command adds a specified node to one or more echo areas.
You should note that by specifying "ALL" for an echo area TicIt
will add the node to all available echo areas.
Example:
TICIT allfix add 1:328/104 tribbs c_echo
TICIT allfix add 6:32/400 all
TICIT ALLFIX DELETE <FidoNet address> <Echo> <Echo> <...>
The DELETE command deletes a specified node from one or more echo
areas. You should note that by specifying "ALL" for the echo
area TicIt will delete the node from all available echo areas.
Example:
TICIT allfix delete 328/104 comm fdecho
TICIT allfix delete 6:32/400 all
8
TICIT ALLFIX NOTIFY
The NOTIFY command will send a message to each of your AllFix
nodes that lists all of the areas that are available to the node
and what areas each node is active in.
9
ALLFIX MESSAGES
How do downlinks use TicIt's AllFix capabilities? Pretty easy,
actually. They simply address a message to AllFix or TicIt at your
system's address. On the subject line, they MUST put their AllFix
password. Then add any of these commands to the body of the message.
%LIST This switch instructs TicIt to write a message with a
list file. This list is configured in the TicIt
configuration file with the FILE_LIST command.
%QUERY This switch instructs TicIt to send a list of of active
areas in a message.
%HELP This switch instructs TicIt to send a message on how to
use the ALLFIX message capabilities
%PASS This switch instructs TicIt to change your password,
providing the correct one is supplied in the subject of
this AllFix message.
Example:
%PASS cityscape
In the body of an AllFix message, a downlink can turn echoes on and
off by simply listing them one echo name per line. An echo will be
deleted if it is preceded by a hypen (-) or added if it's preceded by a
plus (+). The list of echoes must be followed by a tearline
(---). Anything after the tearline is ignored by TICIT. Here's an
example body of an AllFix message:
----------------------------------------------------------------------
+COMM
+TRIBBS
-FDECHO
+DBRIDGE
%QUERY
---
Hi! This is ignored by TICIT. :)
----------------------------------------------------------------------
This message would instruct TicIt to turn on the COMM, TRIBBS, and
DBRIDGE echos and turn off the FDECHO. It would also send a list
of all the connected areas for that node.
10
OTHER TICIT COMMAND LINE COMMANDS
TicIt supports two other important command line commands. This
section details how these commands are used.
TICIT RESET
The RESET command forces TicIt to reset the files index
pointers in the TICIT.IDX file. Reset is very important after
adding a file base to TicIt's configuration files, as it will
start tossing all the files found in the new base if RESET is
not run before the HUB switch.
TICIT HUB
The HUB command instructs TicIt to search the specified
directories in TICIT.BBS for new files which are not found in
the TICIT.IDX file. TICIT.IDX is a record of the files name
which is loaded into a linked list, enabling for fast scanning.
Hub scans the specified areas from your TICIT.BBS, so if you have
more then one TICIT.BBS you will need to run HUB multiple times.
Hub also is one of two commands which needs a human operator, as it
asks information about each new file it finds. The HUB command
will prompt the user for information:
S - Sends the file to downlinks in specified group
U - Update Index Only will add the file to the indexes without
sending to anyone
P - Pass will bypass the file for another day
Q - Quits out of Hub mode for later use
TICIT SEND
The SEND command is a fast way to distribute a file without
using the hub command. Send distributes a file upto 30
nodes at a time. Send also requires a human operator to be
present.
If you wish to send files without the operator being present you
can now use a command line option to do it.
TICIT SEND /A<AreaName> /F<FileName> /P<FilePath> /D<Description>
/N<Nodes>... /N<Nodes> Up to 30 Nodes can be listed
Parameters:
/A - AreaName for the File to be sent under
/F - Actual File Name being sent
/P - Path to the File * Be Sure to Include Trailing Back Slash \
/D - Description * NO SPACES ALLOWED! - Use the Underscore "_"
/N - Each node to send this file to * up to 30 nodes can be
specified
11
MULTIPLE CONFIGURATION AND AREA FILES
TicIt allows you to use multiple configuration and area files. To
use multiple configuration files use the following TicIt command
line:
TicIt <configuration file number> ALLFIX <command>
or
TicIt <configuration file number> RESET
or
TicIt <configuration file number> HUB
The <configuration file number> must be a number from 1 to 9 and you
should name your files as follows:
TICIT1.CFG and TICIT1.BBS
TICIT2.CFG and TICIT2.BBS
etc.
1
SUPPORT
City Scape BBS - 413-568-5241
28.8k! V.FC!
Online 24hrs a Day
David Alger
1125 Shaker Rd
Westfield, Ma 01085
InterNet: dalger@k12.ucs.umass.edu
13