Category : BBS Programs+Doors
Archive   : PLST_130.ZIP
Filename : PARSELST.CFG

; Sample ParseLst control file
;
; You should edit this as needed for your own circumstances
;

; Stuff everyone should have

Node 1:132/99 ; My network address
Country 1 ; My country code
MaxBaud 9600 ; My highest baud rate

; Some optional additions

MyList MyNodes.Lst ; A private node list (for points)
Password 1:132/100 hispw ; Set up a password for 132/100
Phone 1:132/100 1-234-567-8901 ; Substitute a phone number
Baud 1:132/100 1200 ; Substitute a baud rate
CM 1:132/100 ; He can handle crash mail

; Nodelist format statements (find your system(s))
; More than one type can be generated from one run of ParseLst. It is
; necessary to decide if "Gated" or "Complete" should be used (Complete
; is generally safe, even on SEAdog or TBBS systems), and whether or not
; "UseZone" should be used (again, it is generally safe). Finally, the
; different nodelist format lines should be uncommented. It is possible
; to generate all of them during one run by uncommenting the proper lines.

; For BinkleyTerm, Opus, or QuickBBS systems, use the following:
Complete ; Give entire nodelist
UseZone ; Don't change Zone to Region

; For SEAdog or TBBS systems, you need the following:
;Gated ; Use zonegates only
;TBBSList ; Generate TBBS/SEAdog nodelists

; For Fido 11 systems, use the following:
;Complete ; Give entire nodelist

; Any/all of the following nodelist types can be created during one run
; of ParseLst. Uncomment all that apply for your situation.

; For BinkleyTerm or Opus 1.10 systems use:
Version6 ; Generate Version 6 format files

; For TBBS Systems using BinkleyTerm 1.50 or higher as a front end use:
;BinkList ; Generate extra BinkleyTerm files

; For Opus 1.03 or Fido 11 systems use:
;Version5 ; Generate Version 6 format files

; For QuickBBS 2.01 systems use
;QuickBBSList ; Generate QuickBBS v2.01 files


; Optional output control
; Determine which options you wish to support. For BinkleyTerm, SEAdog,
; and Opus 1.10 systems, it is generally wise to generate an "InterList",
; rather than "NoFidoList". This will allow you to use sysop names rather
; than net/node numbers for most operations. Routing information via
; "Route" instead of "NoRoute" is necessary for any system that uses
; RouteGen from SEA to do mail routing. Generating the Nodelist.Bbs file
; is not generally needed since ParseLst goes directly from the FSC002
; formatted nodelist to the various machine readable forms without the
; intermediate Nodelist.Bbs file.

NoComments ; Don't output comment lines
NoRoute ; Don't generate Nodelist.Fon file
NoNodeList ; Don't generate Nodelist.Bbs file
NoFidoList ; Don't generate human readable files
NoUserList ; Don't generate FidoUser.Lst file

; Now the dialing translations

; SEAdog and BinkleyTerm users should delete this and use the DIAL statement
; in their respective configuration files instead (that can be changed
; easily with just an editor, rather than recompiling the nodelist)

; The dialing table is scanned in order, and the first matching
; entry is the one that is used. The defaults are applied ONLY if
; no table entries apply.

Dial / 011- ; Add 011- to international calls

; The following set up local calls from Nashua, NH

1-603-432- 432-/
1-603-434- 434-/
1-603-465- 465-/
1-603-424- 424-/
1-603-429- 429-/
1-603-672- 672-/
1-603-673- 673-/
1-603-594- 594-/
1-603-880- 880-/
1-603-881- 881-/
1-603-882- 882-/
1-603-883- 883-/
1-603-884- 884-/
1-603-885- 885-/
1-603-886- 886-/
1-603-888- 888-/
1-603-889- 889-/
1-603-635- 635-/
1-603-891- 891-/
1-603-893- 893-/
1-603-898- 898-/
1-603-649- 649-/
1-603- 1-/

End

; Now the cost table

;
; Cost table:
;
; The COST statement at the head of the table can take two
; arguments, which are the default costs in pennies to apply to
; domestic and international calls, respectively.
;
; Each entry in the cost table consists of a partial phone number
; followed by a cost in pennies for sending a message to any node
; whose phone number begins with that string. As with the dialing
; table, the first matching entry is the one that is used.
;
; Cost table entries can take an optional third item, which is a
; maximum baud rate to use when calling into that area. This can be
; used to allow for "trouble spots". You cannot specify a baud rate
; without also specifying a cost.
;
;
; An example follows:
;

Cost 1 250 ; Give a cost of 1 cent to long
; distance nodes, and $2.50 international

; The following numbers are free from Nashua, NH

1-603-432- 0
1-603-434- 0
1-603-465- 0
1-603-424- 0
1-603-429- 0
1-603-672- 0
1-603-673- 0
1-603-594- 0
1-603-880- 0
1-603-881- 0
1-603-882- 0
1-603-883- 0
1-603-884- 0
1-603-885- 0
1-603-886- 0
1-603-888- 0
1-603-889- 0
1-603-635- 0
1-603-891- 0
1-603-893- 0
1-603-898- 0
1-603-649- 0
1-800 0

End