home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
DOOR
/
CDMX2204.ZIP
/
CDMX2DOR.CFG
< prev
next >
Wrap
Text File
|
1994-03-19
|
8KB
|
168 lines
; CDMX2DOR
; NEXT GENERATION CDROM DOOR .CFG FILE
;
; Instructions: Do NOT remove the semi-colons from comment lines.
; Change lines that start WITHOUT semi-colons as necessary as
; indicated to meet your system's needs.
;
;-------- GENERAL NEXT GENERATION DOOR INFO ---------
;
; 1)The next line contains the DRIVE letter with a colon where you have
; placed the Next Generation CDRom Door...
C:
;
; 2)This next line contains the full path name to the subdirectory where
; you have placed the Next Generation CDRom Door. Note there is no
; backslash at the end of the line. Note you MUST have a subdirectory
; here and not just a drive main directory, i.e., C:\ or B:\ or whatever
; will not work. You must have a subdirectory.
C:\cdbob
;
; 3)This next line contains the default DRIVE letter with a colon of your
; CDRom drive. NOTE that this is just a default. If you have CD's on
; other drives, you will configure these in the CDSONLIN.LST (see docs).
E:
;
; 4)This next line is where you specify the DRIVE letter with a colon of
; your temporary scratch subdirectory. You will specify the path to it
; in the next line, but I also need the drive letter and a colon.
C:
;
; 5)This next line contains the full path name to your a scratch subdirectory
; that can be used for file extractions, copying, sending, and other
; functions. Note that this subdirectory is volatile and any file in it
; is subject to deletion without notice, so keep this in mind. Note there
; is no backslash at the end of the line. NOTE: The door will take this
; information and look for the "test" sub (as in c:\max\temp\TEST) and
; expect to find a "TEST" sub for each node you have, e.g., 0TEST, 1TEST,
; 2TEST, 3TEST, etc., one sub per each node. For example, eventhough I
; have c:\max\temp\test shown below, here, if I have a caller calling on
; node 3, then the door is going to look for c:\max\temp\3TEST to use as
; his temporary subdirectory. Be sure to have as many of these subs as
; you have nodes with the first character in the sub name being the node
; number... but ONLY put the general label here, e.g., TEST, instead of
; 2TEST or 3TEST, or whatever.
C:\max\temp\test
;
; 6)This next line contains the filename of your BBS's comment file that
; will be attached to outgoing CDRom files when users download. Be sure
; that this comment file is in your scratch subdirectory which you
; specified immediately above.
NCB.ADV
;
; 7)The next line contains a base Kbyte amount that is used by CDMX2DOR to
; determine maximum KBytes a user may download from your CDRom(s) or other
; drives in a single day. The maximum bytes amount varies by a user's
; security level and is determined by the formula:
;
; Maximus KBytes per day = base Kbyte * int(user securitylvl/7)
;
; With a base Kbyte of 500, a security level of 30 would get 2000k, a
; security level of 20 gets 1000k, 80 gets 5500 kbytes, and so on.
500
;
;
;
;-------- MAXIMUS BBS INTEGRATION INFO ---------
;
; 8)The next line is for Maximus BBS sysops using the Next Generation CDRom
; door. If you are using Maximus BBS software for your BBS then the next
; line should be 'yes.' If you are using some other kind of BBS software
; than Maximus BBS software, then the next line should be 'no.'
Yes
;
; 9)If you are a Maximus BBS sysop then the next line should be the DRIVE
; letter with a colon of the drive where your Maximus BBS software is
; located. If you are not using Maximus BBS software, then the next line
; can be left unchanged, do not remove the line -- just leave it as is.
C:
;
; 10)If you are a Maximus BBS sysop then the next line declares the full
; pathname to your Maximus BBS's lastuser.bbs file. Do not have a
; trailing backslash at the end. If you are not using Maximus BBS
; software, then the next line should be left unchanged.
C:\max
;
; 11)If you are a Maximus BBS sysop then the next line declares the filename
; of the lastuser.bbs appropriate for your node. If you are using a
; single node, then 'lastuser.bbs' is correct. If you are multinoded, then
; this filename may change, e.g., to 'lastus01.dat' or something else.
lastuser.bbs
;
;
;
;-------- DOOR SECURITY/KEYS/REGISTRATION INFO ---------
;
; 12)The next line is the name of your registration key file. Once you
; have registered this file will either be sent to you by electronic mail
; or be made available to you for download on New Century BBS. All
; 'unregistered' messages and delays will be removed thereby speeding up
; use of the door. If you have not registered then leave this line alone.
;
cdmx2dor.key
;
;--------------------------------------------------------
;
; 13)The next line is a security check. You need not change this line.
New Century BBS
;
;
; The next 3 data lines are file names that cdmx2dor needs to have in
; order to report to you what has been happening. You may have these
; three filenames each be different or, if you wish, you may have them
; all named by the same name. These files will always be written in
; CDMX2DOR's home directory.
;
; 14)The next line is the name of your NGDL.LOG file. In this file will be
; information concerning who downloaded what file when and with what
; outcome. This file will have this general output structure:
;
; Darroll Coulston 17:53:12 09-04-1993 D:\GAMEAP\_1PTOMB.ZIP Z OK
; Lloyd Welch 15:01:01 09-05-1993 D:\035A\AQUARIUM.GIF Z OK
;
; Name Time Date File Modem Result
;
; This log will be written in your CDMX2DOR's home subdirectory.
;
ngdl.log
;
; 15)This next line is the name of the file that keeps a record of bad
; sends, i.e., files that were aborted and/or somehow failed in being
; sent to a user. Be on the lookout for a single user repeatedly having
; bad sends as it may be indication of a user employing leech modem
; techniques. Data in here will be of this format:
;
; Dino Vozikis 17:34:20 09-06-1993 D:\014A\PCB1.ZIP Z BAD
;
; This log will be written in your CDMX2DOR's home subdirectory.
;
badsend.lst
;
; 16)The next line is the filename of CDMX2DOR's error log. Data in here
; is a record of something "fatal" happening to CDMX2DOR while it is
; in operation. For example, an "error write-protect error" means that
; a file CDMX2DOR was expecting to find was not found. Data in here is
; of this format:
;
; Error write-protect error violation in device: on 09-06-1993::01:13:14
;
; This error log will be written in your CDMX2DOR's home subdirectory.
;
cdmx2dor.err
;
;---- PIONEER CAROUSEL CD READER MULTINODE LOCK information ------------
;(17)This next line regards whether you have a Pioneer carousel CD reader.
; The filename you specify in the next line will be written while the
; current user is reading using the carousel to read CD information and
; will lock others off a read until the present read is finished. This
; only need be instituted if you are multinode with a carousel. If
; you are not a carousel user then you may leave this line as "NONE."
; If you are a carousel user but are not multinode, then you may leave
; this line as "NONE." Only in the case of multinode AND carousel do
; you need to enter a "lock" filename here. Please refer to the docs
; if you are in this situation. IF you have a carousel AND are
; multinode, then you might consider using "c:\intercom\lock.fil" as
; your filename here (make sure you have a c:\intercom subdirectory).
NONE
; End of configuration file.