home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
RBTCH242.ZIP
/
EXAMPLE.ZIP
/
SAMPLE.CFG
< prev
next >
Wrap
Text File
|
1994-01-01
|
25KB
|
591 lines
##############################################################################
# This is a sample configuration file for RBatch. As you can see, any line #
# that starts with a "#" is considered a comment. Note also that the #
# description for each line in the configuration file appears BEFORE the #
# actual entry. #
# #
# The ability to have comments in the configuration file is a new feature #
# of RBatch and is only available with version 2.10 on up. Case does not #
# matter when entering data in the configuration file. #
##############################################################################
#
# Path to Upload Directory;Pause Prompt
#
# - This is the full path to your Upload Directory.
# (Path/Dir - NO TRAILING BACKSLASH)
#
# - 20 Second Pause Prompt - enter YES after semi-colon.
#
# *** If you just have your path to the Upload Directory and NO
# SEMI-COLON then the feature is DISABLED. The pause prompt
# stays for 20 seconds or until user hit ENTER Key.
#
#
d:\new;yes
#
#=============================================================================
#
# Shall RBatch create a DORINFOx.DEF?;Path/name of the DORINFOx.DEF file
#
# First parameter MUST be either YES or NO. If you are
# running RBBS-17.4, you would specify "NO." (RBBS v.17.4
# is the first version to create its own DORINFOx.DEF file
# for DOORING protocols) for the first parameter, and the
# location of the DORINFOx.DEF file for the second parameter.
# All earlier versions of RBBS prior to 17.4 specify "YES"
# and RBatch will create a "working" copy of the DEF file in
# this specified location. (Note semicolon...)
#
# NO = RBatch DOES NOT create ; path to RBBS's (17.4) own file
# YES = RBatch DOES create ; where you want us to put it
#
NO;c:\rbbs\dorinfo1.def
#
#=============================================================================
#
# Extensions to check for duplicates -- or NONE:
#
# This parameter allows the SysOp to specify which
# extensions to check when RBatch checks for duplicates
# of uploaded files. If SysOp only wants the uploaded file
# checked just input the word NONE here instead.
#
# NOTE: ALL THE EXTENSIONS MUST BE SEPARATED BY A SEMI-COLON!!!
# *** MAXIMUM NUMBER OF EXTENSIONS = 15 ***
#
ZIP;ARJ;EXE;COM;ZOO;BAT;LZH
#
#=============================================================================
#
# Security Level,Time CREDIT percentage given for UPLOADS
#
# SECURITY LEVEL1,PERCENTAGE1;SECURITY LEVEL2,PERCENTAGE2
#
# Here is an example: 5,125;10,150;15,175;25,200
#
# Users with security levels LESS THAN OR EQUAL TO 5
# would get 125%,
# Users with security levels between 6 and 10 would get 150%,
# Users with security levels between 11 and 15 would get 175%,
# Users with security levels between 16 and 25 would get 200%.
#
# ~(Note the way commas and semicolons are used on this line.)
#
# You must have the HIGHEST value security level at the minimum
# if just using one time credit percentage. In other words, if
# the highest security level of a user on your BBS is 100, and you
# want ALL your users to have 100% time credits, then your
# configuration line would be:
#
# 100,100
#
# Remember that RBatch checks to see if the user's security
# level is LESS THAN OR EQUAL TO the security level(s) on this
# line and then uses the associated percentage.
#
# **** Currently you may define up to twenty security levels.
#
# The amount of time credit received (based on the percentage) is
# calculated as shown in these examples:
#
# Ex. # 1 - File upload time = 5:00 Minutes
# Time Credit% = 150% (7:30 Minutes)
# 5:00 + 7:30 = 12:30 of Time Credits
# Ex. # 2 - File Upload Time = 5:00 Minutes
# Time Credit% = 50% (2:30 Minutes)
# 5:00 + 2:30 = 7:30 of Time Credits
# Ex. # 3 - File Upload Time = 5:00 Minutes
# Time Credit% = 0%
# 5:00 + 0 = 5:00 of Time Credits
#
# The User always gets the time back it took to upload the file,
# plus the percentage that you assign in the configuration file.
#
5,200;6,200;5,200;6,200;5,200;6,200;5,200;6,200;5,200;6,200;20,200
#
#=============================================================================
#
# Path/Name primary FMS/.DIR;Path/Name secondary FMS/.DIR;Remove period
#
# This is the text directory where the uploaded filenames and their
# descriptions are WRITTEN. If you wish to post this information
# to more than one file, list the path/name of the second file AFTER
# the Semi-Colon. If you do not wish to post to more than one file,
# then you must enter "NONE" as the second parameter. The last
# parameter will post the filenames without the period. RBatch will
# pad with spaces and line up the extensions. DO NOT USE ANY
# PARAMETER PAST THE SECONDARY FILENAME IF YOU WANT PERIODS!
#
C:\RBBS\MASTER.DIR;C:\RBBS\STUFF.DIR
#
#=============================================================================
#
# Path to the .DIRs - Enter the word "BLANK" if using FMS:
#
# This is the path to where your .DIR's are. An example of
# this is:
# C:\FILES\
#
BLANK
#
#=============================================================================
#
# Path/Name to MESSAGES File: (Self Explanatory)
#
c:\rbbs\messages
#
#=============================================================================
#
# Path/Name to USERS File: (Self Explanatory)
#
c:\rbbs\users
#
#=============================================================================
#
# Path/Name to CALLERS File: (Self Explanatory)
#
C:\rbbs\caller1
#
#=============================================================================
#
# Path/Name to DIR.CAT File: (Self Explanatory)
#
c:\rbbs\dir.cat
#
#=============================================================================
#
# Path/Name to XFER-?.DEF File:
#
# Protocols ALWAYS write the Xfer-?.Def file in the CURRENT directory
# when the protocol is invoked. Make sure that you have your
# SET DSZLOG=XFER-?.DEF (? = Node #) in your AUTOEXEC.BAT or your
# DESQVIEW startup window batch file. Do not use a path in
# your SET DSZLOG statement.
#
# For example, if you are in the RBBS directory when you execute
# DSZ, the XFER-?.DEF file will reside in the RBBS Directory.
# If you change to your upload directory when you invoke DSZ,
# the XFER-?.DEF file will reside in your upload directory.
# Note that RBatch will DELETE the XFER-?.DEF file, when there
# are just uploads.
#
# If you are doing bidirectional transfers, the XFER will have
# to be located in the current directory as the user when doing
# a transfer (the Main RBBS directory or the Node Directory).
# RBatch will not delete the XFER due to RBBS needing to "see"
# the XFER file to report a successful transfer.
#
d:\new\xfer-1.def
#
#=============================================================================
#
# SysOp's secret name :
#
# Enter "BLANK" if you do not wish the USERS file to be updated
# with file count information for SysOp file transfers.
#
# Also if you wish to be notified of a personal upload you MUST
# use your Secret Name, otherwise RBatch does not know who you
# are and cannot set the personal upload flag.
#
SECRET NAME
#
#=============================================================================
#
# Min Security Level to Categorize;Path/Name of UPCAT.HLP File:
#
# The First Parameter is the MINIMUM security level a user must have
# in order to categorize a file that he/she uploaded. If their level
# is LOWER than this value, the uploaded file will have the default
# category code for FMS (line #15), and in the .DIR system, will be
# posted to the file listed on line #5 in this configuration file.
# The Second Parameter is the path/filename of the UPCAT.HLP file.
#
# < A useful feature for SYSOPS is that you do not have
# to use the SAME UPCAT.HLP file you specify in RBBS's
# CONFIG parameter #! The file you specify here may
# display entirely different categories, or you may
# create a special one for local/SYSOP only uploads! >
#
# RBatch now supports colorized UPCAT.HLP files for users that
# have color chosen as their graphics type. The program will look
# for the following:
#
# Non-Color Graphics Choice Color Graphics Choice
# ------------------------- ---------------------
#
# UPCAT.HLP UPCATC.HLP
#
# You will note that the program looks for the filename with a "C"
# appended to the filename. If the "C" file does not exist then
# the non-color file is used. Also, remember that you can call
# RBatch's UPCAT.HLP file whatever you wish, as long as it is specified
# in the configuration file.
#
5;C:\RBBS\UPCAT.HLP
#
#=============================================================================
#
# Are you using FMS or .DIR?
#
# Enter: FMS or DIR
#
FMS
#
#=============================================================================
#
# Default Category or Path/Name of SysOp-only uploads file (.DIR):
#
# This is the category given to uploads:
# 1. that are saved by the SysOp after a user times out
# (falls asleep, too busy getting a beer, etc.) during or
# after the upload WITHOUT entering the category.
# 2. if a user drops carrier during the upload process.
# 3. where the user does not have a high enough security level
# to categorize uploads.
#
# If the SysOp is using the .DIR file system, then this entry will be
# the path/name of the file that the SysOp wants the personal (/) uploads
# posted to. This file is only for the .DIR file system and not the FMS.
#
UNC
#
#=============================================================================
#
# Compression type all files are converted to:
#
# Enter "NONE" if you perform no conversions in your Batch File
#
# If you have batch files (PHASE?.BAT, CARCZIP.BAT, etc.) which convert
# all uploaded files to a common format, enter the extension converted
# TO here, otherwise, enter "NONE."
#
ZIP
#
#=============================================================================
#
# Save files on User Timed Out or Dropped Carrier Uploads?;Delete Partial Files?
# Enter: YES or NO
#
# If you just have YES on this line and nothing else, then RBatch will not
# delete partial file uploads (uploads with "E" or "L" in the DSZLOG file).
# If you wish to delete partial files, have this line entered as "YES;YES"
# or "NO;YES".
#
YES;YES
#
#=============================================================================
#
# Use Fossil Driver?
#
# Enter: YES or NO
#
# RBatch has support for the fossil drivers X00 or BNU.
# Enter either "YES" or "NO" on this line in the configuration file.
#
# (We also support 16550AFN UARTS.)
#
# If you run with a special type of COM Port setup (non-standard
# IRQ's, etc.) you will be required to utilize a FOSSIL driver,
# or RBatch will not function properly!
#
NO
#
#=============================================================================
#
# Size of first FMS/.DIR File Description Line:
#
# Enter: a number from 40 to 46
#
45
#
#=============================================================================
#
# Number of Lines for Extended Descriptions;Use BAMA support;Post BamaWho if SysOp?
#
# Enter: # of lines;YES or NO;YES or NO
#
# Place the value of the maximum number of lines you will allow in
# your FMS/.DIR's for extended FMS descriptions as the FIRST parameter
# on this line. For the second parameter, enter either "YES" or "NO"
# YES if you use the BAMA WHO mod for posting the name of the
# uploader to the FMS, "NO" to disable this feature.
#
# If you do not wish to have "Uploaded by SysOp" when you upload a file
# to your own system, then have the third parameter set to "NO".
#
# If you wish to have "Uploaded by SysOp", then set the third parameter
# to "YES"
#
# ==== (For NO extended descriptions, enter "0" as the FIRST parameter.) ====
#
6;YES;NO
#
#=============================================================================
#
# Use FFS System;Path/Name of Fidx.Def file;Path/Name of Lidx.Def;Sec Level
#
# YES or NO - for using FFS System.
#
# It is assumed that if the SysOp uses the TAB file of the FFS system,
# that the filename is the same as the FIDX.DEF file, except that it
# has a "T" in it & resides in the same directory as FIDX. The security
# level is who can overwrite an existing file if RBatch detects a
# duplicate file. RBatch will prompt the user to overwrite the existing
# file and if user says "Y", RBatch copies the upload to the same directory
# as the duplicate file and then deletes the file from the upload directory.
#
YES;c:\rbbs\fidx.def;c:\rbbs\lidx.def;1
#
#=============================================================================
#
# Path/Name of file listing Directories to check for duplicate Uploads:
#
# This is a FILE that contains PATHS to file directories
# to be checked for duplicate files in ADDITION to the ones that the
# FFS already indexes. Here is an example of a listing:
#
# Do not enter each of these paths in the configuration file!!
# The filename you specify on the configuration line contains
# these paths.
#
# c:\temp\
# c:\testing\
# d:\other\
#
# (One directory per line, and each line MUST END WITH A BACKSLASH!)
#
# If you specify "NO" for using a FFS system in line #22, then this
# list of directories is what is used by RBatch to check for duplicate
# uploads. *** MAXIMUM NUMBER OF DIRECTORIES SUPPORTED = 80 ***
#
c:\rbbs\dupelist.lst
#
#=============================================================================
#
# Environment Running under (choose one):
#
# Enter: DOS - Running RBBS-PC\RBatch in DOS
# DV - Running RBBS-PC\RBatch in DV
# NET - Running RBBS-PC\Rbatch in a Network Environment
# that REQUIRES running DOS's SHARE.EXE
#
DV
#
#=============================================================================
#
# BBS Name to appear on Registered Versions:
#
# Enter: 50 characters Maximum
#
YOUR BBS NAME HERE
#
#=============================================================================
#
# Registration Number:
#
# Enter: 20 Alpha-Numeric Registration Code
#
# (Input all "0"s if unregistered)
#
00000000000000000000
#
#=============================================================================
#
# Process .DIZ/.SDI/.DOZ files?;Work Directory;File with archive commands;DOZ Priority
# 1 2 3 4
#
# Enter: 1. YES or NO - This tells RBatch to process FILE_ID.DIZ,
# DESC.SDI, or .DOZ files.
# 2. Path to the work directory we will use to decompress
# the DIZ, DOZ*, or SDI file into. NOTE: This directory
# must actually exist in order to process these files!
# RBatch creates, then deletes, NODE# directories under
# this specified directory.
# 3. The THIRD parameter is the filename that contains
# a list of archive extensions and their associated
# command lines for DEcompressing (unZIPping, unARCing,
# etc.) for the decompressors that you wish to support.
# 4. DOZ files take priority over .DIZ/.SDI files if the
# word DOZ is the last parameter. If no parameter is
# used .DIZ/.SDI files take precedence for file
# descriptions.
#
# Ex.: ARC.LST (or whatever name you choose) is a text file
# like this:
#
# ARJ;C:\RBBS\ARJ E
# ZIP;C:\PKZIP\PKUNZIP -O
# ^ ^
# 1 2
#
# The FIRST part is the extension to process
# The SECOND parameter is the path/command line
# to use for that particular extension.
#
# NOTE: If a file is uploaded and its extension does not match an
# entry in this file, the upload will not be checked for an
# embedded description file (FILE_ID.DIZ or DESC.SDI).
#
# For more information on .DOZ files, see the
# WHATISA.DOZ file included in this archive.
#
# SysOp's now have the ability for the .DOZ file to OVERRIDE the
# .DIZ/.SDI files. If you wish to OVERRIDE, put ";DOZ" as the last
# parameter on this line. If you do not add anything to the end
# of this line, the program will read a .DIZ/.SDI file before it
# reads a .DOZ file for the file description.
#
# Here is an example of .DIZ/.SDI having priority:
#
# YES;D:\WORK;F:\TC\ARC.LST
#
YES;D:\NEW\WORK;C:\RBBS\ARC.LST
#
#=============================================================================
#
# Allow Personal Files;Sec Level;Path/Filename of Personal File;Upld UserName
#
# This consists of 4 parts (each seperated by a SEMI-COLON) :
#
# a. Allow Personal Uploads - YES or NO
# b. Security Level ( Greater than or equal to) to use Personal Uploads
# c. Path/Filename of the Personal Upload File (Priv.Def)
# [This is the same directory as where your personal files are]
# d. YES if you wish to have the Username of the person uploading the file
# as part of the file description.
#
# IF YOU DO NOT WANT THE USERNAME AS PART OF THE DESCRIPTION, DO NOT
# ADD ANYTHING AFTER THE PATH/FILENAME OF THE PERSONAL FILE!!
#
YES;2;C:\RBBS\PRIVATE\PRIV.DIR;YES
#
#=============================================================================
#
# Allow Dist. Lists;Security Level to use List;Path to Distribution Lists
#
# This consists of 4 parts (each seperated by a SEMI-COLON) :
#
# a. Allow distribution lists for Personal Uploads - YES or NO
# b. Security Level to be allowed to use distribution lists. This
# security level must be equal to or greater than the .cfg level
# in order to use the distribution list feature.
# c. Path to directory that contains the distribution lists
# [ NOTE: THIS MUST END WITH A TRAILING BACKSLASH !! ]
# Also, all distribution list MUST end with a .LST, as
# per RBBS rules.
# d. This is the name of the help file that is displayed to the user
# if they select "H" when prompted for a distribution list name.
# See the file WHATSNEW for details on the format of this file.
#
YES;1;C:\RBBS\;DIST.HLP
#
#=============================================================================
#
# Ext Descriptions;# of lines;Sec Level for Sec Level Pers Uploads;Start Pos.;Length
#
# This consists of 5 parts (each seperated by a SEMI-COLON) :
#
# a. Allow extended descriptions in persoal uploads - YES or NO
# b. Number of extended description lines allowed
# c. Security Level (greater than or equal to this) for a user to
# be able to post a personal upload to a security level
# d. Starting point in user record for identifying field
# e. Length of identifying field from starting point in user record
#
# Note: The most common way to use the Identifying field is to
# start at 1 and have 31 characters (The persons Name).
# Check your RBBS configuration file to see what you have
# set up as your identifying field. The default for RBBS
# is the username (start = 1, length = 31).
#
NO;5;20;1;31
#
#=============================================================================
#
# Sec Level;Batch file;Batch file;Batch file
#
# --- This is new in RBatch version 2.00 ---
#
# This consists of 1 to 4 parts (each seperated by a SEMI-COLON) :
#
# - Part 1 is mandatory while parts 2-4 are optional -
# ^^^^^^^^^ ^^^^^^^^
# a. Security Level (greater than or equal to) to bypass the batch
# files to check uploads.
# b. Name of the first batch file to check uploads
# c. Name of the second batch file to check uploads
# d. Name of the third batch file to check uploads
#
# If no batch files are named, the program defaults to using
# PHASE1.BAT, PHASE2.BAT & PHASE3.BAT IF THEY EXIST. Note that
# the batch file(s) MUST RESIDE in the SAME directory as the
# RBatch.CFG file.
#
# One important point to remember is that RBatch looks for the batch
# file in the SAME DIRECTORY as the Configuration File.
201
#
#=============================================================================
#
# BBS systems that have download/day byte ratios can now give
# byte credits back based upon the users security level. These
# byte credits will only be in affect for the current day and
# users cannot "Bank" these credits for use another day.
# (RBatch modifies the "Bytes Downloaded Today" field in the
# users record). This new feature is enabled by having the
# word "YES" as the first parameter on line 32 of the
# configuration file. If you do not wish to use this feature
# then put "NO" as the first parameter (do not use the quotes
# in the configuration file. If you do use this new feature,
# then the next parameters are the security level and the
# percentage of the size of the file uploaded to give to the
# user as byte credits. The format of these entries is the
# same as the time credit entries used on line 3 in the
# configuration file. Here are examples of the new feature:
#
# A. I do not want to use the new feature:
#
# NO;
#
# B. I want to use the new feature:
#
# YES;5,25;10,25;15,35;50,100
#
# Choice "A" is self-explainatory.
#
# Choice "B" is setup so that user with a security level less
# than or equal to 4 get a 25% byte credit, users with security
# levels from 5-9 will get a 25% credit of files uploaded, users
# with a security level from 10-14 will get a 25% credit, users
# with a security level from 16-49 will get a 35% credit, and
# users with security level of 50 will get 100% credit.
#
# All users with a security level ABOVE 50 will not get ANY
# credits (these higher security levels are USUALLY your
# subscribers/contributing users and don't need any byte
# credits).
#
YES;5,25;10,25;15,35;50,100
#
#=============================================================================
#
# Support for BusiMods(STUNY) and RFM is noted here. If
# you run the BusiMods then your first entry will be YES
# and if you use RFM, the second entry will also be YES.
# See below for samples.
#
# The entry is as follows:
#
# Syntax: LARGE FFS;RFM
#
# Example: YES;NO - Use Large FFS;Don't use RFM
# YES;YES - Use Large FFS;Use RFM
# NO;NO - Don't use Large FFS;Don't use RFM
# NO;YES - Don't use Large FFS;Use RFM
#
NO;NO
#
#
#