home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Rat's Nest 1
/
ratsnest1.iso
/
bbs
/
utils
/
flstd111.arj
/
FASTLST.CFG
next >
Wrap
Text File
|
1993-06-13
|
13KB
|
264 lines
;*****************************************************************************
;* *
;* (C) Copyright 1992-1993 by Alberto Pasquale *
;* *
;* A L L R I G H T S R E S E R V E D *
;* *
;*****************************************************************************
;* *
;* FastLst required many hours of work: if you like it and would like to *
;* support me in developing this and other similar products, please *
;* register. See REGISTER.FRM for more details. *
;* *
;*****************************************************************************
;* *
;* How to contact the author: Alberto Pasquale of 2:332/504.1@fidonet.org *
;* Viale Verdi 106 *
;* 41100 Modena *
;* Italy *
;* *
;*****************************************************************************
;
;
; Sample FastLst 1.11 config file
;
;
;
;RegKey RegistrationKey ; If you are a registered user, put your
; ; registration key here (not case sensitive)
;
;
Address 2:332/504.0 ; Your network address (4D)
Country 39- ; Your country code (Intl phone code: 1- for the USA)
MaxBaud 9600 ; Your highest baud rate (as in your nodelist entry)
;
;StatusLog c:\opus\bt.log ; Binkley style log file
;
TmpPath d:\tmp ; DOS only, not used in OS/2 version.
; Path for temporary files: please be sure there is
; enough space for the nodelist size you usually compile
; You can use a Ram Disk to speed-up the
; Merge-Sort process, provided you have an
; adequately sized one.
;
AutoErase ; Delete old nodelist and nodediff after applying nodediff
;
;KillOld ; Kill old nodelist files.
; ; When a nodelist file is processed, existing old versions
; ; are erased.
;
;Kill999 ; Delete the final .999 when Merging (MergeList).
;
KillAfter ; Old NODEX.* files are killed after the new ones have been
; ; successfully written.
; ; Thus you will always have a valid nodelist, even in the case
; ; of a compilation error. On the other hand you need some more
; ; spare disk space to hold the old and new files during
; ; compilation.
;
;Dash2Comma ; Change dashes to commas in the phone number
;NoDash ; Remove dashes from the phone number
; Nodelist format
;Gated ; If you want to keep the output files small,
; ; you can use this option: only zones/regions/nodes
; ; that are listed in GateAddr will be present in
; ; the output files. Anyway the coordinators at
; ; GateCoord level or above will always be in the
; ; output files.
;
;GateAddr 1 2:33 3:632 4:801/17
; ; Defaults to your zone.
; ; You can specify zone, region/net and node numbers.
; ; The example compiles: zone 1, region 33 of zone 2,
; ; net 632 of zone 3, node 4:801/17
;
;GateCoord NC ; Defaults to NC, can be ZC, RC, NC, HC.
; ; The coordinators of the specified and upper levels
; ; are always present in the output files.
; ; If you use V6, you _must_ include coordinators of
; ; all levels above any of the segments selected
; ; via the GateAddr statement: if you are unsure,
; ; leave it commented out.
;
;Version6 ; Generate Version 6 format files
Version7 ; Generate Version 7 format files
;Comments ; Output comment lines to video
;NoReport ; Do not output nodelist statistics
;FidoTxt ; Output 80 Column Text List of nodes
;FidoPrn ; Output 132 Column Text List of nodes
;FidoUserLst ; Generate fidouser.lst text list of sysop names
SysopNdx ; Generate SYSOP.NDX (version 7 sysop name list)
Interlist ; Put all zones in above sysop lists,
; instead of your zone only.
;SysDup 2:332/504 2:332/505 2:332/104
; ;
; ; When a SysOp name is present in various nodes
; ; only a single name/address couple remains in the
; ; SysOp lists (fidouser.lst/sysop.ndx).
; ; By default FastLst chooses the address following
; ; the criteria explained in .DOC.
; ; If you want to override FastLst's choice you can
; ; use one or more SysDup lines, specifying all the
; ; addresses you want to be present in the sysop lists
; ; after Dupe killing.
; MergeList allows to Merge the main nodelist with
; a segment of it. I used to merge the complete
; fidonet nodelist with my region's segment, in order
; to have it always up to date.
; If you use V7 you should generally prefer Mylist.
;MergeList region33 ; The latest region.nnn is merged with the latest nodelist
;MergeList c:\opus\hub.500 ; My Hub segment is merged with the latest region33.nnn
; before it is merged with the main nodelist.
;MyList region33 ; The latest region33.nnn is added to the compilation.
;MyList c:\opus\hub.500 ; If you use Version7, in the case of duplicate nodes,
; the last compiled ones are put in the indexes.
; With Version7 you can save time by using "MyList"
; instead of "MergeList" for local nodelist segments:
; all the new and changed nodelist entries will be
; active, but the deleted ones will still be present.
;MyList region88 39 ; The latest region88.nnn is added to the compilation.
; ; It is considered in Zone 39 (using Version7).
; ; If you use Version6 you need a "ZONE,39,..." line
; ; at the start of region88.nnn.
;
;MyList Hub400.lst 1:120 ; Hub400.lst is added to the compilation.
; ; It is considered in Zone 1, Net 120 (Version7).
; ; With Version6 you need Zone and Host lines.
;
;PvtList Points.Lst ; A private node list (not in the Text outputs).
;Password 2:332/501.0 pass501 ; Set a session password with 2:332/501.0
;include c:\opus\fastlst.pwd ; You can put here all your "password" lines
; Definitions for modem_type flags:
; TypeDef <flag> <value>
; If <flag> is found in the flag portion of the nodelist entry, the
; corresponding modem_type byte is OR-ed with <value>.
; e.g.: a V32B entry will get both the V32 and V32B bits
;
;TypeExact ; Use this option with Binkley 2.55 and newer.
; ; The modem type will be determined by the first match
; ; only: If you define HST before V32 a node with
; ; both V32 and HST will have a plain HST modem type.
; ; Thus you can use 255 different modem types (1 -> 255)
; ; since this field is not bit oriented anymore.
;
TypeDef HST 1 ; Set bit 0 of modem_type byte when HST flag is present
TypeDef H14 1 ; Set bit 0 of modem_type byte when H14 flag is present
TypeDef H16 1 ; Set bit 0 of modem_type byte when H16 flag is present
TypeDef PEP 2 ; Set bit 1 of modem_type byte when PEP flag is present
TypeDef V32 4 ; Set bit 2 of modem_type byte when V32/V32B flag is present
TypeDef V32B 8 ; Set bit 3 of modem_type byte when V32B flag is present
;TypeDef MNP 16 ; Set bit 4 of modem_type byte when MNP flag is present
;TypeDef V42 16 ; Set bit 4 of modem_type byte when V42/V42B flag is present
;
; ; A V32bis+HST modem will get:
; ; TypeExact commented out -> 1|4|8 = 13
; ; TypeExact uncommented -> 1
;
;Name 2:332/504.0 800_support ; Substitute a Board Name
;Phone 2:332/501.0 39-59-399999 ; Substitute a phone number
;Baud 2:332/501.0 9600 ; Substitute a baud rate
;CM 2:332/501.0 ; It can handle crash mail
; Cost table:
;
; The COST statement at the head of the table takes two
; arguments, which are the default costs to apply to
; domestic and international calls.
;
; Each entry in the cost table consists of a partial phone number
; followed by a cost for any node whose phone number begins with that
; string. The first matching entry is the one that is used.
;
; Cost table entries can take an optional third item, which is a
; mask for modem type to use when calling into that area.
; The bits not contained in the mask are removed from modem type.
;
;
; An example follows:
;
cost 60 300 ; 60 for domestic (Country prefix) calls
39-586-5555 10 12 ; Allows only V32/V32b bits (4+8) (no HST/PEP)
39-574-444 10 1 ; Allows only HST bit in modem type
39-59 0
end
; UCost table:
; Same as Cost table, but for User_Cost (Fee for a netmail message on BBS)
; There is not the third optional argument.
; If UCost is commented out, the User_Cost is taken equal to Call_Cost.
;
ucost 60 300 ; 60 for domestic (Country prefix) calls
39-586-5555 10
39-574-444 10
39-59 0
end
;Type 2:332/501.0 4 ; Substitute a modem type as defined
; via TypeDef.
; The Flags statement allows to set the "user
; defined" bits in the Flags word of the compiled
; nodelist entry.
; These bits are named 5,6,7,8,9,A,B,D,E,F;
; where bit 5 is the 6th bit and F is the 16th
; bit of the word.
;Flags 2:332/501.0 AB5 ; Set bits 5,A & B.
;Flags 2:332/503.0 A ; Set bit A only.
; Cost Override (<type> as defined via TypeDef/TypeExact)
; TypeCost <type> <cost>
;
;TypeCost 1 100 ; Cost override for HST nodes
;TypeCost 2 50 ; Cost override for PEP nodes
;TypeCost 4 100 ; Cost override for V32 nodes
;Cost 2:332/501.0 150 ; Call_Cost override.
; If the UCOST table is not defined, then
; the User_Cost is overriden too.
;UCost 2:332/501.0 10 ; User_Cost override.
; Dialing Translations
;
; The Dial statement at the head of the table takes two arguments for
; domestic and international prefix/suffix default specifications.
; The subsequent lines contain a partial phone number and a single
; argument for the prefix/suffix to be used for nodes whose phone number
; begins with that string.
;
; The first matching entry is the one that is used.
; If no entry apply, the defaults are used.
;
Dial 0 00 ; Prefix 0 to domestic and 00 to international calls
39-59- ; Remove the country and area codes for local calls
End ; If you want to specify a suffix, then you must precede
; it with a slash ("/<suffix>"). If both a prefix and a
; suffix are specified, they must be separated by a slash
; ("<prefix>/<suffix>"). No spaces are allowed
; between prefix, suffix and the separating slash.