home *** CD-ROM | disk | FTP | other *** search
- ; * Sample.cfg updated 8-30-92 for UltraBBS CNet v1.20
-
- ; * Some general assumptions are made:
-
- ; * 1. You have a basic understanding how the QWK networks operate.
- ; * 2. You have already made arrangements with your HOST system to
- ; * have net status activated.
- ; * 3. You have a basic understanding how UltraBBS operate.
-
- ; * Please note: any comments followed by the ; are comment fields. In order
- ; * to activate an option or disable an option simply remove or add the ;
-
- ; * Any comment lines containing the ; * are not options but comment fields
- ; * only.
-
- ; * Be sure to rename SAMPLE.CFG to reflect the name of the system you will
- ; * be calling. (i.e. LSO.QWK = LSO.CFG) You can have as many config files as
- ; * you wish. CNet is designed to network with many systems at a given time.
-
- ; * You will need to use a term program with a script file or Robocomm to
- ; * send/receive QWK and REP files. CNet simply imports/exports messages
- ; * into your HS message base. Actually downloading/uploading your QWK/REP
- ; * files is not in the scope of this manual and will not be covered in
- ; * the following examples.
-
- ; * Now onto configuring CNet
-
- ; * What system are you running. The following field should always be RA or
- ; * SUPERBBS
-
- SYSTEM=ULTRABBS
-
- ; * This is your name. It is substituted into messages that are from/to
- ; * "SYSOP" upon export.
-
- SYSOPNAME=BILL CASTLE
-
- ; * This is the location of UBBS.DAT.
-
- UBBSDAT=C:\Ubbs
-
- ; * This is the directory that contains your QWK message packet you
- ; * receive from your host. Please remember you must have net status
- ; * enabled on your host system otherwise CNet will not import your
- ; * messages!
-
- QWKDIR=C:\ROBOCOMM\QWK\
-
- ; * This directory is where your .REP reply packet will be created.
-
- REPDIR=C:\ROBOCOMM\REP\
-
- ; * This is the name and location of your log file. You may have one
- ; * log file for all of your configuration files or you may have one
- ; * for each.
-
- LOGDIR=C:\CNET\CNET.LOG
-
- ; * This is the location of your pointer file. The pointer file is an
- ; * 800 byte file that tracks the last messages imported for each conference.
- ; * This should NOT be a ramdrive! CNet will maintain 9 generations of pointer
- ; * files named SAMPLE.PN?, where ? is a number 1 through 9.
-
- ; * Never delete the *.pnt file since it contains the pointers for the last
- ; * import/export. If for some reason you loose your pointer file simply run
- ; * CNET S SAMPLE A 0 to reset your pointers to the last message in
- ; * the message base. Please refer to the CNET.DOC for more details.
-
- ; * When using the external pointer option it is also important to reset the
- ; * pointers to 0 after a message base renumber or purge.
-
- POINTERDIR=C:\CNET\POINTERS
-
- ; * This is the directory for your CRC files. If it is blank, they
- ; * will be stored in the same directory as your message files. It is not
- ; * recommended to delete the CRC files since the CRC files contain the
- ; * duplicate message information and are compared during imports. Deleting
- ; * these files could result in MASS dupes and many un-happy users.
-
- CRCDIR=C:\CNET\CRC
-
- ; * This field is used to tell CNet how to rebuild your CRC files.
- ; * A value of 0 will tell CNet to rebuild your CRC files anytime it finds
- ; * them out of date. Any other value will tell CNet not to rebuild your
- ; * CRC files. Instead, it will maintain at the most X number of records
- ; * regardless of the state of the message base, where X is the number you
- ; * specify.
-
- ; * Note: This number is by conference, not for the whole message base.
- ; * Also, there is a limit of 3000 CRC records for each conference.
-
- CRCREBUILD=0
-
-
- ; * This next field is the name of your Host SysOp which will be used if a
- ; * message with the name of "SYSOP" is found in the from/to field on import.
-
- HOSTSYSOP=Klaus Lamort
-
- ; * This field is the drive and directory where you would like all temporary
- ; * files to be created. Most commonly a ramdisk. Please be sure you have
- ; * enough space on this drive. Rule of thumb, largest sized QWK/REP packet
- ; * times 3. If left blank $temp$ will be used on the current drive.
-
- TEMPDIR=M:\RAMDISK
-
- ; * (Registered) You may define up to 20 different aliases.
-
- ; * Would translate all messages containing "El Guapo" to Rollin White
- ; * upon exporting and all messages containing Rollin White to El Guapo
- ; * upon importing.
-
- ALIAS=El Guapo,ROLLIN WHITE
-
- ; * (Registered) If not used correctly the append command can cause duplicate
- ; * messages when uploading to your host. This is used for systems that scan
- ; * outgoing messages several times a day but only call thier host once a day
- ; * or every other day for example. This function allows you to append messages
- ; * into an existing REP file otherwise the REP file is deleted and a new
- ; * file is created for the newly exported messages.
-
- ; * IT IS EXTREMLY IMPORTANT TO MAKE SURE THE *REP* FILE IS DELETED AFTER
- ; * UPLOADING TO YOUR HOST WHEN USING THIS OPTION!
-
- APPEND=N
-
- ; * (Registered) Ah a Sysops nightmare. Twits, modem scum, Telco-lice etc.
- ; * Use this option to delete any messages imported with the name listed
- ; * in the TCAN field. The example below will tell CNet not to import
- ; * any messages from Joe Shmuck
-
- TCAN=JOE SHMUCK
-
- ; * This keyword is used to indicate conferences that are to be read only.
- ; * Often major networks will have news conferences available for the
- ; * administration to post informational news items. Usually users are
- ; * not permitted to post messages in this type of conference. Making a
- ; * conference read only will prevent any messages from being exported.
- ; * (Registered)
-
- READONLY=100,101
-
- ; * The next statement controls what CRC method is used for each conference.
- ; * The CRC files are compared on import to check for duplicate messages. If
- ; * a duplicate message is encountered it is deleted and not imported into the
- ; * message base. You can have multiple CRCMETHOD statements, even for the same
- ; * CRCMETHOD
-
- ; * 16 bit CRCs = good
- ; * 32 bit CRCs = excellent
- ; * 0 bit CRCs = nutz
-
- ; * You may have as many of these statements as you like. The format is
- ; * CRCMETHOD=X:CONF1,CONF2,CONF3, etc. where:
-
- ; * X = 1 for 16 bit CRCs
- ; * X = 2 for 32 bit CRCs
- ; * X = 0 for none
-
- ; * NOTE: 0 is the default.
-
- CRCMETHOD=2:2,9,12,13,14,15,16,17,18,19,23,25
- CRCMETHOD=2:26,27,39,43,44,46,47,48,49,50,51
- CRCMETHOD=2:52,53,54,55,56,57,58,60,61,62,63
- CRCMETHOD=2:64,65,76,77,78,79,80,81,82,83,84
- CRCMETHOD=2:85,86,87,88,89,90,91,92,93,94
-
- CRCMETHOD=1:
-
- ; * The following is a list of conferences that allow private messages.
- ; * Note: If a private message is found in a conference not listed on the
- ; * PRIVATE option line, it will not be exported.
-
- PRIVATE=50,51
-
- ; * The next statement defines your tagline and your host's tagline. You can
- ; * have up to nine statements
-
- YOURORGIN1=Intelec - LSO Systems
- HOSTORGIN1=Intelec - The French Connection
-
- ; * CNet now supports multiple archiving formats. Please be carefull if you
- ; * decide to change from one format to another, delete the QWK or REP files
- ; * before running CNet.
-
- ; * ZIP
-
- EXTRACT=PKUNZIP -o
- COMPRESS=PKZIP -m
-
- ; * ARJ
-
- ; EXTRACT=ARJ e -y
- ; COMPRESS=ARJ a
-
-
- ; * The rest of this file describes the conferences. A CONFERENCE Statement is
- ; * required for each conference. Each conference statement has three parts
- ; * The format is: CONFERENCE=HOST_CONF_NUM,YOUR_CONF_NUM,TAGLINE NUMBER
- ; * Note: if tagline number 0 is used, no tagline will be appended. This is
- ; * used primarily when gating conferences from one network to another.
-
- ; * Using tagline 0 is only available in the registered version.
-
- ; * HOST_CONF_NUM YOUR_CONF_NUM TAGLINE_NUMBER
- ; * |_____ ____| |
- ; * | | |
- ; * CONFERENCE=147,98,1------------------
-
- CONFERENCE=25,50,1
- CONFERENCE=174,51,1
- CONFERENCE=20,52,1
- CONFERENCE=1,53,1
- CONFERENCE=2,54,1
- CONFERENCE=6,55,1
- CONFERENCE=13,56,1
- CONFERENCE=24,57,1
- CONFERENCE=40,58,1
- CONFERENCE=64,60,1
- CONFERENCE=3,61,1
- CONFERENCE=4,62,1
- CONFERENCE=19,63,1
- CONFERENCE=65,64,1
- CONFERENCE=98,65,1
- CONFERENCE=804,76,0
- CONFERENCE=805,77,0
- CONFERENCE=809,78,0
- CONFERENCE=810,79,0
- CONFERENCE=819,80,0
- CONFERENCE=820,81,0
- CONFERENCE=822,82,0
- CONFERENCE=823,83,0
- CONFERENCE=824,84,0
- CONFERENCE=827,85,0
- CONFERENCE=843,86,0
- CONFERENCE=844,87,0
- CONFERENCE=858,88,0
- CONFERENCE=873,89,0
- CONFERENCE=892,90,0
- CONFERENCE=898,91,0
- CONFERENCE=911,92,0
- CONFERENCE=931,93,0
- CONFERENCE=965,94,0
-