home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 15
/
CD_ASCQ_15_070894.iso
/
vrac
/
fnp110a.zip
/
FNP110-A.DOC
< prev
next >
Wrap
Text File
|
1994-05-16
|
259KB
|
4,979 lines
FEATHERNET PRO!
FEATHERNET PRO! FEATHERNET PRO!
FEATHERNET PRO! FEATHERNET PRO! FEATHERNET PRO!
FEATHERNET PRO! FEATHERNET PRO!
FEATHERNET PRO!
PROFESSIONAL BULLETIN BOARD SOFTWARE
Version 1.10
Copyright (c) 1993-1994 by FeatherNet Software, Inc.
All Rights Reserved
FeatherNet Software, Inc.
FEATHERNET PRO! COMPUTER BULLETIN BOARD SYSTEM
Version 1.10
Documentation Revision 1.10a
For the IBM-PC AT Class and 100% Compatibles
Copyright (c) 1993-1994 FeatherNet Software, Inc.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page iii ║
╚════════════════════════════════════════════════════════════════════════════╝
ACKNOWLEDGEMENTS
Information in this manual is subject to change without notice and does
not constitute or represent a commitment on the part of FeatherNet
Software, Inc. The Software, documentation, and information described
in this document is furnished under agreement or nondisclosure agreement
and may be used or copied only in accordance with the terms of the
agreement. It is against the law to copy the Software and/or
documentation except as specifically stated in the license or
nondisclosure agreement.
Copyright(c)1993-1994 FeatherNet Software, Inc. All Rights Reserved.
Documentation Printed in the United States of America.
FeatherNet Software, Inc. is a U.S. Corporation based in Florida, U.S.A.
FeatherNet PRO!, FEATHERNET PRO! and all other FeatherNet Software
products are proudly designed, programmed, and supported in the United
States of America.
FeatherNet PRO!, FEATHERNET PRO!, FeatherNet Software, FNet,
ULTester, PCBULT, and FNCMT are protected trademarks of
FeatherNet Software, Inc.
FeatherNet BBS (All versions) is a trademark of FeatherNet Software, Inc.
DSZ is a trademark of OMEN Technologies
SDPD is a trademark of Stream Line Design
MS-DOS is a registered trademark of Microsoft Corporation
Windows is a trademark of Microsoft Corporation
IBM, AT, PS/2, PC-DOS and OS/2 are registered trademarks of IBM
Hayes is a registered trademark of Hayes Microcomputer Products, Inc.
HST is a trademark of USRobotics, Inc.
Intel is a registered trademark of Intel Corporation
DESQview and QEMM are registered trademarks of Quarterdeck Offices Systems
PCBoard is a registered trademark of Clark Development Co. Inc.
QEdit is a trademark of SemWare
RIPscrip, RIPaint, and RIPterm are trademarks of TeleGrafix Communications,
Inc.
TheDraw is a trademark of TheSoft Programming Services
All other trademarks are the property of their respective owners. Their
use in this documentation does not suggest or constitute an attempt by
FeatherNet Software, Inc. to claim them as their own, nor does
FeatherNet Software, Inc. specifically endorse or suggest the use of
these products or services.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page iv ║
╚════════════════════════════════════════════════════════════════════════════╝
PIRATING
IS
STEALING!
No Hassles - No Questions - Please Don't Do It! - Thank You.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page v ║
╚════════════════════════════════════════════════════════════════════════════╝
COPYRIGHT NOTICE
The FEATHERNET PRO! Computer Bulletin Board System and all of it's Associated
materials are copyright(c)1993-1994 by FeatherNet Software, Inc. All rights
reserved. FEATHERNET PRO! is a trademark owned and protected by FeatherNet
Software, Inc. This document is copyright (c) 1993-1994 by FeatherNet
Software, Inc.
The look, see, feel, and structure of this program is uniquely designed and
any similarity between it and any other program is unintentional.
FEATHERNET PRO! shall under no circumstances be considered in the Public
Domain. FeatherNet Software, Inc. holds and protects all copyrights and
trademarks on it's products. Copying, duplicating, selling, or otherwise, in
any way distributing the registered version of any of FeatherNet Software,
Inc.'s products is in violation of the laws of The United States of America
and International Treaties.
If you are currently using the SHAREWARE version, you may do so for a
REASONABLE period (30 days and no longer is considered reasonable) after which
time you should register the program or discontinue its use. If you continue
to run the SHAREWARE version longer than thirty (30) days you shall be
considered in violation of FeatherNet Software, Inc.'s copyright and in
violation of United States of America and International Copyright laws and
other applicable treaties.
LIMITED WARRANTY
FeatherNet Software, Inc. warrants to the ORIGINAL LICENSEE of a registered
FeatherNet product that the program diskette(s) on which the program is
recorded will be free from defects in materials and workmanship under normal
use and service for the period of ninety (90) days from the date of delivery
as evidenced by a copy of your receipt. FeatherNet Software, Inc. states unto
you that the entire liability and your exclusive remedy shall be replacement
of the diskette(s) not meeting FeatherNet Software, Inc.'s Limited Warranty if
returned to FeatherNet Software, Inc. during the ninety (90) day period.
Except for the forgoing, this product is provided "as is" without warranty of
any kind. The entire risk as to the results and performance of the program is
assumed by you. FeatherNet Software, Inc. does not warrant, guarantee, or
make any representations regarding the use of, results of, merchantability or
fitness for a particular use of the product. Should the program prove
defective, you, (and under no circumstances FeatherNet Software, Inc. or any
of it's dealers) assume the entire cost of all necessary servicing, repair or
correction. Furthermore, FeatherNet Software, Inc. does not warrant,
guarantee, or make any representations regarding the use of, or the results of
the use of the software in terms of correctness, accuracy, reliability,
currentness, or otherwise; and you rely on the program and results solely at
your own risk. FeatherNet Software, Inc. will not be liable for any damages,
including but not limited to system damage, service, repair, correction, loss
of profit, lost savings, or any other incidental, consequential, or special
damages of any nature whatsoever resulting from the use or inability to use
this software. Your continued use of this Software and any Associated
Materials confirms your intention to abide by the licensing agreement and your
understanding of the limited warranty.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page vi ║
╚════════════════════════════════════════════════════════════════════════════╝
LICENSE AGREEMENT
IMPORTANT!
PLEASE READ THIS ENTIRE SECTION BEFORE YOU OPEN THE ENVELOPE CONTAINING YOUR
NEW COPY OF FEATHERNET PRO! BY OPENING THE ENVELOPE CONTAINING YOUR FEATHERNET
PRO! DISKETTE(S) OR THE ENVELOPE CONTAINING THE SOFTWARE REGISTRATION CODE YOU
ACKNOWLEDGE YOUR AGREEMENT TO THE TERMS OF THIS LICENSE. YOU MAY HAVE
SPECIFIC RIGHTS WHICH WILL VARY FROM STATE TO STATE.
OBTAINING A REFUND;
If you do NOT wish to agree to and/or abide by the terms of this license
agreement, you may obtain a full refund by returning this entire package to
FeatherNet Software, Inc. within five (5) business days, provided you have
NOT opened either the diskette(s) or registration envelopes.
IF EITHER OF THESE ENVELOPES HAVE BEEN OPENED OR TAMPERED WITH, NO REFUND
REQUEST WILL BE GRANTED.
This Software is a unique item as it needs a registration code to run. Once
you open a registration envelope you have the key. You can return the disks
and the manual, but you can not return that key. We have very little recourse
if you decide to run with that key after you return the product. Once you
decide to register it you have licensed what you have. There will be NO
REFUNDS on opened packages, period. You are under no obligation to upgrade.
DEFINITIONS;
The term "Software" as used in this license agreement, the disclaimer,
and(c)copyrights notice, all within this documentation means the FULL SYSTEM
AND ALL UTILITY COMPUTER PROGRAMS contained on the diskette(s) in this
package, together with any upgrades or updates subsequently supplied by
FeatherNet Software, Inc. The term "Author" as used in this license
agreement, the disclaimer, and(c)copyright notice, all within this
documentation means FeatherNet Software, Inc. and it's principal officers.
The term "User" as used in this license agreement, the disclaimer,
and(c)copyright notice, all within this documentation means the person or
entity that has licensed the Software for use. (You! The SYStem OPerator.)
The term "Copies" means the actual copies of any portion of or all of the
Software, including back-ups, updates, merged or partial copies permitted
hereunder or subsequently supplied by FeatherNet Software, Inc. The term
"Associated Materials" means all the printed materials provided in this
package or subsequently supplied by FeatherNet Software, Inc. for use with
the Software. This also applies to any unprinted ASCII files which may appear
on the diskette(s) with last minute release notes or other Associated
information.
PERMITTED USES; YOU MAY:
Use the Software on a single computer or on multiple computers that are
connected via a physical cable to the same network server. This is
specifically includes single computers and local area networks (LANS)
connected without the use of telephony or modulation/demodulation (MODEM)
equipment. The use of this software on a Wide Area Network (WAN),
specifically those networks connected using Satellite, Radio, or Telephony
Carrier is prohibited under this license but may be obtained under other
licenses offered by FeatherNet Software, Inc.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page vii ║
╚════════════════════════════════════════════════════════════════════════════╝
You may install the Software onto a semi-permanent storage device (a hard disk
drive or floptical diskette drive).
This license gives you certain limited rights to use the Software. You do not
become an owner of the Software. FeatherNet Software retains title to all the
Software, Copies, and Associated Materials. In addition, you agree to use
reasonable care to protect the Software from unauthorized use, reproduction,
distribution, or publication. All rights not specifically granted in this
license are reserved by FeatherNet Software, Inc,
You are granted a personal non-exclusive, non-transferable license to use the
enclosed program and documentation solely for your own internal needs on one
central processing unit or network of physically connected computers. You
assume the entire responsibility for the selection of the program to achieve
your intended results, and for the installation, use and results obtained from
the program.
YOU MAY NOT;
Sub-license, assign, or transfer your rights under this agreement. You agree
not to transfer the FEATHERNET PRO! Software, or the materials supplied, in
any form to any person without the prior written consent of FeatherNet
Software, Inc. Rent, lease, sub-license, or transfer The Software, Copies,
Associated Materials or your rights under this license, without first gaining
the prior written consent of FeatherNet Software, Inc. Alter, decompile,
disassemble, or reverse engineer the Software. Remove, obscure, alter, or
cause to be hidden the FeatherNet Software copyright and/or trademark.
DURATION OF AGREEMENT;
This agreement is effective from the day you open the sealed either of the
sealed envelopes containing your Software diskettes or your Software
Registration codes. Your license continues for the period of twenty years or
until you return the Software, Copies, and Associated materials to FeatherNet
Software, Inc., whichever comes first. If you breach your agreement, we can
terminate this license by notifying you in writing. You will be required to
return all Software, Copies and Associated Materials. We may also, at that
time, choose to enforce any other legal rights. If for any reason, FeatherNet
Software, Inc. finds it necessary to force legal action, the user, licensed
or not, shall bear all reasonable costs of such actions. This agreement
represents our entire understanding and agreement regarding the use of the
Software, Copies, and Associated Materials & supersedes any prior purchase
order, communications, advertising, or representations. This license may only
be modified in a written amendment signed by at least two officers of
FeatherNet Software, Inc. If any provision of this agreement shall be
unlawful, void, or for any reason unenforceable, it shall be deemed severable
from, and shall in no way affect the validity or enforceability of the
remaining provisions of this agreement. This agreement shall be governed by
FLORIDA law. You acknowledge that you have read every provision of this
contract. By opening the envelope containing either the diskette(s) or the
Registration code, and/or running either the SHAREWARE or REGISTERED version
of the Software, you acknowledge that you have read and agree to this
contract.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page viii ║
╚════════════════════════════════════════════════════════════════════════════╝
DISTRIBUTION
The SHAREWARE version of FEATHERNET PRO!, FEATHERNET PRO! v1.10 BBS Software
may be copied freely and distributed globally within the following guidelines;
All software must be distributed intact, including programs, utilities, and
documentation and must not have been altered in anyway, whatsoever. You may
NOT insert a BBS Ad or any other advertising (commercial in nature or not)
file into the archive. You are authorized to include a "ZIP comment" which
displays only as the archive is being opened. The 'Zip/Arj Comment' which
displays only as the file is unZIP'd/unARJ'd may be an advertisement for your
BBS/Group.
Clubs and user groups are authorized to charge a nominal fee not to exceed
$7.50 for the distribution of FEATHERNET PRO! or any other FeatherNet Software
program.
SysOps ONLY are eligible for the DISTRIBUTION SITE INCENTIVE PROGRAM. With
v1.10 of the FEATHERNET PRO! BBS System, FSI has instituted it's D.S.I.P.
program making it possible for you to make some extra cash when you make the
FEATHERNET PRO! BBS available for download on your system or even when you
upload it to other systems! Participation in this new program is available to
any SYSOP and is easy to setup. If The FEATHERNET PRO! BBS system is
registered by a user and the registration form shows your DEMOG CODE, showing
it was LAST DISTRIBUTED by you, we will send you 5% (five percent) of the
registration (does not including SALES TAX or SHIPPING CHARGES) at month's
end. This program is NOT available to COMMERCIAL FILE DISTRIBUTION SYSTEMS,
COMPANIES, AND/OR CD-ROM PRODUCERS.
SYSOP INSTRUCTIONS: For participation in this program you must edit the file
DEMOG.COD in the archive FNP110SW.ZIP. In this file you may put in a small
BBS ad and your DEMOG CODE (Make sure the SysOp can find it) and delete any
previous information that was contained in the file.
The DEMOG CODE (Demographics Code or BBS Identifier) is a 5 DIGIT code for
the identification of your BBS. This code may be a series of numbers such as
'48653' or letters such as 'FN-HQ' or a combination of both like 'FHQ01'.
You must then log on to the FeatherNet HQ BBS or NETMAIL us, and leave your
DEMOG CODE, your MAILING ADDRESS and the NAME to make any checks payable to
in a message. Your BBS NAME/BBS PHONE NUMBER will then be added to the
OFFICIAL DISTRIBUTION SITE list and you will be notified of any new updates
available.
For more information on the DSIP program, you may NETMAIL us at 1:377/59 or
call BBS at (813)249-8422 or call us voice (813) 249-8322 M-F 9-5 ET.
Commercial Shareware Distributors, to include, but not necessarily limited to,
Mail Order Houses, Commercial BBSes, and/or CD-ROM disc authors, may
distribute FEATHERNET PRO! or any other FeatherNet Software program and are
authorized to charge a nominal fee not to exceed $7.50 for the distribution
ONLY AFTER NOTICE IS GIVEN IN WRITING to FeatherNet Software, Inc. of your
intention to do so.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page ix ║
╚════════════════════════════════════════════════════════════════════════════╝
REQUIRED PREREQUISITES
FEATHERNET PRO! REQUIRES MS/PC DOS v3.1+ or a compatible operating system such
as OS/2 2.1+. FEATHERNET PRO! will also run under Windows 3.1 and Windows for
Work Groups 3.1, however, your system will be limited in performance and
number of ports thus we do not recommend this setup. An INTEL or 100% INTEL
Compatible processor (80386-SX or Faster recommended) on a 100% compatible
motherboard is mandatory. FEATHERNET PRO! will NOT run on an 8086 XT class
processor. Approximately 250K of RAM is utilized by the program while
operating (Memory requirements increase by approximately 100 bytes for each
file transfer directory and by 35 bytes for each file download path configured
for a conference). Any 100% IBM clone, 80286+, will run FEATHERNET PRO! well.
It is recommended a machine with a large (1 MB min.) disk cache be used for
optimum performance. A 1-2 MB RAM disk can also dramatically increase your
performance while running FEATHERNET PRO! It should be noted that while
FEATHERNET PRO! does support Digiboards, Digiboards are not compatible in OS/2
VDM's and you should confine your use of these to another operating system.
There are a number of programs that will be needed by you to operate a
successful Bulletin Board System. FeatherNet Software, Inc. can not provide
you with these files due to size and legal requirements. These files are
DSZ/GSZ protocol driver (unregistered version provided in your FEATHERNET PRO!
package) or SDPD (For use with the DigiBoard version), ZIP/ARJ/LZH etc file
archive utilities, BNU/X00/DigiFossil fossil drivers (Not required by
FEATHERNET PRO! but can be used) and DOOR programs for your users to use.
Other programs you should have on hand are a good ANSI editor, a good TEXT
(ASCII) editor, and if you will be changing from the default RIPscrip screens
we provided you with, a good RIPscrip paint program.
Most of these programs are SHAREWARE and in most cases a SEPARATE registration
is required to operate them with all abilities unlocked. Please see the
individual documentation files of the programs for more information in this.
Some of these files you may already have, some you will need to get, most can
be found on the FeatherNet HQ BBS or other fine BBS systems.
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page x ║
╚════════════════════════════════════════════════════════════════════════════╝
TABLE OF CONTENTS (RD=Registered Docs Only)
ACKNOWLEDGMENTS ........................................................ iii
PIRATING IS STEALING!................................................... iv
COPYRIGHT NOTICE........................................................ v
LIMITED WARRANTY........................................................ v
LICENSE AGREEMENT....................................................... vi
DISTRIBUTION............................................................ viii
REQUIRED PREREQUISITES.................................................. ix
TABLE OF CONTENTS ...................................................... x
INTRODUCTION............................................................ 1
INITIAL SETUP & INSTALLATION............................................ 3
Structure Flow Chart .................................................. RD
Directory Files Listing................................................ RD
A FEW NOTES ON YOUR BBS DISPLAY SCREENS ............................... 7
FNCFG.EXE - The Configuration Editor................................... 9
Main Configuration Menu................................................ 10
CONFERENCE SELECTION, ADDITION, LISTING................................. 11
CONFERENCE SETUP PAGE # 1 .............................................. 12
Conference Name ....................................................... 12
Allow Aliases.......................................................... 12
Co-SysOp's Name ....................................................... 12
Message File Path & Name .............................................. 13
Conference Introduction File........................................... 13
Read Security Level ................................................... 13
Attachment Directory .................................................. 14
Reply Security Level .................................................. 14
Write Security Level .................................................. 14
Receipt Security Level................................................. 14
Upload Directory Security Level........................................ 14
Upload Description File................................................ 14
Upload File Path....................................................... 15
Bulletin Menu File..................................................... 15
Bulletin List File..................................................... 15
Bulletin path & filename .............................................. 16
Creating a bulletin ................................................... 16
Saving the bulletin configuration file................................. 16
Door Menu File ........................................................ 16
Door List File ........................................................ 16
Door batch file name .................................................. 17
Door password.......................................................... 17
Door security level ................................................... 17
Auto logon doors....................................................... 18
Create DOOR.SYS file .................................................. 18
Shell/Swap to door..................................................... 19
Path to door batch file................................................ 19
RIPscrip supported by door............................................. 19
Saving the door configuration file .................................... 20
Menu for Directory Listing............................................. 20
Directory listing control file for this conference .................... 20
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xi ║
╚════════════════════════════════════════════════════════════════════════════╝
Directory text filename & path ........................................ 20
Hard disk sub directory................................................ 21
File directory security................................................ 21
Category of directory.................................................. 21
Saving the directory listing file...................................... 21
Alternate download path listing file................................... 22
Alternate download path................................................ 22
Security level for download path....................................... 22
Additional notes on the alternate download listing .................... 23
Saving the alternate d/l directory listing file........................ 23
Index File Name ....................................................... 23
Prohibited Words Data File............................................. 24
Echo This Conference .................................................. 24
Make This A Public Conference ......................................... 24
Message Blocks ........................................................ 25
Use Graphics Quoting Feature........................................... 25
Private Mail Only...................................................... 25
Public Mail Only....................................................... 25
CONFERENCE SETUP PAGE #2 .............................................. 26
Conference Password ................................................... 26
Conference NEWS File .................................................. 26
Conference MAIN Menu File ............................................. 26
Conference SysOp MAIN Menu File ....................................... 27
Conference MESSAGE Menu File. ......................................... 27
Conference SysOp MESSAGE Menu File .................................... 28
Conference Specific Listing File ...................................... 28
Conference FILE Menu File ............................................. 29
Conference SysOp FILE Menu File ....................................... 29
Ignore Security When Viewing Files In This Conference ................. 29
GENERAL INFORMATION ................................................... 30
Name Of Your BBS....................................................... 30
SysOp's Name........................................................... 30
Use SysOp's Real Name.................................................. 30
"Today" Function....................................................... 31
Enable Questionnaires.................................................. 31
Number Of Questionnaires .............................................. 31
Registration Number ................................................... 32
Minimum User Password Length........................................... 32
Add "Uploaded by:" To Description...................................... 32
Use Color Graphics During Local Logon.................................. 32
Confirm Users Name & Address........................................... 33
Minimum Upload Drive Space............................................. 33
Minutes Before FEATHERNET PRO! Recycles to DOS......................... 33
Time Credit For Uploads................................................ 34
Limit SysOp Paging Hours .............................................. 34
SysOp Start Time....................................................... 34
SysOp Stop Time ....................................................... 34
Number Of Chat Rooms .................................................. 34
GENERAL INFORMATION 2................................................... 35
Pre-Load FNETTEXT File................................................. 35
Warn Callers At Logoff If "Download Flags" Are Set .................... 35
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xii ║
╚════════════════════════════════════════════════════════════════════════════╝
Prompt Callers To Set Message Pointers At Logoff....................... 35
Confirm Logoff Command................................................. 35
Swap to XMS, EMS or Disk During A Shell ............................... 36
Enable Logon/Logoff Broadcasting....................................... 36
Allow [P]rivate Transfers ............................................. 36
Operate As A Closed System............................................. 36
Allow Split Screen Chat To Be Used .................................... 37
Force Users To Read New Mail At Logon.................................. 37
Always Force Users To Select Transfer Protocol......................... 37
Have The "Do You Want Color" Question Default to Y/N................... 37
Disable The Auto ANSI Detect Function At Logon......................... 37
Display Users Statistics File At Logon................................. 38
Allow "Aliases" Or Single Word Names................................... 38
Allow Sending of One Liners............................................ 38
Maximum Lines To Display When Reading From Archive .................... 38
Use Which Parallel (Printer) Port (0-3) ............................... 38
Force Users Into Bulletin Menu At Logon ............................... 38
Maximum Lines Allowed In Message Editor ............................... 39
MODEM/NODE/SUBSCRIPTION INFORMATION .................................... 40
Modem Initialization String............................................ 40
Communications Driver To Use........................................... 40
Which Communications Port (0-64) Is This Node.......................... 40
Baud Rate To Open Communications Port At (300-115200).................. 40
Lock Communications Port At Opening Baud Rate ......................... 41
Answer On Which Ring .................................................. 41
Seconds To Wait For Connect............................................ 41
Minimum Baud Rate Allowed ............................................. 41
Pause For 3 Seconds After Connect At 2400.............................. 41
Operate in Subscription Mode........................................... 41
Default New User Subscription In Days.................................. 42
Days Warning Before Subscription Expires .............................. 42
Expired Subscription Security Level ................................... 42
Operate In A Ring Back Mode............................................ 42
How Ring Back Mode Works .............................................. 42
Seconds To Wait For Ring Back ......................................... 42
Node Number............................................................ 42
Node Password.......................................................... 43
Filter All High ASCII Characters....................................... 43
Using A Network Or Multi-Tasker........................................ 43
Using A "Front-End" To Load FEATHERNET PRO!............................ 43
EVENT & COMMAND TRANSLATION CONFIGURATION............................... 44
Event List File Path & Name............................................ 44
Events List File Editor................................................ 44
Is this event active .................................................. 44
Event mode ............................................................ 44
Event batch file name.................................................. 45
Begin event time....................................................... 45
End event time ........................................................ 45
Event date ............................................................ 45
Last event date ....................................................... 46
Event day flags ....................................................... 46
Event Examples ........................................................ 46
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xiii ║
╚════════════════════════════════════════════════════════════════════════════╝
Saving the event configuration file ................................... 46
Minutes Prior To Event To Disallow Callers............................. 46
Modem Off-Hook (Busy) When An Event Is Pending......................... 47
Main Menu Command Translation File .................................... 48
Message Menu Command Translation File.................................. 48
File Menu Command Translation File .................................... 49
FILE LOCATIONS SCREEN 1................................................. 50
Path Of Main BBS Directory............................................. 50
Path Of Node Work Directory............................................ 50
Path Of Node Home Directory............................................ 50
Path Of Security Level Files........................................... 50
Duplicate Upload "Hold" Directory...................................... 51
File To Run Before And After File Transfer............................. 51
Path Of The Private File Transfer Directory............................ 51
Path & Name Of "FNETTEXT" File ........................................ 51
Path Of User Index Files .............................................. 52
Path Of Special "Help" Files........................................... 52
Path & Name Of "PWRD" File............................................. 52
Security level ........................................................ 52
Time allowed on system................................................. 52
Maximum k-bytes to download today...................................... 53
Standard baud rate..................................................... 53
Batch file transfer limit ............................................. 53
File download ratio ................................................... 53
Byte download ratio ................................................... 53
File download limit ................................................... 53
K-byte download limit.................................................. 54
File credits........................................................... 54
K-byte credits ........................................................ 54
Use hourly subscription................................................ 54
Birthday Verification Security ........................................ 54
Phone Number Verification Security .................................... 54
Saving The "PWRD" Configuration File................................... 55
Path & Name Of The Quote Text File .................................... 55
Path & Name Of The Multi Language File................................. 55
Slow Drive Letters..................................................... 56
Path & Name Of The Co-SysOp Bit Map File .............................. 56
Path & Name Of The User's Information File............................. 56
Path & Name Of The Protocol Data File.................................. 56
Path & Name Of The "Trash" File........................................ 56
FILE LOCATIONS SCREEN 2................................................. 57
Main Menu File ........................................................ 57
SysOp's Main Menu File................................................. 57
Message (Conference) Command Menu File................................. 57
SysOp's Conference Command Menu File................................... 57
Path & Name Of The Conference listing Menu............................. 58
File Transfer Menu File................................................ 58
SysOp's Transfer Menu File............................................. 58
Script Questionnaires Menu File........................................ 58
Newuser Script File Name .............................................. 59
Script Questionnaires.................................................. 59
Prelog File............................................................ 59
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xiv ║
╚════════════════════════════════════════════════════════════════════════════╝
News File ............................................................. 59
Hello File ............................................................ 60
Newuser File........................................................... 60
Closed BBS File ....................................................... 61
Caller Log File ....................................................... 61
Logoff File............................................................ 61
Today File ............................................................ 62
User Statistics File .................................................. 62
FILE LOCATIONS SCREEN 3................................................. 63
Post Upload File....................................................... 63
Failed Upload File..................................................... 63
Post Download File..................................................... 63
Failed Download File .................................................. 64
Path Of The "Free" Files To Download Directory......................... 64
Path Of The "Paid" Files To Download Directory......................... 64
Group Chat Menu ....................................................... 65
Location Of Chat Files................................................. 65
Expired Warning File .................................................. 65
Expired File........................................................... 66
Pre-Download Warning File ............................................. 66
Pre-Upload Warning File................................................ 66
Prohibited Words Warning File ......................................... 67
Path & Name Of FNCONF.@@@ ............................................. 67
Path & Name Of FNCONF.LST File ........................................ 67
Path & Name Of USERS File ............................................. 67
Path & Name Of FNEXTUSR File........................................... 68
SECURITY FILES - SYSTEM/SYSOP .......................................... 69
Security Level To Use The [CALL] Command .............................. 69
[F]ile Transfer Area Security Level ................................... 69
Security Level For The [H]elp Command.................................. 69
Security Level To [J]oin A Conference.................................. 69
Security Level To [K]ill Any Message................................... 69
Security Level To Use Toggle E[X]pert Mode............................. 69
Security Level To Use [*] Global New Read.............................. 69
Security Level To Carbon Copy Messages................................. 69
Security Level To Edit Any Message .................................... 69
Security Level To Edit Your Messages................................... 70
Security Level To Use "@" Macros In Messages .......................... 70
New User Security Level................................................ 70
Security Level To Read All Mail & Comments............................. 70
Security Level To Zero Time At Each Logon.............................. 70
Allow Quick Logons..................................................... 70
SECURITY LEVELS - MAIN MENU............................................. 71
Security Level To View [B] Menu........................................ 71
Security Level To Leave A [C]omment ................................... 71
Security Level For The [D]oor Command.................................. 71
Security Level To Edit User [I]nformation.............................. 71
Security Level To Use The [O]perator Command .......................... 71
Security Level To Use The [P]age Length Command........................ 71
Security Level To Use The [Q]uestionnaire Command ..................... 71
Security Level To [S]elect Color Graphics.............................. 71
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xv ║
╚════════════════════════════════════════════════════════════════════════════╝
View [T]oday's Callers Security Level.................................. 72
Security Level To List System [U]sers Command ......................... 72
Security Level To [V]iew Selected Statistics .......................... 72
Security Level To View The [W]elcome File.............................. 72
Security Level To Use [VER] BBS Version Command........................ 72
SECURITY LEVELS - FILE MENU SCREEN ..................................... 73
[D]ownload Security Level ............................................. 73
Security Level To view Logged [F]ile Directory......................... 73
Security Level To Search For [N]ew Files .............................. 73
Security Level To [TP] Change Transfer Protocol........................ 73
[U]pload Security Level................................................ 73
Security Level To [V]iew Archives...................................... 73
Security Level For [Z]ippy Directory Search............................ 73
SECURITY LEVELS - MESSAGE MENU ......................................... 74
Security Level To [A]rchive & Download Mail............................ 74
Security Level Required To [K]ill A Message`........................... 74
Security Level To [S/SS] Scan/SuperScan Messages....................... 74
Security Level To [U]pdate Set Conference Scans........................ 74
Attach File To Message [SA] Security Level............................. 74
FUNCTION KEY PROGRAMMING ............................................... 75
Shifted Function Key Assignments....................................... 75
MESSAGE HEADER & TEXT ENTRY COLLORS .................................... 76
Message Header Line Colors............................................. 76
Text Entry Colors...................................................... 76
QWK CONFIGURATION....................................................... 77
NET ID................................................................. 77
BBS Location........................................................... 77
BBS Phone Number....................................................... 77
CRC 32 Duplicate Checking ............................................. 77
QWK Packet Directory for Local Use .................................... 77
REP Packet Directory for Local Use .................................... 77
HELLO File to Include.................................................. 77
NEWS File to Include .................................................. 77
GOODBYE File to Include................................................ 78
.QWK Menu to Use....................................................... 78
Number of Messages Differnt Baud Rates May Download.................... 78
Tagline ............................................................... 79
SAVING THE FNCFG.EXE (SRCONFIG) FILE.................................... 79
RUNNING FEATHERNET PRO!................................................. 80
Modem ................................................................. 80
BBS Files ............................................................. 80
THE ORDER OF DISPLAY.................................................... 81
WAITING FOR CALL SCREEN................................................. 82
Screen Information..................................................... 82
The Header ............................................................ 82
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xvi ║
╚════════════════════════════════════════════════════════════════════════════╝
The Center Screen...................................................... 82
Node .................................................................. 82
New users ............................................................. 82
Old users ............................................................. 82
Calls ................................................................. 82
Calls Total............................................................ 82
Calls Today............................................................ 82
Next Event............................................................. 82
Sysop mail ............................................................ 82
The Bottom Screen...................................................... 82
Comx .................................................................. 83
Current activity....................................................... 83
Last caller............................................................ 83
Quick description...................................................... 83
SysOp Option Fields ................................................... 83
Local-in busy.......................................................... 83
DOS busy............................................................... 83
SysOp in busy.......................................................... 83
DOS not busy........................................................... 83
FNFiler................................................................ 83
View Caller Logs....................................................... 83
FNetSM................................................................. 83
Printer on (y/n)....................................................... 83
FNCfg ................................................................. 84
SysOp page (y/n)....................................................... 84
Node monitor........................................................... 84
Beep (y/n) ............................................................ 84
SysOp Configurable Options From WFC Screen............................. 84
SysOp Help Functions Within The BBS <F10>.............................. 84
SysOp Help <F1> ....................................................... 85
SysOp Help <F2> ....................................................... 85
SysOp Help <F3> ....................................................... 85
SysOp Help <F4> ....................................................... 85
SysOp Help <F5> ....................................................... 85
SysOp Help <F6> ....................................................... 85
SysOp Help <F7> ....................................................... 85
SysOp Help <F8> ....................................................... 85
SysOp Help <F9> ....................................................... 85
SysOp Help <F10>....................................................... 85
SysOp Help <Alt><C> ................................................... 85
SysOp Help <Alt><P> ................................................... 85
SysOp Help <Space>..................................................... 85
SysOp Help <ESC>....................................................... 85
SysOp Help "CALL"...................................................... 85
MAIN MENU .............................................................. 86
[*] Global New Message Scan Command ................................... 86
[B]ulletin Menu Command................................................ 86
[C]omment To The SysOp Command ........................................ 86
[D]oor Menu Command ................................................... 86
[F]iles Menu Command .................................................. 86
[G]oodbye Command...................................................... 86
[H]elp Command ........................................................ 86
[I]nformation Change (User) Command ................................... 87
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xvii ║
╚════════════════════════════════════════════════════════════════════════════╝
[J]oin A Conference Command............................................ 87
[L]anguage Change Command ............................................. 87
[M]essage Menu Command................................................. 87
[N]ode Status Command.................................................. 87
[NEWS] Display Command................................................. 87
[O]perator Command..................................................... 87
[P]age Length Set Command ............................................. 87
[Q]uestionnaire Menu Command........................................... 88
[QWK] command menu .................................................... 88
[S]creen Color Toggle Command ......................................... 88
[T]odays Callers Command .............................................. 88
[TODAY] Option Command................................................. 88
[U]sers Listing Command................................................ 88
[V]iew User Statistics Command ........................................ 88
[VER]sion of FEATHERNET PRO! Command................................... 88
[W]elcome (Hello) Screen Display Command .............................. 88
[X] Expert Mode Toggle Command ........................................ 88
[CALL] View Caller Logs Command (SysOp Status Only).................... 88
MESSAGE MENU............................................................ 89
[*] Global Scan New Mail Command....................................... 89
[A]rchive Mail Command................................................. 89
[E]nter A Message Command ............................................. 89
[F]iles Menu Command .................................................. 89
[G]oodbye Command...................................................... 89
[H]elp Command ........................................................ 89
[J]oin A Conference Command............................................ 89
[K]ill Messages Command................................................ 89
[L]evel Reset High Message Pointers Command............................ 90
[N]ew Mail Command..................................................... 90
[Q]uit To Main Menu Command............................................ 90
[QWK] Command Menu .................................................... 90
[R]ead Mail Command ................................................... 90
[S]can Mail Command ................................................... 90
[SS] SuperScan Mail Command............................................ 90
[T]ext Search Command.................................................. 90
"OR" search function................................................. 90
"AND" search function................................................ 91
[U]pdate Flagged Conferences Command................................... 91
[X] Expert Mode Toggle Command ........................................ 91
FILE MENU .............................................................. 92
[D]ownload A File Command ............................................. 92
[F]iles in Current Conference File Directory Command................... 92
[G]oodbye Command...................................................... 92
[H]elp Command ........................................................ 92
[J]oin A Conference Command............................................ 92
[L]ist File Directories Command........................................ 92
[M]essage Menu Command................................................. 92
[N]ew Files Command ................................................... 93
[P]rivate File Transfers Command....................................... 93
[Q]uit To Main Command................................................. 93
[QWK] Command Menu .................................................... 93
[TEST] An Archive Command ............................................. 93
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xviii ║
╚════════════════════════════════════════════════════════════════════════════╝
[TP] Transfer Protocol Change Command.................................. 93
[U]pload A File Command................................................ 93
[V]iew Contents Of An Archive Command.................................. 93
[X] Expert Mode Toggle Command ........................................ 94
[Z]ippy Text Search Command............................................ 94
"OR" search function................................................. 94
"AND" search function................................................ 94
BULLETIN MENU........................................................... 95
[A]ll Bulletins Read Command........................................... 95
[D]ownload Bulletins Command........................................... 95
[N]ew Bulletins Read Command........................................... 95
[T]ext Search In Bulletins Command .................................... 95
[#] Bulletin Read Command (# = Actual Number) ......................... 95
QUESTIONNAIRE MENU...................................................... 96
[#] Questionnaire Read Command (# = Actual Number) .................... 96
[Q]uit Back To Main Menu Command....................................... 96
QWK MENU................................................................ 97
[?] Command............................................................. 97
[C]onfigure QWK Settings Command........................................ 97
[D]ownload QWK Packet Command........................................... 97
[DG]ownload QWK Packet and Logoff Command............................... 97
[H]elp Command.......................................................... 97
[P]ointer Reset Command................................................. 97
[Q]uit Command.......................................................... 97
[S]et Conference Flag Command........................................... 97
[S #]et Conference Flag Starting At Conference Number "#" Command....... 97
[U]pload REP Packet Command............................................. 97
[UG]pload REP Packet and Logoff Command................................. 98
[X] Expert On/Off Command............................................... 98
DOOR MENU .............................................................. 99
VISUAL EDITOR........................................................... 100
Key Commands........................................................... 100
Insert Mode............................................................ 101
Note For SysOps With Non-PC Keyboard Users............................. 101
BATCH FILES............................................................. 102
SFN.BAT................................................................ 102
FNP*.BAT............................................................... 104
FNETTEST.BAT........................................................... 105
Running Multiple Nodes................................................. 106
Tips & Troubleshooting................................................. 108
Other Files You Should Have To Run the BBS............................. 110
Error Codes............................................................ 111
SYSOP UTILITIES ........................................................ 112
General................................................................ 112
FNETSM.EXE ............................................................. 113
[A] Edit Users ........................................................ 113
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xix ║
╚════════════════════════════════════════════════════════════════════════════╝
Key controls........................................................... 114
User's name............................................................ 114
City & state user is from ............................................. 114
User's security password .............................................. 114
Business/data phone number............................................. 114
Voice phone number..................................................... 114
Users security level .................................................. 115
Deleted user flag...................................................... 115
Expiration date ....................................................... 115
Last date on system ................................................... 115
Time used today ....................................................... 115
User's text page length................................................ 115
Times logged onto bbs.................................................. 115
File transfer protocol................................................. 115
Files downloaded today................................................. 115
Number of uploads...................................................... 116
Number of downloads ................................................... 116
Bytes downloaded today................................................. 116
Bytes uploaded to bbs.................................................. 116
Bytes downloaded from bbs ............................................. 116
Allowed to use the [P]rivate files function............................ 116
Private files awaiting download........................................ 116
User's name............................................................ 116
User's alias name...................................................... 116
Users street address #1................................................ 117
Users street address #2................................................ 117
User's city............................................................ 117
User's zipcode ........................................................ 117
Number of messages the user has left................................... 117
User's date-of-birth .................................................. 117
User's sex ............................................................ 117
User's personal comment................................................ 117
Sysop's user comment .................................................. 117
User's state or province .............................................. 118
User's country ........................................................ 118
Clear screen between messages ......................................... 118
Scroll screen while reading messages................................... 118
Use the hi-lited flag and/or view option .............................. 118
STEALTH Mode........................................................... 118
Amount received ....................................................... 118
Amount to Debit........................................................ 118
Total Money Recieved................................................... 119
Cost per hour.......................................................... 119
Current money used..................................................... 119
Amount of balance...................................................... 119
Current hours used..................................................... 119
Current hours available................................................ 119
Days before expire..................................................... 119
Last payment date...................................................... 119
Conference registration flag........................................... 120
Co-sysop registration flag............................................. 120
Listing Users.......................................................... 120
[B] Create User Index.................................................. 120
[C] Pack Users ........................................................ 121
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xx ║
╚════════════════════════════════════════════════════════════════════════════╝
[D] Purge Users ....................................................... 121
[E] Define Editors..................................................... 121
[F] Access FNCFG`...................................................... 122
[G] Access FNFILER..................................................... 122
[H] Print User Records................................................. 122
[I] Sort User Records.................................................. 123
[J] Standardize Phone Formats ......................................... 123
Command Line Operation................................................. 124
FNFILER.EXE............................................................. 125
General................................................................ 125
Edit DIRxx Files....................................................... 125
Selecting Conference/Directory ........................................ 125
Key Commands........................................................... 126
Locate file on disk ................................................... 127
Locate file in DIRxx file ............................................. 128
Locate text in DIRxx file ............................................. 128
Edit FNFILER defaults.................................................. 128
FNFiler Command Line Options........................................... 129
Sorting.............................................................. 129
Building an ALL FILES List........................................... 129
MKFNTEXT.EXE............................................................ 130
Prompt Editor.......................................................... 130
Key Controls........................................................... 130
FNCHK.EXE .............................................................. 131
Overview............................................................... 131
FNCHK.CFG ............................................................. 131
Upload Integrity Checker Configuration................................. 132
ULTESTER UPLOAD PROCESSOR & VIRUS CHECKER............................... 133
Overview............................................................... 133
Features............................................................... 134
Observations & Conciderations.......................................... 134
The ULT%NODE%.BAT File................................................. 134
Setting Up............................................................. 135
FNETTEST.BAT............................................................ 141
FNPACK.EXE ............................................................. 142
Pack The Message File.................................................. 142
Renumber the Message Base.............................................. 142
Rebuild the Message Base............................................... 142
Resize the Message Base................................................ 142
FN-NET.EXE ............................................................. 143
Message Pointer Utility................................................ 143
The QWK Parameter...................................................... 143
MODEMSET.EXE............................................................ 144
Modem Setup Utility ................................................... 144
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xxi ║
╚════════════════════════════════════════════════════════════════════════════╝
BUILDNDX.EXE............................................................ 145
File Index Compiler ................................................... 145
CONFUTIL................................................................ 148
Running CONFUTIL....................................................... 149
Copying Conferences ................................................... 149
Swapping Conferences .................................................. 149
Deleting Conferences .................................................. 149
Blanking Conferences .................................................. 150
Moving Conferences..................................................... 150
Inserting Conference .................................................. 150
Summary Conferences ................................................... 150
CNAMES40.EXE............................................................ 152
PCBoard's CNAMES.@@@ Utility........................................... 152
FNODEMON.EXE............................................................ 153
Node Monitoring Utility................................................ 153
CONTROL FILES........................................................... 154
UPSEC ................................................................. 154
DIRxx ................................................................. 155
FNETPROT.DAT........................................................... 157
SRCONFIG............................................................... RD
USERS ................................................................. RD
USERNET.DAT............................................................ RD
MESSAGE FORMAT ........................................................ RD
FNPUSER.SYS............................................................ RD
DOOR.SYS............................................................... RD
PCBOARD.SYS............................................................ RD
DOORS.LST ............................................................. RD
FNCONF.@@@ ............................................................ RD
FNCONF.SEC ............................................................ RD
FNEXTUSR............................................................... RD
COSYSOP.BIT............................................................ RD
% Syntax............................................................... 159
Remote Mode Doors...................................................... 160
Downloadable Files..................................................... 161
FILE STRUCTURES ........................................................ 162
Files Listing........................................................... RD
APPENDIX A - Running With A Front-End Loader ........................... 163
APPENDIX B - Running Under DESQview & OS/2 ............................. 164
APPENDIX C - Macros .................................................... 165
Addressing messages ................................................... 165
Macros - Information About The Caller.................................. 166
Addressing messages ................................................... 167
Macros - System Information............................................ 167
Macros - System & Display Controls .................................... 167
Macros - Special Screen & Cursor Controls.............................. 168
╔════════════════════════════════════════════════════════════════════════════╗
║ Feathernet PRO! v1.10 Page xxii ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX D - Color Macros (@XCodes) .................................... 170
Charts & Examples...................................................... 170
APPENDIX E - Aborted Download Credits................................... 171
APPENDIX F - Script Questionnaire Instructions.......................... 172
Sample New User Script Questionnaire................................... 173
APPENDIX G - Private "Personal" File Transfers.......................... 174
APPENDIX H - Attaching Files To Messages ............................... 175
APPENDIX I - Manipulating The Default RIPScrip Screens ................. 176
What is RIP............................................................ 176
Where Can I Get RIPaint................................................ 176
Manipulating RIPScrip With An ASCII Editor............................. RD
FeatherNet's RIP menu/display file listing............................. RD
Samples................................................................ RD
OK, I Give Up - Solutions ............................................. 179
APPENDIX J - Converting From PCBoard.................................... 180
Conferences............................................................ 180
Userbase............................................................... 180
Filebase............................................................... 181
Doors ................................................................. 182
SUPPORT................................................................. 183
UPGRADES................................................................ 184
BUG REPORTS............................................................. 185
Software............................................................... 185
Documentation.......................................................... 189
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 1 ║
╚════════════════════════════════════════════════════════════════════════════╝
INTRODUCTION
Hello and Welcome to the Wonderful World of BBSing!
We at FeatherNet Software, Inc. would like to take a moment to thank you for
evaluating FEATHERNET PRO! v1.10. You will soon find that FEATHERNET PRO! is
a powerful, full-featured Bulletin Board System (BBS) that has been designed
to meet the needs of a wide range of both SysOp and user requirements. We at
FeatherNet Software, Inc. know that SysOps are a skeptical bunch, so we
created FEATHERNET PRO! in a manner and design to make use of a wide range of
existing utilities already in the Public Domain and Shareware arenas. You
will find as you read these pages that almost anything you wish to do is
possible with the FEATHERNET PRO! system, with the help of utilities included
with the package and those already found in the Cyber Space.
As the world of Telecommunications expands, the market expands with it, and to
survive in the market you have to have a number of things;
A Quality Product, which WE DO!
Great Service, which WE DO!
And last but not least, dedicated SysOps who use your product,
This is where YOU come in!
At this time, I would like to extend an invitation to you from all of us here
at FeatherNet Software to call us if you ever incur a problem. It is our
hope, that if you ever have any problem running our software, you pick up the
phone and call us immediately! We will help you to the best of our ability!
You may ask for us personally if you do not get help from one of our staff!
Ron Pierce - CEO/Pres. - Head Programmer, Ideas
David Place - VP. - Tech support, Marketing, Programming, Ideas
Sam Gudgel - VP. - Programming, Ideas
We are dedicated to you, the SysOp, without you we can not survive and become
a major contender in this game. We WANT to hear from you! Tell us what you
like, don't like, want to see, options you want, don't want, changes you want
made. While we can't promise you everything will be done, we will promise you
that we will look hard at every single item and see if we can fit into our
product. In case you didn't know, our rule is this, "If they want it, MAKE IT
AN OPTION!".
There are literally thousands of possible configurations and ways to customize
the FEATHERNET PRO! BBS System. You can NOT expect to learn everything there
is to know in a few short days, nor in a month or even two! Tricks to
manipulating files, inserting redirection commands and over-riding default
commands come with experience via trial and error. If there is a special
feature or function you are trying to figure out, there is a good possibility
that it can be accomplished. If you can't figure it out, give us a call or
leave a message on the FeatherNet HQ BBS in the appropriate Echo Mail
conference. It is a very strong probability another SysOp has managed to do
it and can tell you how. Talk with us and/or your fellow SysOps, we, and they,
can be a valuable resource.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 2 ║
╚════════════════════════════════════════════════════════════════════════════╝
While every precaution has been taken to provide you with the best possible
BBS program of today, it is possible that you MIGHT incur an occasional bug.
Our beta test team has tested and re- tested but with so many possible
combinations of equipment, memory handlers, operating systems, etc., it is
impossible to have tested EVERY conceivable combination. So, with all that in
mind, let's continue on with the installation of the hottest, most innovative
BBS program today.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 3 ║
╚════════════════════════════════════════════════════════════════════════════╝
INITIAL INSTALLATION
FEATHERNET PRO! comes with an automated setup program called INSTALFN.EXE.
This program will install the "Default" FEATHERNET PRO! BBS structure. This
structure includes all necessary files, directories and file attribute changes
(We strongly suggest in multi node applications that you run all .EXE and .BAT
files as READ ONLY). In addition it creates and modifies all the necessary
default .BAT files.
WE STRONGLY RECOMMEND THAT YOU USE THE "AUTOMATED" METHOD, however, for the
sake of documentation, we will outline the default structures.
THE AUTOMATED SETUP:
The automated setup of the FEATHERNET PRO! BBS System is quite simple and you
can have a board up and running in the matter of a few minutes if you follow a
few guiding steps outlined below.
First, choose a temporary directory to work from. We will assume that you
have probably done this as you are reading these directions, but for the sake
of it, we include this step. You should not choose a directory in which you
will have as your BBS HOME directory. A good choice would be \TEMP or \WORK.
Second, you must unzip the distribution package that you received into the
temp work directory, in most cases this will be a single file called
FNP###TD.ZIP (where ### is the version number). Inside this .ZIP file are
four (4) smaller .ZIP files labeled as FNP###[A-D].ZIP. UnZIP ONLY
FNP###A.ZIP!
Type: PKUNZIP FNP110A
You now have access to this file and the installation program, INSTALFN.EXE.
DO NOT UnZIP the B-D .ZIP files as the installation program will do that for
you. Unzipping these additional files in advance will cause an ERROR.
Third, PRINT OUT THE DOCUMENTATION. While the initial installation is quite
simple to accomplish, the full power and configurability of the FEATHERNET
PRO! BBS System can not be realized without reading the documentation and
learning about all it's various features.
It is important that you understand that there are THOUSANDS of configuration
options within the FEATHERNET PRO! System and you can not expect to learn
everything in the program in a night and can not expect to have an
installation program setup everything for you, in the exact format you want.
This installation program will setup a running version of the FEATHERNET PRO!
BBS System with minimal input from you using DEFAULT menus and configuration.
You will then have to edit and mold the BBS to your own tastes. Before
running INSTALFN we recommend that you read through the documentation
thoroughly and familiarize yourself with the various sections.
Before you run INSTALFN, you should know that it will ask you a few questions
which you can decide upon now. These questions are as follows;
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 4 ║
╚════════════════════════════════════════════════════════════════════════════╝
WHAT DRIVE WILL YOU BE RUNNING FeatherNet PRO FROM? WHAT DIRECTORY DO YOU WANT
FOR A BBS HOME DIRECTORY? WHAT IS THE NAME AND LOCATION OF YOUR TEXT EDITOR?
WHAT IS THE NAME AND LOCATION OF YOUR ANSI DRAWING PROGRAM?
TYPE: INSTALFN
This will bring up the first installation screen which will ask the drive and
directory you wish to use as the HOME BBS directory. The home BBS directory
is the directory where most all the BBS's executable files will be placed for
use by all nodes of the system and what all the sub directories will be built
off of.
Example: C:\FNET
Next, select "Y" to have the BBS HOME directory placed in your path statement
"SET NODE=1" added in to your autoexec.bat file. Your CONFIG.SYS will be
scanned to make sure you have enough file handles and environment space, if
not, they will be adjusted upwards.
Next, enter "Y" to INSTALL FEATHERNET PRO!
At this point, INSTALFN will create the required sub directories under your
specified HOME directory and move the appropriate files to each of them. It
will also modify your SFN.BAT (the SFN batch file is the main batch file to
Start FEATHERNET PRO!) file to show the correct paths.
When done, INSTALFN will ask you if you wish to run FNETSM, the system manager
or Quit, it is suggested that you run FNETSM at this time and finish the
initial setup.
Once in FNETSM you will be prompted for the PATH and FILENAME of your TEXT
EDITOR.
Example: C:\QED\QE.EXE
Next it will prompt you for your ANSI EDITOR such as TheDraw.
Example: C:\TDRAW\THEDRAW.EXE
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 5 ║
╚════════════════════════════════════════════════════════════════════════════╝
Once this is done you will be switched immediately into FNCFG the FeatherNet
configuration editor. There is a detailed section in this manual on FNCFG,
but for now you need to worry about a very few things. You should quickly
answer the questions in the General Information Screen 1 about the BBS name,
the SysOp name and make sure you enter your registration number or 000 if you
are not registered.
For now you can press <PgDn> TWICE which will bring you into the MODEM, NODE
and SUBSCRIPTION Information Screen. Here you need to input your modem
initialization string. If you are not sure about this step, please see the
section in "SysOp Utilities" under MODEMSET. Answer the FOSSIL, COMM PORT,
BAUD RATE, and LOCKED PORT questions. Next, skip to the bottom of the screen
and answer the NODE questions, for now we will assume you are setting up node
#1. If you are using a network or another Multi tasked you must answer "Y" to
that question. If you are running a Test Drive or Multi Line Registered
package you MUST have SHARE loaded in your AUTOEXEC.BAT or CONFIG.SYS file.
For now, that is all that must be done here. Press <ESC> to the MAIN FNCFG
menu then <ESC> once again where it asks if you want to quit, answer "Y" here
and MAKE SURE YOU HIT "Y" WHEN IT ASKS IF YOU WANT TO SAVE YOUR INFORMATION!
When done, [PRESS ANY KEY]
Re-BOOT your computer at this time for all changes to take place.
Once the re-boot has taken place you should change to your node 1 directory
[CD\FNET\NODE1] and type FNETSM. Once in FNETSM press "A" or <ENTER> to EDIT
USERS. RECORD ONE MUST BE THE SYSOP! Please fill in your information here
making sure to hit F2 to fill in the second page of information. When
finished, press <ESC> and then <ESC> or "Q" to return to the main menu of
FNETSM and then press "B" or Arrow Down to CREATE USER INDEX FILES and press
<ENTER>. Press <ESC> to leave FNETSM.
Your system is almost ready to run. There are a few more items that you need
to complete first.. If you do not have a registered copy of DSZ you need to
read the DSZ DOCS provided for you and register it. Some of the file
protocols defined will not work until it is registered. You can remove those
protocols by editing the file FNETPROT.DAT in the \FNET\FNSYS directory and
defined in this manual. Next you need to go to the \FNET\ULT directory and
setup ULTester, the FEATHERNET PRO! Upload processor. Instructions for this
are provided in the SysOp utilities section of this manual. Once this is
finished, you must then configure your QWK Mail delivery system, FNMail.
Instruction for configuring FNMail are also provided in the SysOp Utilities
section of this manual and the files are placed in the directory \FNET\FNMAIL.
After you have completed these steps you are finished! Your board, while not
completely setup for your particular style, is ready and can be placed on-line
to accept calls! (Make sure SHARE is loaded if needed!)
Go to your \FNET\NODE1 directory and type: SFN
There you go. You may log on with the SysOp logon command. (Not too hard,
was it!)
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 6 ║
╚════════════════════════════════════════════════════════════════════════════╝
IF YOU ARE RUNNING MULTINODE! Once all the files have been placed in their
respective directories you will need to change to the FEATHERNET PRO! "Main"
directory (\FNET) and change all the .EXE files to "read-only". DO NOT set ALL
files to READ ONLY as your BBS will NOT RUN if you do so!
This is accomplished using the DOS command "ATTRIB".
EXAMPLE: ATTRIB +R *.EXE
For more information on the ATTRIB command, please refer to your DOS manual.
You are now ready to configure your BBS!
DETAILED INSTRUCTIONS ON "FNCFG CONFIGURATION" FOLLOW IN THE NEXT SECTION.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 7 ║
╚════════════════════════════════════════════════════════════════════════════╝
A FEW NOTES ON YOUR BBS DISPLAY SCREENS
Edit all your ASCII files with a simple text editor and ANSI files with an
ANSI editor or drawing program. A good ANSI editor is TheDraw v4.60+ which
can be found on most computer bulletin boards systems and supports FEATHERNET
PRO! color Xcodes (Use the PCB@ code selection).
All default RIP menus are soft coded with @BBS@ codes and will automatically
place your BBS name in the appropriate places so that no initial editing is
required.
RIPscrip Graphics Note: RIP graphics will immediately be available on your
system with the default menus and display files. You should make sure to
allow access to the file "FNETICN.ZIP" which was included in your package.
Your BBS Name will be automatically be inserted into your RIP Menus, HOWEVER
there are some menu's which CAN NOT be setup for you, and you should edit
them, following the directions in the 'Editing RIP menus' section of these
docs, or take them off-line until edited (ANSI in Full Screen RIP mode will be
displayed in their place). These menu's and/or display files are; QUESR (Menu
of Questionnaires available), DORMR (Menu of DOORS available), CLR (Menu of
Conference areas available), DIRMR (Menu of File areas available), and BLTR
(Menu of Bulletins available).
NOTE: TheDraw(TM) does NOT support FEATHERNET PRO! @codes@ but you will find
that a POP UP TSR called FNET@.EXE has been included with your FEATHERNET PRO!
package and with it you can insert the correct @codes@ as you make your ANSI
or ASCII screens.
Files may be "chained" by adding a "%FILENAME" to an existing file. When
FEATHERNET PRO! sees this syntax is will immediately open the file and display
it's contents. A prime example of this is in the display file DIRxx which
gives a listing of a file directory's files. At the top of each listing is a
"HEADER" which may display information about the contents, type of files in
the directory, and information on which column is the filename, the date,
size, description, etc. Instead of having three DIRxx files with three
different headers which not only is redundant, but also can use up large
amounts of disk space (One of each of ASCII, ANSI, and RIP) you could have one
DIRxx file with the header of "%C:\FILES\DISP\HDR-STDR" (the R would denote
RIP). Next you would simply create 3 small header files of each type and they
will be amended to the top of your DIRxx file when called. Another instance
of this might be to create a HELLO1 file in which you want 3 screens. On the
first three lines you could put;
%C:\DISPLAY\NEWFILES @WAIT@
%C:\DISPLAY\NEWCDROM @WAIT@
%C:\DISPLAY\READRULZ @WAIT@
This would call each one of your display files and place a "PRESS ENTER TO
CONTINUE" after each is displayed. Simple and easy!
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 8 ║
╚════════════════════════════════════════════════════════════════════════════╝
Another example of using the redirection command '%PATH/FILENAME' is in the
FEATHERNET PRO! Prompt Editor. When you enter the prompt editor (More on this
in the SysOp Utilities section) you may replace a prompt with a DISPLAY FILE
by simply removing the default prompt and placing the command line:
%DRIVE\PATH\FILENAME_TO_DISPLAY i.e.: %D:\FNET\DISP\LOOKHERE
Thus, when the system went looking for the prompt that you redirected and saw
the '%' signal, it would look at the filename specified and display that file
instead! This in itself make for a POWERFUL customization feature.
In the making of your MENU, DISPLAY, and BULLETIN menus/display files, you do
not have to make separate ASCII/ANSI files. To get away from two separate
files, simply save all files with @X color or ANSI codes and save them WITHOUT
the "G" at the end of the file name. FEATHERNET PRO! will strip out the @X or
ANSI color codes if the caller is not in ANSI mode or has ANSI turned off. The
only time you must use separate files for ASCII/ANSI is if you wish to have a
straight TEXT ASCII file with NO upper ANSI at all (No boxes, etc.). In ALL
cases you MUST have a separate file for all RIP display files. All RIP files
must also end with an "R". Display and Menu files MUST NOT have any extension
or they will not display properly.
In the conference configuration screens you will notice that at times a RED
BAR appears at the bottom of the screen with information. There are two
different bars, one for display files and one for CONTROL files. The first one
will allow you to PRESS <F2> to enter your pre-defined TEXT EDITOR and edit a
TEXT menu or display file or PRESS <F3> to enter your pre-defined ANSI EDITOR
and edit a ANSI menu or display file. (You MUST pre- define these editors
within FNETSM. If you ran the INSTALFN program this step has already been
accomplished). The second one only has the option PRESS <F2>, which will
allow you to setup files such as your BULLETIN LIST and DOOR LIST files.
THESE FILES ARE CONTROL FILES AND ARE VERY IMPORTANT! WATCH CAREFULLY AS SOME
OF THESE FILES ARE MULTI-LAYERED and ALL SCREENS MUST BE ATTENDED TO FOR
PROPER OPERATION!
A full listing of file types, structures, editability, and purpose can be
found in the FILE STRUCTURES section of this document.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 9 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - The FEATHERNET PRO! Configuration Editor
PRELIMINARY NOTES:
FNCFG.EXE is the Main FEATHERNET PRO! configuration editor. With the
configuration editor you can modify the contents of the SRCONFIG data file
which MUST reside in each and every node directory. You may access FNCFG.EXE
from any NODE directory, from the call waiting screen, or from inside the BBS
locally or while a user is on-line.
To access the configuration editor you may:
In DOS. Type : FNCFG from any NODE directory
Inside The BBS Press : F6 then: 2
At the Call Waiting Screen : FNCFG
FNCFG.EXE must be in your PATH. The same sub directory which contains your
FNCFG.EXE file must also contain the files FNCFG.HLP and FNCFG.NDX to operate
properly.
NOTE: Help is available from ANY area and/or prompt by Pressing <F1> within
FNCFG.
Please remember, there are thousands of configuration possibilities with the
FEATHERNET PRO! BBS System and it can get somewhat confusing sometimes.
Please take some time and read though this manual before you start
configuring. If you have trouble in one spot, make a note and skip on and
return later, sometimes it will make more sense then. If you still have
trouble with a certain concept or aspect of the configuration or feel the
documentation is not clear on what you need to know, leave a message on the
FeatherNet HQ BBS or give our technical support line a call and we'll help you
out.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 10 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Main Configuration Menu
Starting FNCFG will bring you to the MAIN FNCFG menu.
You can move around on this screen by using your keyboard arrow-up,
arrow-down, arrow-left and arrow-right keys. Then press <ENTER> to make your
selection. You may also simply press the corresponding letter for your
choice. Pressing the <ESC> key will start the EXIT process from FNCFG.EXE
which will be covered at the end of the FNCFG section.
The easiest way in which to learn your way around the configuration editor is
to go through all the screens and options while reading this documentation.
The documentation will take you screen by screen and explain in detail all
choices. You may also request and receive full help by pressing the <F1> key
at any menu option.
NOTE: Please read the UPDATE.DOC file on the FEATHERNET PRO! diskette for any
last minute changes in the software. This file may contain important
information on changes that were not possible to insert into the documentation
before it was compiled!
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 11 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Conference Information - Selection
CONFERENCES AVAILABLE: [0 - 4095]
This area simply lets you know how many conferences you have currently
configured which may be edited. Version 1.10 increases the maximum number of
conferences from 1024 to 4096. Enter the # of a Conference to edit. This
will allow you to edit an existing conference area. You may EDIT any
conference with a number within these limits. Conference 0 is your MAIN or
DEFAULT conference. When you choose ADD a Conference, it uses your CONFERENCE
0 or DEFAULT directory as a model for default information.
Enter [A] to add a conference (maximum conferences is 4096) to those already
configured. You will have to add each conference separately that you wish to
use. As stated above, when creating a new conference, the default information
is taken from your CONFERENCE 0 information. Please also see CONFUTIL in the
SysOp Utilities Section for adding, deleting, or switching around conferences.
Enter [L] to list conference information. This will give you a condensed
listing of all your configured conference areas and their paths. Information
provided by this option includes Conference Number, Conference Name, Security
level to access, Private area flag, Echo flag information, and path to the
message data files.
Enter [Q] to Quit. Quits back to the Configuration Editor's main menu.
In some cases, like when you add an entire Echo Mail network, it is faster to
modify and save settings in CONFERENCE 0 for the new network, create all your
new conferences, and then change your conference 0 settings back to normal.
You may also wish to note the COPY command in CONFUTIL which can make dealing
with mail networks much easier!
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 12 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Conference Setup - Page 1
CONFERENCE NAME:
Enter the name of the conference. It may be up to 25 characters in length.
Try to be specific enough to let your users know what the conference is all
about. You should not name your conferences: CONF0, CONF1, etc.
EXAMPLE: Assembly Programming
Keep in mind that you may use a conference header display file (explained
later) which will display as a user joins the conference. In the conference
header display file you may list the rules of the conference or any other
pertinent information. Each conference may also use a separate MAIN, MESSAGE,
and FILE menu which can make each conference just like a separate TOPIC
specific BBS. More on this later in the CONFERENCE SETUP #2 screen.
CONFERENCE #:
Simply shows the conference you are currently editing.
ALLOW ALIASES IN THIS CONFERENCE:
Y = Allow users to use "aliases" within this conference. If aliases are
allowed, messages will be addressed as from the user's Alias Name (asked for
from the user at initial log on to the system and later editable with the [I]
command from the main BBS command prompt). If a user enters a message in a
conference which allows aliases and he/she has no Alias Name on file, the
user's real name will be used in the "From" field. The user also has the
option of saving messages with the 'SR' (Save with Real name) command.
N = Do not allow aliases to be used in this conference. Most echo mail
networks *DO NOT* allow aliases or restrict them to certain echoes..
SEE ALSO: Stealth Mode in FNETSM
NOTE: Users may still save the messages entered in an ALIAS conference using
their REAL NAME. At the end of the message when it presents the SAVE OPTIONS,
if they chose "SR" (Save with Real name) it will do this.
CO-SYSOP'S NAME: Enter the name of the Co-SysOp for this conference. The
significance of the name is that all mail addressed to "SYSOP" in THIS
conference area will be automatically re-addressed to this Co-SysOp's name.
NOTE: A person (if anyone) chosen as the Co-SysOp for this conference must
have his or her Co-SysOp bit flag for this conference turned on in FNETSM or
by using the internal user editor [I] from the main BBS command area (Must
have SysOp access to use the [I] command). Leaving this item BLANK disables
the re-addressing of any mail from the SysOp to the Co-SysOp and will write
YOUR name in the message instead. See also; SYSOP'S NAME and USE SYSOP'S REAL
NAME later in the GENERAL INFORMATION, PART ONE section of FNCFG and this
documentation.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 13 ║
╚════════════════════════════════════════════════════════════════════════════╝
MESSAGE FILE PATH & FILE NAME: Enter the complete file path and file name for
this conference's message database.
EXAMPLE: C:\FNET\CF0000\MSGS
NOTE: The message file name MUST NOT have a file extension. There is an
accompanying index file created with each message file. It has a ".NDX" file
extension appended to the name of the message file.
DO NOT name the message database name the same thing you name the conference
directory. This is a limitation imposed by SOME operating systems such as
DOS.
EXAMPLES: C:\FNET\CF0000\CF0000 would be INCORRECT
C:\FNET\CF0000\MSGS would be ACCEPTABLE
You may place all your message base files in the same directory as long as you
have different message area names. However, if you are carrying, or planning
on carrying Echo Mail, check your TOSSER/PACKER software, some of these
packages require you to have a separate directory for EACH and EVERY echo mail
conference area. In some cases, echo mail tossers create CRC check or DUPE
files and for this reason you must have a separate directory for each and
every message conference. While in some cases you may have all message bases
in one sub directory, it is our strong recommendation that you do use a
separate directory for each conference.
CONFERENCE INTRODUCTION FILE: Enter the full path & name of the conference
introduction file. The conference "introduction" file is displayed each and
every time a user [J]oins a conference. This file is not required and is
offered as a configuration option to assist users in understanding what is
available in the specific conference joined. This may also be used to display
the 'rules' of the echo. Each conference may have a unique "introduction"
file. The filename should be 7 or fewer characters to allow the adding of the
"G" (graphics version) or "R" (RIPscrip version) to the filename to display an
ANSI or RIP version to callers in graphics mode. This file may be shared
between conferences but it is suggested that each conference have it's own
descriptive welcome header describing it's contents and rules.
EXAMPLE: C:\FNET\CF0000\INTRO
NOTE: There are no extensions on DISPLAY or MENU files. Placing an extension
on these files will cause FEATHERNET PRO! to ignore them.
READ SECURITY LEVEL:
Enter the security level required to read messages in this conference (0-255).
This setting along with the USER'S security level allows you to control access
to conferences. Also see PUBLIC and PRIVATE conference flags later in this
section.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 14 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONFERENCE'S ATTACHMENT DIRECTORY:
Enter the directory path where you want file attachments to messages in this
conference to be placed after uploading. Leaving this BLANK disables file
attachments for this conference. This option, if enabled, allows a user to
enter a message, then upload a file to the message. When another user reads
the message, they will then be asked if they wish to download that file which
they may answer yes or no to.
This attachment directory may be shared between conferences.
EXAMPLE: C:\FNET\CF0000\ATTACHED\
REPLY SECURITY LEVEL:
Enter the security level required to reply to a message after reading it
(0-255). This setting along with the USER'S security level allows you to
limit a user to being able to read messages but not being able to reply to a
message after reading it.
WRITE SECURITY LEVEL:
Enter the security level required to enter a new message (0-255). This setting
along with the USER'S security level allows you to control the privilege of
writing messages. You may also force the entered message PRIVATE by toggling
the PRIVATE conference flag.
RECEIPT SECURITY LEVEL:
Enter the security level required to request a return receipt (0- 255). This
setting will allow a user to request a receipt be sent via mail upon the
reading of the subject message by the intended recipient.
CONFERENCE UPLOAD DIRECTORY SECURITY LEVEL (PUBLIC Uploads):
Enter the security level required to VIEW, SEARCH, and DOWNLOAD files from
within the PUBLIC UPLOAD file directory and to list the files and descriptions
of these files. The security level may be from 0-255.
CONFERENCE UPLOAD DESCRIPTION FILE (PUBLIC Uploads):
Enter the path and name of the file to contain the descriptions for new PUBLIC
uploads in this conference. These files are available for downloading if a
user's security level is sufficient. This directory listing file may be
shared between conferences. You may want to set this security level higher so
that UPLOADS may be scanned by you before being made public to avoid
'commercial' files from being downloaded before you catch them.
EXAMPLE: C:\FNET\CF0000\PVT
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 15 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONFERENCE UPLOAD FILE PATH (Private Uploads):
Enter the PRIVATE UPLOAD file path. This is the DOS directory which new
PRIVATE uploads will be kept in after being uploaded.
NOTE: New files are RECEIVED in the NODE work directory then moved to this
PRIVATE UPLOAD directory after being tested/verified.
EXAMPLE: C:\FNET\FILES\CF0000\UPLPV\
CONFERENCE UPLOAD DESCRIPTION FILE (PRIVATE Uploads):
Enter the path and name of the file to contain the descriptions for new
PRIVATE uploads in this conference. These files are available for downloading
if a user's security level is sufficient. This directory listing file may be
shared between conferences.
EXAMPLE: C:\FNET\CF0000\PVT
BULLETIN MENU FILE:
The Bulletin display file will show your users the available bulletins on your
system. Enter the path and name for the Bulletin Menu file for this
conference. The name should be 7 letters or less to give room for a "G" or
"R" for ANSI and RIP versions. You may share the same file for both ASCII and
ANSI versions if you use wish. The menu MUST correspond with your conference
bulletin list file which is discussed next. Each conference may have it's own
Bulletin Menu file.
EXAMPLE: C:\FNET\CF0000\BLTM
BULLETIN LIST FILE:
The Bulletin Listing file is the file the system uses to determine the
bulletins you have configured to show your users and where they are located.
Enter the path and name for the Bulletin Listing file for this conference.
EXAMPLE: C:\FNET\CF0000\BLT.LST
This file must be edited from here. And each bulletin your wish to present to
your users must be entered separately.
WHILE ON THIS SELECTION PRESS <F2> TO SETUP YOUR BLT.LST FILE.
Each conference has it's own bulletin listing file. In this file you place
the path and display file name for each bulletin in the conference. Each path
and bulletin name is numbered to correspond to the conference bulletin menu
discussed previously. You will notice at the bottom of the screen that there
are options to insert, delete, or repeat a line in the listing.
The bulletin list file should normally be on your server (if operating in a
network environment) so that all nodes may address it, but may be copied over
to each node if you wish. However, if you chose the node method, (if
bulletins change) you will have to update each and every node's bulletin list
file. Each conference may have it's own bulletin menu and listing file.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 16 ║
╚════════════════════════════════════════════════════════════════════════════╝
BULLETIN PATH AND FILENAME:
Enter the path and name of the bulletin for this entry number. The actual file
name should be limited to 7 or fewer characters to permit appending a "G" or
"R" to the filename for an ANSI or RIP bulletin display. No extension can be
used with the filenames.
These paths and bulletin files may be shared between conferences.
EXAMPLE: C:\FNET\CF0000\BLT1
CREATING A BULLETIN:
A bulletin can be as simple as an ASCII text file or you can create ANSI or
RIP screens to display your information. When you finish making your bulletin
display file, enter the path and bulletin filename into the bulletin list
editor (discussed previously). The line that you enter this information on
will have a number, this is now the call number for the bulletin. You should
at this point edit your bulletin menu to reflect this new choice.
You may use @X color codes and @INFO@ codes in your bulletin files.
WHEN DONE PRESS <ESC> TO QUIT AND THEN SAVE YOUR INFORMATION.
YOU WILL THEN BE RETURNED TO THE CONFERENCE CONFIGURATION SCREEN.
SAVING THE BULLETIN CONFIGURATION FILE:
After you are done editing the configuration file, press the <ESC> key and it
will ask you if you want to save the changes you have just made, if any. This
option defaults to "NO". Press <ENTER> if you do NOT want to save the changes
otherwise enter a "Y" then the press <ENTER> to save all changes. After you
select one option or the other you will be returned to the Conference
Configuration Screen.
DOOR MENU FILE:
This file displays to the caller the DOORS available to him/her. Enter the
path and name for the Door Menu file for this conference. The actual file
name should be limited to 7 or fewer characters to permit appending a "G" or
"R" to the filename for an ANSI or RIP display. You may have a separate Door
Menu for each conference.
This file may be shared between conferences.
EXAMPLE: C:\FNET\CF0000\DORM
DOOR LIST FILE:
Enter the path and name for the Door list file for this conference. The
DOOR.LST file provides a list of all this conference's DOORS. Each conference
may have a separate DOORS.LST file although all or some of your conferences
may share a single DOORS.LST file between themselves if no discrepancies
exist.
The file consists of eight fields: Filename, Password, Security, Logon,
DOOR.SYS, Shell Type, Path, and RIPscrip Compatible. Below this is a sample
DOORS.LST screen and below that is a description of each.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 17 ║
╚════════════════════════════════════════════════════════════════════════════╝
EXAMPLE: C:\FNET\CF0000\DOORS.LST
WHILE ON THIS SELECTION PRESS <F2> TO SETUP YOUR DOORS.LST FILE.
DOOR BATCH FILENAME:
This is the name of the DOOR's "RUN FILE" or "CALL FILE". This file should
NOT contain any extension.
EXAMPLE: MAIL
The name entered here corresponds with the exact name of the DOOR's control
file on disk. To further explain this, this is the DOOR's .BAT file WITHOUT
the .BAT extension! The file may not be an .EXE or .COM file. This should
contain all information needed to run the door as explained in each separate
DOOR.
For further information on setting up the CALL FILE, please see the specific
program's setup instructions. Each entry in this list is numbered and should
correspond to the DOOR MENU discussed earlier.
In the example, "MAIL" would be DOOR MENU choice "1" but could also be called
from any menu by the user by typing "MAIL" at any of the menu prompts (MAIN,
FILE, or MESSAGE). FEATHERNET PRO! would then take the file "MAIL" and copy
it to a batch file called "DOOR.BAT" and run it. When the program finishes, it
will then return to FEATHERNET PRO! and delete the file "DOOR.BAT". The
location of the file is determined by your answer to the Path question. When
blank, the NODE directory is assumed to contain your CALL FILE.
These door RUN or CALL files may be shared by all nodes but caution should be
taken when giving access to doors by multiple nodes. Not all doors will allow
multi node access. Some single node doors will lock up or corrupt data if not
protected from access by another node while in use.
NOTE: The RUN file is a .BAT file WITHOUT the .BAT extension! FEATHERNET PRO!
uses the filename that you enter here in the DOORS.LST file when creating a
DOOR.BAT file which is actually used in running the DOOR.
DOOR PASSWORD:
If a password is entered in this field then the caller must know the password
in order to open this door. If the field is blank then no password is
required.
This option may be left blank. If the option is blank, it will be ignored.
The DOOR PASSWORD works in conjunction with the DOOR SECURITY. Even if the
user has the password, but his security level is too low, he will not gain
access.
See DOOR SECURITY LEVEL (TIP) for more information. This option is presented
to restrict access to some doors in which certain users should not have access
for one reason or another. CD-ROM doors or Adult Doors are two good examples.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 18 ║
╚════════════════════════════════════════════════════════════════════════════╝
DOOR SECURITY LEVEL:
Enter the security level required in order for a caller to open this door (0 -
255).
A user must have this security level or HIGHER to access this door. This
option works in conjunction with DOOR PASSWORD. Each DOOR has it's own
security level requirements as a SysOp may want to restrict usage of certain
doors by security level.
TIP
You may want to put ADULT or security level restricted DOORS in their own
conference and DOORS.LST file so that you do not have users leaving you mail
asking why they don't have access to certain doors and younger users wanting
access to adult files, etc. What they can't see can't intrigue them!
AUTO LOGON DOORS:
When a caller logs on to FEATHERNET PRO! the software will check the DOORS.DAT
file for any Auto Logon Doors which are specified by answering "Y" under this
column. A user having a security level that matches EXACTLY that which is
specified under the Security Level column will then be sent into the door
automatically as part of the logon process.
NOTE: The security level MUST MATCH the users security level EXACTLY or else
the user will not be sent into the door. This is beneficial to SysOps who
want to FORCE new users into a door for a particular logon process (Call back
verifier, or what have you). If you wish to have more than one security level
sent into the same door, you will have to setup each security level call
separately.
This door executes after the HELLO, NEWS, and SECURITY specific files are
displayed and before the main menu is reached.
Answering "N" to this tells FEATHERNET PRO! this is a regular door to be
accessed by the choice of the user from the DOOR MENU by number or another
menu with the "Call Filename".
NOTE: If you wish ALL security levels to be sent into a particular door you
may use the $$LOGIN.BAT file. See $$LOGIN.BAT and $$LOGOFF.BAT under SYSTEM
BATCH FILES.
CREATE DOOR.SYS FILE:
Enter a "Y" if you want FeatherNet to create a "DOOR.SYS" file. Most door
programs will use a DOOR.SYS file. If you select "N" a PCBOARD.SYS door drop
file will be created instead of a DOOR.SYS drop file.
NOTE: FEATHERNET PRO! uses the advanced DOOR.SYS which will place a RIP
notation in the DOOR.SYS file for use with newer doors. Please also note that
FEATHERNET PRO! will NOT do this, even if the user is in RIP mode, if you do
not specify the door as using RIPscrip.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 19 ║
╚════════════════════════════════════════════════════════════════════════════╝
SHELL / SWAP TO DOOR:
This option gives you a choice in how you want FEATHERNET PRO! to handle how
it relinquishes control to your DOOR programs. You have three choices in this
matter and it basically comes down to how your system hardware is configured,
how much system memory you have, and how you handle that memory with extended
and expanded memory utilities such as EMM386 and QEMM. FEATHERNET PRO! will
use whatever type memory available during a swap, whether EMS, EEMS, XMS, or
DISK. Since we have no idea how each individual SysOp will handle this on
his/her particular system, we have made available a number of choices. In
most cases choosing "Y" and SHELLing out to the DOOR will be appropriate and
give you the best results.
Y = Yes, shell out to the DOOR (gives faster return from door) S = SWAP
FeatherNet out during the shell N = Do not shell, exit FeatherNet completely
NOTES: The DOOR file should end with a call to SFN.BAT if this switch is set
to "N" and should NOT end with SFN.BAT if set to "Y" or "S". In other words,
when you SHELL, FEATHERNET PRO! is already loaded so the door file need not
reload it, but when not shelling the software must be reloaded in order to
continue. See your DOOR's documentation for setup configuration for your door
under DOOR.SYS BBS, FEATHERNET PRO! BBS, or as a last resort, PCBOARD.SYS
(DOOR.SYS or PCBOARD.SYS).
PATH TO DOOR BATCH FILE: Enter the path to the door "CALL FILE". FEATHERNET
PRO! will look in the specified directory for the door batch file if you enter
a path. Otherwise, the NODE directory will be searched for the door "CALL
FILE". Remember, the CALL File MUST NOT end with any filename extension (i.e.:
.BAT).
EXAMPLE: C:\FNET\DOORS\FNMAIL\
RIPscrip SUPPORTED BY DOOR:
This option allows FEATHERNET PRO! to determine whether it should modify the
DOOR.SYS file before running a DOOR. This option should be used with care!
You may only use this option if you set the "DOOR.SYS" option to "Y". You may
also only use this option if the DOOR supports RIPscrip graphics.
What this option does is checks to see if a user is in RIP graphics mode, if
he is, the program checks to see if this option is set to "Y", if it is, it
allows the "RIP" identifier to go through in the DOOR.SYS file. If this
option is set to "N" it inserts a "GR" (meaning ANSI) in the DOOR.SYS file, if
the user is in ASCII or NON-ANSI mode, a "NG" is passed, thus over-riding the
fact the user is in RIP mode. This allows older doors (such as TradeWars 2002
v1.0+) to run that do not know how to handle the "RIP" identifier in the
DOOR.SYS file.
Y = This door directly supports RIPscrip graphics. N = This door does not
directly supports RIPscrip graphics.
WHEN DONE PRESS <ESC> TO QUIT AND THEN SAVE YOUR INFORMATION.
YOU WILL THEN BE RETURNED TO THE CONFERENCE CONFIGURATION SCREEN.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 20 ║
╚════════════════════════════════════════════════════════════════════════════╝
SAVING THE DOOR CONFIGURATION FILE:
After you are done editing the configuration file, press the <ESC> key and it
will ask you if you want to save the changes you have just made, if any. This
option defaults to "NO". Press <ENTER> if you do NOT want to save the changes
otherwise enter a "Y" then the press <ENTER> to save all changes. After you
select one option or the other you will be returned to the Conference
Configuration Screen.
MENU FOR DIRECTORY LISTING:
Enter the path and name of the ASCII/ANSI/RIP file for this conference's
directory listings. This display file contains the listing of file
directories available in this conference. The filename should be limited to 7
characters or less to allow for the graphics identifier to be added (a "G" or
"R" for ANSI or RIP). This file may be shared between conferences.
EXAMPLE: C:\FNET\CF0000\DIRS
DIRECTORY LISTING CONTROL FILE FOR THIS CONFERENCE (DIR0.LST):
Enter the Directory listing file name to use with this conference Assigning a
directory listing file to a conference enables file transfers within a
conference. If no DIR.LST file exists there can be NO file transfers from
that particular conference. Users with proper security level may use the "F"
command after joining the conference and perform file transfer functions on
the files available.
EXAMPLE: C:\FNET\CF0000\DIR.LST
Each and every conference may have it's own directory listing file. In this
file the SysOp places the path and filename of DIRxx file that list the files
available for download. It also assigns a DOS directory where the files
exist, the security level required to access each area, and the category name
for each area.
NOTE: There are TWO sections in the DIR.LST editor. Press <F2> once to get to
the first page, then press <F2> again to access the second page of the DIR.LST
editor.
WHILE ON THIS SELECTION PRESS <F2> TO SETUP YOUR DIR.LST FILE.
DIRECTORY TEXT FILE NAME AND PATH:
Enter the path and name of the file which will contain the descriptions for
the files available for downloading from this entry. This sometimes referred
to as the DIRxx file.
EXAMPLE: C:\FNET\CF0000\DIRS\DIR001
This file contains the files available for download information. This
information includes the FILENAMES, FILE DATES, SIZE, and DESCRIPTIONS of the
files.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 21 ║
╚════════════════════════════════════════════════════════════════════════════╝
HARD DISK SUB-DIRECTORY:
This represents the drive and sub directory on your hard drive (or CD-ROM
drive) where the files in this DIRxx file can be found. The directory in
question holds the physical files described in the corresponding DIRxx file.
This is the directory of files that will be searched if a user tries to
download, view inside and archive, or check file integrity on a file listed in
your DIRxx listing.
EXAMPLE: C:\FILES\CF0000\DL001
NOTE: If a file is NOT listed in the DIRxx file but DOES exist in a directory
path and the user has both the FILENAME and the required SECURITY to access
the file directory, he may download that file.
IMPORTANT!
See DLPATH.LST, INDEX FILE, and SLOW DRIVES for more information on CD-ROM
setup and use with FEATHERNET PRO!
FILE DIRECTORY SECURITY:
This is the security level required to access this file directory. FEATHERNET
PRO! imposes a security level restraint on EACH file directory listing as well
as each download path. A user must have this security level or HIGHER to gain
access to VIEW, DOWNLOAD, or SEARCH within the directory. You may enter a
number between 0-255.
WHILE INSIDE OF THE DIR.LST EDITOR PRESS <F2> TO SETUP THE SECOND
PAGE OF THE DIR.LST FILE.
CATEGORY OF DIRECTORY:
Enter a "TITLE" for this directory. It is normally related to the type of
files included and available for download within it. When a user does a global
file search within this conference these category names will be displayed so
that the user can determine where the file was found and what areas were
searched.
EXAMPLE: FeatherNet Software
NOTE: This does NOT replace the directories listing display file.
WHEN DONE, PRESS <ESC> TO QUIT AND THEN SAVE YOUR INFORMATION.
YOU WILL THEN BE RETURNED TO THE CONFERENCE CONFIGURATION SCREEN.
SAVING THE DIRECTORY LISTING CONFIGURATION FILE:
After you are done editing the configuration file, press the <ESC> key and it
will ask you if you want to save the changes you have just made, if any. This
option defaults to "NO". Press <ENTER> if you do NOT want to save the changes
otherwise enter a "Y" then the press <ENTER> to save all changes. After you
select one option or the other, you will be returned to the Conference
Configuration Screen.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 22 ║
╚════════════════════════════════════════════════════════════════════════════╝
ALTERNATE DOWNLOAD PATH LISTING FILE (DLPATH.LST):
Enter a path and filename for this entry. This is a file which contains hard
drive or CD-ROM directories to search if a file is not found in a specified
directory in your DIR.LST file.
Each file area in each conference has a default physical file directory
defined in your DIR.LST. You can assign other physical paths to search here
in the ALTERNATE download path listing.
The SysOp may use the ALT functions at the bottom of the screen to delete,
insert, or repeat lines in the editor.
EXAMPLE: If a user does a search in the file directory C:\FILES\CF0000\DL003\
for a file called ANSIART.ZIP and the file is not found and you have ALTERNATE
paths defined, FEATHERNET PRO! will then search each and every alternate path
for the file name.
NOTE: As you might guess, this could be a VERY SLOW process if you include
CD-ROM directories in your alternate download path listing file. For this
reason FEATHERNET PRO! has a second alternate file listing type called
INDEXING. If you run CD-ROM drives you should definitely read and use the
sections on FILE INDEXING and SLOW DRIVES.
WHILE ON THE ALTERNATE D/L PATH LISTING OPTION PRESS <F2> TO SETUP THE
DLPATH.LST FILE.
IMPORTANT!
If you use the INDEX file discussed later in this document you MUST include
ALL PATHS which appear in your DIR.LST file here in your DLPATH.LST! Failure
to do this will cause FEATHERNET PRO! to not find files which are requested by
the user if on your hard drive. See the INDEX configuration section for more
information on this.
ALTERNATE DOWNLOAD PATH:
This must be a directory on your hard drive or a CD-ROM. FEATHERNET PRO! will
search this directory path for files if a user's security level is sufficient.
EXAMPLE: C:\FNET\CF0000\ALT001\
SECURITY LEVEL FOR DOWNLOAD PATH:
Enter the security level required to access files in this path. The security
level must be 0-255. This controls access to this path for any file functions
(i.e. download, archive manipulations, reading text file).
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 23 ║
╚════════════════════════════════════════════════════════════════════════════╝
ADDITIONAL NOTES ON THE ALTERNATE DIRECTORY LIST:
Ensure that the alternate download path is protected by an adequate security
level. It is anticipated that the DLPATH.LST file will be small, if used at
all. The major reason to use this file is if the SysOp has an extremely large
amount of files available and wants to group them in separate directories on
his hard drive or limit the number of files per single sub directory on his
hard drive for faster searching or location. Again, it should be noted that
the use of the DLPATH.LST file with CD-ROM drives will SLOW your system down
to a CRAWL! Please see the File INDEXING and SLOW DRIVES sections for further
important information on running CD-ROM drives with FEATHERNET PRO!
WHEN DONE PRESS <ESC> TO QUIT AND THEN SAVE YOUR INFORMATION.
YOU WILL THEN BE RETURNED TO THE CONFERENCE CONFIGURATION SCREEN.
SAVING THE ALTERNATE DOWNLOAD DIRECTORY CONFIGURATION FILE:
After you are done editing the configuration file, press the <ESC> key and it
will ask you if you want to save the changes you have just made, if any. This
option defaults to "NO". Press <ENTER> if you do NOT want to save the changes
otherwise enter a "Y" then the press <ENTER> to save all changes. After you
select one option or the other you will be returned to the Conference
Configuration Screen.
INDEX FILE NAME:
Enter the path and name of the INDEX file to use (if any) for locating files
available for downloading within this conference. You should only use the
INDEX feature if you utilize CD-ROM drive(s), floptical drive(s), or have an
extremely large file base, usually over 10,000 files or more.
NOTE: This feature is usually desired ONLY if you utilize a CD-ROM or
Floptical drive for storage of download files due to the slow seek times they
have. This option may also be beneficial to you if you have an extremely
large file base of more than 10,000+ files.
FEATHERNET PRO! supports an "INDEXED" file search of your file directories if
desired. The searching of the INDEX file will determine if the file is listed
as being present in usually under 1 second. This will result in saving the
user from having to wait while the system searches through multiple sub
directories on your hard or CD-ROM drive which could take up to five minutes
per CD-ROM. Once FEATHERNET PRO! determines that the file is listed in the
INDEX file, it will then access the directory that is pointed to, verifying
the file does actually exist. Because of this there will be an additional
delay of approximately 1-2 seconds (depending on the seek time of your CD-ROM
or Floptical drive and the number of files in the directory) while it is
verified. The real test to this speed is to try and search for or download a
file that does not exist in the INDEX such as, "IMNOFILE.YET" and see how fast
the INDEX is searched and the file is not found.
To facilitate conference configurations which may have different file areas
and directories, FEATHERNET PRO! allows each and every conference to have
separate INDEX files if desired. These INDEX files may also be shared between
conferences.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 24 ║
╚════════════════════════════════════════════════════════════════════════════╝
The INDEX file is created using the utility program BUILDNDX.EXE and the
procedure is described in detail in the UTILITIES section of this
documentation.
IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT!
This file is designed primarily for CD-ROM/Floptical users and in most cases
should contain only files on your CD-ROM and Floptical drives. If you enter a
path and name for this entry, THIS FILE WILL BE SEARCHED FIRST for filenames
specified by users and if not found FEATHERNET PRO! will THEN search the
DLPATH.LST for alternate paths (those on your hard drive). It is VERY
IMPORTANT that you put ALL HARD DRIVE PATHS into your DLPATH.LST file when
using the INDEX file as FEATHERNET PRO! will NOT search the PATHS specified in
the DIR.LST file if using an INDEX file. You do NOT have to specify your
upload and private upload directories as FEATHERNET PRO! handles these as
constants.
EXAMPLE: C:\FNET\CF0000\INDEX_1
PROHIBITED WORDS DATA FILE:
Enter the path and name of the "prohibited" words data file. Specify this file
*only* if you want the words in the data file to cause a warning to be sent to
the user. If this warning file exists and a user has used a "prohibited" word
in a message, the user will be returned to the message editor until the
message complies with your standards or is aborted by the user. An entry is
made in the caller log file.
This is a straight ASCII text file with one word on each line of the file
followed by a CR/LF combination.
ECHO THIS CONFERENCE:
"ECHO" refers to a conference's messages being connected to other systems via a
net mail or relay mail network such as the huge Fido network or smaller
networks such as LinkUSA. These networks use what is called an FTS or Fido
Technology Standard front end mailer which handles the passing of mail from
one board to another. If your board is using a front end mailer such as
FrontDoor, Binkleyterm or D'Bridge and this is an echoed conference, you
should set this to yes.
Enter a "Y" if you wish to echo this conference or an "N" if you do not desire
to echo it.
MAKE THIS A PUBLIC CONFERENCE:
A public conference is one that any user may join provided his security level
is sufficient. A private conference is one in which the SysOp MUST grant
access to individual users with the FeatherNet System Manager (FNETSM). A
user MUST have the required security level to join a private conference as
well.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 25 ║
╚════════════════════════════════════════════════════════════════════════════╝
MESSAGE BLOCKS:
Enter the number of message blocks to allocate to this conference (1-8). Each
message block allows up to 1024 messages to be contained in the message file
for a given conference. The maximum number of message blocks is 8 which
allows up to 8192 messages for a conference.
USE GRAPHICS QUOTING FEATURE:
Y = Use the graphics "box" to display newly quoted text in the message editor.
N = Use the Initials of the person the message is TO followed by the ">"
character.
Why use the Graphics Quote: It looks nice. Why not use the Graphics Quote:
Some echo mail networks such as FIDO do not permit the use of a graphics type
quoting feature as it does add extra data to each quoted message. This
ultimately results in greater cost and longer transmission times to send and
receive the messages throughout the network.
PRIVATE MAIL ONLY:
Enter a "Y" if you want to allow ONLY private (E-MAIL) mail to be entered in
this conference. If you specify private mail only, all mail posted by users
will automatically be marked private.
All user's high message read pointers will be updated when they read any
waiting mail in a "private mail only" conference.
PUBLIC MAIL ONLY: Enter a "Y" if you want to allow *only* PUBLIC mail to be
entered in this conference. If you specify PUBLIC mail only, you might
consider advising users this conference permits *only* public mail (readable
by anyone with conference access). The option to tag a private will not exist
if a "public mail only" conference.
AFTER YOU ARE FINISHED SETTING UP PAGE #1 OF THE CONFERENCE'S CONFIGURATION,
PRESS YOUR PgDn KEY TO CONTINUE ON TO PAGE #2 OF THE CONFERENCE'S
CONFIGURATION
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 26 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONFERENCE CONFIGURATION SCREEN 2
CONFERENCE NAME:
The name of the conference you are editing. This is defined in the conference
setup screen #1.
CONFERENCE #:
The number of the conference you are editing.
CONFERENCE PASSWORD:
Enter the PASSWORD a user must enter to gain access to this conference. The
PASSWORD is CasE SenSITiVe! Leaving this option BLANK disables this option.
LOCATION/NAME OF CONFERENCE NEWS FILE:
Enter the full path & name of the conference SPECIFIC NEWS file. The
conference "NEWS" file is displayed ONCE a user [J]oins a conference. It is
not shown to that user again until it is updated or the user types "NEWS" at
the conference main menu. This file is not required and is offered as a
configuration option to assist users in understanding what is available in the
specific conference joined. This may also be used to display the 'rules' of
the echo. Each conference may have a unique "NEWS" file. The filename should
be 7 or fewer characters to allow the adding of the "G" (graphics version) or
"R" (RIPscrip version) to the filename to display an ANSI or RIP version to
callers in graphics mode. This file may be shared between conferences. If
this file is not defined, the default NEWS file will be used if found. If no
NEWS file is defined at all, it will be ignored totally.
EXAMPLE: C:\FNET\CF0000\NEWS
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
LOCATION/NAME OF CONFERENCE MAIN MENU FILE:
Enter the full path & name of the conference SPECIFIC MAIN MENU file. The
conference "MAIN MENU" file is displayed each and every time a user [J]oins a
conference unless the user has EXPERT MODE enabled. This file is not required
and is offered as a configuration option to assist users in understanding what
is available in the specific conference joined. This file may be used to show
specific options in one conference but not another when using the COMMAND
TRANSLATION section of FNCFG or calling DOORS. Each conference may have a
unique "MAIN MENU" file. The filename should be 4 or fewer characters to
allow the adding of the "G" (graphics version) or "R" (RIPscrip version) and a
security level to the filename to display an ANSI or RIP version to callers in
graphics mode and/or make it security level specific. This file may be shared
between conferences. If a conference specific MAIN MENU file is not found,
the default MAIN MENU file will be used. If no MAIN MENU file is found, an
error message will be displayed to the user asking them to leave a comment to
the SysOp.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 27 ║
╚════════════════════════════════════════════════════════════════════════════╝
EXAMPLE: C:\FNET\CF0000\MENU\MM
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
LOCATION/NAME OF CONFERENCE SYSOP MAIN MENU:
Enter the full path & name of the conference SPECIFIC SYSOP MAIN MENU file.
The conference "SYSOP MAIN MENU" file is displayed each time the SYSOP [J]oins
the conference unless the SYSOP has EXPERT MODE enabled. This file is not
required and is offered as a configuration option. Each conference may have a
unique "SYSOP MAIN MENU" file. The filename should be 4 or fewer characters
to allow the adding of the "G" (graphics version) or "R" (RIPscrip version)
and a security level to the filename to display an ANSI or RIP version to
callers in graphics mode and/or make it security level specific. This file
may be shared between conferences. If a conference specific SYSOP MAIN MENU
file is not found, the default SYSOP MAIN MENU file will be used.
EXAMPLE: C:\FNET\CF0000\MENU\SMM
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
LOCATION/NAME OF CONFERENCE MESSAGE MENU FILE:
Enter the full path & name of the conference SPECIFIC MESSAGE MENU file. The
conference "MESSAGE MENU" file is displayed each and every time a user [J]oins
a conference's MESSAGE AREA unless the user has EXPERT MODE enabled. This
file is not required and is offered as a configuration option to assist users
in understanding what is available in the specific conference joined. This
file may be used to show specific options in one conference but not another
using the COMMAND TRANSLATION section of FNCFG or when calling DOORS. Each
conference may have a unique "MESSAGE MENU" file. The filename should be 4 or
fewer characters to allow the adding of the "G" (graphics version) or "R"
(RIPscrip version) and a security level to the filename to display an ANSI or
RIP version to callers in graphics mode and/or make it security level
specific. This file may be shared between conferences. If a conference
specific MESSAGE MENU file is not found, the default MESSAGE MENU file will be
used. If no MESSAGE MENU file is found, an error message will be displayed to
the user asking them to leave a comment to the SysOp.
EXAMPLE: C:\FNET\CF0000\MENU\MENU\CM
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 28 ║
╚════════════════════════════════════════════════════════════════════════════╝
LOCATION/NAME OF CONFERENCE SYSOP CONFERENCE MENU FILE:
Enter the full path & name of the conference SPECIFIC SYSOP MESSAGE MENU file.
The conference "SYSOP MESSAGE MENU" file is displayed each and every time the
SYSOP [J]oins a conference's MESSAGE area unless the SysOp has EXPERT MODE
enabled. This file is not required and is offered as a configuration option.
Each conference may have a unique "SYSOP MESSAGE MENU" file. The filename
should be 4 or fewer characters to allow the adding of the "G" (graphics
version) or "R" (RIPscrip version) and a security level to the filename to
display an ANSI or RIP version to callers in graphics mode and/or make it
security level specific. This file may be shared between conferences. If a
conference specific SYSOP MESSAGE MENU file is not found, the default SYSOP
MESSAGE MENU file will be used.
EXAMPLE: C:\FNET\CF0000\MENU\MENU\SCM
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
LOCATION/NAME OF CONFERENCE LISTING FILE:
Enter the full path & name of the conference SPECIFIC CONFERENCE LISTING MENU
file. The conference specific "CONFERENCE LISTING" file is displayed each and
every time a user uses the "[J]oin a conference" command from THIS conference.
This enables you to show certain conference areas being available from THIS
conference which would not generally be shown from another conference. This
file is not required and is offered as a configuration option to allow wider
configuration in developing your system. This file may be used to offer
specific conferences from one conference but not another. Each conference may
have a unique "CONFERENCE LISTING" file.
The filename should be 4 or fewer characters to allow the adding of the "G"
(graphics version) or "R" (RIPscrip version) and a security level to the
filename to display an ANSI or RIP version to callers in graphics mode and/or
make it security level specific. This file may be shared between conferences.
If a conference specific CONFERENCE LISTING file is not found, the default
CONFERENCE LISTING file will be used. If no CONFERENCE LISTING file is found,
an error message will be displayed to the user asking them to leave a comment
to the SysOp.
EXAMPLE: C:\FNET\CF0000\MENU\CL
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 29 ║
╚════════════════════════════════════════════════════════════════════════════╝
LOCATION/NAME OF CONFERENCE FILE MENU:
Enter the full path & name of the conference SPECIFIC FILE MENU file. The
conference "FILE MENU" file is displayed each and every time a user [J]oins a
conference FILE AREA unless the user has EXPERT MODE enabled. This file is not
required and is offered as a configuration option to assist users in
understanding what is available in the specific conference joined. This file
may be used to show specific options in one conference but not another when
using the COMMAND TRANSLATION section of FNCFG or calling DOORS. Each
conference may have a unique "FILE MENU" file. The filename should be 4 or
fewer characters to allow the adding of the "G" (graphics version) or "R"
(RIPscrip version) and a security level to the filename to display an ANSI or
RIP version to callers in graphics mode and/or make it security level
specific. This file may be shared between conferences. If a conference
specific FILE MENU file is not found, the default FILE MENU file will be used.
If no FILE MENU file is found, an error message will be displayed to the user
asking them to leave a comment to the SysOp.
EXAMPLE: C:\FNET\CF0000\MENU\FM
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
LOCATION/NAME OF CONFERENCE SYSOP FILE MENU:
Enter the full path & name of the conference SPECIFIC SYSOP FILE MENU file.
The conference "SYSOP FILE MENU" file is displayed each time the SYSOP [J]oins
the conference's FILE AREA unless the SYSOP has EXPERT MODE enabled. This
file is not required and is offered as a configuration option. Each
conference may have a unique "SYSOP FILE MENU" file. The filename should be 4
or fewer characters to allow the adding of the "G" (graphics version) or "R"
(RIPscrip version) and a security level to the filename to display an ANSI or
RIP version to callers in graphics mode and/or make it security level
specific. This file may be shared between conferences. If a conference
specific SYSOP FILE MENU file is not found, the default SYSOP FILE MENU file
will be used.
EXAMPLE: C:\FNET\CF0000\MENU\SFM
NOTE: There are no extensions on DEFAULT DISPLAY or MENU files unless it is a
LANGUAGE SPECIFIC display or menu file. SEE LANGUAGE FILES in FILE LOCATIONS
#1. Placing an extension on these files without matching them to a LANGUAGE
SPECIFIC EXTENTION will cause FEATHERNET PRO! to ignore them completely.
IGNORE SECURITY LEVEL WHEN VIEWING FILE DIRECTORIES: This option, if set to
"Y" will allow users to look through all the public download directories
regardless of security level, including PUBLIC UPLOADS. If the users security
level is not high enough to download, they will still be restricted from doing
so. This option can be used to let users browse your file database in order
to entice them into sending a donation.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 30 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - General Information Screen 1
This screen allows editing of the General BBS Configuration Information. This
is screen 1 of 2 for General information.
NAME OF YOUR BBS:
Enter the name of your Bulletin Board. This name is displayed to all callers
at logon. All doors you register should be registered using THIS name as most
DOOR authors will create KEY files that read your DOOR.SYS file and check the
name of the BBS and SysOp there. If the names do not match the DOOR will not
run.
WARNING This name must be entered EXACTLY THE SAME as shown on your
registration card. If the information is incorrect on your registration card,
contact FeatherNet Support immediately.
If this or your registration number are entered differently than what is shown
on your registration card, your board will run in the TEST DRIVE mode until
corrected.
See also, "Changing your BBS name in the 'UPGRADES' section".
SYSOP'S NAME:
Enter the name of the system operator. This name MUST have account #1 in the
USERS file (See FNETSM). This name must be EXACTLY the same as the name you
registered your BBS under.
The SysOp Name is displayed during various program executions. When a SysOp
leaves or receives a message, this name is indicated in the message header or
if a user leaves a message to "SysOp" this name will be automatically inserted
(unless otherwise specified under the Use Real Name field below or a
Conference Co- SysOp has been specified for the present conference). All
doors you register should be registered using THIS name as most DOOR authors
will create KEY files that read your DOOR.SYS file and check the name of the
BBS and SysOp there. If the names do not match the DOOR will not run.
USE SYSOP'S REAL NAME:
Allows you to configure the name used when leaving messages, comments, etc.
You may use your name as specified above or simply the word SysOp.
Y = When the SysOp logs into a system, any messages left, comments made, or
screens displayed use information contained in record number one of the USERS
file or the same name as specified above.
N = When the SysOp logs into the system, any messages left, comments made, or
screens displayed use the word SYSOP rather than information contained in
record number one of the USERS file or the name specified above.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 31 ║
╚════════════════════════════════════════════════════════════════════════════╝
"TODAY" FUNCTION:
FEATHERNET PRO! has a built in call for a "Today in History" display file
which is popular with many SysOps. Because these SysOps all have their
favorite programs or wish to not be locked into a particular one, FEATHERNET
PRO! does not supply one with FEATHERNET PRO!. There are many such programs
available on the shareware circuit.
Enter a "Y" to enable the TODAY function.
This function requires that you have the event function enabled. When you run
your events you should have it run your today in history program and generate
the display files for the day. You must have the program TODAY.EXE (or some
other version of this program) defined in the file location section of FNCFG.
The today program must create two files with your today program. (1)
TODAY.TXT (non-graphics version) and (2) TODAYG.TXT (graphical version).
Ensure these files are created in your main BBS directory. If your today
program creates a text and graphics file of a different name, you must
instruct your batch files to either rename them or instruct FNCFG of the
proper name in the FILE LOCATIONS 2 section.
ENABLE QUESTIONNAIRES:
This option simply tells FEATHERNET PRO! whether or not you wish to make use
of the QUESTIONNAIRE or SCRIPT functions it is capable of. If this question
is answered in the affirmative, you will be asked how many questionnaires will
be available.
IMPORTANT!
If you ENABLE questionnaires, you MUST have a new user questionnaire.
Y = If you wish to enable questionnaire functions. N = To disable the
questionnaire functions.
NOTE: Disabling questionnaires has no effect upon the NEW USER QUESTIONNAIRE
discussed later in the documentation.
NUMBER OF QUESTIONNAIRES: This question sets the parameters of the users
choices when accessing the questionnaire menu. If you specify there will be
"6" questionnaires here and there are only five, a user will see on the
questionnaire command line there are 6 specified, even if your ASCII or ANSI
menu only lists 5. If a user chooses #6 an error message will be generated
saying, "(Path/Bulletin Name) Not Found, Please Notify SysOp". If the user
chooses #7 he will be told that isn't a choice.
Enter the number of questionnaires that will be available for users. If you
enabled script questionnaires, this value must be at least 1 if you have
enabled the questionnaire functions.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 32 ║
╚════════════════════════════════════════════════════════════════════════════╝
GENERAL INFORMATION SCREEN 1
REGISTRATION NUMBER:
Enter the BBS registration number you received with your registered version of
FEATHERNET PRO! The registration number is in three parts, your registration
CODE is first, your registration identifier is second and third is your Node
capability identifier. You should NEVER tell anyone your registration CODE.
Your registration and node IDENTIFIER is shown upon entering your BBS to all
users. When you enter your registration number is should be in the form of;
<REGISTRATION CODE> <REGISTRATION IDENTIFIER> <NODE IDENTIFIER>
EXAMPLE: 7834598128 94-0000 /10
NOTE: Before opening the envelope with your registration number you should
have read the entire license agreement, copyright notice and limited warranty
statements at the beginning of this documentation.
If you have not yet registered FEATHERNET PRO! enter a "000" as your
registration number. This will enable you to run the Software until you have
decided to register.
MINIMUM USER PASSWORD LENGTH:
Enter the minimum number of characters a user can have in their password.
This can be a number between 2 and 12 in length. If a user tries to enter a
password of fewer characters the system will prompt them for a longer one. If
you have users that already have shorter ones than specified, the system will
allow them until they change it with the "I" command at the MAIN MENU.
ADD "UPLOADED BY" TO DESCRIPTION:
FEATHERNET PRO! optionally will add the name of a user who uploads to the
description of the file. This may be an incentive for users to upload.
The format for this is: "Uploaded By:" <User's Name>
Enter "Y" if you want FeatherNet to append "Uploaded By: " and the caller's
name to the file description after each upload. Enter "N" if you would prefer
not to have this option enabled.
USE COLOR GRAPHICS DURING A LOCAL LOGON:
This option will enable or disable color ANSI in local logins. Because
FEATHERNET PRO! is designed as a multi-node BBS system many nodes will
probably be running on monochrome monitors. This setting will disable the
color in local mode when running in a monochrome environment.
Enter "Y" if you wish FEATHERNET PRO! to use ANSI color in local logins.
NOTE: Color may still be turned off/on at the main menu with the [S] command
irrespective of this setting.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 33 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONFIRM USER'S NAME & ADDRESS:
FEATHERNET PRO! will act two ways in regards to users and their names.
Most BBS software will allow only one user per name. FEATHERNET PRO! can
handle users two ways.
1: If JOE TESTER attempted to logon to your board and there already was a JOE
TESTER it would tell them sorry, that user already exists and ask them to use
a different name.
2: If JOE TESTER attempted to logon to your board and there already was a JOE
TESTER, FEATHERNET PRO! would ask, "Are you JOE TESTER from ANYWHERE, USA?"
and if the user answers NO then the user would go into the new user
questionnaire. In this method, if there are one or more users with the same
name, if a user leaves a message to a user name with more than one user, it
will then also verify location at that point also.
Normally, FeatherNet will stop searching for a user name as soon as it is
found in the user index files. This user's password would be required to
enter the system under the logon name. Since this could easily be a problem
when two or more users have the same name, set this option to "Y" to confirm
the name at logon and when addressing a message.
MINIMUM UPLOAD DRIVE SPACE (Kilobytes):
FEATHERNET PRO! has a safeguard to prevent your hard drive from completely
filling up and thus causing errors or corruption. This will completely disable
UPLOADS to the system if the specified number of bytes or less is reached.
Enter the number of kilobytes which must be free on your upload drive before
an upload is permitted. This number entered is multiplied by 1024 to get the
actual number of bytes that must be free.
NOTE: This will NOT prevent mail from being entered via the message base,
FNMail (FEATHERNET PRO!'s QWK mail door) or via a front end mailer!
TIP
It is strongly recommended that you set this number relatively high, a
minimum of 10 megabytes is suggested.
MAXIMUM NUMBER OF MESSAGES TO CAPTURE:
No longer used.
MINUTES BEFORE FEATHERNET PRO! RECYCLES TO DOS:
Enter the number of minutes before FEATHERNET PRO! will terminate and allow
the "SFN.BAT" file to re-load the BBS and reset the modem when waiting for a
call. This is available due to some modems that become "DEAD" after a period
of being idle. This is generally only necessary when running under an
emulated multi-tasker such as older versions of DESQview.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 34 ║
╚════════════════════════════════════════════════════════════════════════════╝
TIME CREDIT FOR UPLOADS:
FEATHERNET PRO! has the option of "rewarding" users for their uploads through
"time credit".
Enter the amount of on-line time credited to a user for uploading files. This
number may have 2 decimal places. A credit of "0" will charge the user for
actual time used during the upload with no "extra" credit given. A credit of
1.0 will make the time of the upload "free" time. More than 1.0 will result in
additional on-line time.
TIP
It is a nice perk for callers to gain "extra" time through uploads. A lot of
SysOps set this option to 1.5. This way, if a user uploads a file taking 10
minutes, they get their 10 minutes back plus a 5 minute bonus.
LIMIT SYSOP PAGING HOURS:
This allows you to disable the hours the SysOp is available for chat. If this
options is selected to "N" users may page the SysOp at any time provided the
SysOp has the chat page turned on. Regardless of this setting, the SysOp may
still turn the "Page SysOp" status from the Waiting for Call screen off and
on.
SYSOP PAGE START TIME:
When the SysOp is turned OFF, the SysOp cannot be Paged. When SysOp is turned
ON, this field is the Start time at which callers may page the SysOp for chat.
If you are only available from 17:00 until 22:00 you might want to use these
times as the chat page start and stop times. The time must be input in 24 hour
military format for both SysOp Start and Stop times. (i.e.: HH:MM)
SYSOP PAGE STOP TIME:
When the SysOp is turned OFF, the SysOp cannot be Paged. When SysOp is turned
ON, this field is the stop time at which callers are not permitted to page the
SysOp for chat. If you are only available from 17:00 until 22:00 you might
want to use these times as the chat page start and stop times.
NUMBER OF CHAT ROOMS:
FEATHERNET PRO! has a multi-node chat system built into it. This chat system
is built around "chat rooms" defined by the SysOp. This will allow 2 or more
persons to go into the same or different rooms and chat with other users. A
"room" can be thought of as where a specific topic might be open for
discussion. Enter the number of group chat "ROOMS" to be available. The
maximum number of rooms is 255.
FEATHERNET PRO! is designed to be a single or multi-node system. If you are
running a single node system this option will not apply to you and you should
set this parameter to zero (0).
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 35 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - General Information 2
PRE-LOAD FNETTEXT FILE:
FEATHERNET PRO! has the ability to load it's command and prompt file into DOS
memory. This option may result in faster access to the FNETTEXT (prompt data)
and reduce disk wear. Pre-Loading the FNETTEXT file provides increased
efficiency when the FNETTEXT file is accessed to display various text strings,
such as command prompts. This also helps reduce wear on your hard drive since
the drive is not accessed for each of the various text strings. The only
possible drawback is that approximately 21k of DOS memory is required to
pre-load the FNETTEXT file.
If you are running FEATHERNET PRO! with less than 50k memory (51,200 bytes)
available when waiting for a call, you would probably be wise to leave this
option set to "N". If you have sufficient memory, it is strongly recommended
you enable the pre-loading of the FNETTEXT file by answering "Y".
TIP
Another alternative to loading the FNETTEXT command and prompt file into DOS
memory is to copy it to a RAM drive before loading FEATHERNET PRO! and
pointing to it there in the FILE LOCATIONS SCREEN later in FNCFG.
WARN CALLERS AT LOGOFF IF "DOWNLOAD FLAGS" ARE SET:
Enter "Y" if you wish to prompt users at logoff who have files flagged for
download. This will give them a chance to download the files before the flags
are "reset" after logoff.
PROMPT CALLERS TO SET MESSAGE POINTERS AT LOGOFF:
Enter "Y" if you desire to have the callers asked if they want their "high"
message read flags to be set to the highest message in each conference defined
for the BBS. The advantage of setting the high message read pointer to the
highest message in each conference is that callers who usually only read
private mail will keep their high message read pointers continually updated in
all conferences by the date of last call. A user reading private mail or
public mail addressed to him during the logon sequence does not get the
message read pointers updated. The disadvantage is that this process could
take an extremely long time. It is recommended that if you have a large
message board that you set this option to "N"
NOTE: The user can manually set pointers regardless, by using the [L] command
at the message menu.
CONFIRM LOGOFF COMMAND:
Enter "Y" if you wish callers to confirm a logoff when the [G]oodbye command
is entered. If selected the BBS will ask, "Are you SURE you want to logoff?"
(Y/n). The default answer is (N)o, do not ask, just log them off.
SWAP FEATHERNET TO XMS, EMS, OR DISK DURING A "SHELL":
FEATHERNET PRO! "shells" to DOS when the SysOp presses the <F9> key or when
running FNCFG.EXE, FNETSM.EXE , or FNFILER.EXE from within the BBS.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 36 ║
╚════════════════════════════════════════════════════════════════════════════╝
SHELLing is also performed when file transfers or archive manipulations are
performed. Before you choose to "Shell", ensure that there is enough memory
remaining to support the external protocol driver(s) used. For PKZIP/PKUNZIP,
you need approximately 120K of RAM when FEATHERNET PRO! "Shells". ARJ can
require over 200k of ram for maximum compression.
If a user performs archive manipulations and downloads a file or files from an
archive FEATHERNET PRO! now uses a temporary work directory to do the archive
extraction and creation in. A sub directory called "FNTMPDIR" is created off
of the BBS work directory. It will hold the archive until the user downloads
it. If additional files are manipulated and the user selects files to download
from them, these files are also placed in the single archive file in the
temporary directory. The temporary directory is purged when the user logs off
the BBS.
If you have ample EMS/XMS and run your BBS on a 386 or greater machine you may
tell FEATHERNET PRO! to "SWAP" when shelling. This ensures maximum memory for
the archive utilities.
Entering a "Y" will cause FEATHERNET PRO! to attempt to SWAP itself to
Extended Memory (supplied by an XMS driver, such as HIMEM.SYS), expanded
memory (EMS version 4.0), or disk, thus freeing up more memory for DOS.
If attempting to swap and all three methods fail then FEATHERNET PRO! will
SHELL while remaining in DOS memory.
ENABLE LOGON/LOGOFF BROADCASTS TO OTHER NODES:
If set to "Y", FEATHERNET PRO! will announce each user as they log on or off
to the other IN USE nodes unless the user coming in or leaving is in STEALTH
mode. This function will allow users to "see" when friends arrive, etc. For
single node boards this should always be set to "N" to prevent FEATHERNET PRO!
from searching for any other nodes and thus using the .25 seconds it might
take.
ALLOW [P]RIVATE FILE TRANSFERS:
FEATHERNET PRO! has the ability to allow private uploads and downloads between
two users only. Enter "Y" if you wish to allow certain users the ability to
upload and download PRIVATE files.
NOTE: A user may only send private files to another user who is authorized
this function by the SysOp. The ability to use this function must be set by
the SysOp in FNETSM for each individual user he wishes to let use it.
OPERATE AS A CLOSED SYSTEM:
This option lets you control how your system will operate. It is mainly here
for businesses and groups who do not wish to have the "public" logging onto
their systems. If you enter a "Y" FEATHERNET PRO! will prevent anyone from
logging on as a new user. You will have to manually add each and every user
into the system via FNETSM.
NOTE: New users will be able to fill out the new user questionnaire (if
available) and then will be logged off immediately.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 37 ║
╚════════════════════════════════════════════════════════════════════════════╝
ALLOW SPLIT SCREEN CHAT TO BE USED:
Enter a "Y" if you want the Split Screen Chat mode available to callers with
ANSI capability detected at logon. The Split Screen Chat mode allows the
simultaneous sending and receiving of data thus increasing the efficiency of
the chat mode. Answering "N" to this option will force the "line by line"
type chat mode.
FORCE USERS TO READ NEW PERSONAL MAIL AT LOGON:
FEATHERNET PRO! can optionally force users to read mail waiting for them
during the logon process. This can be useful for those users the SysOp wants
to read messages but seldom takes the time to do. Enter "Y" if you want to
force users to read all their new personal mail at logon. Enter "N" if you
prefer to let the users read new personal mail at their leisure. (They will
still be asked if they want to read new personal mail at logon).
ALWAYS FORCE USERS TO SELECT TRANSFER PROTOCOL:
Enter a "Y" to force all users to select the file transfer protocol after they
enter a [D] or [U] from the file transfer area. Users taking advantage of the
"command stacking" feature will not be forced to select a protocol. Setting
this to "N" will have FEATHERNET PRO! use the protocol the user selected when
they first signed on as a new user. If set to "N", the user may still change
their protocol before the download begins or record a new choice for a
transfer protocol using the "I" command at the main menu.
HAVE THE "DO YOU WANT COLOR" QUESTION DEFAULT TO "Y" OR "N":
When a user logs into the BBS it will detect whether or not they are in TEXT,
ANSI, or RIP mode. If the user is in ANSI, they have the choice to select
COLOR on or off after the mode detection. Enter a "Y" if you want the "Do you
want Color Graphics" question at logon to default to (Y)es. Enter an "N" to
have it default to (N)o.
NOTE: The default to this question is "N". If you set it to "Y" for yes, then
you MUST change Prompt # 9 in FNETTEXT to reflect the change to "Y". (See the
FeatherNet UTILITIES section MKFNTEXT for more on diting the FNETTEXT file).
DISABLE THE AUTO ANSI DETECT FUNCTION AT LOGON:
Some networks apparently have trouble dealing with the ANSI status request
("[6n") and this option allows the SysOp to completely disable the ANSI
detection at logon. Disabling the auto ANSI will mean ALL users will not have
the quicker ANSI cursor movement sequences available unless they are using the
Visual Message Editor. Ensure the "apparent problem" with the auto ANSI
detect sequence is not unique to one user which may be a configuration problem
before disabling this function.
NOTE: If you disable Auto ANSI you also disable the split screen chat mode.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 38 ║
╚════════════════════════════════════════════════════════════════════════════╝
DISPLAY THE USER STATISTICS FILE AT LOGON:
This option allows the SysOp to Force the users to view the USRSTAT display
file each time they logon to the BBS. The USRSTAT display file is also an
option from the main menu by pressing [V] (View User Statistics) if the user
security level is sufficient.
ALLOW "ALIASES" OR SINGLE WORD NAMES:
FEATHERNET PRO! allows you the option to run an "Alias Board". This is that
all users are known by an alias name rather than by their real names. The
SysOp may still require that the user fill out the new user questionnaire with
their real name before allowing access to the BBS. Enter a "Y" if you want to
allow users to logon with Aliases or with one Name.
NOTE: All user names must begin with letters between A-Z and contain NO HIGH
ANSI CHARACTERS!
ALLOW SENDING ONE LINERS TO OTHER NODES:
FEATHERNET PRO! allows you the option to let one node send or "whisper" to
other nodes, whether the other node is in CHAT or not. In all cases the user
sending the message must be in chat to accomplish this. Set this option to
"N" if you do not want users to whisper to other nodes or if you run a single
line board. Set this option to yes if you do want the whisper option enabled.
MAXIMUM LINES TO DISPLAY WHEN READING FROM ARCHIVE:
Enter the maximum number of lines users will be allowed to read when
performing archive manipulations. This option allows the SysOp to prevent
users from capturing complete text files and bypassing their download file or
byte ratios.
USE WHICH PARALLEL (Printer) PORT (0-3):
Enter the parallel port to send the output to. If a port 1-3 is specified and
the "Printer" option on the Waiting for Call screen is toggled to YES ( or the
<ALT><P> key combination from within the BBS is used), caller log entries will
be sent to the printer in the same format that they are saved in the caller
log file. Enabling this option will also let you print messages from the
message base by entering a <CTL><P> key combination from within the Visual
Editor. Entering a "0" will disable output to the printer. If you have no
printer attached to the system and powered up, ensure that this option is set
to "0". Each node configured has it's own printer control.
FORCE USERS INTO BULLETIN MENU AT LOGON:
You have the option of forcing users into the bulletin menu at logon if one or
more bulletins have been updated since they last logged on. Enter "Y" to force
ALL users into the bulletin menu at logon if new or updated bulletins are
present since the caller's last logon. If you set this option to "N" they the
users will be informed at logon that bulletins have been updated and asked if
they wish to view the bulletin menu.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 39 ║
╚════════════════════════════════════════════════════════════════════════════╝
MAXIMUM LINES ALLOWED IN MESSAGE EDITOR:
FEATHERNET PRO! allows you to limit the number of lines a user may input into
the message editor at any one time. This has a two-fold purpose. First, it
will prevent any user from entering entire volumes of text into you system,
filling up your hard drive and possibly causing a system failure (at least not
easily) and second, some echo mail network rules state that you may not pass
messages over a certain number of lines (usually 99).You may enter a number
between 19 and 400.
NOTE: Each 50 lines of text allowed uses approximately 6400 bytes of system
memory.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 40 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Modem/Node/Subscription Information
MODEM INITIALIZATION STRING:
Enter the initialization string for your modem. This will vary from one modem
to another depending on the modem's characteristics. Since there are so many
different modems on the market, and the market itself changes from day to day
it would be almost impossible to list all the possible variations here.
We have provided a utility to help you setup your modem for use with
FEATHERNET PRO! called MODEMSET. Run MODEMSET.EXE and see if your modem is
listed. If it is, it will prepare your modem for use with FEATHERNET PRO! and
insert the initialization string in the configuration for you. See "MODEMSET"
in the SYSOP UTILITIES section of this documentation.
A general string for all modems is: ATE0Q0M1V1S0=0S2=1S7=45&C1&D2H0
If your modem is NOT listed in the MODEMSET program, send us your working
command line and we will add it into the program for other SysOps to use in
the future.
COMMUNICATIONS DRIVER TO USE:
FEATHERNET PRO! has been designed to use ASYNC, FOSSIL and DIGIBOARD/GTEK
driven communications ports. Determine how you will control your com ports
and enter an "A", "F" or "M" here.
If you are running a single node system, a NOVELL or LANtastic network with a
single node per workstation, or other type multi- tasker that does not require
a FOSSIL driver (Uses Asynchronous communications routines) then enter an "A"
here.
If you are running a multi node system under DESQview / OS/2 or use another
program like FrontDoor or Binkley "front-end mailers" that requires the use of
a FOSSIL driver and would like to leave them "hot" all of the time to
continuously control your com ports (lock them), then set this to "F" and
FEATHERNET PRO! will allow your FOSSIL to handle it's communications routines.
SEE: APPENDIX B: MULTITASKING
WHICH COMMUNICATIONS PORT (0-64) IS THIS NODE LINKED TO:
FeatherNet PRO! supports communications ports 0-64. This allows non-standard
serial port addresses and IRQ's to be defined. If you use a serial port higher
than COM2 then ensure you include the correct IRQ and port address. IRQ 1- 15
is supported. For serial port 3 "&H3E8" would normally be the port address
and "&H4" would normally be the IRQ number. NOTE: For a Local Node without a
modem/serial port you MUST specify com port 0 (zero) in the configuration.
BAUD RATE TO OPEN COMMUNICATIONS PORT AT (300-115200): Enter the speed to open
your modem at. This will usually be the highest speed your modem OR HARDWARE
can handle.
EXAMPLES: 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 76800 and 115200
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 41 ║
╚════════════════════════════════════════════════════════════════════════════╝
LOCK COMMUNICATIONS PORT AT OPENING BAUD RATE:
Enter "Y" if you wish to LOCK the computer to modem speed at the OPENING baud
rate. If you do so, it is assumed that RTS/CTS is enabled in your modem
initialization. If your modem has a maximum speed of 2400, you will normally
answer "N" to this option. NOTE: Some doors do not function well with locked
ports. If you have any problems with a DOOR under locked ports, you might try
UNLOCKING the port or checking to see if the DOOR author has included a
"/LOCKED:" configuration option for the DOOR.
ANSWER ON WHICH RING:
Enter the "ring" number you want the modem to answer on. If you are in an
area with the "CALLER I.D." service and your modem can handle it or you have a
"CALLER I.D." display box, you should set the rings to at least 2. Check with
your local phone company to see where the "CALLER I.D." information is passed
in the ring sequence (Usually between the first and second ring). You may
enter a number between 1 and 10.
SECONDS TO WAIT FOR CONNECT:
Enter the number of seconds the BBS should wait for carrier after it has
issued the answer command to the modem. Some modems, particularly high-speed
types with the v.32bis standard, have long carrier detection handshakes. If
you have one of these modems, ensure that this value is set to at least 45
seconds.
MINIMUM BAUD RATE ALLOWED:
This option allows you to restrict slow modem baud rate users from using the
BBS. Enter the minimum baud rate acceptable on your BBS. Callers with lower
baud rates will be notified that their baud rate is not supported and logged
of immediately.
EXAMPLE: If you do not want 300 and 1200 baud users using the BBS, enter: 2400
PAUSE FOR 3 SECONDS AFTER CONNECT AT 2400 OR LESS BAUD:
Enter a "Y" if the BBS should pause for 3 seconds after a CONNECTION is
established at 2400 or less baud. Some modems take longer than others in
detecting the baud rate. As a rule of thumb if there is a 2-4 second delay
from the time the modem establishes a connection until the "CONNECT" message
is reported then you should answer "Y" here. Operate in a Subscription Mode
Enter "Y" if you want to operate your BBS in a paid subscription mode. When a
subscription expires, FEATHERNET PRO! will reduce the caller's security level
to the "expired" level (chosen below).
OPERATE IN SUBSCRIPTION MODE:
Setting this toggle to "Y" will allow you to operate a subscription type BBS.
This will activate the user's EXPIRED date fields and hourly accounting fields
in FNETSM. If you set this option to "Y" you must make sure all users
expiration dates are set otherwise the users will be set to the expired
security level as defined below. Set this option to "N" to disable
subscription mode. Disabling subscription mode will leave users at their set
security level forever.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 42 ║
╚════════════════════════════════════════════════════════════════════════════╝
DEFAULT NEW USER SUBSCRIPTION IN DAYS:
Enter the number of days you want new users to have until their subscription
is expired. This option may be set from between 0 and 999 days, the default
is 5 days if subscription mode is in effect.
DAYS WARNING BEFORE SUBSCRIPTION EXPIRES:
A warning notice will be displayed to users who logon whose subscription
expires within the number of days entered. Usually a SysOp will set this to
about 30 days to give users ample time to re-subscribe if they wish. If using
this you should update the display screens EXPWARN and EXPIRED.
EXPIRED SUBSCRIPTION SECURITY LEVEL:
Enter the security level assigned to users when their subscription expires.
This MUST be a valid security level as set in the security level configuration
editor (PWRD) later in the FNCFG (File Locations 1 Screen).
OPERATE IN A RING BACK MODE:
Enter "Y" if you wish FEATHERNET PRO! to operate in "ring back" mode. This is
handy when only one phone line is available and you wish FEATHERNET PRO! and
the "rest of the family" to share it without a hassle.
When enabled, FEATHERNET PRO! is initialized but will not answer a first call
and awaits a second call (ring back) within a specified period of time as
noted below. If a ring back occurs in the proper time frame, FEATHERNET PRO!
will then answer this second call.
HOW 'RING BACK' Works: Once a "ring back" alert is triggered by the first
ring, FEATHERNET PRO! will wait 7 seconds after the ringing ENDS and reset
the modem. It will then wait the specified number of seconds for a "ring
back" .If a call is received within the specified number of seconds,
FEATHERNET PRO! answers the call and attempts to establish carrier. If no
"ring back" occurs within the specified time, the ring back alert is
discontinued and FEATHERNET PRO! waits for the next alert.
SECONDS TO WAIT FOR RING BACK:
Enter the number of seconds FEATHERNET PRO! will wait for the "Ring Back" call
if operating in ring back mode. 45 - 60 are suggested values. If a ring back
does not occur within the "set" time, the "ring back" is canceled and the BBS
awaits another initial ring.
NUMBER OF THIS NODE:
Enter the node number you are configuring. If you have a single node BBS,
this value MUST be set to 1.
NOTE! If you are running a SINGLE LINE BBS you MUST use 1.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 43 ║
╚════════════════════════════════════════════════════════════════════════════╝
NODE PASSWORD:
Enter the PASSWORD needed to gain access to this node. FEATHERNET PRO! will
ask any user attempting to sign into this node for the password specified
here. If the user does not know that password, they will be logged off
immediately. This is useful for setting up private nodes, nodes for
registered users only, mail only nodes when using QWK and/or added security
for CORPORATE Systems. This option is not active if you leave it blank.
FILTER ALL HIGH ASCII CHARACTERS:
Enter "Y" if you wish FEATHERNET PRO! to filter all ASCII characters above #
127. These are normally associated with line noise. If your BBS has foreign
(non U.S.A.) callers, you might want to leave this option OFF ("N") as some
foreign callers need these characters.
USING A NETWORK OR MULTI TASKER:
This parameter will allow you to set up node numbers greater than 1 with a
multi node version of FEATHERNET PRO!. Unless you are running in a network or
multitasking environment (OS/2 or DESQview, etc.), FEATHERNET PRO! will not
allow you to enter a node number other than 1.
Set this to "Y" if you are operating a multi-node BBS under a multitasking
environment such as DESQview, a multitasking Operating System such as OS/2 or
a network such as LANtastic or NOVELL.
Set this to "N" if you are operating a single node under MS/PC DOS, OS/2 or a
100% compatible DOS emulator.
NOTE: If you set this parameter to "Y" you must have "SHARE" loaded in your
CONFIG.SYS or AUTOEXEC.BAT file. If you are not multi tasking or operating in
a network environment, set this parameter to "N".
USING A "FRONT-END" TO LOAD FEATHERNET PRO!:
Enter "Y" if you want to use a "front-end" loader to launch FEATHERNET PRO!
when a call is received. The following parameters are used to determine the
caller's baud rate, type of connection, and next event by the front end
mailer; /C:BAUD_RATE ERROR_CORRECTION_TYPE EVENTMINUTES The parameters /C:0
(Local Logon) and /C:8 (Local SysOp Logon to Main Menu) may also be used. An
example of the way it might look in your SFN.BAT would be; "SFN /C:%1 %2
EVENT%3" (without quotes).
If a caller connects using an error correcting modem (to your error correcting
modem), you may pass your error correcting protocols to FEATHERNET PRO! as the
second parameter, right after the baud rate. You may also pass the time until
the next event as a third parameter, to do this include the word EVENT
followed IMMEDIATELY by the MINUTES until the next event in you front end
mail. FEATHERNET PRO! will check this time against the users time limit and
adjust the users time if necessary. If the user's time is adjusted,
FEATHERNET PRO! will send a message to the user explaining why. Any baud rate
may be passed to FEATHERNET PRO! by using the baud rate on the command line as
in: /C:2400 /C:9600 etc.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 44 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Event Configuration & Command Translation
EVENTS
An "EVENT" is a means of unattended running external programs or batch files
which perform system maintenance such as backups, echo mail runs, DOORS
maintenance, DIR list maintenance, message file packing, etc. FEATHERNET PRO!
supports multiple events which provides the SysOp with much flexibility in
planning and coordinating events.
COMMAND TRANSLATION
FEATHERNET PRO! gives you the ability to use a different command letter for
internal options than the default. Thus you could use the letter "P" for Page
instead of the default "O" for Operator Page. Command translation also
provides you with a means to totally disable an internal function and redirect
that command to an external program. Thus you could in fact have "O", instead
of going to Operator page, go to a SysOp Chat DOOR instead. We are sure you
can see the POWER this gives you in customizing your system. This is based on
"other" systems that have built in script languages. When we looked at them
we found that they all had another program to learn and at an extra cost to
you. The way we have set up FEATHERNET PRO!, you can use any programming
language and program your own "mini" doors to do what you want. FeatherNet
Software, Inc. will be releasing a "BASIC" library to allow you to quickly
call information from your data files for use with writing your "mini" doors.
EVENT LIST FILE PATH & NAME:
Enter the path and name of the EVENT.LST (event configuration) file. This file
will contain information on event times, days, dates, and modes of execution
to be utilized. Support for multiple events (up to 99 per node) are
supported. Each node has its own event configuration file.
EXAMPLE: C:\FNET\EVENTS\EVENT.LST
EVENTS LIST FILE EDITOR:
Pressing the <F2> function key when the "Event LST file path and name" is
being edited, in the above edit screen, places you in the event editor.
WHILE ON THE "EVENT.LST PATH AND NAME" OPTION, PRESS <F2> TO
ENTER THE EVENT CONFIGURATION EDITOR.
IS THIS EVENT ACTIVE:
Enter "Y" or "N" to specify if this is an ACTIVE EVENT or not. An "active
event" is an event you wish to be executed when the correct date & time
arrive. If you want to temporarily disable an event at any time, simply enter
a "N" here.
EVENT MODE:
FEATHERNET PRO! has two modes by which events may be controlled. These are
(E)xpedited and (S)liding events.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 45 ║
╚════════════════════════════════════════════════════════════════════════════╝
An EXPEDITED event forces callers off and denies access to the system, doing
everything possible to ensure the event will be run at the specified time.
If the event does not run at the specified time or in the time "window"
specified in the event configuration, it will be skipped.
A SLIDING event is one which will be run during the specified time "window".
Users will not be interrupted and user's time allowed will not be affected.
Whenever a user logs off the system during the time "window", the event will
be executed. This may well be the preferred manner of running daily events
such as mail runs or system maintenance.
Enter an "E" to specify an EXPEDITED event or an "S" to specify a SLIDING
event.
EVENT BATCH FILE NAME:
Enter the event batch file name. An EVENT.BAT is created by FEATHERNET PRO!
to call this batch file. Ensure that you have a .BAT file extension on each
event's actual batch file name.
EXAMPLE: MAILRUN.BAT
BEGIN EVENT TIME:
Enter the time the event is scheduled to run. All attempts will be made to
run events at this time. The time must be specified as HH:MM in military
format.
EXAMPLES: 02:00, 14:30, 23:45, 00:30
END EVENT TIME:
Enter the end time for this event. This is the latest time in which any
attempt will be made to run the event each time it is pending. The period
from the begin time to the end time is the "window" in which FEATHERNET PRO!
will attempt to run the event. The time must be specified as HH:MM in military
format.
EXAMPLES: 02:00, 14:30, 23:45, 00:30
EVENT DATE:
Enter a specific DATE this event is to be run. If it is to be run daily leave
this field blank. Dates *must* be entered in the MM-DD-YY format. A date may
contain wildcards which are "00" in a month (MM) or year (YY) position.
EXAMPLES: 00-01-00, 12-25-00, etc.
In the first example date, an event would be run on the first day of every
month while in the second example an event will be run every CHRISTMAS.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 46 ║
╚════════════════════════════════════════════════════════════════════════════╝
LAST EVENT DATE:
This is a field which FEATHERNET PRO! updates to record when an event is run.
An event will only be run once on the day it is due. You would have to BLANK
this field to have FEATHERNET PRO! run the same event at a later time on a
given day. If you do alter this field in order to force an event to be run
again (or for some other reason), ensure you enter the date (if you do not
leave the field blank) in the MM-DD-YY format.
EXAMPLES: 01-01-93, 12-25-93, 00-01-00, etc.
EVENT DAY FLAGS:
Enter a "Y" or "N" to tell FEATHERNET PRO! the days you want an event
executed. The days are specified as SUNDAY through SATURDAY. SMTWTFS
IMPORTANT!
When you enter a specific date (with or without wildcards, "00"), the DAY
flags are ignored and the DATE field determines on which day an event will be
run. It is *VERY* important to leave the EVENT DATE field blank if you have
an event you want to be run more often than once a month.
EVENT EXAMPLES: (Not In UNREGISTERED DOCS)
You may do anything you wish in the EVENT but remember - DO NOT put "SFN" on
any line in the batch file. The "EVENT.BAT" file is CALLED from the "SFN.BAT"
file so allowing the batch file to "run out" is the proper way to allow
SFN.BAT to regain control once the event is completed. Each FEATHERNET PRO!
node manages its own EVENT.LST file. Run FNCFG from a node directory to
configure events for the node. Normally (used loosely), events are run from
Node #1.
WHEN DONE PRESS <ESC> TO QUIT AND THEN SAVE YOUR INFORMATION.
YOU WILL THEN BE RETURNED TO THE CONFERENCE CONFIGURATION SCREEN.
SAVING THE EVENT CONFIGURATION FILE:
After you are done editing the configuration file, press the <ESC> key and it
will ask you if you want to save the changes you have just made, if any. This
option defaults to "NO". Press <ENTER> if you do NOT want to save the changes
otherwise enter a "Y" then the press <ENTER> to save all changes. After you
select one option or the other you will be returned to the Conference
Configuration Screen.
MINUTES PRIOR TO EVENT TO DISALLOW CALLERS:
Enter the number of minutes prior to the scheduled event time you want
FEATHERNET PRO! to start to disallow all callers. This setting is valid only
when an EXPEDITED event is pending. This effectively starts the event a
number of minutes prior to the event "Begin Time" by keeping the BBS idle
during this period.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 47 ║
╚════════════════════════════════════════════════════════════════════════════╝
MODEM OFF-HOOK (BUSY) WHEN AN EVENT IS PENDING:
Enter a "Y" or "N" to specify if you want the modem taken off-hook when an
event is pending. This will be during the minutes specified above when no
calls will be answered. Rather than having the line open and "ringing off the
hook", you might prefer that the phone line be "off the hook" and busy so any
callers will not think that the BBS has gone down or has crashed.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 48 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Command Translation
There are basically three different functions that may be performed from the
COMMAND TRANSLATION Editor. These functions are as follows;
Add a menu command function.
Replace a menu command letter with another letter.
Replace an internal menu command with an external program.
In the examples shown on the previous page, the "O" command (Operator page)
was replaced by the letter "P" for Page. As there is already an internal "P"
command (Page Length) you must give it a new letter or letters, in this case
it was given the command "ROWS". Now when a user wants to change his page
length they must type ROWS instead of "P" as "P" will now "P"age the SysOp.
In the other examples, a NEW command was added called "ORDER". When the user
types this it will call a file called ORDER and run the program with in. The
file ORDER would be set up exactly the way you set up a CALL file for DOORS.
It is a .BAT file without the .BAT extension. Keep in mind that all
redirected commands to an external program must support the communications
routines that you are using for your BBS, ASYNC, FOSSIL, or DIGIBOARD. The
fourth example shown replaces the CALL command to view your CALLER LOG FILES
with a LOG File Analyzer program. You will notice that we used the same name
"CALL" for the file name thus it is a direct replacement for the internal call
command.
There are a few things that you should be aware of as you set up your command
translation file. The first thing is that you must be sure not to use a
command that is already used. If you do, you must also give the other command
a new menu command letter also. The second thing is that if you assign a
command such as "O"perator Page and new letter like "Y"ell for SysOp and "Y"
was previously unused for anything else, and "O" is not reassigned to a new
function, BOTH "O" and "Y" will perform the same way. This will remain true
until the "O" command is reassigned.
PATH AND NAME OF MAIN MENU COMMAND TRANSLATION FILE:
Enter the PATH and NAME of the file to contain your TRANSLATION COMMAND file
for the MAIN menu. This file will contain all the command translation
information that you specify for the MAIN menu commands.
EXAMPLE: C:\FNET\FNSYS\MXL
After a PATH and NAME have been specified, you can then press F2 to EDIT your
command translation table for the MAIN menu. Pressing F2 will bring up the
following screen.
PATH AND NAME OF CONF (MESSAGE) MENU COMMAND TRANSLATION FILE:
Enter the PATH and NAME of the file to contain your TRANSLATION COMMAND file
for the MESSAGE menu. This file will contain all the command translation
information that you specify for the MESSAGE menu commands.
EXAMPLE: C:\FNET\FNSYS\CXL
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 49 ║
╚════════════════════════════════════════════════════════════════════════════╝
After a PATH and NAME have been specified, you can then press F2 to EDIT your
command translation table for the MESSAGE menu. For more information on this,
please see the previous section dealing with the MAIN MENU TRANSLATION FILE.
PATH AND NAME OF XFER (FILE) MENU COMMAND TRANSLATION FILE:
Enter the PATH and NAME of the file to contain your TRANSLATION COMMAND file
for the FILE menu. This file will contain all the command translation
information that you specify for the FILE menu commands.
EXAMPLE: C:\FNET\FNSYS\FXL
After a PATH and NAME have been specified, you can then press F2 to EDIT your
command translation table for the FILE menu. For more information on this,
please see the previous section dealing with the MAIN MENU TRANSLATION FILE.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 50 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - File Locations (1)
LOCATION OF MAIN BBS DIRECTORY:
Enter the Main directory for your BBS. This directory will contain all the
files to be shared by all nodes such as your FNET.EXE file etc. You can also
use this as your NODE 1 directory, but this is NOT advised. We suggest that
you have a separate directory for all nodes, even when running a single node
BBS system.
EXAMPLE: C:\FNET
PATH OF NODE WORK DIRECTORY:
Enter the work directory for this NODE. This directory MUST be unique to this
NODE and NO permanent files should ever be stored in this directory. The
contents of this directory are purged each call. Safeguards prohibit you from
selecting a BBS NODE or MAIN DIRECTORY as the work directory.
NOTE: A RAM disk ( at least 1 MB ) will greatly speed up the "work" done in
this directory but will limit your uploads to the size of the RAM disk.
EXAMPLE: C:\FNET\NODE1\WORK
PATH OF NODE HOME DIRECTORY:
Enter the directory in which this Node is to be operated from. It may be the
same as the main BBS directory (not recommended) provided no other Node is
already sharing the main BBS directory. You may NOT run multiple nodes from
the same directory.
EXAMPLE: C:\FNET\NODE1
PATH OF SECURITY LEVEL FILES:
Enter the directory where security level specific logon information files are
located.
EXAMPLE: C:\FNET\SECMSGS\
These files MUST be named according to the security level for which they are
intended and will be displayed during the logon sequence.
EXAMPLES: "10" "30" "50" "115" "255" (no quotes and no extensions)
NOTE: An example of a security level message would be a brief disclaimer
regarding policies or procedures displayed to new callers or outlining exactly
what the user does have access to at their security level and what they might
gain by upgrading to a higher one.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 51 ║
╚════════════════════════════════════════════════════════════════════════════╝
DUPLICATE UPLOAD "HOLD" DIRECTORY:
Enter the drive and directory where all uploaded files that duplicate files
already in the "upload directory" should be moved to. This prevents a user
from causing a file in the "upload" directory to be overwritten by a file with
the same name.
EXAMPLE: C:\FNET\FILES\HOLD\
FILE TO RUN BEFORE AND AFTER FILE TRANSFERS:
Enter the FULL path and name of a batch file to execute when a file transfer
(upload or download) is performed. This can allow you to do anything your
system might need to do prior to a file transfer such as enable or disable a
disk cache or stripping file comments from a file contained on a CD-ROM. If
configured, this file is run before a file transfer is performed After the
transfer is complete, this file is called once again with FEATHERNET PRO!
passing an ERRORLEVEL of 1 so that correct labeling can be used in the batch
file. Here you may re-enable or disable disk caches or whatever needs to be
done.
EXAMPLE: C:\FNET\XFERBAT.BAT
PATH OF THE PRIVATE FILE TRANSFER DIRECTORY:
Enter the Complete DOS Directory Path to the [P]rivate file transfer
directory. This directory will contain the PRIVATE files that authorized
users send to other authorized users.
EXAMPLE: C:\FNET\FILES\PVT\
NOTE: This will only be shown "If" you have the "Allow Private File Transfers"
flag set to "Y" found under General Information 2.
PATH AND NAME OF "FNETTEXT" FILE:
Enter the full DOS path and file name for the "FNETTEXT" file. This option
allows you to utilize a RAM drive for faster access to the file and less wear
and tear on your hard disk drive.
EXAMPLE: E:\FNET\FNSYS\FNETTEXT
PATH OF USER INDEX FILES:
Enter the DOS path to where the user index files (FNPNDX.x) are located. Enter
ONLY the sub directory where these files will be located.
EXAMPLE: C:\FNET\USERNDX
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 52 ║
╚════════════════════════════════════════════════════════════════════════════╝
PATH OF SPECIAL "HELP" FILES:
Enter the sub directory the "HELP" files will be kept. The files in this
directory are *.HLP files FEATHERNET PRO! displays for the command [H]. This
directory is also for the "special" help "H <FILENAME>" files that the SYSOP
creates for additional help. The users may read them by entering "H
<filename>" from the main BBS command prompt. The SYSOP should notify users
of these files by bulletin, news, hello file or by menus.
NOTE: The "special" help files function is ONLY usable from the MAIN BBS
command prompt.
EXAMPLE: C:\FNET\HELP\
PATH AND NAME OF "PWRD" FILE:
Enter the complete path and name of the PWRD file to use in this
configuration. The PWRD file determines the amount of time per day a user
gets based on his/her security level.
NOTE: A sample "PWRD" file is included with the BBS package.
EXAMPLE: C:\FNET\FNSYS\PWRD
Pressing the <F2> function key when the "PWRD" file path & name is being
edited in the above edit screen places you in the event editor (below).
WHILE ON THE "PWRD PATH AND NAME" OPTION, PRESS <F2> TO ENTER
THE PWRD SECURITY FILE CONFIGURATION EDITOR.
SECURITY LEVEL:
Enter a Security Level to configure. FEATHERNET PRO! searches for the
security level of the user at logon. If a "match" is found, the user is
assigned the specified time, k-byte, batch transfer limits, ratios, etc. as
specified for the "matched" security level.
NOTE: Only one entry per possible security level (0-255) should be entered as
FEATHERNET PRO! does not continue searching after a "match".
TIME ALLOWED ON SYSTEM:
Enter the number of minutes a caller whose security level matches the level
entered on the current line will be allowed on the system each day.
A caller whose security level equals or exceeds that which is specified for
unlimited daily time (Security Level Configuration) is not limited to any
amount of Time per Day. The time limit for such a user is per session. See
Also Security Level - System SysOp - Zeroing Time Each Login.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 53 ║
╚════════════════════════════════════════════════════════════════════════════╝
MAXIMUM K-BYTES TO DOWNLOAD TODAY:
Enter the maximum number of kilobytes (1024 bytes) that you wish to allow a
caller with the specified security level to be limited to on a daily basis.
These bytes are available provided the user has not reached/exceeded the
specified file or byte ratio requirements for this security level.
STANDARD BAUD RATE:
FEATHERNET PRO! allows you to specify a "standard" baud rate which will be
used to re-calculate the daily K-Byte download limit. You should only use an
anticipated CONNECT baud rate such as 300, 1200, 2400, 4800, 9600, 14400,
16,800, 19,200 or 28,800. If you do not wish to use this feature, it is
disabled by placing a zero in the field. If the "standard" baud rate is 2400
and a caller logs on at 9600 baud, his daily k-bytes will be adjusted to 4
times the value specified for the security level. (9600÷2400 = 4). If the
"standard" baud rate is 9600 and a caller logs on at 2400 baud, his daily
k-bytes will be adjusted to 1/4 the value specified for the security level.
(2400÷9600 = 1/4).
BATCH FILE TRANSFER LIMIT:
Enter the maximum number of files a user with the specified security level may
upload or download at one time utilizing the "batch" method. This value may be
from 1 TO 99.
FILE DOWNLOAD RATIO:
Enter the maximum download to upload FILE ratio to be permitted for this
security level. FEATHERNET PRO! monitors the file ratio continuously and
users are not permitted to exceed the maximum ratio at any time. Entering a
value of 7.5 here would allow users with this security level to download up to
7.5 files for every file uploaded. If 75 files were downloaded and 10 files
had been uploaded, the user would be at the maximum allowed file ratio. No
more downloads could occur until at least one more file was uploaded to the
system.
BYTE DOWNLOAD RATIO:
Enter the maximum download to upload BYTE ratio to be permitted for this
security level. FEATHERNET PRO! monitors the byte ratio continuously and
users are not permitted to exceed the maximum ratio at any time. Entering a
value of 7.5 here would allow users with this security level to download up to
7.5 bytes for every byte uploaded. If 750,000 bytes were downloaded and
100,000 bytes had been uploaded, the user would be at the maximum allowed byte
ratio. No more downloads could occur until at least enough bytes to decrease
the byte ratio have been uploaded to the system.
FILE DOWNLOAD LIMIT:
Enter the maximum number of files allowed to be downloaded from the system.
If this number is reached, FEATHERNET PRO! suspends downloading for the user
until such time the SysOp adjusts the users download counter or increases the
download limit.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 54 ║
╚════════════════════════════════════════════════════════════════════════════╝
K-BYTE DOWNLOAD LIMIT:
Enter the maximum number of K-bytes allowed to be downloaded from the system.
If this number is reached, FEATHERNET PRO! suspends downloading for the user
until such time the SysOp adjusts the users download counter or increases the
download limit.
WHILE INSIDE OF THE PWRD EDITOR PRESS <F2> TO SETUP THE SECOND PAGE OF
THE PWRD FILE.
FILE CREDITS:
You can allow new users to download files prior to uploading any by specifying
an initial upload credit. This value is used by FEATHERNET PRO! to imply
"files uploaded". It is added to all users files uploaded counter when
calculating the download to upload file ratio. Setting this value at 5 would
allow a user to download 50 files before a 10.0:1 file ratio was attained.
K-BYTE CREDITS:
You can allow new users to download files prior to uploading any by specifying
an initial upload k-byte credit. This value is used by FeatherNet to imply
"k-bytes uploaded". It is added to all user's k-bytes uploaded counter when
calculating the download to upload byte ratio.
Setting this value at 100 would allow a user to download 1000 k- bytes (1
megabyte) before a 10.0:1 byte ratio was attained.
USE HOURLY SUBSCRIPTION:
"Y" = Users with this security level will be paying by the hour. You will need
to use FNETSM to set the hourly cost and enter and moneys received. "N" =
Users with this security level will not be paying by the hour.
B-DAY DAYS:
FEATHERNET PRO! will verify the users BIRTHDATE every X number of calls for
added security on your system. Enter the number (0-99) of logins users with
this security level may achieve before being asked to verify their birthday.
A user will be given 4 chances to get the birthday right, if not correct, they
will FORCED to leave a message to the SysOp then logged off. The users call
counter will NOT be updated and thus will be asked the same question they
failed upon their next attempt to login to your system. Entering a "0" will
disable the BITHDATE verification for any particular security level.
PHONE DAYS:
FEATHERNET PRO! will verify the users PHONE NUMBER every X number of calls for
added security on your system. Enter the number (0- 99) of logins users with
this security level may achieve before being asked to verify their PHONE
NUMBER.. A user will be given 4 chances to get the PHONE NUMBER right, if not
correct, they will FORCED to leave a message to the SysOp then logged off.
The users call counter will NOT be updated and thus will be asked the same
question they failed upon their next attempt to login to your system. Entering
a "0" will disable the PHONE NUMBER verification for any particular security
level.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 55 ║
╚════════════════════════════════════════════════════════════════════════════╝
WHEN DONE PRESS <ESC> TO QUIT AND THEN SAVE YOUR INFORMATION. YOU WILL THEN
BE RETURNED TO THE FILE LOCATIONS (1) CONFIGURATION SCREEN.
SAVING THE "PWRD" CONFIGURATION FILE:
After you've finished editing the configuration file, press the <ESC> key and
it will ask you if you want to save the changes you have just made, if any.
This option defaults to "NO". Press <ENTER> if you do NOT want to save the
changes, otherwise enter a "Y" then the press <ENTER> to save all changes.
After you select one option or the other you will be returned to the
Conference Configuration Screen.
PATH & NAME OF QUOTE TEXT FILE:
Enter the path and filename of the file which contains the QUOTES you wish to
use on your BBS. These quotes will be displayed to users when they logon,
just prior to the Main Menu being shown.
The file must be formatted as:
# The number of Quotes in File
Quote text
Quote text
<BLANK LINE>
Quote text
<BLANK LINE> The BLANK line is the "terminator" marking the end of the Quote.
Quote text
Quote text
Quote text
Quote text
<END OF FILE TERMINATOR - NO BLANK LINE>
EXAMPLE: C:\FNET\DISP\QUOTES.BBS
PATH & NAME OF THE MULTI LANGUAGE LISTING FILE:
Enter the complete PATH & FILENAME for your multi language listing file. This
is the file that will contain all available FNETTEXT.XXX files. Each file must
have a unique file extension which will denote it from others. Once you enter
the path and file name, PRESS F2 TO ENTER THE CONFIGURATION EDITOR.
All multi language FNETTEXT.XXX files MUST be kept in the same directory as
your default FNETTEXT prompt file. The default FNETTEXT language is english.
FEATHERNET PRO! will look for the .ENG or FNETTEXT file with NO Extension for
default. Each unique FNETTEXT file you have must have to unique extension
(such as .TRK) similar to the one shown above in the Star Trek example. The
reasoning for this is two fold. FEATHERNET PRO! will know how to
differentiate between FNETTEXT files when a user selects one and it will allow
FEATHERNET PRO! to use MENU and DISPLAY files matched to the particular
extension chosen by the user.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 56 ║
╚════════════════════════════════════════════════════════════════════════════╝
SLOW DRIVE LETTERS:
Enter the letter(s) of any slow storage devices such as network servers,
CD-ROMS or multi-disk CD-ROMs. "HIJ" could be entered to indicate that files
found on drive H, I or J should be copied to the "Work Directory" on a hard
drive or ram disk prior to performing the file transfer. This will speed up
file transfer time for your users and also allow you to manipulate the file
with a batch file before the file transfer takes place. A batch file can be
configured (above) to run prior to the file transfer to perform tasks such as
stripping old and adding a new archive comment.
EXAMPLE: HIJ
PATH & NAME OF THE CO-SYSOP BIT MAP FILE:
Enter the path and name of the Co-SysOp BitMap file. This file would
generally be located in the BBS home directory. It is conceivable that a
SysOp might want to have different Conference Configurations for different
nodes. The Co-SysOp BIT map's are used to specify which users may be
Co-SysOps in a given Conference. If designated as a Co-SysOp for a given
conference the user may do the following in that conference: EDIT ANY
Messages, Read ANY Messages, KILL ANY Messages.
EXAMPLE: C:\FNET\FNSYS\COSYSOP.BIT
PATH & NAME OF THE USERS INFORMATION FILE:
Enter the path and name for the USERS information file. This file contains
hourly subscription information for each user and additional personal data
both the user and SysOp enter.
EXAMPLE: C:\FNET\FNSYS\FNUSERS.INF
PATH & NAME OF THE PROTOCOL DATA FILE:
Enter the path and name of the FNETPROT.DAT File. The file may be shared by
ALL nodes. You should leave it in the "\FNSYS" sub directory unless something
unique about your system requires it to be located elsewhere. FNETPROT.DAT
contains information FeatherNet uses for file transfer protocol
implementation. Its structure and detailed description are in the
documentation.
EXAMPLE: C:\FNET\FNSYS\FNETPROT.DAT
PATH & NAME OF THE "TRASH" FILE:
Enter the path and name of the TRASH File. The file should be in the same
location for ALL nodes. You should leave it in the "\FNSYS" sub directory
unless something unique about your system requires it to be located elsewhere.
The file contains names "LOCKED OUT" of the system or those names you do not
wish to be able to log in to the system.
EXAMPLE: C:\FNET\FNSYS\TRASH
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 57 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - File Locations Screen 2
MAIN MENU FILE:
Enter the path and name of the Main Menu File. This is the file users see at
the main BBS command prompt when in non-expert mode or when they enter the [?]
command at the main BBS command prompt.
EXAMPLE: C:\FNET\MENU\MM
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: MM would be shown to non-ANSI users
MM would be shown to ANSI users
MM110R would be shown to RIP users with a security level of 110
SYSOP'S MAIN MENU FILE:
Enter the path and name of the SysOp's Main Menu File. This is the file the
SysOp sees at the main BBS command prompt when in non-expert mode or when the
[?] command is executed at the main BBS command prompt.
EXAMPLE: C:\FNET\MENU\MMS
CONFERENCE COMMAND MENU FILE:
Enter the path and name of the Conference Menu Text File. This is the file
users see at the conference command prompt when in non-expert mode (or hitting
a 'J' at the Main, File, or Message Menus) or when they enter the [?] command
at the conference command prompt. This menu will show the user the message
command menu choices available on your BBS.
EXAMPLE: C:\FNET\MENU\CM
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: CM would be shown to non-ANSI users
CMG would be shown to ANSI users
CM110R would be shown to RIP users with a security level of 110
SYSOP'S CONFERENCE COMMAND MENU FILE:
Enter the path and name of the SysOp's Conference Menu Text File. This is the
file you will see at the conference command prompt when in non-expert mode or
when you enter the [?] command at the conference command prompt. This menu
will show the message command menu choices available on your BBS.
EXAMPLE: C:\FNET\MENU\CMS
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 58 ║
╚════════════════════════════════════════════════════════════════════════════╝
PATH & NAME OF THE CONFERENCE LISTING MENU:
Enter the path and name of the file to be displayed to users when the [J]
command is invoked to JOIN a conference. This menu will show the users what
CONFERENCES are available on your BBS.
EXAMPLE: C:\FNET\MENU\CL
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: CL would be shown to non-ANSI users
CLG would be shown to ANSI users
CL110R would be shown to RIP users with a security level of 110
FILE TRANSFER MENU FILE:
Enter the path and name of the File Transfer Menu Text File. This is the file
users see at the File Transfer command prompt when in non-expert mode or when
they enter the [?] command at the File Transfer command prompt. This menu
will show the users what commands are available on your BBS for file
transfers.
EXAMPLE: C:\FNET\MENU\FM
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: FM would be shown to non-ANSI users
FMG would be shown to ANSI users
FM110R would be shown to RIP users with a security level of 110
SYSOP'S TRANSFER MENU FILE:
Enter the path and name of the SysOp's File Transfer Menu Text File. This is
the file you see at the File Transfer command prompt when in non-expert mode
or when you enter the [?] command at the File Transfer command prompt. This
menu shows the you what commands are available on your BBS for file transfers.
EXAMPLE: C:\FNET\MENU\FMS
SCRIPT QUESTIONNAIRE MENU FILE:
Enter the path and name of the Script Questionnaire Menu Text File. This is
the file users see after entering [Q] from the main menu to list the available
questionnaires to answer.
EXAMPLE: C:\FNET\QUES\QUES
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 59 ║
╚════════════════════════════════════════════════════════════════════════════╝
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: QUES would be shown to non-ANSI users
QUESG would be shown to ANSI users
QUES110R would be shown to RIP users with a security level of 110
NEWUSER SCRIPT FILE NAME:
Enter the path and name of the NEWUSER questionnaire. This is presented to a
new user after he/she completes the BBS' new user registration edits.
EXAMPLE: C:\FNET\QUES\SCRIPT.0
NOTE: FEATHERNET PRO! will ask for all information needed to complete the user
fields in the System Manager (FNETSM) before this file is called. This script
is for additional information that you might want. You may want to review the
questions FEATHERNET PRO! already asks before answering this question. You
may review the questions already present by doing a User Local Logon and
entering a new user name at the prompt.
SCRIPT QUESTIONNAIRES:
Enter the location of the script questionnaires. This is where FeatherNet
will look for the script questions you create to ask your users when they
enter [Q] from the Main Menu.
EXAMPLE: C:\FNET\QUES\
PRELOG FILE:
Enter the path and name of the Pre-Logon Display File. This file is displayed
at logon immediately after a user selects to use graphics mode or non-graphics
mode and BEFORE they are asked for their name.
EXAMPLE: C:\FNET\DISP\PRELOG
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: PRELOG would be shown to non-ANSI users
PRELOGG would be shown to ANSI users
PRELOGR would be shown to RIP users
NEWS FILE:
Enter the path and name of the News Display File. This file is displayed at
logon immediately after a user enters his/her password. It is ONLY displayed
if the file date/time is more recent that the date/time of the caller's last
use of the BBS.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 60 ║
╚════════════════════════════════════════════════════════════════════════════╝
EXAMPLE: C:\FNET\DISP\NEWS
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: NEWS would be shown to non-ANSI users
NEWSG would be shown to ANSI users
NEWSR would be shown to RIP users
HELLO FILE:
Enter the path and name of the Welcome Display File. This file is displayed
at logon immediately after the NEWS file.
EXAMPLE: C:\FNET\DISP\HELLO
EXCEPTION! EXCEPTION! EXCEPTION!
This display file should be no more than FIVE (5) CHARACTERS! This is so that
the actual filenames can have a numeric identifier 1-99 (2 characters max.)
and a graphics identifier (1 character) attached to them. NO FILE EXTENSIONS
ARE ALLOWED ON DISPLAY FILES (EXCEPTION TO LANGUAGE SPECIFIC).
EXAMPLES: HELLO1 would be shown to non-ANSI users
HELLO32G would be shown to ANSI users
HELLO99R would be shown to RIP users
The HELLO file allows the SysOp to STACK screens but if you do, the first
screen MUST have the numeric identifier of 1 and the rest must follow in
order. FEATHERNET PRO! will keep displaying Hello screens as long as it finds
them.
EXAMPLES: HELLO1 <Will Be Displayed>
HELLO2 <Will Be Displayed>
HELLO3 <Will Be Displayed>
HELLO5 <DOES NOT DISPLAY THIS BECAUSE THERE IS NO #4>
NOTE: There are NO SECURITY specific HELLO display files. See File Locations
Screen One, Location of Security Level Files, for more information.
NEWUSER FILE:
Enter the path/name of the NEWUSER Display File. This file is displayed to
NEW users after they fill in the registration questions and the new
registration questionnaire.
EXAMPLE: C:\FNET\DISP\NEWUSERG (graphics file)
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 61 ║
╚════════════════════════════════════════════════════════════════════════════╝
EXAMPLES: NEWUSER would be shown to non-ANSI users
NEWUSERG would be shown to ANSI users
NEWUSERR would be shown to RIP users
CLOSED BBS FILE:
Enter the path and name of the CLOSED Display File. This file is displayed to
NEW callers if the BBS is operated in a "CLOSED" mode. Unregistered callers
will be allowed to answer the new registration questions. Then this file will
be displayed and the users logged off.
EXAMPLE: C:\FNET\DISP\CLOSED
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: CLOSED would be shown to non-ANSI users CLOSEDG would be shown to
ANSI users CLOSEDR would be shown to RIP users
CALLER LOG FILE:
Enter the path and name of the CALLER log file for this node. This file
contains information about what each user on the system does or attempts to
do.
EXAMPLE: C:\FNET\LOGS\CALLER1
NOTE: There is no graphics version of this SYSTEM file.
LOGOFF FILE:
Enter the path and name of the LOGOFF display file. This file is displayed at
logoff after a user enters the [G] command to log off the system.
EXAMPLE: C:\FNET\DISP\LOGOFF
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: LOGOFF would be shown to non-ANSI users
LOGOFFG would be shown to ANSI users
LOGOFFR would be shown to RIP users
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 62 ║
╚════════════════════════════════════════════════════════════════════════════╝
TODAY FILE (if used):
Enter the path and name of the TODAY Display File. This file is displayed if
you have enabled the "TODAY" function. The program TODAY.EXE (or some version
thereof) creates this file. TODAY.EXE may be run from the $$LOGON.BAT file
during logon or during an event. If you are running your system under a
"front end" you may opt to run the TODAY.EXE from the batch file you start
FeatherNet with (SFN.BAT).
EXAMPLE: C:\FNET\DISP\TODAY
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: TODAY would be shown to non-ANSI users
TODAYG would be shown to ANSI users
TODAYR would be shown to RIP users, if your TODAY program
supports RIP.
USER STATISTICS FILE:
Enter the path and name of the USER STATISTICS Display File. This file is
displayed when a user logs onto the BBS and where you have the DISPLAY USER
STATS FILE TO USER UPON LOGON option set to "Y" or when he/she enters the [V]
command from the main BBS command prompt.
EXAMPLE: C:\FNET\DISP\USRSTAT
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: USRSTAT would be shown to non-ANSI users
USRSTATG would be shown to ANSI users
USRSTATR would be shown to RIP users
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 63 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - File Locations Screen 3
POST UPLOAD FILE:
Enter the Path and Name of a file to display after a successful upload.
EXAMPLE: C:\FNET\DISP\POSTUP
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: POSTUP would be shown to non-ANSI users
POSTUPG would be shown to ANSI users
POSTUPR would be shown to RIP users
FAILED UPLOAD FILE:
Enter the Path and Name of a file to display after an unsuccessful upload.
EXAMPLE: C:\FNET\DISP\FAILUP
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: FAILUP would be shown to non-ANSI users
FAILUPG would be shown to ANSI users
FAILUPR would be shown to RIP users
POST DOWNLOAD FILE:
Enter the Path and Name of a file to display after a successful download.
EXAMPLE: C:\FNET\DISP\POSTDN
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: POSTDN would be shown to non-ANSI users
POSTDNG would be shown to ANSI users
POSTDNR would be shown to RIP users
FAILED DOWNLOAD FILE:
Enter the Path and Name of a file to display after an unsuccessful download.
EXAMPLE: C:\FNET\DISP\FAILDN
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 64 ║
╚════════════════════════════════════════════════════════════════════════════╝
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: FAILDN would be shown to non-ANSI users
FAILDNG would be shown to ANSI users
FAILDNR would be shown to RIP users
PATH OF THE "FREE" DOWNLOAD LISTING FILE:
Enter the path and file name for your FREE LISTING file. This is the file
that will contain the list of all your FREE file directories and/or filenames.
EXAMPLE: C:\FNET\FILES\FREE.LST
PRESS F2 to enter the FILE DIRECTORIES and/or FILE NAMES that will bet FREE
DOWNLOADS.
Enter the complete path and sub directory names in which all "FREE" download
files will be located. You may also enter a particular filename to be a free
file by giving the path and filename instead of just a directory. "FREE"
downloads are those files which users may download and NOT be charged for
against their BYTE or FILE ratio/count. You may also set the area not to
charge against the users TIME limit. You may have 512 FREE areas and/or
filenames per conference for a maximum of 2,097,152 FREE areas.
Some suggestions of FREE DOWNLOAD areas might be:
1: The rule files for your BBS
2: Application files for your BBS
3: RIP Icons for your BBS
4: File Listings for your BBS
5: Distribution Site Files
PATH OF THE "PAID" DOWNLOAD LISTING FILE:
Enter the path and file name for your PAID LISTING file. This is the file
that will contain the list of all your PAID file directories and/or filenames.
EXAMPLE: C:\FNET\FILES\PAID.LST
PRESS F2 to enter the FILE DIRECTORIES and/or FILE NAMES that will bet PAID
DOWNLOADS.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 65 ║
╚════════════════════════════════════════════════════════════════════════════╝
Enter the complete path and sub directory names in which all "PAID" download
files will be located. You may also enter a particular filename to be a PAID
file by giving the path and filename instead of just a directory. "PAID"
downloads are those files which users may download AT A CHARGE! You may charge
for the file being downloaded per Kilobyte, by file or both. You will notice
that the per Kilobyte charge space is brought out to 5 decimal places, this is
so that you can charge as little as 1 cent per Megabyte. Users MUST have
enough money in their account (SEE FNETSM) to download the specified file
otherwise they will be denied download rights to it. Once the paid file is
downloaded successfully, the charge will be deducted from their accounts. You
may also set a PASSWORD for each PAID download area or FILENAME specified for
added security. You may have 1024 PAID file areas/filenames.
Some suggestions of PAID DOWNLOAD areas might be:
1: On-line magazines
2: On-line stories
3: General file download charge
4: Adult files
5: Program Authors Registration
GROUP CHAT MENU:
Enter the full path and name of the menu to be displayed when a user selects
the Group Chat function. This file may be ASCII, ANSI or RIP so the file name
must be kept to 4 or fewer characters to allow for the security level of the
caller to be added in case you want some security level specific Group Chat
Menus.
EXAMPLE: C:\FNET\MENU\CHTM
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: CHTM would be shown to non-ANSI users
CHTMG would be shown to ANSI users
CHTM110R would be shown to RIP users with a security level of 110
LOCATION OF CHAT RELATED FILES:
Enter the path to the chat related files. This path is where the chat data
files will be created by FeatherNet.
EXAMPLE: C:\FNET\FNSYS\
EXPIRED WARNING FILE:
Enter the path and name of the EXPIRED WARNING display File. This file is
displayed at logon if the BBS is run in a subscription mode and the user's
expiration is within the number of days specified in the
modem/subscription/node configuration.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 66 ║
╚════════════════════════════════════════════════════════════════════════════╝
EXAMPLE: C:\FNET\DISP\EXPWARN
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: EXPWARN would be shown to non-ANSI users
EXPWARNG would be shown to ANSI users
EXPWARNR would be shown to RIP users
EXPIRED FILE:
Enter the path and name of the EXPIRED Text File. This file is displayed at
logon if the BBS is run in a subscription mode and the user's account is
expired.
EXAMPLE: C:\FNET\DISP\EXPIRED
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: EXPIRED would be shown to non-ANSI users
EXPIREDG would be shown to ANSI users
EXPIREDR would be shown to RIP users
PRE-DOWNLOAD WARNING FILE:
Enter the path/name of the DOWNLOAD WARNING Display File. This file is
displayed when a user enters [D] to download a file from the file transfer
command prompt.
EXAMPLE: C:\FNET\MENU\PREDN
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: PREDN would be shown to non-ANSI users
PREDNG would be shown to ANSI users
PREDNR would be shown to RIP users
PRE-UPLOAD WARNING FILE:
Enter the path/name of the UPLOAD WARNING Display File. This file is
displayed when a user enters [U] to upload a file to the BBS from file
transfer command prompt.
EXAMPLE: C:\FNET\DISP\PREUP
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 67 ║
╚════════════════════════════════════════════════════════════════════════════╝
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: PREUP would be shown to non-ANSI users
PREUPG would be shown to ANSI users
PREUPR would be shown to RIP users
PROHIBITED WORDS WARNING FILE:
Enter the path and name of a file to be displayed to a user when a
"prohibited" word is used when entering a message. This file is used *only*
if the affected conference has a "Prohibited Words" data file defined
(conference configuration editor).
EXAMPLE: C:\FNET\DISP\CUSWORD
NOTE: All DISPLAY file names should be NO MORE THAN SEVEN (7) CHARACTERS! This
is so that the actual file names can have a graphics identifier (1 character)
attached to them. NO FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES (EXCEPTION
TO LANGUAGE SPECIFIC).
EXAMPLES: CURWORD would be shown to non-ANSI users
CUSWORDG would be shown to ANSI users
CUSWORDR would be shown to RIP users
PATH & NAME OF FNCONF.@@@:
Enter the path and name of the FNCONF.@@@ file. Nodes can share this file if
desired. It must be flagged as READ only to be used by more than one node.
EXAMPLE: C:\FNET\FNSYS\FNCONF.@@@
PATH & NAME OF FNCONF.LST FILE:
Enter the path and name of the FNCONF.LST file. This is a straight ASCII text
file created by FNCFG to facilitate quickly determining if a NAME entered for
a conference to join is that of a conference the user is allowed to join.
EXAMPLE: C:\FNET\FNSYS\FNCONF.LST
PATH AND NAME OF USERS FILE:
Enter the path and name of the USERS File. The file *must* be in the same
location for ALL nodes. You should leave it in the "\FNSYS" sub-directory
unless something unique about your system requires it to be located elsewhere.
EXAMPLE: C:\FNET\FNSYS\USERS
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 68 ║
╚════════════════════════════════════════════════════════════════════════════╝
PATH AND NAME OF FNEXTUSR FILE:
Enter the path and name of the FNEXTUSR File. The file MUST be in the same
location for ALL nodes. You should leave it in the "\FNSYS" sub directory
unless something unique about your system requires it to be located elsewhere.
FNEXTUSR is used when more than 40 conferences are configured. It is
maintained by FNCFG and the FeatherNet MAIN executable (FNET.EXE).
EXAMPLE: C:\FNET\FNSYS\FNEXTUSR
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 69 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Security Files - System/SysOp
SECURITY LEVEL TO USE THE [CALL] COMMAND:
Enter the security level (0-255) required to use the [CALL] command from the
Main BBS prompt to view the CALLER log file. Discretion is recommended.
[F]ILE TRANSFER AREA SECURITY LEVEL:
Enter the security (0-255) level required to use the [F] command from the main
BBS menu or from a conference to enter the file transfer area.
SECURITY LEVEL FOR THE [H]ELP COMMAND:
Enter the security level (0-255) required to use the [H] command from the
MAIN, CONFERENCE and FILE TRANSFER prompts to view the system HELP files.
SECURITY LEVEL TO [J]OIN A CONFERENCE:
Enter the security level (0-255) required to use the [J] command to Join a
Conference.
SECURITY LEVEL TO [K]ILL ANY MESSAGE:
Enter the security level (0-255) required to KILL any message in any
conference on the system. A user with this security level may also:
Execute a DOS command. Edit his/her Security Level field by using the [I]
command from the Main BBS Prompt. Change the [S] Status of any message to/from
PUBLIC and RECEIVER ONLY. Enter Messages to a SPECIFIC Security Level (@###@)
or a range of Security Levels (@##-#@). Allow ONLY a Co-SysOp or VERY CLOSE
Associate to use these commands.
SECURITY LEVEL TO USE TOGGLE E[X]PERT MODE:
Enter the security level (0-255) required to use the [X] command to Toggle
Expert mode ON/OFF.
SECURITY LEVEL TO USE [*] GLOBAL NEW MESSAGE READ:
Enter the security level (0-255) required to use the [*] command from the
Conference or Main BBS prompts to perform a GLOBAL new message read scan.
SECURITY LEVEL TO CARBON COPY MESSAGES:
Enter the security level (0-255) required for a user to send a "Carbon Copy"
of a message to another user. A user with sufficient security level can send
as many "CC" messages as he or she wishes.
SECURITY LEVEL TO EDIT ANY MESSAGE:
Enter the security level (0-255) required to EDIT any message he/she reads.
This is another VERY Powerful command and much discretion is warranted. Allow
ONLY a Co-SysOp or VERY Close Associate to use this command.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 70 ║
╚════════════════════════════════════════════════════════════════════════════╝
SECURITY LEVEL TO EDIT YOUR MESSAGES:
Enter the security level (0-255) required for a user to EDIT his/her OWN
messages. This command can also be viewed as allowing a user to KILL a
message since the entire contents may be discarded. Discretion Recommended.
SECURITY LEVEL TO USE "@" MACROS IN MESSAGES:
Enter the security level (0-255) required to use the "@" variables in the
message conferences.
NOTE: Many ECHO MAIL networks do not allow the use of these so discretion is
strongly recommended.
NEW USER SECURITY:
Enter the security level to be assigned new users (0-255). This security level
MUST also be included in the "PWRD" file. See the section on the PWRD earlier
in this documentation.
SECURITY LEVEL TO READ ALL MAIL & COMMENTS:
Enter the security level (0-255) required to use read ALL messages and
COMMENTS. It is strongly recommended you reserve this privilege for users you
have unquestionable faith in such as a Co-SysOp or business partner.
SECURITY LEVEL TO ZERO TIME AT EACH LOGON:
Enter the security level (0-255) required for a user to receive unlimited
daily time on the system. A user with this privilege has his "time on today"
counter automatically reset to ZERO (0) each time he/she logs onto the system.
ALLOW QUICK LOGONS:
Enter the minimum security level allowed for users to make use of the Quick
Logon option.
EXAMPLE: 60
This option allows users to skip all the hello, news, and bulletin files when
logging into the system. To use this option they must enter an [*] before
their first name when logging on.
EXAMPLE: Please enter your First and Last name? : *Joe User
No space between the * and First Name - Discretion Warranted!
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 71 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Security Levels - Main Menu
SECURITY LEVEL TO VIEW [B]ULLETIN MENU:
Enter the security level (0-255) required to list bulletins.
SECURITY LEVEL TO LEAVE A [C]OMMENT:
Enter the security level (0-255) required to Leave a COMMENT to the SysOp.
SECURITY LEVEL FOR THE [D]OOR COMMAND:
Enter the security level (0-255) required to use the [D] command from the MAIN
BBS prompt to OPEN a DOOR.
SECURITY LEVEL TO EDIT USER [I]NFORMATION:
Enter the security level (0-255) required to use the [I] command from the MAIN
BBS prompt to edit user information.
IMPORTANT!
ANY user with at least this security level can edit the PASSWORD, PHONE #'s
and CITY/STATE fields of his/her user record. It is recommended you allow
ONLY mature users to use this command as it permanently alters the above
fields in the user's record in the USERS file.
SECURITY LEVEL TO USE THE [O]PERATOR PAGE COMMAND:
Enter the security level (0-255) required to use the [O] command from the Main
BBS prompt to the System Operator for a CHAT Session.
SECURITY LEVEL TO USE THE [P]AGE LENGTH COMMAND:
Enter the security level (0-255) required to use the [P] command from the Main
BBS prompt to adjust the default screen size.
SECURITY LEVEL TO USE THE [Q]UESTIONNAIRE COMMAND:
Enter the security level (0-255) required to use the [Q] command from the Main
BBS prompt to answer the script questionnaires.
SECURITY LEVEL TO [S]ELECT COLOR GRAPHICS:
Enter the security level (0-255) required to use the [S] command from the Main
BBS prompt to toggle the color graphics mode (ASCII/ANSI ONLY, this command
will not affect RIP Mode).
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 72 ║
╚════════════════════════════════════════════════════════════════════════════╝
VIEW [T]ODAY'S CALLERS SECURITY LEVEL:
Enter the Security level (0-255) required to utilize the command [T]oday's
callers from the main menu area.
SECURITY LEVEL TO LIST SYSTEM [U]SERS COMMAND:
Enter the Security level (0-255) required to list users with the [U] Command
from the Main Menu.
SECURITY LEVEL TO [V]IEW SELECTED STATISTICS:
Enter the security level (0-255) required to use the [V] command from the Main
BBS prompt to view selected personal statistical information. The information
displayed is in a file created by the System Operator.
SECURITY LEVEL TO VIEW THE [W]ELCOME FILE:
Enter the security level (0-255) required to use the [W] command from the
Main BBS prompt to view the Welcome file.
SECURITY LEVEL TO USE [VER] BBS VERSION COMMAND:
Enter the security level (0-255) required to use the [VER] command from
the Main BBS prompt to list the BBS Version information.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 73 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Security Levels - File Menu
[D]OWNLOAD SECURITY LEVEL:
Enter the security level (0-255) required to use the [D] command from
the file transfer area to "DOWNLOAD" files from the BBS to the user's
system.
SECURITY LEVEL TO VIEW LOGGED [F]ILE DIRECTORY:
Enter the security level (0-255) required to use the [L] command from the File
Transfer prompt to view the currently LOGGED file directory listing.
SECURITY LEVEL TO SEARCH FOR [N]EW FILES:
Enter the security level (0-255) required to use the [N] command from the File
Transfer prompt to search for new files from a specified (or given) date.
SECURITY LEVEL TO [TP] CHANGE TRANSFER PROTOCOL:
Enter the security level (0-255) required to use the [TP] command from the
Main BBS and File Transfer prompts to change the default file transfer
protocol.
[U]PLOAD SECURITY LEVEL:
Enter the security level (0-255) required to use the [U] command from the file
transfer area to "UPLOAD" files to the BBS from the user's system.
SECURITY LEVEL TO [V]IEW ARCHIVES:
Enter the security level (0-255) required to use the [V] command from the File
Transfer prompt to VIEW file archive contents and perform manipulations [R]ead
or [D]ownload thereon.
SECURITY LEVEL FOR [Z]IPPY DIRECTORY SEARCH:
Enter the security level (0-255) required to use the [Z] Zippy File directory
search to locate any text within the file descriptions.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 74 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Security Levels - Message Menu
SECURITY LEVEL TO [A]RCHIVE & DOWNLOAD MAIL:
Enter the security level (0-255) required to archive and download mail.
SECURITY LEVEL REQUIRED TO [K]ILL A MESSAGE:
Enter the security level (0-255) required to KILL a message addressed TO or
written BY a user.
SECURITY LEVEL TO [S/SS] SCAN SUPERSCAN MESSAGES:
Enter the security level (0-255) required to use the [S/SS] commands from the
Conference prompt to perform the [S] Scan and [SS] SuperScan of messages.
SECURITY LEVEL TO [U]PDATE SET CONFERENCE SCANS:
Enter the security level (0-255) required to use the [U] command from the
Conference prompt to UPDATE the Conferences to be scanned when using the [*]
Global New Mail Read Command.
ATTACH FILE TO MESSAGE [SA] SECURITY LEVEL:
Enter the security level required to "attach" a file to a message. The user
can upload a file which will be placed in the conference's ATTACHMENT
directory (if configured to allow file attachments in the conference). The
level must be (0-255). Allowing file attachments is an excellent way to permit
repetitious uploading of the same file while preserving each file by uniquely
renaming it (troubleshooting/developing).
DOWNSIDE! Users could potentially utilize the function to carry on illegal
uploading & downloading of software. Monitor its use on your system closely.
(SEE ALSO: PRIVATE FILE TRANSFERS - FNETSM & GENERAL INFORMATION 2)
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 75 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Function Key Programming
SHIFTED FUNCTION KEY ASSIGNMENTS:
You may enter up to ten SHIFTED function key assignments. These "strings" may
be entered at the local keyboard instead of having to type the text in each
time.
EXAMPLE: F N S A^M - Show you FILES NEW SCAN ALL <ENTER>
EXAMPLE: Joe SysOp^M - This would place your signature in a
Generic BBS^M - message for you.
123-1234^M
The ^M is interpreted the same as Pressing the <ENTER> key.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 76 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - Setting Message Header & Text Entry Colors
FEATHERNET PRO! allows you to control the colors of your Message headers and
text entry prompts by setting the colors here in the editor. Standard ANSI
color format is used (SEE APPENDIX: MACROS and COLOR CODES for more
information). Keep in mind that the color you chose will be for the entire
line across the screen in the message header, and only for the area where
users INPUT information for text entry. You may want to experiment with color
combinations to find the colors that suits you best.
COLOR FOR MESSAGE HEADER "CONFERENCE:" LINES:
Enter the color that you want to appear on the CONFERENCE NAME line.
COLOR FOR MESSAGE HEADER "DATE:" LINES:
Enter the color that you want to appear on the MESSAGE DATE line.
COLOR FOR MESSAGE HEADER "TO:" LINES:
Enter the color that you want to appear on the TO line.
COLOR FOR MESSAGE HEADER "FROM:" LINES:
Enter the color that you want to appear on the FROM line.
COLOR FOR MESSAGE HEADER "SUBJECT:" LINES:
Enter the color that you want to appear on the SUBJECT line.
DEFAULT COLOR FOR TEXT ENTRY PROMPTS:
Enter the color that you want to appear when the user inputs text at a prompt.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 77 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCFG - .QWK Configuration
FEATHERNET PRO! includes a built in .QWK Mail system for your users to easily
download new mail and upload replies into your system. The FEATHERNET PRO!
internal .QWK mail system is NOT meant for hubing mail on QWK Mail networks.
It is simply a means for your users to easily read mail off-line with any
standard .QWK mail reader system. If you need to hub a .QWK mail network, we
suggest you take a look at RNET, a shareware package that is compatible with
FEATHERNET PRO!
YOUR BBS NET ID:
Enter an ID that your BBS will use for .QWK and .REP packets. Your NET ID must
be between 1-8 characters in length. .QWK packets will be created for your
users using this ID and all users .REP packets must be uploaded using this ID.
CITY/STATE YOUR BBS IS LOCATED IN:
Enter the City and State that your BBS is located in.
THE PHONE NUMBER OF YOUR BBS:
Enter the phone number of your BBS.
LOCATION/NAME OF THE CRC 32 DUPLICATE DATABASE FILE:
If set, this will enable CRC 32 Duplicate checking of all new uploaded REP
packets to your system. If no path and filename is given, no duplicate
checking will occur.
SUB DIRECTORY TO COPY QWK PACKETS TO FOR LOCAL USE:
Enter the path that you wish QWK packets to be copied to when created. This
may NOT be a work directory or a RAM drive. This is a required field. This
is the directory your off-line mail reader will use to read your QWK packets.
SUB DIRECTORY TO COPY REP PACKETS FROM LOCALLY:
Enter the path that you wish REP packets to be copied FROM. This may NOT be a
work directory or a RAM drive. This is a required field. This should be the
directory your off-line mail reader creates your REP packets in.
LOCATION/NAME OF HELLO FILE TO INCLUDE:
Enter the path and filename of the HELLO file you would like included in all
.QWK packets. Leaving this blank disables the function.
LOCATION/NAME OF NEWS FILES TO INCLUDE:
Enter the path and filename of the HELLO file you would like included in all
.QWK packets. Leaving this blank disables the function.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 78 ║
╚════════════════════════════════════════════════════════════════════════════╝
LOCATION/NAME OF GOODBYE FILE TO INCLUDE:
Enter the path and filename of the HELLO file you would like included in all
.QWK packets. Leaving this blank disables the function.
LOCATION/NAME OF YOUR QWK MENU DISPLAY FILE:
Enter the path and filename of the MENU file to display all the QWK menu
functions.
EXAMPLE: C:\FNET\MENU\QWKM
NOTE: All MENU file names should be NO MORE THAN FOUR (4) CHARACTERS! This is
so that the actual file names can have a security level (3 characters) and a
graphics identifier (1 character) attached to them. NO FILE EXTENSIONS ARE
ALLOWED ON MENU FILES.
EXAMPLES: QWKM would be shown to non-ANSI users
QWKMG would be shown to ANSI users
QWKM110R would be shown to RIP users with a security level of 110
NUMBER OF MESSAGES < OR = TO 2400 BAUD CALLERS CAN DOWNLOAD:
Enter the number (0-32000) of messages 300 to 2400 baud callers may download.
Because of time limitations, you may want to limit lower speed callers to
downloading fewer messages to give other callers a chance at your system. You
may want to experiment with the number of messages different baud rate can
download in a given amount of time and then set these numbers according to
your preference.
NUMBER OF MESSAGES 2400+ - 4800 BAUD CALLERS CAN DOWNLOAD:
Enter the number (0-32000) of messages 2400 to 4800 baud callers may download.
Because of time limitations, you may want to limit lower speed callers to
downloading fewer messages to give other callers a chance at your system. You
may want to experiment with the number of messages different baud rate can
download in a given amount of time and then set these numbers according to
your preference.
NUMBER OF MESSAGES 4800+ - 9600 BAUD CALLERS CAN DOWNLOAD:
Enter the number (0-32000) of messages 4800 to 9600 baud callers may download.
Because of time limitations, you may want to limit lower speed callers to
downloading fewer messages to give other callers a chance at your system. You
may want to experiment with the number of messages different baud rate can
download in a given amount of time and then set these numbers according to
your preference.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 79 ║
╚════════════════════════════════════════════════════════════════════════════╝
NUMBER OF MESSAGES 9600+ - 14400 BAUD CALLERS CAN DOWNLOAD:
Enter the number (0-32000) of messages 9600 to 14400 baud callers may
download. Because of time limitations, you may want to limit lower speed
callers to downloading fewer messages to give other callers a chance at your
system. You may want to experiment with the number of messages different baud
rate can download in a given amount of time and then set these numbers
according to your preference.
NUMBER OF MESSAGES 14400+ BAUD CALLERS CAN DOWNLOAD:
Enter the number (0-32000) of messages greater than 14400 baud callers may
download. Because of time limitations, you may want to limit lower speed
callers to downloading fewer messages to give other callers a chance at your
system. You may want to experiment with the number of messages different baud
rate can download in a given amount of time and then set these numbers
according to your preference.
YOUR TAGLINE:
Enter the TAGLINE that you would like to appear at the bottom of each one of
the messages EXPORTED from your system. The TAGLINE may be up to 60
characters in length and typically includes your BBS Name, City/State, and
primary BBS phone number.
FNCFG - Saving the CONFIGURATION
When <ESC> is pressed from the FNCFG main menu and you answer "Y" to the "Save
Configuration" screen. Answer "Y" to Quit and "Y" to save your configuration.
The present configuration is then saved and the file paths in the
configuration will be verified.
Note: Pressing "Q" will cause FNCFG to perform a "QUICK" save which
verifies/creates NO paths/files. Use this save option if you make
changes in your configuration which DO NOT modify any paths or file
names.
Any DOS Sub directories not present will be created.
All conference file paths and file names are verified.