home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
o
/
o_qwk10.zip
/
SAMPLE.CFG
< prev
next >
Wrap
Text File
|
1992-12-31
|
15KB
|
381 lines
%%%%%%%%%%%%%%%%%%%%%%%%%%%
% %
% Sample O_QWKer.CFG %
% %
%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% BBSID Identification of the QWK packet. This name is
% limited to 8 (DOS filename) characters and must be
% chosen in a way which can help users to identify
% your BBS. It should be as unique as possible.
%
BBSID MidiThru
%
% BBSWHERE Location of your system, to be included in the QWK
% (optional) packet header. This parameter is just to keep
% compatibility with QWK format definition.
%
BBSWHERE Aveiro, Portugal
%
% BBSPHONE Data phone number of your system to be included in
% (optional) the QWK packet header. This parameter is just to
% keep compatibility with QWK format definition.
%
BBSPHONE 351-34-313554
%
% PRM .PRM file. In the absence of this command, the
% (optional) door uses the OPUS environment variable (defined
% with SET OPUS=xxxx.PRM).
%
% PRM C:\OPUS\BBS.PRM
%
% NEWS News file to be included in the QWK packets.
% (optional)
% NEWS C:\OPUS\QWK\NEWS.TXT
%
% WELCOME ANSI screen to be included in the QWK packets
% (optional) (it's shown at the beginning of the users off-line
% reading session).
%
% WELCOME C:\OPUS\QWK\HELLO.ANS
%
% GOODBYE ANSI screen to be included in the QWK packets
% (optional) (shown to the users at the end of their off-line
% reading session).
%
% GOODBYE C:\OPUS\QWK\BYEBYE.ANS
%
% NEWFILES New files list, to be included in the QWK packets.
% (optional) This file must be created by a separate program
% (not included) like Opus-Fam.
%
NEWFILES C:\OPUS\FILES\NEWFILES.TXT
%
% BULLETINS Bulletins directory. This directory contains files
% (optional) with names BLT-*.*, and the inclusion in the QWK
% packets is based upon the file date. This means
% that all new bulletins since the users last call
% date are included in his/her packet.
%
% BULLETINS C:\OPUS\BULL\
%
% FORCE The user may active and deactivate several options
% (optional) in his/her O_QWKer configuration menu, to control
% what is included in their QWK packet. This command
% exists to control the use of those options and it
% is applicable on the following:
%
% WELCOME always include Welcome Screen
% GOODBYE always include Goodbye Screen
% NEWS always include News file
% NEWFILES always include new files list
% BULLETINS always include new bulletins
% REPLIES always include messages originated by
% the user
% NOVICE force Novice help level inside O_QWKer
%
% FORCE NEWS
%
% There is another syntax for this command, which
% allows you to force the scan of certain message
% areas, so that the user is not allowed to turn
% them off. That's the AREAS option.
%
% FORCE AREA 1
%
% EXCLUDE This command has the opposite effect of FORCE. In
% (optional) its first syntax, it allows you to deny the user
% option of scanning message base for his/her Opus
% Alias name. For that you use the option ALIAS.
%
EXCLUDE ALIAS
%
% The second syntax is AREAS, and allows you to
% define message areas to be excluded from the
% available O_QWKer areas list to any user with
% privilege bellow AsstSysop.
%
EXCLUDE AREAS 0 31 99
%
% FULLSCAN AREA This command makes the message scanning process
% (optional) ignore user pointers and always scan all messages
% in the areas to which it is applied.
%
% It is useful in an area where messages are
% frequently deleted, such as your Local Mail area.
% In such areas, it is not difficult to have an user
% pointer directed beyond the last message, which
% means no messages will be included in the packet,
% even if there are some unread. With the full scan,
% you guarantee that all eligible messages are
% delivered.
%
% You should activate a maintenance procedure to
% periodically erase received messages in the areas
% that you full scan, because even received messages
% keep being included in the user packets.
%
% FULLSCAN AREA 1
%
% PACKER TEXT
% PACKER COMPRESS
% PACKER UNCOMPRESS
% These three commands groups define the packet
% compression scheme available for user selection.
%
% TEXT - description shown to users
% COMPRESS - command used to compress QWK packets
% UNCOMPRESS - command to uncompress REP packets
%
% You may define up to eight compression methods.
% The first one defined is used as default.
%
PACKER TEXT Zip 1.10
PACKER COMPRESS C:\UTIL\PKZIP.EXE -U
PACKER UNCOMPRESS C:\UTIL\PKUNZIP.EXE
%
% REDIRECT COMPRESSORS
% (optional) This option allows the redirection of compressor
% output to the user, thus giving visual feedback
% while their QWK packet is being compressed.
%
% When defined, it is applied to any capable defined
% compressor, like PKZIP and LHA.
%
% It is automatically disabled for Local usage.
%
REDIRECT COMPRESSORS
%
% PROTOCOL TEXT
% PROTOCOL UPLOAD
% PROTOCOL DOWNLOAD
% These groups of three commands define the transfer
% options available for user selection.
%
% TEXT - description shown to users
% UPLOAD - batch file to upload REP packets
% DOWNLOAD - batch file to download QWK packets
%
% You may define up to eight protocols. The first
% one defined is used as default.
%
% Please note you must use a batch file, so that
% parameters can be passed to the protocol engine.
%
PROTOCOL TEXT Zmodem (DSZ)
PROTOCOL UPLOAD C:\OPUS\RZ.BAT
PROTOCOL DOWNLOAD C:\OPUS\SZ.BAT
%
% NEWLINE This option defines what character will be used as
% (optional) CR/LF in messages included in the packet. All
% known off-line readers expect the character "π"
% (ASCII 227 decimal), so this is the default value.
%
% Changing the default implies the need of a special
% reader, but will give the possibility to work with
% codepages where char 227 may not be made available
% for separator functions (e.g. Chinese).
%
% NEWLINE 160
%
% MSGID KLUDGE If this option is defined, all messages entered on
% (optional) Echomail areas will include a MSGID kludge.
%
% MSGID KLUDGE
%
% SHOW KLUDGES If this option is defined, all messages scanned to
% (optional) Sysop or AsstSysop will include Kludges, Seen-by's
% and Path lines.
%
% SHOW KLUDGES
%
% ALTER TEARLINE
% (optional) According to FTSC documents and Echomail Policy,
% only one tearline may appear on an echomail
% message. Nevertheless it is not uncommon to find
% messages containing 2 or even 3 of those. O_QWKer
% avoids deleting lines from the received messages
% but will substitute any candidate occurrence to
% -*-
%
% Going further, there are many echomail processors
% which do not respect the existence of a tearline
% in the message and add another one, so this option
% will avoid the normal inclusion of a tearline, and
% will rather include:
%
% -*- Opus-CBCS x.xx via O_QWKer vxxx
%
% If you use the internal Opus echomail scanner,
% forget about this option, since you'll never need
% it.
%
% ALTER TEARLINE
%
% HELPPATH If this option is defined, it states where O_QWKer
% (optional) will be looking for the on-line help OEC files. By
% default, it is used the path to the executable
% O_QWKer.EXE.
%
% HELPPATH c:\o_qwker\help
%
%
% STATUS LINE When this option is defined, a status line will
% (optional) appear at the console, allowing the Sysop to know
% who is using the mail door, the baudrate, and the
% caller's remaining time inside O_QWKer.
%
STATUS LINE
%
% TIMELIMIT Maximum allowed time (in minutes) for an O_QWKer
% (optional) session. It defaults to 10 (minutes).
%
% TIMELIMIT 15
%
% IDLETIME Maximum inactivity time (in minutes) allowed while
% (optional) inside the mail door. It defaults to 3 (minutes).
%
% IDLETIME 2
%
% REFUND Percentage of time used inside the door to be
% (optional) refunded to the user. It defaults to 0% (no time
% refunded).
%
% REFUND 50
%
% MAXMSGS Maximum number of messages which can be included
% (optional) in a single QWK packet.
%
% If used with the PROPORTIONAL qualifier, this
% command refers to the number of messages allowed
% if the user is connected at 1200 baud, so for 2400
% it's the double the 1200 baud rate, and so on. By
% default it assumes the fixed value of 200.
%
% When O_QWKer is used in local mode, PROPORTIONAL
% resolves to 2,147,483,647 so we may say it is
% unlimited.
%
MAXMSGS 300
% MAXMSGS PROPORTIONAL 100
%
% MAXLINES Maximum number of lines for each message included
% (optional) in the QWK packet. If the message is bigger, it is
% automatically split in chunks (several messages
% with the same number at the reader). Default is 60
% lines.
%
MAXLINES 100
%
% LOGMODE Detail level of the log. The options are:
% (optional)
% LOGMODE TERSE (light)
% LOGMODE VERBOSE
% LOGMODE TRACE (lots of info)
%
% It defaults to VERBOSE.
%
% LOGMODE TERSE
%
% LOGFILE O_QWKer log filename. It defaults to O_QWKer.LOG
% (optional) in the executable (O_QWKer.EXE) directory.
%
% For multi-line Opus installations you should use
% one different file for each task. You can specify
% it by using the standard Opus wildcard for task
% number (##).
%
% LOGFILE C:\LOG\O_QWKer.LOG
LOGFILE C:\O_QWKER\LOG##.LOG
%
% TEMPDIR Directory used by O_QWKer to process packets. All
% files in this directory are erased, so be sure to
% define it properly. The TEMPDIR value can also
% point to a RAMdisk.
%
% For multi-line Opus installations you should use a
% different directory for each task. You may specify
% it by using the standard Opus wildcard for task
% number (##).
%
% For security reasons TEMPDIR defaults to the name
% \O_QWKER$.TMP on the executable's volume, but
% please note this isn't an option but rather a
% protection to your system.
%
% A swap directory is also created inside TEMPDIR.
%
% TEMPDIR C:\TMPQWK
TEMPDIR E:\QWK##
%
% QWKAREA Opus File Area number or Pathname to where QWK
% (optional) packets are to be moved in case of a Download
% failure, so that the user is allowed to perform a
% deferred download after quitting the mail door.
%
% In your NERF.BAT file you should check if there is
% any *.QWK file on the corresponding directory and
% erase it after each user logs out, to guarantee
% that no one will be able to receive packets
% belonging to another user.
%
% If this option is not defined in the configuration
% file, O_QWKer will not try to move the packet to
% somewhere in case of Download failure.
%
% QWKAREA 10
% QWKAREA F:\QWKPKT
%
% BADPATH DOS path where orphaned messages are stored. This
% (optional) option has precedence over the BAD_ECHO pathname
% in BBS.CTL. If neither exist (either BADPATH in
% .CFG file or Opus BAD_ECHO) then the orphaned
% messages are discarded.
%
BADPATH F:\BADQWK
%
% ASSIGN This command allows you to use O_QWKer across
% (optional) networks. Although it exists mainly to support
% local usage, it applies to both local and remote
% sessions.
%
% All occurrences of the path defined as the first
% parameter will be searched in Opus system files
% (SYSMSG.DAT, SYSFILE.DAT) and processed by this
% door as being the path corresponding to the second
% parameter, just like DOS Assign command.
%
% You may declare up to 5 ASSIGN paths.
%
% ASSIGN C: O:
% ASSIGN X:\OPUS\SYSTEM C:\OPUS
%
% LOCALQWK Directory where QWK packets generated in local
% mode are stored. This is useful to a Sysop using
% his/her off-line reader across a network.
%
% Default is \O_QWKER$.LOC on the volume where the
% executable is installed.
%
LOCALQWK N:\SLMR\QWK
%
% LOCALREP Directory where REP packets to be processed in
% local mode are stored. This is useful to a Sysop
% using his/her off-line reader across a network.
%
% Default is \O_QWKER$.LOC on the binary's volume.
%
LOCALREP N:\SLMR\REP
%
% LOCALUSER Name of the LASTUSxx.DAT file to be used in local
% mode. Be aware that if you want to take advantage
% of the auto-scan O_QWKer feature in barefoot Opus
% installations, you should use the name of correct
% LASTUSxx.DAT file for your keyboard mode Opus task.
%
LOCALUSER C:\OPUS\LASTUS02.DAT
%
%%%%%%%%%%%%%%%%%
% END OF Sample %
%%%%%%%%%%%%%%%%%