home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
RTUTI102.ZIP
/
RTUTI.DOC
< prev
next >
Wrap
Text File
|
1994-02-03
|
16KB
|
342 lines
RBBS 'Turbo' Universal Text Interface Version 1.00 (RTUTI)
Copyright 1993 by Walter C. Ames. ALL RIGHTS RESERVED
1.00 Released October 28, 1993
1.01 Released October 29, 1993
1.02 Released February 3, 1994
╓───────────────────────────────────────────────────────────────╖
║ TABLE OF CONTENTS ║
╙───────────────────────────────────────────────────────────────╜
1. License/Warranty/Registration......................... 1
1.1 License.......................................... 1
1.2 Warranty......................................... 1
1.3 Registration..................................... 1
2. Introduction.......................................... 2
2.1 About RTUTI...................................... 2
2.2 RTUTI Features................................... 2
2.3 Kudos............................................ 2
3. Installation.......................................... 3
3.1 Assumptions...................................... 3
3.2 System Requirements.............................. 3
3.3 Installation Summary............................. 3
4. Creating Your Configuration File...................... 4
5. Appendix.............................................. 6
5.1 Error Levels..................................... 6
5.2 Problem Reporting................................ 7
1. LICENSE * WARRANTY * REGISTRATION
1.1 License
Distribution and/or use is permitted under the following terms:
You may copy and distribute verbatim copies of the RTUTI
documentation and executable code as you receive it, in any medium,
provided that you conspicuously and appropriately publish on each
copy a valid copyright notice "Copyright 1993 by Walter C. Ames";
keep intact the notices on all files that refer to this license
agreement and to the absence of any warranty. PROVIDE UNMODIFIED
COPIES OF THE DOCUMENTATION AS PROVIDED WITH THE PROGRAM; and give
any of the other recipients of the RTUTI program a copy of this
license agreement along with the program. You may charge a
distribution fee for the physical act of transferring a copy, but
no more than is necessary to recover your actual costs incurred in
the transfer. Under no circumstances is RTUTI to be distributed in
such a way as to be construed as "value added" in a sales
transaction, such as, but not limited to, software bundled with a
modem or CD-ROM software collections, without the prior written
consent of the author.
1.2 Warranty
THIS PRODUCT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND,
INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE RESULTS AND
PERFORMANCE OF THIS PROGRAM IS ASSUMED BY YOU. FURTHERMORE, I THE
AUTHOR DO NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS
REGARDING THE USE OF OR THE RESULTS OF THE USE OF THE PROGRAM, OR
THAT THE PROGRAM WILL RUN WITHOUT ERROR, AND YOU RELY ON THE
PROGRAM AND RESULTS SOLELY AT YOUR OWN RISK. I THE AUTHOR CANNOT
ACCEPT RESPONSIBILITY FOR SYSTEM DAMAGE, LOSS OF PROFIT, OR ANY
OTHER SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES RESULTING FROM
THE USE OR INABILITY TO USE THIS PRODUCT.
1.3 Registration
This program is being released under the "SHAREWARE" concept. This
means that you can evaluate the program for a period of 30 days to
see if it meets your needs. If after a period of 30 days you
continue to use the program then registration is required. If you
do not register the program after 30 days you must discontinue use
of the program. See REGISTER.TXT for details on registration.
NOTE: If you feel that 30 days is insufficient time to evaluate
this program, please contact me electronically at any of the
enclosed network addresses or by calling my BBS. I may, at my
discretion extend the evaluation period on a case-by-case basis.
2. Introduction
2.1 About RTUTI
The RBBS 'Turbo' Universal Text Interface (RTUTI) is a series of
programs that are used to create a Standard Interface Layer for
Bulletin Board message traffic. These programs, in conjunction
with Networking software that supports the UTI format make it
possible for RBBS-PC Sysops to participate in Message Networks that
connect a multitude of BBS formats together.
2.2 Features:
■ Optimized for use with the Postlink(tm) Network Mail system
■ Handles any size message even if it exceeds RBBS's limits
■ Progress reporting for ease of operation
■ Verbose error trapping and reporting
■ Handles RBBS-PC v17.4 message header format
■ Will not re-export previously exported or imported mail
■ Updates RBBS mail waiting flags
■ Tagline checking and concatenation for a cleaner look
■ (*)User definable tagline or tagline suppression
■ Will re-address mail to SYSOP under several conditions.
(These conditions are user definable)
■ Author Supported Software!
(*) Denotes a (REGISTERED ONLY) Feature
2.3 Kudos
I would like to thank the following individuals for helping me
develop and test RTUTI. Without there help RTUTI would not be the
product it is.
Bruce Jackson
Dan Shore
Sam Coleman
3. INSTALLATION
3.1 Assumptions
Three basic assumptions are made:
1. You are an RBBS-PC SysOp with an operational RBBS
installation.
2. You are familiar with the operation of both DOS and RBBS.
3. You have a need for a UTI driver.
3.2 System Requirements
Although RTUTI was designed to be as generic as possible, the
following system configuration is required as a minimum:
1. An IBM PC, XT, AT, PS/2, or a 100% compatible.
2. A completely operational copy of RBBS-PC CPC12 - CPC17.4.
3. MS/PC-DOS 3.1 or above.
3.3 Installation Summary
1. Read the documentation to become familiar with available
options.
2. Determine the configuration options to be used.
3. Edit the parameters in the RBBS-UTI.CFG file.
4. Place all of the RTUTI Executable (.EXE) programs in a
directory reflected in your PATH statement.
Note: The file RBBS-UTI.CFG MUST reside in the local or DOS
Current directory at Runtime. This would be your Postlink
Home directory for a Postlink installation.
4. Creating your Configuration File
The RBBS 'Turbo' Universal Text Interface uses a common
configuration file to obtain all of it's system specific
information. The accuracy of the data contained in this file
is very important for proper operation of the UTI.
The configuration file is a standard ASCII text file. You may
use any ASCII Text editor to edit this file. All lines that
begin with the Pound '#' symbol are UTI command lines. These
lines will all have keywords following the pound symbol. All
lines that begin with a Semi-Colon ';' are considered comments
and are ignored. You may enter as many comment lines as you
feel necessary.
The following is a list of valid Keywords:
#NETWORK_AKA: This Keyword is used to define possible
Network Alias's. ie. Some networks like to
send messages to 'ALL SYSOPS'. Since your
name is not 'ALL SYSOPS' the message may not
get to you or it may not set your RBBS Mail
Waiting Flag. With this Keyword you can
define up to 10 Network Alias's for yourself.
This will cause the UTI to import any message
addressed to a Network AKA to be re-addressed
to SYSOP and set the Mail Waiting Flag. Each
Network AKA Keyword must be on a line by
itself.
#REAL_NAME: This Keyword is used to define the Real Name
of the SYSOP of this system. This is
necessary so that the UTI Export program can
re-address outbound messages From SYSOP (the
way RBBS enters it) to your Real name.
#REG_CODE: This Keyword is used to define the
Registration code for this copy of RTUTI. By
entering a valid registration code here you
will unlock the Registered Only features.
#REMOTE_NAME: This Keyword is the RBBS Remote Pseudonym.
This name will be used by the UTI to set the
RBBS Mail Waiting Flag for all inbound
messages to SYSOP. If a message comes in to
SYSOP, SYSOP_REALNAME or any of the Useable
AKA's the UTI will set this users Mail Waiting
Flag.
#SYSOP_AKA: This Keyword is used to define additional
AKA's for the SYSOP of this system. The best
use for this feature is to place the most
common misspellings of your name here. This
will ensure that all mail addressed (or mis-
addressed) to you will be re-addressed to you.
Confused yet? Lets take the user named
'Walter Ames' for example. A message comes in
addressed to 'Walter Aims' same guy?
(probably) ok if there was a SYSOP_AKA entry
with 'Walter Aims' defined that message would
have been re-addressed to SYSOP. You may have
up to 10 SYSOP_AKA's defined, each on a line
by itself.
#SYSTEM: This Keyword is probably one of the most
important. This is the full path and filename
to your RBBS CONFMAIL.DEF file. RTUTI uses
this file to resolve pathnames of your RBBS
conference USERS files. This way it can set
the RBBS Mail Waiting Flag for any user on
your system that receives a Network message.
If this keyword is NOT defined your Mail
Waiting Flags will NEVER get set.
#USE_TAGLINE: This Keyword is only available in the
Registered version. It takes 'Y' or 'N' as
it's parameter. If set to 'Y' it will append
an RTUTI Tagline to each and every message
that is exported from your system. If set to
'N' it will suppress the addition of RTUTI
Taglines.
#UTI_TAGLINE: This Keyword is only available in the
registered version. This is a user definable
Tagline. This string may be 40 characters in
length.
5. APPENDIX
5.1 Error Levels
Universal Text Interface programs (UTI) are virtually never run as
user applications. As a rule they are normally called by other
programs. Due to this, any error that may occur in processing must
be passed back to the parent task for processing/logging. The
parent process will usually log the error and reference it by it's
Errorlevel only (since most parent processes don't know how the UTI
handles errors or what error means what). The following list
contains the Errorlevels of all UTI programs by program type.
■ UTIEXPRT.EXE
0 Normal Termination
1 Error in Command Line Syntax. See File 'RBBS_UTI.ERR'
2 Unable to Open Input Message File
3 Unable to Open Output UTI_Txt File
4 Error Reading from Input Message File
5 Input Message Number Out of Range, Exiting
6 Next Message Record Number too Low, Exiting
7 Total Number of Node Records out of Range, Exiting
8 Unable to Open RBBS_UTI Configuration File
■ UTIIMPRT.EXE
0 Normal Termination
1 Unable to Open Confmail.def
2 Unable to Open Input UTI_Text File
3 Unable to Open Output Message File for write
4 Unable to Open Output Message File for read
5 Unable to Open Output Message File for update
■ UTIHIGH.EXE
0 Normal Termination
1 Unable to Open Input Message File
2 Unable to Open Output UTI_Text File for write
5.2 PROBLEM REPORTING
If you uncover a problem with the operation of this program please
contact the author using one of the following methods.
1. BBS - The GreyHawk BBS (410)720-5083 AT&T V.32Bis
-5084 USR DS V.32Bis
(410)290-3260 AT&T V.32Bis
-3261 USR DS V.32Bis
2. USPS - Walter C. Ames
9246 Moonfire Place
Columbia, MD 21045
3. NetMail - RelayNet ->GREYHAWK R/O Capable
FidoNet 1:261/1116 or 1:261/1117
RBBSNet 8:936/203 or 8:936/204
4. InterNet - walter@ghawk.com