; BINKLEY.CFG => BinkleyTerm/ST Configuration File! ; ; by.... ; ; *** ** Erik Williams ; ** *** SunFox Productions, Ltd. ; *** ** University of Central Florida, Orlando ; ** *** REALITY.SYS corrupted! Restart universe (Y/N)? ; ; This BinkleyTerm/ST Configuration file is for BinkleyTerm/ST ; versions 3.00 and above and is representative of the appropriate ; configuration for a multizone network setup! Adding even more ; networks should be quite easy by following this basic format! If you ; are only running in one zone (say, AtariNet! plug! plug!), then all ; you have to do is delete the FIDO configuration statements. ; ; All you should have to do is edit the paths to reflect your system's ; setup. ; ; Feel free to distribute this file as you please...all I ask is that you ; keep the entire configuration archive together! Thanks! ; ; If you have any questions, try reading the docs first to see if it ; explains things better than I can. If you are still confused, then ; please feel free to contact me on the following networks: ; ; Erik Williams @ FIDO 1:363/169.0 {SunFox's Realm} ; Erik Williams @ AtariNet 51:1/11.0 {SunFox's Realm} ; SUNFOX @ GEnie ; ; You can FREQ the latest version of these configs from the above ; addresses (FIDO and AtariNet) 24 hours a day using the MAGIC name ; CONFIGS! ; ; ; READY?!? Let's CONFIG... ;) ; ; ; The Domain statements take care of associating the correct nodelist ; with the appropriate network. Put these in the order in which you ; plan on putting the address statements (this is important as the ; first statement will be considered your primary network, and the ; others as secondary!). ; ; Domain atrinet.ftn atarinet atarlist Domain fidonet.org fidonet nodelist ; ; ; The Address statements should be fairly obvious...these are for ; our node in the respective network. The parameter will always be ; a node number followed by the appropriate domain defined in the ; Domain statements above. ; ; Address 51:1/11.0@atrinet.ftn ; Address for AtariNet Zone 51 Address 1:363/169.0@fidonet.org ; Address for FIDONet Zone 1 ; ; ; The IOS keyword notifies BinkleyTerm that IOS is being used as the ; message tosser for this system (I highly recommend IOS...it is the ; best message tosser out there!). IOS supports full 4D addressing, ; so this keyword forces addressing to be 4D. ; ; IOS ; ; ; The following set of keywords is used to set up the terminal ; portion of BinkleyTerm/ST. The original comments from the CFG ; file I used to set up Bink with is reproduced below...additional ; comments are inserted as needed. ; ; ---------------------------------------------------------------------------- ; All configuration options are explained in detail in the Reference ; Guide section, "Configuration File." ; ---------------------------------------------------------------------------- ; ; Port The desired FOSSIL port to use, normally 1=COM1: and 2=COM2: ; Baud Maximum baud rate (300,1200,2400,4800,9600,19200,38400) ; Carrier Your carrier mask in hex (usually 80) ; Init Initialization string for your modem ; TermInit Initialization for terminal mode only operation ; Prefix Your modem's dial prefix (ATDT or ATDP) ; Suffix Your modem's dial suffix (if you need one, normally not) ; Busy What BinkleyTerm sends to the modem while doing other things ; Answer Use when modem isn't set to auto-answer, string to send to answer ; PreDial Modem string sent before dial string (Prefix) to override default ; PreInit Modem string sent before init string (Init) to override default ; ModemTrans Dynamic selection of modem prefix and suffix based on nodelist ; DTRHigh Leaves DTR (data terminal ready) line "high" on exit ; Protocol To use an Opus-CBCS style external protocol for Terminal Mode ; StatusLog Path/filename of the desired log file, if any ; Downloads Path to put downloaded files into ; CaptureFile Designates file to use with Alt-L session logging feature ; LogLevel Amount of logging desired, 1-5 (1=minimal, 5=maximal) ; Gong Gong on successful connection or file transfer in terminal mode ; Rev3 Forces BinkleyTerm to assume Revision 3 FOSSIL driver ; SlowModem Add 1/10th second delay between modem command characters ; LockBaud This statement is obsolete - lock your FOSSIL baud rate instead! ; AutoBaud Always dial at baud rate listed above instead of nodelist rate ; TaskView Tells BinkleyTerm to release time slice on TaskView systems ; TopView Tells BinkleyTerm to release time slice on TopView systems ; MultiLink Tells BinkleyTerm to release time slice on MultiLink systems ; Macro Sends string over the line in Terminal Mode (Alt-F1 thru Alt-F9) ; Include Designates name of file with additional configuration statements ; Application Ignored by BinkleyTerm, may be used by other applications ; AnswerBack Sends designated text in response to ENQ char in Terminal Mode ; PollTries Number of times BT will dial during a dial or poll ; SwapDir Enables shell swapping and designates dir to place swap file ; ; ---------------------------------------------------------------------------- ; Port 1 Baud 19200 Carrier 80 ; ; ; These five keywords control how your modem responds to the following ; situations...these are configured for my HST. Your mileage may vary. ; ; Init ATZ| TermInit ATM1| Prefix ATDT Busy ATM0H1| Answer ATA| ; ; ; Here are the logging keywords...LogLevel 5 has Bink log almost ; everything it does in the file pointed to by StatusLog. I haven't ; used CaptureFile yet, but that is supported in the dumb terminal mode. ; ; LogLevel 5 StatusLog d:\logs\binkley.log CaptureFile d:\logs\session.log ; ; ; Downloads delineates the directory that all incoming files will be ; placed by Bink/ST...this is a very critical keyword! Files that you ; request from other systems (FREQ) or files that are sent to you will ; be placed in this directory! ; ; Downloads d:\netfile\ ; ; ; These are miscellaneous keywords and MACROS...almost all installations ; will use these! ; ; Gong STLockBaud AutoBaud ; NOTE! In the next statement, Alt-F1 would send "Name" + carriage return Macro 1 Erik Williams| ; NOTE! In the next statement, Alt-F2 would send "Password" + carriage return Macro 2 foxy| AnswerBack Erik Williams| ; ; ; This is the number of times that your system will attempt to poll (or ; call) another (either by using an ALT-M or Bink/ST trying to send mail ; automatically). I use a big number as my hubs tend to be very busy! ; ; PollTries 400 ; ; ; The next set of options are what make your BBS unique in the world and ; are very important. Among other things, they will contain your system's ; name, the sysop name, keys for password protected sessions with other ; FIDO-style mailers, and so forth. A quick listing of these commands ; is given below...and additional comments will be near the commands ; themselves. ; ; System Name of your system (if mail interface, BBS name) ; Sysop Your name ; Address Your network address, including zone ; NoZones Causes zone support to be turned off, as in BT 1.50 and ealier ; PrivateNet Designates private network number, used mostly with point nets ; Boss Net/Node of your Boss (if NOT a point, then your node address) ; BossPhone Phone number for your Boss (override nodelist) ; BossPwd Password for use during Boss mail sessions (overrides nodelist) ; NetMail Location of your "Matrix" message area ; NetFile (Default) Location of your inbound files area ; KnownInbound (Known) Location of your inbound files area ; ProtInbound (Protected) Location of your inbound files area ; Hold Location of your outbound hold area ; Domain Define domain name, 8-char abbreviation, nodelist filename ; Nodelist Where your system stores its nodelist files ; NewNodelist Tells BinkleyTerm to expect "new format" Opus-style nodelist ; QuickNodelist Use QuickBBS 2.01 nodelist as compiled by ParseLst ; TBBSList Use TBBS nodelist as compiled by ParseLst ; Dial Dial translation entries (refer to docs for details) ; ScriptPath Designates directory to find outward dialing scripts ; Reader Command line to invoke reader/editor with Alt-E command ; Overwrite Allows overwriting of existing inbound files of the same name ; (ARCmail files excepted) ; Unattended Makes BinkleyTerm always start-up in unattended (mailer) mode ; NoFullScreen Forces BinkleyTerm to not use the fancy full screen mode ; BoxType Designates type of boxes to draw for windowed interface ; Colors For windowed interface, gives screen color attributes ; NOTE! The winner of our screen colors contest is Mark Kromm of 1:261/1034 ; NOTE! Mark gets a configuration verb named after him - and here it is! ; Mark_Kromm Makes colors 112, 9, 10, 11, 14 and 12 ; ScreenBlank If used, makes screen blank after 10 minutes of inactivity ; CursorCol Gives screen column number for cursor "resting place" ; CursorRow Gives screen row number for cursor "resting place" ; NoSlo Tells BinkleyTerm not to use SEAlink Overdrive ; SmallWindow Reduces "run ahead" during LoTek transfers (for hi-speed modems) ; Okfile (Default) List of files okay for file request (for Binkley) ; Avail (Default) List of files okay for file request (for humans) ; About (Default) Your system's advertisement ; MaxReq (Default) Maximum files to be sent during any one f'req session ; MaxBytes (Default) Maximum bytes to be sent in one session's freqs ; KnownReqList (Known) List of files okay for file request (for Binkley) ; KnownAvail (Known) List of files okay for file request (for humans) ; KnownAbout (Known) Your system's advertisement ; KnownReqLim (Known) Maximum files to be sent during any one f'req session ; KnownMaxBytes (Known) Maximum bytes to be sent in one session's freqs ; ProtReqList (Protected) List of files okay for file request (for Binkley) ; ProtAvail (Protected) List of files okay for file request (for humans) ; ProtAbout (Protected) Your system's advertisement ; ProtReqLim (Protected) Maximum files to be sent during any one f'req sess ; ProtMaxBytes (Protected) Maximum bytes to be sent in one session's freqs ; NoRequests Makes your system refuse any and all file requests ; ReqOnUs Whether to send inbound F Reqs when you initiate the call ; ReqTemplate (Default) Name of request response file template ; KnownReqTpl (Known) Name of request response file template ; ProtReqTpl (Protected) Name of request response file template ; NoPickup Tells BinkleyTerm to send mail during a session and not take any ; SameRing For modems that use RING reponse on inbound and outbound calls ; NoCollide Disables call collision detection for modems that hate it ; Shell DOS Shells...jumps to DOS, issues command (Alt-F1 thru Alt-F9) ; Timeout How long to wait for mail before assuming a human caller ; Banner Line displayed when someone calls ; BBSNote String to send to callers after they press Escape ; DoingMail String to send to callers during non-BBS events ; EnterBBS String to send to callers to prompt for input to access BBS ; ExtrnMail Designates errorlevel exit and string to match for external ; mailer or user-selected BBS functionality ; MailNote String to send when external mail handler is being loaded ; BBS Type of exit to the BBS to make when someone calls ; AfterMail Program or batch file invoked after receiving mail to process ; Cleanup Program or batch file invoked once before each scheduled event ; Packer Program or batch file invoked once just after 'Cleanup' is run ; NoWaZOO Forces BT to be an FSC-only mailer ; Janusbaud Baud rate at or below which all sessions could do Janus ; JanusOK Modem connect string for Janusbaud exception condition ; TaskNumber Arbitary task identifier for use in multitasking situations ; Flags Directory in which task identifier is created ; ; ---------------------------------------------------------------------------- ; ; ; System and Sysop are functionally identical to those little nametags ; you were given in Kindergarten. "Hello, my name is..." ;) ; ; System SunFox's Realm BBS Sysop Erik Williams ; ; ; The Boss keyword should have your primary node number if you are a node ; or the node number of the system that you exchange mail with if you are ; a point system. It is very important that you put your PRIMARY node ; number here (the node number referenced in the FIRST Address keyword up ; at the top of the file!) as this is the address that Bink/ST wants to ; see as your Boss (do this ONLY if you are a full-fledged node!). ; ; If you are running multizone, you only need to put in your primary ; node number...Bink/ST will pick up your alternate node numbers (provided ; you are listed in the nodelist!) as an equivalent Boss specification. ; ; If you are a point, then you will need to put the phone number of your ; Boss as well as your session password in the BossPhone and BossPwd ; keywords. ; ; Boss 51:1/11 ; ; BossPhone 679-6238 ; BossPwd Password ; ; ; The Keys are your passwords that you have set up with your hub. These ; are important as they provide a measure of security in preventing some ; hoser from fraudulently picking up YOUR mail! These keywords are easy ; to set up but you and your hub need to agree on the password BEFORE you ; add them to this configuration file or else Bink/ST will choke (mainly ; because the two mailers won't agree on the password and will terminate ; the connection). ; ; Key !xxxxx 51:1/0 Key !xxxxx 1:363/31 Key !xxxxx 1:363/112 ; ; ; These next path specifications are critical for your node to function ; correctly! Make sure you are CONSISTENT in every programme that you ; run for your node (it helps for all of them to be looking in the same ; places!)... ;) ; ; ; NetMail specifies the path that NetMail will be stored...NetMail is ; special as it is user->user private mail (as opposed to echomail which ; goes everywhere and then some!). The main use of the NetMail directive ; is to tell Bink/ST where the .HDR and .MSG files for your NetMail area ; are stored. ; ; NetMail d:\netmail\ ; ; ; This is the path that Bink/ST will put your normal mail packets. Your ; mail tosser should be looking at this folder so it can process your ; packet and toss your messages to the appropriate locations. NetFile ; is perhaps one of the most important keywords in this configuration as ; it determines where your received mail will be stored! ; ; NetFile d:\netfile\ ; ; ; This path should be the outbound area of your default DOMAIN (the first ; Domain listed in the Domain keywords above). For my setup, my primary ; network is AtariNet, so my Hold area will be d:\atarinet.033\. Make ; sure that you get the extension of that folder correct...it is the hex ; representation of the zone that that folder serves as an outbound ; folder (i.e. AtariNet is Zone 51, and 51 = 33 in hex (3*16 + 3*1)). ; ; Hold d:\atarinet.033\ ; ; ; The Nodelist directive is absolutely critical to the correct functioning ; of Bink/ST. The nodelist for a FIDO-style network contains all of the ; node numbers for member nodes, phone numbers for those nodes, and other ; important information for routing echomail/NetMail. You will probably ; want to put all of your nodelists in one path for ease of use. ; ; Nodelist d:\nodelist\ ; ; ; Miscellaneous setup options for the screen display... ; ; Unattended NiceOutbound BoxType 0 ; ; ; The next set of keywords will control how other nodes will be able to ; grab files from your node using the File Request (FREQ) system. The ; first set of FREQ keywords controls the files that *ANYONE* can FREQ ; from you, the second set controls the files that *SYSTEMS KNOWN TO YOU* ; can FREQ from your node, and the last set controls the files that ; requires a *PASSWORD PROTECTED* connection for FREQ to be allowed. ; ; All three sets are similar in composition in having an OKFILE, and ; AVAIL file, a file about your BBS, and finally some limits on the ; number and size of files that can be FREQ'd in a given session. ; ; The OKFILE is a list of files that are cleared for FREQ. ; ; The AVAIL file is the listing of files available for FREQ that will ; be sent if the other system FREQs the file "FILES". ; ; The ABOUT file is an advertisement or description of your BBS. ; ; See the Bink docs for more information on the FREQ system! :) ; ; ; These keywords control FREQ access for *ANYONE* with a FIDO mailer. ; ; Okfile c:\turbo\bink\okfile1.txt Avail c:\turbo\bink\sunfox.txt About c:\turbo\bink\aboutbbs.txt MaxReq 20 MaxBytes 900000 ; ; ; These keywords control FREQ access for any mailer known to your ; system! ; ; KnownReqList c:\turbo\bink\okfile1.txt KnownAvail c:\turbo\bink\sunfox.txt KnownAbout c:\turbo\bink\aboutbbs.txt KnownReqLim 20 KnownMaxBytes 900000 ; ; ; These keywords control FREQ access for any mailer that has a ; a password-protected session. ; ; ProtReqList c:\turbo\bink\okfile1.txt ProtAvail c:\turbo\bink\sunfox.txt ProtAbout c:\turbo\bink\aboutbbs.txt ProtReqLim 20 ProtMaxBytes 900000 ; ; ; Miscellaneous FREQ controlling keywords... ; ; ; NoRequests ; ReqOnUs ; ; ; These three files give the path to the template file that will give ; "on the fly" responses to failed FREQs for you automatically. I have ; found that the sample template file is good enough for me. ; ; ReqTemplate c:\turbo\bink\sample.tpl KnownReqTpl c:\turbo\bink\sample.tpl ProtReqTpl c:\turbo\bink\sample.tpl ; ; ; More miscellaneous options... ; ; ; NoPickup ; SameRing NoCollide Timeout 20 PollDelay 20 ;in tenths of a second ; ; ; These keywords control the messages that your system will give to ; callers for your BBS. There are provisions for messages telling ; users that you are processing mail (i.e. you are in a MAIL event in ; BINKLEY.EVT) or that you will let them log onto the board. ; ; Banner Welcome to SunFox's Realm BBS! BBSNote Thank you. Now loading BBS. One moment Please... DoingMail Sorry, we're not available right now. Processing mail only. EnterBBS Please press your Escape key to enter the BBS, or wait a few moments. ; ; ; If you are also a FNET node, these keywords will allow Bink/ST to shell ; out to the FMAILER automagically. ; ExtrnMail 170 u ExtrnMail 170 U ExtrnMail 170 / ExtrnMail 170 \ MailNote / ; ; ; These three keywords will control how Bink/ST shells out to other ; BBS programmes when a BBS caller is detected. Most systems will use ; BBS Batch (I know ///Turbo version 1.0 does, and so does FoReM!). ; ; ; BBS Exit ; BBS Spawn BBS Batch ; ; ; Here is a test of your mythological knowledge! Janus was the Roman ; god reputed to have two faces facing in opposite directions...and ; that's very descriptive of what the JANUS protocol does. It is ; tailored for the V.32/V.32bis modems that have a full duplex ; connection (i.e. for a v.32bis modem, you will have 14.4K in both ; directions as opposed to a HST which usually has 14.4K in one ; direction and 450 baud in the other). ; ; If you don't have a v.32/v.32bis modem, then leave this alone! ; Otherwise, make the appropriate substitutions (refer to the docs for ; the full description). ; ; Janusbaud 2400 ;JanusOK /Arq/V32 ;JanusOK /V32 ; ; ; NoEMSI is required for FrontDoor mailers as they do not properly ; handle EMSI for some reason. This will force Bink/ST to use the ; WaZOO/2U2 protocol for mail transfer (it isn't as good as EMSI, but ; it works! ; ; NoEMSI 1:363/32