home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
ROMPR138.ZIP
/
ROMPROC.CFG
< prev
next >
Wrap
Text File
|
1994-03-19
|
10KB
|
230 lines
;
;
;
; ┌────┐
; │──═─│
; │ ── │ ─────┐ ┌────┐ ROMProc Configuration File
; │ │ ROMProc │──═─│ Version 1.38
; │ │ └────> │ ── │ (c) Copyright 1993-1994 - Stacy Smith
; │ │ │ │
; │ │ │ │
; ─┴────┴─ ─┴────┴─
;
;
; The latest version of ROMProc can always be obtained from my BBS:
;
; The Bloom Beacon-Picayune BBS
; Node 1: (919) 557-3845 (USRobotics Courier Dual Standard)
; Node 2: (919) 557-0645 (USRobotics Courier V.32bis)
; Node 3: (919) 557-0745 (Hayes Optima 288 V.FC)
; Fidonet 1:151/106 (magic tag ROMPROC)
;
;
; ╔════════════════════════════════════╗
; ║ General Options And Parameters ║
; ╚════════════════════════════════════╝
;
; The registration code, BBS name and sysop name EXACTLY as provided to you on
; your registration letter. If this is an unregistered version, comment out
; these lines, or don't change them. Note that these are case-sensitive!
REG_CODE 0000000000
BBS_NAME UNREGISTERED
SYSOP_NAME SYSOP
; The full path for the specific subdirectory for ROMProc to store file(s) to
; be downloaded. This must include the trailing backslash! If this directory
; does not exist at runtime, ROMProc will attempt to create it. This can be
; set to a RAM disk for greater speed, since ROMProc will detect an out of
; disk space condition and allow the download to continue from the original
; file. An environment variable may also be entered using the standard
; %VARIABLE% notation DOS uses; note that the environment variable definition
; must adhere to the same requirements as specifying a work directory.
WORK_DIR d:\work\
; The full path for the subdirectory for ROMProc to place its locking semaphore
; file(s). This subdirectory must be available to all CPUs on your LAN and
; must include the trailing backslash!
COMMON_DIR h:\romproc\
; The size of the disk I/O buffers you wish to allocate in bytes (valid values
; are between 2048 bytes and 16384 bytes). Optimal performance is obtained with
; a value that is a multiple of 2048 (a typical hard disk cluster size).
DISK_BUFFER 4096
; The path/filename of the log file for ROMProc to record errors. Comment
; out if you don't want any disk error logging.
LOG_FILE c:\romproc\romproc.log
; If you want ROMProc to preserve two lines at the top or bottom of the
; local display, enter TOP or BOTTOM as desired, otherwise, enter NONE or
; comment the line out.
LOCK_LINES top
; The directory path and filename for your BBS ad to be added to each and every
; archive processed by ROMProc. Note that you must provide a path, or it will
; not be copied. Please use the archive comment instead, as BBS ad files
; are the scourge of the BBS world...
;BBS_AD_FILE c:\romproc\bbs_ad.txt
; If you want ROMProc to comment archives (if supported by the archive format)
; enter YES. If not, enter NO or comment the line out.
COMMENT_ARC yes
;
; ╔══════════════════════════════════╗
; ║ Drive Processing Definitions ║
; ╚══════════════════════════════════╝
;
; Specify the drive letters for file preprocessing (BBS ad insertion and/or
; commenting). Ranges may be seperated by a hyphen, and/or individual drives
; may be seperated by spaces, commas or semi-colons. Any file requested from
; a non-specified drive will be tranmitted, unmodified, from the original
; location.
PROC_DRIVE C D E-J
; Specify the drive letters for locking, by entering the individual drives
; to be locked, one physical drive per line. Ranges may be seperated by a
; hyphen, and/or individual drives may be seperated by spaces, commas or
; semi-colons. Note that you normally lock by physical drive; if you have
; multiple logical drives per physical drive (e.g. a partitioned hard disk or
; CD-ROM changer), list all the logical drive letters on the same LOCK_DRIVE
; command line.
LOCK_DRIVE C
LOCK_DRIVE D
LOCK_DRIVE E-J
; The amount of time (in seconds) that ROMProc will wait for a drive to unlock
; before displaying the text indicated by DELAY_PROMPT. This defaults to 5
; seconds if commented out.
DELAY_TIME 5
; This is the amount of time (in seconds) that ROMProc will wait for a drive
; to unlock. If this time is exceeded, ROMProc will abort the transfer.
; This defaults to 30 seconds if commented out.
ABORT_TIME 30
;
; ╔═══════════════════════════════╗
; ║ Communication Definitions ║
; ╚═══════════════════════════════╝
;
; If you want ROMProc to output status information to the user on-line, enter
; YES; if you do not want ROMProc to output information, enter NO or comment
; the line out.
COMM_IO yes
; This line of text will be displayed to the user upon the start of download
; file processing. It should be used to inform the user that it may take a
; few moments to get the files ready. If you desire a message longer than 80
; characters, an external ASCII text file may be defined by preceding the
; filespec with a '%' character.
PROC_PROMPT Please wait while ROMProc prepares your files for download...
; This line of text will be displayed to the user upon the start of the
; transfer protocol. It should be used to inform the user to start the download
; on their end. If you desire a message longer than 80 characters, an external
; ASCII text file may be defined by preceding the filespec with a '%'
; character.
DL_PROMPT Preparation complete. Begin your download now...
; This line of text will be displayed to the user if ROMProc waits for a
; locked drive to unlock for the amount of time specified by DELAY_TIME. An
; ASCII text file may be defined for this parameter as well.
DELAY_PROMPT ...Waiting for slow drive to become available
; This line of text will be displayed to the user if ROMProc waits for a
; locked drive to unlock for the amount of time specified by ABORT_TIME. An
; ASCII text file may be defined for this parameter.
ABORT_PROMPT Timed out waiting for slow drive...transfer aborted
;
; ╔══════════════════════════╗
; ║ Archiver Definitions ║
; ╚══════════════════════════╝
;
; Each archiver, is denoted by ARCHIVER x, where x is a sequential number. Up
; to 10 archivers can be executed by ROMproc. ROMProc is capable of
; automatically detecting ARC, ARJ, HYP, LZH, PAK, SQZ, ZIP and ZOO archives.
; The next 4 keywords are required after the ARCHIVER statement; do not
; comment any of them out or insert other parameters or comments between them.
; I would also advise against changing the command options I have set, unless
; you have need to do so.
; ARCHIVER = denotes a new archiver definition.
; ARC_EXT = the extension for this particular archiving format.
; ARC_ADD = the command line to add files to an archive, including all
; command-line switches desired. Place the variable @ARCHIVE@
; where the filename is to be inserted in the command line and
; @FILE@ where the filespec is to be inserted.
; ARC_COMMENT = the command line to comment archives, including all command-
; line switches desired. Place the variable @ARCHIVE@ where the
; filename is to be inserted in the command line. Leave this line
; blank if the archiver does not support commenting.
; ARC_ERR = the errorlevel that the archiver returns upon success. This
; information should be available in the program's documentation.
ARCHIVER 1
ARC_EXT arj
ARC_ADD arj a -e -m0 -s1 @ARCHIVE@ @FILE@
ARC_COMMENT arj c -s1 -y -zc:\romproc\comment.txt @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 2
ARC_EXT lzh
ARC_ADD lha a /m1 @ARCHIVE@ @FILE@
ARC_COMMENT
ARC_ERR 0
;
ARCHIVER 3
ARC_EXT sqz
ARC_ADD sqz a @ARCHIVE@ @FILE@
ARC_COMMENT sqz c @ARCHIVE@ c:\romproc\comment.txt
ARC_ERR 0
;
ARCHIVER 4
ARC_EXT zip
ARC_ADD pkzip -a -k @ARCHIVE@ @FILE@
ARC_COMMENT pkzip -k -z < c:\romproc\comment.txt @ARCHIVE@
ARC_ERR 0
;
; ╔══════════════════════════╗
; ║ Protocol Definitions ║
; ╚══════════════════════════╝
;
; Each protocol, is denoted by PROTOCOL x, where x is the letter designating
; the protocol. Up to 15 protocols can be executed by ROMproc. The next
; keyword is required after the PROTOCOL statement; do not comment it out or
; insert other parameters or comments between them. I have configured most of
; the popular protocols, using the PCBoard default lettering scheme.
; PROTOCOL = denotes a new protocol definition
; PROT_SEND = the command line to transmit the file(s) to remote, including
; all command-line switches desired. Place the following
; variables as needed for ROMProc to properly invoke the
; protocol.
; @PORT@ COM port to be used by the protocol
; @SPEED@ COM port computer-to-modem speed (DTE)
; @CARRIER@ modem-to-modem carrier speed (DCE)
; @FILE@ File (or batch list file) to be downloaded
; @UPLOAD@ path to upload directory for bi-directional
; protocols.
;
; Xmodem-CRC
PROTOCOL C
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both pB4096 sc @FILE@
;
; 1K-Xmodem/G
PROTOCOL F
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both pB4096 sx -k -g @FILE@
;
; Ymodem/G
PROTOCOL G
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both est 0 @CARRIER@ pB4096 sb -k -g @FILE@
;
; HS/Link
PROTOCOL H
PROT_SEND hslink -p@PORT@ -b@SPEED@ -e@CARRIER@ -u@ULDIR@ -a @FILE@
;
; Zmodem MobyTurbo
PROTOCOL M
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both est 0 @CARRIER@ pB4096 sz -m @FILE@
;
; 1K-Xmodem
PROTOCOL O
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both pB4096 sx -k @FILE@
;
; Xmodem
PROTOCOL X
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both pB4096 sx @FILE@
;
; Ymodem
PROTOCOL Y
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both est 0 @CARRIER@ pB4096 sb -k @FILE@
;
; Zmodem CRC-32
PROTOCOL Z
PROT_SEND dsz port @PORT@ speed @SPEED@ ha both est 0 @CARRIER@ pB4096 sz @FILE@
;
; *** End of ROMProc configuration file ***
;