home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR3
/
FN102UPG.ZIP
/
FNP102.DOC
< prev
next >
Wrap
Text File
|
1994-01-20
|
700KB
|
15,932 lines
█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
█ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ █
█ █ █ █
█ █ W E L C O M E T O █ █
█ █ ═══╗ ╔═╗ ╦═╗ ╔═╗ ╔╦╗ ╦ ╦ ╔═╗ ╦═╗ ╔╗╔ ╦═╗ ╔╦╗ ╔═══ █ █
█ █ ═════╣ ╠═ ╠═ ╠═╣ ║ ╠═╣ ╠═ ╠╦╝ ║║║ ╠═ ║ ╠═════ █ █
█ █ ═══╝ ╩ ╩═╝ ╩ ╩ ╩ ╩ ╩ ╚═╝ ╩╚╝ ╝╚╝ ╚═╝ ╩ ╚═══ █ █
█ █ PRO! v1.02 █ █
█ █ █ █
█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ █
█▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
Copyright 1993 by FeatherNet Software, Inc. All Rights Reserved
FEATHERNET PRO!
PROFESSIONAL BULLETIN BOARD SOFTWARE
VERSION 1.02
FeatherNet PRO! v1.02 Documentation Page i
╔═══════════════════════════════════════════════════════════════╗
║ ACKNOWLEDGMENTS ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet Software, Inc.
FEATHERNET PRO! COMPUTER BULLETIN BOARD SYSTEM
Version 1.02
Documentation Revision 1.02
For the IBM-PC XT/AT and 100% Compatibles
Copyright (c) 1993 FeatherNet Software, Inc.
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.
(c)1988-1993 FeatherNet Software, Inc. All Rights Reserved.
Printed in the United States of America.
FeatherNet Software, Inc. is a U.S. Corporation based in Florida.
FeatherNet PRO! and all other FeatherNet Software products are
proudly designed, programmed, and supported in the United States
of America.
FeatherNet PRO!, FeatherNet, FN PRO!, and FNet are trademarks of
FeatherNet Software, Inc.
MS-DOS is a registered trademark of Microsoft Corporation
Windows is a trademarks of Microsoft Corporation
IBM, AT, PS/2, PC-DOS and OS/2 are registered trademarks of
International Business Machines
Hayes is a registered trademark of Hayes Microcomputer Products,
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page ii
╔═══════════════════════════════════════════════════════════════╗
║ ACKNOWLEDGMENTS - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.02 Documentation Page iii
╔═══════════════════════════════════════════════════════════════╗
║ PIRATING IS STEALING! ║
╚═══════════════════════════════════════════════════════════════╝
If someone gives you their registration code and you decide to
run the Software with it, remember, we at FeatherNet Software do
this for a living. When you or others steal our hard work, one of
our children may have just gone without a new pair of shoes or
may not have seen the dentist because of your thoughtlessness. We
provide a quality product at a great price. If you do not feel
this is the case, please do not use the Software.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page iv
╔═══════════════════════════════════════════════════════════════╗
║ COPYRIGHT NOTICE ║
╚═══════════════════════════════════════════════════════════════╝
The FeatherNet PRO! Computer Bulletin Board System and all of
it's Associated materials are copyright (c)1988-1993 FeatherNet
Software, Inc. All rights reserved. FeatherNet PRO! is a
trademark owned and protected by FeatherNet Software, Inc. This
document is copyright (c) 1993 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 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 a violation of the
law.
If you are currently TESTING the TEST DRIVE 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 Test Drive
version longer than thirty (30) days you shall be considered in
violation of FeatherNet Software, Inc. copyright and in violation
of the law.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page v
╔═══════════════════════════════════════════════════════════════╗
║ 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 acknow-
ledge your agreement to the terms of this license.
REFUNDS:
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) bus-
iness 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page vi
╔═══════════════════════════════════════════════════════════════╗
║ DEFINITIONS ║
╚═══════════════════════════════════════════════════════════════╝
The term "Software" as used in this license agreement, the
disclaimer, and (c) copyrights notice, all within this documenta-
tion 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 documenta-
tion 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 document-
ation 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 part-
ial 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page vii
╔═══════════════════════════════════════════════════════════════╗
║ 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 soft-
ware 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.
You may install the Software onto a semi-permanent storage device
(a hard disk drive or floptical diskette drive).
You may make one working copy of the Software. If the working
copy becomes corrupted and/or will no longer work properly, the
User is granted permission to make another single copy of the
Software diskette(s) after the original working copy is
destroyed.
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.
Use FeatherNet PRO!, it's documentation, and related materials on
a single computer system or on a network of physically connected
computers of your belonging. If you wish to run the program on
more than one computer not connected to a network, you must
request a multi-user license.
Copy the program for back-up and archive purposes only, or copy
the program to other computers of your belonging for use on a
network of physically connected computers.
Upload copies of FeatherNet PRO! TEST DRIVE VERSION ONLY to any
BBS provided that you upload the *COMPLETE* TEST DRIVE package.
By "complete", we mean that all programs, including
documentation, must be included in the package. By "TEST DRIVE
PACKAGE", we mean that you may *NOT* include any type of
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page viii
╔═══════════════════════════════════════════════════════════════╗
║ PERMITTED USES - Continued ║
╚═══════════════════════════════════════════════════════════════╝
registration key file or registration number that you may have
obtained from ANY SOURCE.
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.
Reproduce, transmit, transcribe, store in any information
retrieval system, or translate into any foreign language or
computer language, in any form, FeatherNet PRO!, any of it's
accompanying programs or materials, including The FeatherNet PRO!
documentation.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page ix
╔═══════════════════════════════════════════════════════════════╗
║ 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page x
╔═══════════════════════════════════════════════════════════════╗
║ GENERAL INFORMATION ║
╚═══════════════════════════════════════════════════════════════╝
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 an officer 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, you acknowledge
that you have read and agree to this contract.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page xi
╔═══════════════════════════════════════════════════════════════╗
║ 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.02 Documentation Page xii
╔═══════════════════════════════════════════════════════════════╗
║ DISTRIBUTION ║
╚═══════════════════════════════════════════════════════════════╝
The TEST DRIVE version of FeatherNet PRO!, FeatherNet PRO! Test
Drive v1.0 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.
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.
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.02 Documentation Page xiii
╔═══════════════════════════════════════════════════════════════╗
║ REQUIRED PREREQUISITES ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! REQUIRES an operating system to run under. This
operating system may be MS/PC DOS v3.1+, OS/2 v2.1+, DR DOS
v5.0+. An INTEL or 100% INTEL Compatible processor (80386-SX or
Faster recommended) on a 100% compatible motherboard is
mandatory. Approximately 239K 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 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!
┌────────────┐
│ IMPORTANT! │
└────────────┘
If you are operating in a Network environment ensure DOS's SHARE
is loaded prior to starting FeatherNet PRO! This will prevent
"PERMISSION DENIED" errors during network file access. Place an
entry in your "AUTOEXEC.BAT" file to load SHARE at bootup.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page xiv
╔═══════════════════════════════════════════════════════════════╗
║ CREDITS & THANKS ║
╚═══════════════════════════════════════════════════════════════╝
We at FeatherNet Software, Inc. would like to take the time and
space here to give a BIG THANK YOU to all of you who have made
this software possible. It is indeed a long listing and would be
difficult to list everyone's name so suffice it to say that we
owe a great deal of thanks to the following:
All the Registered FeatherNet BBS v0-4.2a SysOps
who stuck it out through the years and believed.
All the Alpha testing team members.
All the Beta testing team members.
All of the SysOps who offered their suggestions and support for
this undertaking.
All of the Second and Third party programmers who have helped and
given programming tips.
All the persons who helped in the documentation and proofing.
WILLIAM DANIEL - FL - The Castle Ryne
RANDALL LABRAKE - MA - Elixir BBS
┌─────────────────────┐
│ A SPECIAL THANKS TO │
└─────────────────────┘
RICK BLOUGH - MA - Lightning Strikes
FRED LAWLESS - AL - The File Exchange
TIM LIND - NH - The Oak Vortex
CHARLES MILLER - CA - Graphic Expressions!
PHIL TREVORROW - MA - Gateway BBS
WILLIAM DANIEL - FL - The Castle Ryne
The complete overhaul into what is now called FeatherNet PRO!
v1.0 could never have happened without all your help! Thank you
to one and all!
Also, a special thanks to William Daniel for the utility
SFLCHK10.ZIP, a program for FeatherNet PRO! v1.0 which will
report on all missing files after configuration.
SFLCHK10.ZIP may be found on the FeatherNet HQ BBS
An additional thanks goes to Wayne Greer of Waynes World, Tulsa,
OK for placing FeatherNet BBS software in the Top 100 Best BBS's
for 1993.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.01
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
ACKNOWLEDGMENTS ............................................ i
PIRATING IS STEALING! ....................................... iii
COPYRIGHT NOTICE ............................................ iv
LICENSE AGREEMENT ........................................... v
DEFINITIONS ................................................. vi
PERMITTED USES .............................................. vii
You May .................................................. vii
You May Not ..............................................viii
DURATION OF AGREEMENT ....................................... ix
GENERAL INFORMATION ......................................... x
LIMITED WARRANTY ............................................ xi
DISTRIBUTION ................................................ xii
REQUIRED PREREQUISITES ......................................xiii
CREDITS & THANKS ............................................ xiv
TABLE OF CONTENTS ......................................... 1.01
INTRODUCTION .............................................. 2.01
INITIAL SETUP & INSTALLATION .............................. 3.01
Structure Flow Chart ................................... 3.02
Directory Files Listing ................................ 3.03
Editing ................................................ 3.05
IMPORTANT NOTES ON CONFIGURING ............................ 4.01
FNCFG.EXE - The Configuration Editor ...................... 5.01
Main Configuration Menu ................................ 5.02
CONFERENCE SETUP ....................................... 6.01
Selection ........................................... 6.01
Conference Name ..................................... 6.03
Allow Aliases ....................................... 6.03
Co-SysOp's Name ..................................... 6.03
Message File Path & Name ............................ 6.03
Conference Introduction File ........................ 6.04
Read Security Level ................................. 6.04
Attachment Directory ................................ 6.05
Reply Security Level ................................ 6.05
Write Security Level ................................ 6.05
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.02
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
Upload Directory Security Level...................... 6.05
Upload Description File ............................. 6.05
Upload File Path .................................... 6.05
Bulletin Menu File .................................. 6.06
Bulletin List File .................................. 6.06
Bulletin path & filename ......................... 6.06
Creating a bulletin .............................. 6.07
Saving the bulletin configuration file ........... 6.07
Door Menu File ...................................... 6.07
Door List File ...................................... 6.07
Door batch file name ............................. 6.08
Door password .................................... 6.09
Door security level .............................. 6.09
Auto logon doors ................................. 6.09
Create DOOR.SYS file ............................. 6.10
RIPscrip graphics in the door setup menu ......... 6.10
Shell/Swap to door ............................... 6.10
Path to door batch file .......................... 6.11
RIPscrip supported by door ....................... 6.11
Saving the door configuration file ............... 6.11
Running Doors From Remote ........................... 6.12
Menu for Directory Listing .......................... 6.12
Directory listing control file for this conference 6.12
Directory text filename & path ................... 6.13
Hard disk subdirectory ........................... 6.13
File directory security .......................... 6.13
Category of directory ............................ 6.14
Saving the directory listing file ................ 6.14
Alternate download path listing file ................ 6.14
Alternate download path .......................... 6.15
Security level for download path ................. 6.15
Additional notes on the alternate download listing 6.15
Saving the alternate d/l directory listing file .. 6.16
Index File Name ..................................... 6.16
Prohibited Words Data File .......................... 6.17
Echo This Conference ................................ 6.17
Make This A Public Conference ....................... 6.18
Message Blocks ...................................... 6.18
Use Graphics Quoting Feature ........................ 6.18
Private Mail Only ................................... 6.18
Public Mail Only .................................... 6.18
GENERAL INFORMATION 1 .................................. 7.01
Name Of Your BBS .................................... 7.01
SysOp's Name ........................................ 7.01
Use SysOp's Real Name ............................... 7.01
"Today" Function .................................... 7.02
Enable Questionnaires ............................... 7.02
Number Of Questionnaires ............................ 7.03
Registration Number ................................. 7.03
Add Custom "Zip" Comments ........................... 7.03
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.03
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
Add "Uploaded by:" To Description ................... 7.04
Use Color Graphics During Local Logon ............... 7.04
Confirm Users Name & Address ........................ 7.04
Minimum Upload Drive Space ............................7.05
Maximum Number Of Messages To Capture .................7.05
Minutes Before FeatherNet PRO! Recycles to DOS ........7.05
Time Credit For Uploads ...............................7.06
Limit SysOp Paging Hours ..............................7.06
SysOp Page Start Time .................................7.06
SysOp Page Stop Time ..................................7.06
Number Of Chat Rooms ..................................7.07
GENERAL INFORMATION 2 .................................. 8.01
Pre-Load FNETTEXT File .............................. 8.01
Warn Callers At Logoff If "Download Flags" Are Set .. 8.01
Prompt Callers To Set Message Pointers At Logoff .... 8.01
Confirm Logoff Command .............................. 8.02
Swap to XMS, EMS or Disk During A Shell ............. 8.02
Allow [P]rivate Transfers ........................... 8.02
Operate As A Closed System .......................... 8.02
Allow Split Screen Chat To Be Used .................. 8.03
Force Users To Read New Mail At Logon ............... 8.03
Always Force Users To Select Transfer Protocol ...... 8.03
Have The "Do You Want Color" Question Default to Y/N 8.03
Disable The Auto ANSI Detect Function At Logon ...... 8.04
Display Users Statistics File At Logon .............. 8.04
Allow "Aliases" Or Single Word Names ................ 8.04
Maximum Lines To Display When Reading From Archive .. 8.04
Use Which Parallel (Printer) Port (0-3) ............. 8.04
Force Users Into Bulletin Menu At Logon ............. 8.05
Maximum Lines Allowed In Message Editor ............. 8.05
MODEM/NODE/SUBSCRIPTION INFORMATION .................... 9.01
Modem Initialization String ......................... 9.01
Communications Driver To Use ........................ 9.01
Which Communications Port (0-4) Is This Node ........ 9.01
Baud Rate To Open Communications Port At (300-115200) 9.02
Lock Communications Port At Opening Baud Rate ....... 9.02
Answer On Which Ring ................................ 9.02
Seconds To Wait For Connect ......................... 9.02
Minimum Baud Rate Allowed ........................... 9.02
Pause For 3 Seconds After Connect At <= 2400 ........ 9.03
Default New User Subscription In Days ............... 9.03
Days Warning Before Subscription Expires ............ 9.03
Expired Subscription Security Level ................. 9.03
Operate In A Ring Back Mode ......................... 9.03
Seconds To Wait For Ring Back ....................... 9.04
Node Number ......................................... 9.04
Using A Network Or Multi-Tasker ..................... 9.04
Filter All High ASCII Characters .................... 9.04
Using A "Front-End" To Load FeatherNet PRO! ......... 9.04
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.04
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
EVENT CONFIGURATION .................................... 10.01
Event List File Path & Name ......................... 10.01
Events List File Editor ............................. 10.01
Is this event active ............................. 10.01
Event mode ....................................... 10.01
Event batch file name ............................ 10.02
Begin event time ................................. 10.02
End event time ................................... 10.02
Event date ....................................... 10.02
Last event date .................................. 10.03
Event day flags .................................. 10.03
Saving the event configuration file .............. 10.03
Minutes Prior To Event To Disallow Callers .......... 10.03
Modem Off-Hook (Busy) When An Event Is Pending ...... 10.04
FILE LOCATIONS SCREEN 1 ................................ 11.01
Path Of Main BBS Directory .......................... 11.01
Path Of Node Work Directory ......................... 11.01
Path Of Node Home Directory ......................... 11.01
Path Of Security Level Files ........................ 11.01
Duplicate Upload "Hold" Directory ................... 11.02
File To Run Before And After File Transfer .......... 11.02
Path Of The Private File Transfer Directory ......... 11.02
Path & Name Of "FNETTEXT" File ...................... 11.03
Path Of User Index Files ............................ 11.03
Path Of Special "Help" Files ........................ 11.03
Path & Name Of "PWRD" File .......................... 11.03
Security level ................................... 11.04
Time allowed on system ........................... 11.04
Maximum k-bytes to download today ................ 11.04
Standard baud rate ............................... 11.04
Batch file transfer limit ........................ 11.05
File download ratio .............................. 11.05
Byte download ratio .............................. 11.05
File download limit .............................. 11.05
K-byte download limit ............................ 11.05
File credits ..................................... 11.06
K-byte credits ................................... 11.06
Use hourly subscription .......................... 11.06
Saving The "PWRD" Configuration File ............. 11.06
Path & Name Of The Quote Text File .................. 11.07
Slow Drive Letters .................................. 11.07
Path & Name Of The Co-SysOp Bit Map File ............ 11.07
Path & Name Of The User's Information File .......... 11.08
Path & Name Of The Protocol Data File ............... 11.08
Path & Name Of The "Trash" File ..................... 11.08
FILE LOCATIONS SCREEN 2 ................................ 12.01
Main Menu File ...................................... 12.01
SysOp's Main Menu File .............................. 12.01
Conference Command Menu File ........................ 12.01
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.05
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
SysOp's Conference Command Menu File ................ 12.02
Path & Name Of The Conference listing Menu .......... 12.02
File Transfer Menu File ............................. 12.02
SysOp's Transfer Menu File .......................... 12.03
Script Questionnaires Menu File ..................... 12.03
Newuser Script File Name ............................ 12.03
Script Questionnaires ............................... 12.03
Prelog File ......................................... 12.04
News File ........................................... 12.04
Hello File .......................................... 12.04
Newuser File ........................................ 12.05
Closed BBS File ..................................... 12.05
Caller Log File ..................................... 12.06
Logoff File ......................................... 12.06
Today File .......................................... 12.06
User Statistics File ................................ 12.07
FILE LOCATIONS SCREEN 3 ................................ 13.01
Post Upload File .................................... 13.01
Failed Upload File .................................. 13.01
Post Download File .................................. 13.01
Failed Download File ................................ 13.02
Path Of The "Free" Files To Download Directory ...... 13.02
Stop The Clock For "Free" Downloads ................. 13.02
Group Chat Menu ..................................... 13.02
Location Of Chat Files .............................. 13.03
Expired Warning File ................................ 13.03
Expired File ........................................ 13.03
Pre-Download Warning File ........................... 13.04
Pre-Upload Warning File ............................. 13.04
Prohibited Words Warning File ....................... 13.04
Path & Name Of FNCONF.@@@ ........................... 13.05
Path & Name Of FNCONF.LST File ...................... 13.05
Path & Name Of USERS File ........................... 13.05
Path & Name Of FNEXTUSR File ........................ 13.05
SECURITY FILES - SYSTEM/SYSOP .......................... 14.01
Security Level To Use The [CALL] Command ............ 14.01
[F]ile Transfer Area Security Level ................. 14.01
Security Level For The [H]elp Command ............... 14.01
Security Level To [J]oin A Conference ............... 14.01
Security Level To [K]ill Any Message ................ 14.01
Security Level To Use Toggle E[X]pert Mode .......... 14.01
Security Level To Use [*] Global New Read ........... 14.02
Security Level To Carbon Copy Messages .............. 14.02
Security Level To Edit Any Message .................. 14.02
Security Level To Edit Your Messages ................ 14.02
Security Level To Use "@" Macros In Messages ........ 14.02
New User Security Level ............................. 14.02
Security Level To Read All Mail & Comments .......... 14.02
Security Level To Zero Time At Each Logon ........... 14.02
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.06
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
Allow Quick Logons .................................. 14.03
SECURITY LEVELS - MAIN MENU ............................ 15.01
Security Level To View [B] Menu ..................... 15.01
Security Level To Leave A [C]omment ................. 15.01
Security Level For The [D]oor Command ............... 15.01
Security Level To Edit User [I]nformation ........... 15.01
Security Level To Use The [O]perator Page Command ... 15.01
Security Level To Use The [P]age Length Command ..... 15.01
Security Level To Use The [Q]uestionnaire Command ... 15.01
Security Level To [S]elect Color Graphics ........... 15.01
View [T]oday's Callers Security Level ............... 15.02
Security Level To List System [U]sers Command ....... 15.02
Security Level To [V]iew Selected Statistics ........ 15.02
Security Level To View The [W]elcome File ........... 15.02
Security Level To Use [VER] BBS Version Command ..... 15.02
SECURITY LEVELS - FILE MENU SCREEN ..................... 16.01
[D]ownload Security Level ........................... 16.01
Security Level To view Logged [F]ile Directory ...... 16.01
Security Level To Search For [N]ew Files ............ 16.01
Security Level To [TP] Change Transfer Protocol ..... 16.01
[U]pload Security Level ............................. 16.01
Security Level To [V]iew Archives ................... 16.01
Security Level For [Z]ippy Directory Search ......... 16.01
SECURITY LEVELS - MESSAGE MENU ......................... 17.01
Security Level To [A]rchive & Download Mail ......... 17.01
Security Level Required To [K]ill A Message ......... 17.01
Security Level To [S/SS] Scan/SuperScan Messages .... 17.01
Security Level To [U]pdate Set Conference Scans ..... 17.01
Attach File To Message [SA] Security Level .......... 17.01
FUNCTION KEY PROGRAMMING ............................... 18.01
Shifted Function Key Assignments .................... 18.01
SAVING THE FNCFG.EXE (SRCONFIG) FILE ................... 19.01
RUNNING FEATHERNET PRO! ................................... 20.01
Modem .................................................. 20.01
BBS Files .............................................. 20.01
WAITING FOR CALL SCREEN ................................... 21.01
Screen Information ..................................... 21.01
The Header .......................................... 21.01
The Center Screen ...................................... 21.01
Node ................................................ 21.01
New users ........................................... 21.01
Old users ........................................... 21.01
Calls ............................................... 21.01
Sysop mail .......................................... 21.01
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.01 Documentation Page 1.07
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
The Bottom Screen ...................................... 21.02
Comx ................................................ 21.02
Current activity .................................... 21.02
Last caller ......................................... 21.02
Quick description ................................... 21.02
SysOp Option Fields .................................... 21.02
Local-in busy ....................................... 21.02
DOS busy ............................................ 21.02
SysOp in busy ....................................... 21.02
DOS not busy ........................................ 21.02
FNFiler ............................................. 21.02
View Caller Logs .................................... 21.03
FNetSM .............................................. 21.03
Printer on (y/n) .................................... 21.03
FNCfg ............................................... 21.03
SysOp page (y/n) .................................... 21.03
Node monitor ........................................ 21.03
Page beep (y/n) ..................................... 21.03
SysOp Help Functions Within The BBS <F10> .............. 21.04
SysOp Help <F1> ..................................... 21.04
SysOp Help <F2> ..................................... 21.04
SysOp Help <F3> ..................................... 21.04
SysOp Help <F4> ..................................... 21.04
SysOp Help <F5> ..................................... 21.04
SysOp Help <F6> ..................................... 21.04
SysOp Help <F7> ..................................... 21.04
SysOp Help <F8> ..................................... 21.04
SysOp Help <F9> ..................................... 21.04
SysOp Help <F10> .................................... 21.04
SysOp Help <Alt><C> ................................. 21.04
SysOp Help <Alt><P> ................................. 21.04
SysOp Help <Space> .................................. 21.04
SysOp Help <ESC> .................................... 21.04
SysOp Help "CALL" ................................... 21.04
MAIN MENU ................................................. 22.01
[*] Global New Message Scan Command .................... 22.01
[B]ulletin Menu Command ................................ 22.01
[C]omment To The SysOp Command ......................... 22.01
[D]oor Menu Command .................................... 22.01
[F]iles Menu Command ................................... 22.01
[G]oodbye Command ...................................... 22.01
[H]elp Command ......................................... 22.02
[I]nformation Change (User) Command .................... 22.02
[J]oin A Conference Command ............................ 22.02
[M]essage Menu Command ................................. 22.02
[N]ode Status Command .................................. 22.02
[NEWS] Display Command ................................. 22.02
[O]perator Page Command ................................ 22.02
[P]age Length Set Command .............................. 22.03
[Q]uestionnaire Menu Command ........................... 22.03
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.08
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
[S]creen Color Toggle Command .......................... 22.03
[T]odays Callers Command ............................... 22.03
[TODAY] Option Command ................................. 22.03
[U]sers Listing Command ................................ 22.03
[V]iew User Statistics Command ......................... 22.03
[VER]sion of FeatherNet PRO! Command ................... 22.03
[W]elcome (Hello) Screen Display Command ............... 22.03
[X] Expert Mode Toggle Command ......................... 22.03
[CALL] View Caller Logs Command (SysOp Status Only)..... 22.03
MESSAGE MENU .............................................. 23.01
[*] Global Scan New Mail Command ....................... 23.01
[A]rchive Mail Command ................................. 23.01
[E]nter A Message Command .............................. 23.01
[F]iles Menu Command ................................... 23.01
[G]oodbye Command ...................................... 23.01
[H]elp Command ......................................... 23.01
[J]oin A Conference Command ............................ 23.02
[K]ill Messages Command ................................ 23.02
[L]evel Reset High Message Pointers Command ............ 23.02
[N]ew Mail Command ..................................... 23.02
[Q]uit To Main Menu Command ............................ 23.02
[R]ead Mail Command .................................... 23.02
[S]can Mail Command .................................... 23.02
[SS] SuperScan Mail Command ............................ 23.02
[T]ext Search Command .................................. 23.03
[U]pdate Flagged Conferences Command ................... 23.03
[X] Expert Mode Toggle Command ......................... 23.03
FILE MENU ................................................. 24.01
[D]ownload A File Command .............................. 24.01
[F]iles in Current Conference File Directory Command ... 24.01
[G]oodbye Command ...................................... 24.01
[H]elp Command ......................................... 24.01
[J]oin A Conference Command ............................ 24.01
[L]ist File Directories Command ........................ 24.01
[M]essage Menu Command ................................. 24.02
[N]ew Files Command .................................... 24.02
[P]rivate File Transfers Command........................ 24.02
[Q]uit To Main Command ................................. 24.02
[TEST] An Archive Command .............................. 24.02
[TP] Transfer Protocol Change Command................... 24.02
[U]pload A File Command ................................ 24.02
[V]iew Contents Of An Archive Command .................. 24.02
[X] Expert Mode Toggle Command ......................... 24.03
[Z]ippy Text Search Command ............................ 24.03
"OR" search function ................................ 24.03
"AND" search function ............................... 24.03
BULLETIN MENU ............................................. 25.01
[A]ll Bulletins Read Command ........................... 25.01
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.09
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
[D]ownload Bulletins Command ........................... 25.01
[N]ew Bulletins Read Command ........................... 25.01
[T]ext Search In Bulletins Command ..................... 25.01
[#] Bulletin Read Command (# = Actual Number) .......... 25.01
QUESTIONNAIRE MENU ........................................ 26.01
[#] Questionnaire Read Command (# = Actual Number) ..... 26.01
[Q]uit Back To Main Menu Command ....................... 26.01
DOOR MENU ................................................. 27.01
VISUAL EDITOR ............................................. 28.01
Key Commands ........................................... 28.02
Insert Mode ............................................ 28.02
Note For SysOps With Non-PC Keyboard Users ............. 28.02
BATCH FILES ............................................... 29.01
General ................................................ 29.01
Required Batch File For FeatherNet PRO! ................ 29.01
SFN.BAT ................................................ 29.02
ARCMxS.BAT ............................................. 29.04
FNETTEST.BAT ........................................... 29.05
Running Multiple Nodes ................................. 29.06
Tips & Troubleshooting ................................. 29.08
Error Codes ............................................ 29.11
SYSOP UTILITIES ........................................... 30.01
General ................................................ 30.01
FNETSM.EXE ............................................. 31.01
[A] Edit Users ...................................... 31.02
Key controls ..................................... 31.02
User's name ...................................... 31.02
City & state user is from ........................ 31.02
User's security password ......................... 31.03
Business/data phone number ....................... 31.03
Voice phone number ............................... 31.03
Users security level ............................. 31.03
Deleted user flag ................................ 31.03
Expiration date .................................. 31.03
Last date on system .............................. 31.03
Time used today .................................. 31.04
User's text page length .......................... 31.04
Times logged onto bbs ............................ 31.04
File transfer protocol ........................... 31.04
Files downloaded today ........................... 31.04
Number of uploads ................................ 31.04
Number of downloads .............................. 31.04
Bytes downloaded today ........................... 31.04
Bytes uploaded to bbs ............................ 31.04
Bytes downloaded from bbs ........................ 31.04
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.10
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
Allowed to use the [P]rivate files function ...... 31.05
Private files awaiting download .................. 31.05
User's name ...................................... 31.05
User's alias name ................................ 31.05
Users street address #1 .......................... 31.05
Users street address #2 .......................... 31.05
User's city ...................................... 31.06
User's zipcode ................................... 31.06
Number of messages the user has left ............. 31.06
User's date-of-birth ............................. 31.06
User's sex ....................................... 31.06
User's personal comment .......................... 31.06
Sysop's user comment ............................. 31.06
User's state or province ......................... 31.06
User's country ................................... 31.06
Clear screen between messages .................... 31.07
Scroll screen while reading messages ............. 31.07
Use the hi-lited flag and/or view option ......... 31.07
Amount received .................................. 31.07
Total money received ............................. 31.07
Cost per hour .................................... 31.07
Current money used ............................... 31.08
Amount of balance ................................ 31.08
Hours purchased .................................. 31.08
Current hours used ............................... 31.08
Current hours available .......................... 31.08
Days before expire ............................... 31.08
Last payment date ................................ 31.08
Conference registration flag ..................... 31.09
Co-sysop registration flag ....................... 31.09
[B] Create User Index ............................... 31.10
[C] Pack Users ...................................... 31.11
[D] Purge Users ..................................... 31.12
[E] Define Editors .................................. 31.13
[F] Access FNCFG .................................... 31.14
[G] Access FNFILER .................................. 31.15
[H] Print User Records .............................. 31.16
[I] Sort User Records ............................... 31.17
[J] Standardize Phone Formats ....................... 31.18
[K] About FeatherNet Software ....................... 31.19
Command Line Operation .............................. 31.20
FNFILER.EXE ............................................... 32.01
General ................................................ 32.01
Key Commands ........................................... 32.01
Edit DIRxx Files ....................................... 32.02
Selecting Conference/Directory ......................... 32.03
DIR File Editing ....................................... 32.04
Key Commands ........................................ 32.04
Locate file on disk ................................. 32.05
Locate file in DIRxx file ........................... 32.05
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.11
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
Locate text in DIRxx file ........................... 32.05
Edit FNFILER defaults ............................... 32.06
Exiting ............. ............................... 32.07
Command Line Options ................................ 32.08
MKFNTEXT.EXE .............................................. 33.01
Prompt Editor .......................................... 33.01
Key Controls ........................................... 33.01
FNCHK.EXE ................................................. 34.01
Overview ............................................... 34.01
FNCHK.CFG ................................................. 35.01
Upload Integrity Checker Configuration ................. 35.01
FNETTEST.BAT .............................................. 36.01
LOCALUP.EXE ............................................... 37.01
Pre-Conditions ......................................... 37.01
Features ............................................... 37.02
FNPACK.EXE ................................................ 38.01
Pack The Message File .................................. 38.01
FN-NET.EXE ................................................ 39.01
Message Pointer Utility ................................ 39.01
MODEMSET.EXE .............................................. 40.01
Modem Setup Utility .................................... 40.01
BUILDNDX.EXE .............................................. 41.01
File Index Compiler .................................... 41.01
CNAMES40.EXE .............................................. 42.01
PCBoard's CNAMES.@@@ Utility ........................... 42.01
FNODEMON.EXE .............................................. 43.01
Node Monitoring Utility ................................ 43.01
FRESHEN.BAT ............................................... 44.01
Update Your Conference Files Index File ................ 44.01
CONTROL FILES ............................................. 45.01
UPSEC .................................................. 45.01
DIRxx .................................................. 45.02
FNETPROT.DAT ........................................... 45.04
SRCONFIG ............................................... 45.06
USERS .................................................. 45.11
USERNET.DAT ............................................ 45.13
PCBOARD.SYS ............................................ 45.15
DOORS.LST .............................................. 45.16
DOOR.SYS ............................................... 45.17
FNCONF.@@@ ............................................. 45.19
FNCONF.SEC ............................................. 45.21
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.12
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
FNEXTUSR................................................ 45.22
COSYSOP.BIT ............................................ 45.23
% Syntax ............................................... 45.24
Remote Mode Doors ...................................... 45.25
Downloadable Files ..................................... 45.26
FILE STRUCTURES ........................................... 46.01
Files Listing .......................................... 46.01
APPENDIX A - Running With A Front-End Loader .............. A-A01
APPENDIX B - Running Under DESQview ....................... A-B01
Basic Hardware Considerations .......................... A-B01
Modifications To CONFIG.SYS & FeatherNet PRO! .BAT Files A-B01
DESQview Setup Default Settings ........................ A-B02
Adding FeatherNet PRO! To DESQview's "Open Window" Menu A-B03
APPENDIX C - Using "RING BACK" Mode ....................... A-C01
APPENDIX D - Macros ....................................... A-D01
Macros - Information About The Caller .................. A-D02
Addressing messages ................................. A-D03
Macros - System Information ............................ A-D03
Macros - System & Display Controls ..................... A-D04
Macros - Special Screen & Cursor Controls .............. A-D04
APPENDIX E - Color Macros (@XCodes) ....................... A-E01
Charts & Examples ...................................... A-E01
APPENDIX F - Aborted Download Credits ..................... A-F01
APPENDIX G - Configuring & Running Multiple Events ........ A-G01
APPENDIX H - Allowing "FREE" Downloads .................... A-H01
APPENDIX I - Duplicate Uploads Protection ................. A-I01
APPENDIX J - Shelling To Archive Manipulations ............ A-J01
APPENDIX K - Script Questionnaire Instructions ............ A-K01
Sample New User Script Questionnaire ................... A-K01
APPENDIX L - Private "Personal" File Transfers ............ A-L01
APPENDIX M - Attaching Files To Messages .................. A-M01
APPENDIX N - Manipulating The Default RIPScrip Screens .... A-N01
What is RIP ............................................ A-N01
Where Can I Get RIPaint ................................ A-N01
Manipulating RIPScrip With An ASCII Editor ............. A-N02
FeatherNet's RIP menu/display file listing .......... A-N03
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 1.13
╔═══════════════════════════════════════════════════════════════╗
║ TABLE OF CONTENTS ║
╚═══════════════════════════════════════════════════════════════╝
Samples ............................................. A-N04
OK, I Give Up - Solutions .............................. A-N11
APPENDIX O - Converting From PCBoard ...................... A-O01
Conferences............................................. A-O02
Userbase ............................................... A-O03
Filebase ............................................... A-O05
Doors .................................................. A-O06
APPENDIX P - Stuffing The Keyboard ........................ A-P01
REGISTRATION .............................................. B-001
SUPPORT ................................................... C-001
UPGRADES .................................................. D-001
REGISTRATION AGREEMENT / APPLICATION ...................... E-001
BUG REPORTS ............................................... F-001
Software ............................................... F-001
Documentation .......................................... F-004
YOUR NOTES ................................................ G-001
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 2.01
╔═══════════════════════════════════════════════════════════════╗
║ 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.0. 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. It is our hope, that if
you ever have any problem running our software, you pick up the
phone and call us! 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
Sam Gudgel - V.P. - Graphics, Programming, Ideas
David Place - V.P. - Marketing, Tech support, Programming
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!"
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, etc, of today, 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 innova-
tive BBS program today.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 3.01
╔═══════════════════════════════════════════════════════════════╗
║ INITIAL SETUP & 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. In addition it creates
and modifies all the necessary .BAT files.
*┌─────────────────────────────────────────────────────────────┐*
*│ WE STRONGLY RECOMMEND THAT YOU USE THE "AUTOMATED" METHOD, │*
*│ however, for the sake of documentation, we will outline the │*
*│ structures, etc. │*
*└─────────────────────────────────────────────────────────────┘*
NOTE: Our recommendations will follow a "default" installation
as we have found it to be the BEST method. This does not,
and is not meant to imply that this method will be the
best for you. It is however, a tried and true method,
found reliable by many SysOps in the past.
THESE INSTRUCTIONS ASSUME A GENERAL FAMILIARITY WITH DOS COMMANDS
The following is a list of NECESSARY "Things To Do"!
1) Decide on the drive you want your FeatherNet PRO! BBS to run
on. This will be the MAIN FeatherNet PRO! directory.
2) Edit your path statement in your AUTOEXEC.BAT to include the
FeatherNet PRO! "Home" directory. (\FNET is recommended)
NOTE: You will need an ASCII text editor such as DOS's "Edit" or
other similar program to make these changes.
3) Add the statement "SET NODE=1" to your AUTOEXEC.BAT file.
NOTE: FeatherNet PRO! is designed to use "Environment Variables"
If this "SET" statement is NOT in your AUTOEXEC.BAT file,
the BBS will NOT operate until you edit all of the default
batch files.
Once the editing has been completed in your AUTOEXEC.BAT you MUST
re-boot your computer for the edited changes to take place.
Once steps 1 through 4 have been completed, you may unarchive the
FeatherNet PRO! disks (1-4) into the "Home" directory you created
The following is the recommended directory structures of Feather-
Net PRO!. Of course you may name the files and directories any-
thing you wish, but for the most part, this documentation refers
to the file and directory names as listed here.
NOTE: It is "STRONGLY RECOMMENDED" that you create these direct-
ories as outlined.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 3.02
╔═══════════════════════════════════════════════════════════════╗
║ INITIAL SETUP & INSTALLATION - Structure Flow Chart ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G1: RECOMMENDED DIRECTORY STRUCTURE MAP
┌───────┐
│ \FNET │
└───┬───┘
┌────┬────┬───┬────┬───┬────┼───┬────┬───┬────┬───┬────┐
│┌───┴───┐│┌──┴───┐│┌──┴───┐│┌──┴───┐│┌──┴───┐│┌──┴───┐│
││ FNSYS │││ MENU │││ QUES │││ HELP │││ DOCS │││ DISP ││
│└───────┘│└──────┘│└──────┘│└──────┘│└──────┘│└──────┘│
┌──┴─────┐┌──┴───┐┌───┴───┐ │ ┌────┴────┐┌──┴───┐┌───┴───┐
│ EVENTS ││ LOGS ││ NODE1 │ │ │ USERNDX ││ CHAT ││ DOORS │
└────────┘└──────┘└───┬───┘ │ └─────────┘└──────┘└───────┘
┌───┴──┐ │
│ WORK │ │
└──────┘ │
┌─────────┬─────────┬┴─────────────┐
┌────┴───┐ ┌──┴──┐ ┌───┴───┐ ┌───┴───┐
│ CF0000 │ │ ULT │ │ DOORS │ │ FILES │
└────┬───┘ └──┬──┘ └───────┘ └───┬───┘
│ ┌───┴───┐ ┌────────┬──┴─────┬──────┐
│ │ WORK1 │ ┌──┴──┐┌────┴───┐┌───┴──┐┌──┴───┐
│ └───────┘ │ PVT ││ CF0000 ││ FREE ││ HOLD │
│ └─────┘└────┬───┘└──────┘└──────┘
┌────┴────┬─────────┐ ┌──┴────┬───────┐
┌────┴─────┐┌──┴───┐┌────┴───┐ ┌───┴───┐┌──┴──┐┌───┴───┐
│ ATTACHED ││ DIRS ││ ALT001 │ │ DL001 ││ UPL ││ UPLPV │
└──────────┘└──────┘└────────┘ └───────┘└─────┘└───────┘
Now move each file shown below from the FeatherNet "Main" dir-
ectory to the appropriate directories shown below.
NOTE: AGAIN, IT IS STRONGLY RECOMMENDED THAT YOU USE THE DIRECT-
DIRECTORY STRUCTURE SHOWN ABOVE!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 3.03
╔═══════════════════════════════════════════════════════════════╗
║ INITIAL SETUP & INSTALLATION - Directory Files Listing ║
╚═══════════════════════════════════════════════════════════════╝
┌───────┐ ┌────────────┐ ┌───────────┐ ┌───────────┐
│ \FNET │ │ FNET\FNSYS │ │ FNET\DISP │ │ FNET\MENU │
└───────┘ └────────────┘ └───────────┘ └───────────┘
ARCMAS.BAT COSYSOP.BIT CLOSED CHTM
ARCMJS.BAT CUSWORD CLOSEDR CHTMR
ARCMLS.BAT FNCONF.@@@ COMMENT CL
ARCMZS.BAT FNCONF.LST CUSSWRB CLR
BUILDNDX.EXE FNCONF.SEC CUSSWRNR CM
CALLFIX.EXE FNETPROT.DAT EXPIRED CMR
CNAME40.EXE FNETTEXT EXPIREDR CMS
DIRLST.EXE FNUSERS.INF EXPWARN CMSR
FNPDRCVT.EXE USERS EXPWARNR FM
FN-NET.EXE FNUSERS.INF FAILDN FMR
FNCFG.HLP PRIV.DAT FAILDNR FMS
FNCFG.NDX PWRD FAILUP FMSR
FNCFG.EXE TCALLS FAILUPR MM
FNCHK.CFG TRASH HDR-STD MMR
FNCHK.EXE USERNET.DAT HELLO1 MMS
FNECHO.EXE USERS.IDX HELLO1R MMSR
FNET.EXE LOGOFF
FNETSM.CFG LOGOFFR
FNETSM.EXE MSGPRIV
FNETSM.HLP NEWS
FNETSM.NDX NEWSR ┌────────────┐
FNFILER.CFG NEWUSER │ FNET\NODE1 │
FNFILER.EXE NEWUSERR └────────────┘
FNPACK.EXE PERSONAL FNET.IMG
LOCALUP.EXE POSTDN LASTNAME
MODEMSET.DAT POSTDNR SRCONFIG
MODEMSET.EXE POSTUP
MODEMSET.PTR POSTUPR
NODE.BAT PREDN
PRIVUTIL.EXE PREDNR ┌─────────────┐
SFN.BAT PREUP │ FNET\EVENTS │
PREUPR └─────────────┘
PRELOG EVENT.LST
PRELOGR
QUOTES.BBS
┌───────────┐ USERSTAT
│ \FNET\ULT │ USERSTATR
└───────────┘
BADFILES.LST
ULT.CFG
ULTCFG.EXE
ULTCFG.HLP
ULTESTER.DOC
ULTESTER.EXE
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 3.04
╔═══════════════════════════════════════════════════════════════╗
║ INITIAL SETUP & INSTALLATION - Directory Structure - Continued║
╚═══════════════════════════════════════════════════════════════╝
┌───────────┐ ┌────────┐ ┌───────────┐ ┌───────────┐
│ FNET\QUES │ │ CF0000 │ │ FNET\DOCS │ │ FNET\HELP │
└───────────┘ └────────┘ └───────────┘ └───────────┘
SCRIPT.0 BLT FNP102.DOC CHAT.HLP
QUES BLTR HS-FNET.TXT FNVISUAL.HLP
QUESR BLT01 README.1ST FT.HLP
BLT02 MAIN.HLP
BLT03 MSG.HLP
BLT.LST MSGR.HLP
DIR.LST MSGRD.HLP
DIRM
DIRMR
┌──────────────┐ DLPATH.LST ┌──────────────────┐
│ FNET\USERNDX │ DOORS.LST │ FNET\CF0000\DIRS │
└──────────────┘ DORM └──────────────────┘
FNPNDX.A DORMR DIR001
(thru) INTRO DIRUP
FNPNDX.Z INTROR DIRPV
MSGS
MSGS.NDX
Once all the files have been placed in their respective direct-
ories you will need to change to the FeatherNet PRO! "Main"
directory (\FNET) and change all the .BAT & .EXE files to "Read-
Only".
This is accomplished using the DOS command "ATTRIB".
EXAMPLES: ATTRIB +R *.BAT
ATTRIB +R *.EXE
You are now ready to configure your BBS!
Every file you need to run FeatherNet PRO! should now be
accessible from the FNET Main Directory. There is a full list
and description of all these files later in this documentation.
Now run the program "FNCFG.EXE" from the FNET NODE directory.
This should be your ?:\FNET\NODE1 sub directory. Ensure ALL
items are answered before attempting to log on to your BBS for
the first time.
DETAILED INSTRUCTIONS ON "FNCFG CONFIGURATION" FOLLOW IN THE NEXT
SECTION.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 3.05
╔═══════════════════════════════════════════════════════════════╗
║ INITIAL SETUP & INSTALLATION - Editing ║
╚═══════════════════════════════════════════════════════════════╝
boards systems and supports FeatherNet PRO! color Xcodes.
NOTE: TheDraw(tm) does NOT support FeatherNet PRO! @codes but
you will find that a TSR called FNET@.EXE has been includ-
ed with your FeatherNet PRO! package and will insert the
correct @codes as you make your ANSI or ASCII screens.
Some of the following configuration screens are not full
size in order to improve clarity and reduce the amount of
"dead" space in the documentation. However, they contain
all the text from the actual configuration screens.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 4.01
╔═══════════════════════════════════════════════════════════════╗
║ IMPORTANT NOTES ON CONFIGURING ║
╚═══════════════════════════════════════════════════════════════╝
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 dir-
ectory'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-STD" (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 DIRx file when
called.
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 @X color
coded or ANSI color screens without the appended "G". FeatherNet
PRO! will strip all @ color codes or ANSI commands for the mono-
chrome user.
In ALL cases you MUST have a separate file for all RIP display
files. All RIP files must also end with an "R".
In the conference configuration screens you will notice that at
times a RED BAR appears at the bottom of the screen with informa-
tion. 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 predefined TEXT EDITOR and edit a TEXT menu or dis-
play file or PRESS <F3> to enter your predefined ANSI EDITOR and
edit a ANSI menu or display file. (You MUST predefine these
editors within FNETSM. If you ran the INSTALFN installation
program, this step has already been accomplished). The second
one only has the option of to 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.02 Documentation Page 5.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - The FeatherNet PRO! Configuration Editor ║
╚═══════════════════════════════════════════════════════════════╝
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 5.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Main Configuration Menu ║
╚═══════════════════════════════════════════════════════════════╝
Starting FNCFG will bring you to the MAIN FNCFG menu.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G2: MAIN CONFIGURATION SCREEN.
You can get 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 config-
uration 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 help by pressing <F1> at any menu option.
NOTE: Please read the UPDATE.DOC file on the FeatherNet PRO!
diskette for any last minute changes in the software.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Information - Selection ║
╚═══════════════════════════════════════════════════════════════╝
CONFERENCES AVAILABLE: [0 - 23]
This area simply lets you know how many conferences you have
currently configured which may be edited.
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.
┌─────┐
│ TIP │
└─────┘
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.
Enter [A] to add a conference (maximum conferences is 1024) to
those already configured. You will have to add each conference
separately that you wish to use. (Note: There is a limit of 5
conference areas in the TEST DRIVE version, areas 0-4). As stated
above, when creating a new conference, the default information is
taken from your CONFERENCE 0 information.
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 Conf-
erence 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.
NOTE: FeatherNet PRO! does not yet directly support conference
deletions. If you wish to delete a conference it is
recommended you just make it inaccessible by making it a
PRIVATE conference and raising the security level to
255. In the conference join menu (conference listings
file) blank the conference name or change it to "Not in
Use" or "Reserved" or some other appropriate title.
It is anticipated a conference deletion "utility" program will be
forthcoming very soon. An enormous amount of "work" is required
to "delete" a conference from the configuration. This is due to
the user's message pointers and flags having to be rewritten to
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Information - Selection - Continued ║
╚═══════════════════════════════════════════════════════════════╝
reflect the conference deletion.
This is why "disabling" a conference is presently considered a
more appropriate means of "removing" a conference.
Another suggestion is to allow for additional conferences to be
inserted at a later time when you plan the conference layout.
You would configure some "Not in Use" conferences at various
positions to possibly be used at a later date when adding or
changing mail networks for example.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G3: CONFERENCE SETUP SCREEN
NOTE: The asterisks (*) on the menu denotes that the file in
question is in fact where the path says it is and the file
is currently in existence.
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 you
conferences: CONF0, CONF1, etc.
EXAMPLE: Assembly Programming
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 (configured with the [I] command from the
main BBS command prompt). If a use 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.
N = Do not allow aliases to be used in this conference. Most echo
mail networks *DO NOT* allow aliases.
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 the
"SYSOP" in THIS conference will be automatically re-addressed to
this Co-SysOp's name.
NOTE: A person (if anyone) chosen as the Co-SysOp for this conf-
erence 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).
Leaving this item BLANK disables the re-addressing of any mail
from the SysOp to the Co-SysOp.
MESSAGE FILE PATH & FILE NAME:
Enter the complete file path and file name for this conference's
message database.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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,
however, if you are carrying, or planning on carrying Echo Mail,
check you TOSSER/PACKER software, some of these packages require
you to have a separate directory for EACH and EVERY echo mail
conference area.
CONFERENCE INTRODUCTION FILE:
Enter the full path & name of the conference intro file. The
conference "intro" 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.
Each conference may have a unique "intro" 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 a 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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 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.
CONFERENCE UPLOAD DIRECTORY SECURITY LEVEL (Private Uploads):
Enter the security level required to VIEW, SEARCH, and DOWNLOAD
files from within the PRIVATE 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 (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
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\
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.06
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
BULLETIN MENU FILE:
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.
EXAMPLE: C:\FNET\CF0000\BLTM
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
BULLETIN LIST FILE:
Enter the path and name for the Bulletin Listing file for this
conference.
EXAMPLE: C:\FNET\CF0000\BLT.LST
WHILE ON THIS SELECTION PRESS <F2> TO SETUP YOUR BLT.LST FILE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G4: BLT.LST SETUP SCREEN
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.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.07
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
See FILE STRUCTURES later in this documentation for the correct
setup of this and other 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:
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.
This file may be shared between conferences.
EXAMPLE: C:\FNET\CF0000\DORM
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
DOOR LIST FILE:
Enter the path and name for the Door list file for this
conference.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.08
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The DOOR.LST file provides a list of all this conference's DOORS.
Each conference has 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.
EXAMPLE: C:\FNET\CF0000\DOORS.LST
WHILE ON THIS SELECTION PRESS <F2> TO SETUP YOUR DOORS.LST FILE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G5: DOORS.LST SETUP SCREEN
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
file on disk. This is the name of a .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 programs 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 and menu by the user typing "MAIL".
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 default
directory is assumed.
These door RUN 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 multinode access. Some single node
doors will lock up or corrupt data if not protected from access
by another node while in use.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.09
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
DOOR PASSWORD:
If a password is entered in this field then the caller must know
the password (if he does not have SysOp Access) 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.
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 that which is specified under the Security
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.10
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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 part-
icular 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.
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 GRAPHICS IN THE DOOR SETUP MENU:
Enter "N" if you do not want a DOOR.SYS file created. In this
case a PCBOARD.SYS file is created for the door to use.
SHELL / SWAP TO DOOR:
This option gives you a choice in how you want FeatherNet PRO! to
handle how it relinquishes control to your DOORS. 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. Since we have no idea how each individual SysOp will
handle this on his 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.11
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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" (i.e. when shelling 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 FILE STRUCTURES later in this documentation for the correct
setup of DOOR files for examples of this discussion.
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".
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, over-riding
the fact the user is in RIP mode. This allows older doors (such
as TradeWars 2002) 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.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.12
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
RUNNING DOORS FROM REMOTE:
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
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
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
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 join-
ing 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.13
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G6: DIR.LST (PAGE 1) SETUP SCREEN
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.
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
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 direct-
ory. 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.14
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
WHILE INSIDE OF THE DIR.LST EDITOR PRESS <F2> TO SETUP THE SECOND
PAGE OF THE DIR.LST FILE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G7: DIR.LST (PAGE 2) SETUP SCREEN
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.
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.
WHILE ON THE ALTERNATE D/L PATH LISTING OPTION PRESS <F2> TO
SETUP THE DLPATH.LST FILE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G8: DLPATH.LST SETUP SCREEN
Each file area in each conference has a default physical file
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.15
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
┌────────────┐
│ 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 the 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 manipula-
tions, reading text file).
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.16
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
drives or have an extremely large file base, usually over 10,000
files or more.
This feature is usually desired ONLY if you utilize a CD-ROM for
storage of download files due to the slow seek times they have.
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 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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.17
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
files may also be shared between conferences.
The INDEX file is created using the utility program FNINDEX.EXE
and the procedure is described in detail in the UTILITIES section
of this documentation.
┌────────────┐
│ IMPORTANT! │
└────────────┘
This file is designed primarily for CD-ROM users and in most
cases should contain only files on your CD-ROMS 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 spec-
ified 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 6.18
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Setup - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 1 ║
╚═══════════════════════════════════════════════════════════════╝
This screen allows editing of the General BBS Configuration Info-
rmation. This is 1 of 2 screens for General information.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G9: GENERAL INFORMATION SCREEN ONE
NAME OF YOUR BBS:
Enter the name of your Bulletin Board.
This name is displayed to all callers at logon.
┌─────────┐
│ 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.
SYSOP'S NAME:
Enter the name of the system operator.
This name should have an account in the USERS file. User record
ONE ( 1 ) in the user editor portion of FNETSM should be the same
as the name entered here.
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).
USE SYSOPS REAL NAME:
This will allow you to use a different name other than the one
specified in your FeatherNet System Manager (FNETSM) User Record
One ( 1 ). The FNETSM user record one should be your name. The
SysOp Name stated above in the SysOp Name field in FNCFG -
General Information Screen One may be your real name, the word
"SYSOP", or an alias.
Y = If the SysOp logs into a system using the SysOp In - Busy or
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
Local In - Busy options, any messages left, comments made,
or screens displayed use information contained in record
number one of the USERS file.
N = When the SysOp logs into the system, any messages left,
comments made, or screens displayed use the SysOp Name
specified above rather than information contained in record
number one of the USERS file.
"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
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 question-
naire.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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. 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..
REGISTRATION NUMBER:
Enter the BBS registration number you received with your
registered version of FeatherNet PRO!
NOTE: Before opening the envelope with your registration number
you should have read the entire license agreement, copy-
right notice and limited warranty statements at the
beginning of this documentation.
If you have not yet registered FeatherNet PRO! enter a "0" as
your registration number. This will enable you to run the
Software until you have decided to register.
ADD CUSTOM "ZIP" COMMENTS:
FeatherNet PRO! has the optional ability to add custom "ZIP"
comments to new uploads as they are received. To do this, you
must set up a few things first. Please read the notes below.
Enter "Y" if you wish uploads to receive a "CUSTOM" zip
comment.
Enter "N" if you do not wish to add zip comments.
NOTE: To add zip comments, you MUST set an environment variable
in your autoexec.bat or SFN.BAT file. It should be "SET
FZIPCMT=<PATH><NAME>" where <PATH> is the DOS path to the
file containing the ZIP comment and <NAME> is the name of
the file which is the comment to be added to new uploads.
EXAMPLE: SET FNZIPCMT=C:\FNET\DISP\ZCOMMENT.TXT
If FNZIPCMT can't find this file it will abort and set a DOS
ERRORLEVEL of 1.
A sample .ZIP comment file might look like this:
This Quality Program Was Downloaded From
The Joe SysOp BBS
Call us Soon at 555-1212!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
You may name this any <PATH><FILENAME> you wish as long as the
SET command in your SFN.BAT (Start FeatherNet) or AUTOEXEC.BAT
file points to it.
NOTE: To manually add zip comments to files already on your sys-
tem, we have added a utility called FNZIPCMT. Run FNZIPCMT
from the directory where the ZIP files are located and it
will automatically add/change the zip comments of all
files in the directory.
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 logons.
Because FeatherNet PRO! is designed as a multinode 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
logons.
NOTE: Color may still be turned off/on at the main menu with the
[S] command irrespective of this setting.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Conference Configuration 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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, FN-MAIL (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 recommended.
MAXIMUM NUMBER OF MESSAGES TO CAPTURE:
This value determines the maximum number of messages that can be
archived into the capture file.
NOTE: Keep in mind that the captured messages are processed in
the work directory. If the work directory is a ram disk
it could fill up and the capture command will fail.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.06
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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 multitasker such as older versions of
DESQview.
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 up-
loads. 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 Page is turned OFF, the SysOp cannot be Paged.
When SysOp Page 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. (ie: HH:MM)
SYSOP PAGE STOP TIME:
When the SysOp Page is turned OFF, the SysOp cannot be Paged.
When SysOp Page 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 7.07
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NUMBER OF CHAT ROOMS:
FeatherNet PRO! has a multinode 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 max-
imum number of rooms is 255.
FeatherNet PRO! is designed to be a single or multinode 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.02 Documentation Page 8.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 2 ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G10: GENERAL INFORMATION SCREEN TWO
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 8.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
A user reading private mail or public mail addressed to him
during the logon sequence does not get the message read pointers
updated.
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.
The default answer is (N)o.
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. SHELLing is also performed when file
transfers or archive manipulations are performed.
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.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 8.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: New users will be able to fill out the new user question-
naire (if available) and then will be logged off immed-
iately.
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 MAIL AT LOGON:
FeatherNet PRO! can optionally force users to read waiting mail
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.
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 # ? in FNETTEXT to
reflect the change to "Y". (See the FeatherNet
UTILITIES section for more on editing the FNETTEXT file).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 8.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
NOTE: If you disable Auto ANSI you also disable the split screen
chat mode.
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.
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
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
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 8.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - General Information 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 9.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Modem/Node/Subscription Information ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G11: MODEM/NODE/SUBSCRIPTION INFORMATION SCREEN
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.
A general string for all modems is:
ATE0Q0M1V1S0=0S2=1S7=45&C1&D2H0
COMMUNICATIONS DRIVER TO USE:
FeatherNet PRO! has been designed to use both ASYNC and FOSSIL
driven communications ports. Determine how you will control your
com ports and enter an "A" or "F" here.
If you are running a single node system, a NOVELL or LANtastic
network with a single node per workstation, or other type
multitasker that does not require a FOSSIL driver (Uses
Asynchronous communications routines) then enter an "A" here.
If you are running a multinode system under DESQview 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.
If you are running under OS/2 you MUST select "A" for Asynchronous
communications.
WHICH COMMUNICATIONS PORT (0-8) IS THIS NODE LINKED TO:
Communications ports 0-8 are directly supported by FeatherNet
PRO! FeatherNet PRO! also allows non-standard serial port
addresses and IRQ's to be defined. If you use a serial port
higher than #2 then ensure you include the correct IRQ and port
address. IRQ 1-15 is supported.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 9.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Modem/Node/Subscription Information - Continued ║
╚═══════════════════════════════════════════════════════════════╝
For serial port #3 "&H3F8" 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 can handle.
EXAMPLES:
300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 76800 and
115200
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.
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 rinds 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.
NOTE: USR Dual Standards fall within this category, among others.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 9.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Modem/Node/Subscription Information - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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).
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.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 9.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Modem/Node/Subscription Information - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
NODE NUMBER:
Enter the node number you are configuring. If you have a single
node BBS, this value should be set to 1.
USING A NETWORK OR MULTI-TASKER:
This parameter will allow you to set up node numbers greater than
1. Unless you are running in a network or multitasking environ-
ment, FeatherNet PRO! will not allow you to enter a node number
other than 1.
Set this to "Y" if you are operating a multinode 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 multitasking or operating in a network environment,
set this parameter to "N".
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")
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 and type
of connection.
/C:0 (Local Logon)
/C:8 (SysOp Logon to Main Menu)
If a caller connects using an error correcting modem (to your
error correcting modem) "/ERR" is also passed. Any baud rate
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 9.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Modem/Node/Subscription Information - Continued ║
╚═══════════════════════════════════════════════════════════════╝
may be passed to FeatherNet PRO! by using the baud rate on the
command line as in: /C:2400 /C:9600 etc.
Examples: FNET /C:7
FNET /C:14400
FNET /C:7 /ERR
FNET /C:28800 /ERR
FNET /C:%1 %2
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 10.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Event Configuration ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G12: MAIN EVENT CONFIGURATION SCREEN
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.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G13: EVENT CONFIGURATION SCREEN
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.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 10.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Event Configuration - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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. DO NOT put a ".BAT
file extension on the event's actual batch file name. You may
make the event node specific by adding an extension to the
actual batch file with the node number, padded to the left with
with zeros.
EXAMPLES: DAILY (Run by all that are NOT Node specific)
DAILY.003 (Node specific)
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.02 Documentation Page 10.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Event Configuration - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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.02 Documentation Page 10.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Event Configuration - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 ║
╚═══════════════════════════════════════════════════════════════╝
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.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G14: FILE LOCATIONS ONE SCREEN
PATH OF MAIN BBS DIRECTORY:
Enter the Main directory for your BBS. This directory may be
shared by a single NODE but may NOT be shared by multiple nodes.
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 DOS drive and directory which this Node is to be
operated from. It may be the same as the main BBS directory
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 DOS drive and 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
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.
See FILE STRUCTURES later in this documentation for the correct
setup of this and other files.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G15: PWRD SCREEN ONE
SECURITY LEVEL:
Enter a Security Level to configure file ratios for. 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.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
"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.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.06
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
WHILE INSIDE OF THE PWRD EDITOR PRESS <F2> TO SETUP THE SECOND
PAGE OF THE PWRD FILE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G16: SAMPLE PWRD SCREEN TWO
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 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 monies received.
"N" = Users with this security level will not be paying by the
hour.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.07
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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:
# of Quotes in File
Quote text
Quote text
<BLANK LINE>
Quote text
<BLANK LINE>
Quote text
Quote text
Quote text
Quote text
<BLANK LINE> The BLANK line is the "terminator" marking
the end of the Quote.
EXAMPLE: C:\FNET\DISP\QUOTES.BBS
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 11.08
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 1 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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 addi-
tional 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.02 Documentation Page 12.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G17: SAMPLE FILE LOCATIONS SCREEN TWO
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 ident-
ifier (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 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 12.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 12.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
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.
SCRIPT QUESTIONNAIRES:
Enter the location of the script questionnaires. This is where
FeatherNet will look for the script questions you create to ask
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 12.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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.
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.
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! │
└────────────┘
This display file should be no more than FIVE (5) CHARACTERS!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 12.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
This is so that the actual filenames can have a numeric ident-
ifier 1-99 (2 characters max.) and a graphics identifier (1
character) attached to them. NO FILE EXTENSIONS ARE ALLOWED ON
DISPLAY FILES.
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.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 12.06
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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.
EXAMPLES: LOGOFF would be shown to non-ANSI users
LOGOFFG would be shown to ANSI users
LOGOFFR would be shown to RIP users
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 "frontdoor" 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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 12.07
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 2 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
FILE EXTENSIONS ARE ALLOWED ON DISPLAY FILES.
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.
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.02 Documentation Page 13.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 3 ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G18: SAMPLE FILE LOCATIONS THREE SCREEN
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.
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.
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.
EXAMPLES: POSTDN would be shown to non-ANSI users
POSTDNG would be shown to ANSI users
POSTDNR would be shown to RIP users
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 13.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 3 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
FAILED DOWNLOAD FILE:
Enter the Path and Name of a file to display after an
unsuccessful download.
EXAMPLE: C:\FNET\DISP\FAILDN
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.
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" FILES TO D/L DIRECTORY:
Enter the sub directory name in which all "FREE" download files
will be located. "FREE" downloads are those files which users
may download and NOT be charged for against their BYTE or FILE
ratio/count.
Download time for "FREE" files may be controlled in the next
configuration option.
EXAMPLE: C:\FNET\FILES\FREE\
STOP THE CLOCK FOR "FREE" DOWNLOADS:
Enter an "N" if you want to charge users for the TIME used when
downloading "FREE" files. Enter a "Y" to STOP the clock when
downloading "FREE" files.
NOTE: ONLY the calculated time for a "FREE" download is credited
(thus STOPPING the clock). Any additional time spent down-
loading "FREE" files is charged against the user's daily
time allowance. However, if the time used in a "FREE"
download sequence is less than the calculated time, only
the time used for the download is credited.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 13.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 3 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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 ident-
ifier (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 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.
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.
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.
EXAMPLES: EXPIRED would be shown to non-ANSI users
EXPIREDG would be shown to ANSI users
EXPIREDR would be shown to RIP users
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 13.04
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 3 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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
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.
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.
EXAMPLES: CURWORD would be shown to non-ANSI users
CUSWORDG would be shown to ANSI users
CUSWORDR would be shown to RIP users
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 13.05
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - File Locations Screen 3 - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
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.02 Documentation Page 14.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Files - System/SysOp ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G19: SAMPLE SECURITY LEVELS SCREEN - 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:
1) Execute a DOS command.
2) Edit his/her Security Level field by using the [I] command
from the Main BBS Prompt.
3) Change the [S] Status of any message to/from PUBLIC and
RECEIVER ONLY.
4) Enter Messages to a SPECIFIC Security Level (@###@) or a
range of Security Levels (@##-##@).
5) 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 14.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Files - System/SysOp - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.
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
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 14.03
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Files - System/SysOp - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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
Discretion Warranted!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 15.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Levels - Main Menu ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G20: SAMPLE SECURITY LEVEL - MAIN MENU SCREEN
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.
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 Page 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.02 Documentation Page 15.02
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Levels - Main Menu - Continued ║
╚═══════════════════════════════════════════════════════════════╝
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.02 Documentation Page 16.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Levels - File Menu ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G21: SAMPLE SECURITY LEVEL - FILE MENU SCREEN
[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.02 Documentation Page 17.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Security Levels - Message Menu ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G22: SAMPLE SECURITY LEVEL - MESSAGE MENU SCREEN
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 soft- ware. Monitor its use on your
system closely.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 18.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Function Key Programming ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G23: SAMPLE FUNCTION KEYS SCREEN
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.02 Documentation Page 19.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCFG.EXE - Saving the SRCONFIG File ║
╚═══════════════════════════════════════════════════════════════╝
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.
* Any DOS Sub directories not present will be created.
* All conference file paths and file names are verified.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 20.01
╔═══════════════════════════════════════════════════════════════╗
║ RUNNING FEATHERNET PRO! ║
╚═══════════════════════════════════════════════════════════════╝
After running the configuration program (FNCFG.EXE), you are
ready to run FeatherNet PRO!. There are several housekeeping
details you must attend to first.
MODEM:
Ensure that your modem is properly installed. If it is an ext-
ernal modem, make certain that it is connected to the proper COM
PORT. If it is an internal modem, make sure that you have the
proper COM PORT selected on your modem or COMM PORT card as app-
licable.
BBS FILES:
Ensure that FNET.EXE is in each NODE directory or somewhere in
the DOS PATH and that FNCFG.EXE, FNCHK.EXE, FNETSM.EXE, FNFILER.
EXE and FNZIPCMT.COM are in your MAIN directory (ie: \FNET)
You can now confidently run FeatherNet PRO! Do this by invoking
the SFN.BAT file. TYPE "SFN" and press <ENTER>. It is also
recommended that you place the SFN command as the last line in
your AUTOEXEC.BAT to automatically re-boot the BBS in case of a
power failure.
NOTE: Ensure the paths in SFN.BAT are correct before running the
BBS. INSTALFN.EXE does modify SFN.BAT with the proper
paths but it is advisable to view the file yourself before
starting the BBS.
If you are running FeatherNet PRO! with a FRONT-END mailer, you
will have to make extensive modifications to the SFN.BAT file.
There is a sample MAILER type SFN.BAT in the "RUNNING FeatherNet
PRO! with a Front End Mailer" appendix. You should make sure
FeatherNet PRO! is running properly BEFORE modifying your SFN.BAT
file. If you set the "USING A FRONT-END TO LOAD FNET" question
in FNCFG to "Y", you should re-enter FNCFG and set it to "N"
during initial testing. Once you are sure that FeatherNet PRO!
is operating properly and you then make the modifications to your
SFN.BAT to encompass your front end mailer, you can reset this
option to "Y".
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 21.01
╔═══════════════════════════════════════════════════════════════╗
║ RUNNING FEATHERNET PRO! - Waiting For Call Screen ║
╚═══════════════════════════════════════════════════════════════╝
The Waiting For Call Screen will look something like this.
Options are selected with the Up/Dn/Left/Right arrow keys and
executed the command by Pressing [ENTER].
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G24: THE WAITING FOR CALL SCREEN
SCREEN INFORMATION:
The "Waiting For Call" (or "WFC") screen contains a wealth of
information for the SysOp if it is read correctly. This section
will cover the information fields and option available from the
waiting for call screen.
THE HEADER:
The Header area of the WFC screen contains three pieces of infor-
mation, they are the Current Date, The BBS Name, and the Current
Time. The Current Date and Time are read from your PC's internal
clock. All are here for your convenience. The BBS name is read
from your configuration file (setup in FNCFG) and is here for
show.
THE CENTER SCREEN:
The Center area of the screen provides information on the BBS
itself and gives the SysOp time saving information. These items
are as follows:
NODE - The NODE fields simply shows what node #
you are viewing.
NEW USERS - The NEW USER field shows how many NEW USERS
have logged on since midnight the previous
night.
OLD USERS - The OLD USERS field shows you how many users
you have on the system that had logged on
previously to midnight the previous night.
CALLS - The CALLS field show the total number of calls
to the system.
SYSOP MAIL - The SYSOP MAIL field shows if you have unread
mail waiting.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 21.02
╔═══════════════════════════════════════════════════════════════╗
║ RUNNING FEATHERNET PRO! - Waiting For Call Screen - Continued ║
╚═══════════════════════════════════════════════════════════════╝
THE BOTTOM SCREEN:
The Bottom area of the WFC screen provides the balance of the
information available from this location. Among these items are
the following:
COMx - The COM field shows what COM PORT this node is
currently on.
CURRENT ACTIVITY - The CURRENT ACTIVITY field shows what the
system is doing right now, this could be
"Waiting For A Call" or "Waiting To Start
Event", etc.
LAST CALLER - The LAST CALLER field shows you who the last
caller was, where they were from and at what
time they logged off.
QUICK DESCRIPTION- The QUICK DESCRIPTION field gives you a ref-
erence about what each of the option fields do
as you move through them with the arrow keys.
SYSOP OPTION FIELDS:
LOCAL IN BUSY - This option will take you into the BBS and ask
you to sign in with name & password. You will
go through all welcome screens etc. As through
you were logging on from remote. An ATH1 will
also be sent to your modem so callers will get
a busy signal when trying to call in.
DOS BUSY - This option will exit to DOS and send an ATH1
to your modem so callers will get a busy
signal when trying to call in.
SYSOP IN BUSY - This option will take you in based on infor-
mation in USER RECORD ONE. It will not ask
you for your name, password, or make you go
through the welcome screens etc. It will show
you if there are new bulletins and new mail
waiting before it leaves you at the mail menu.
This option also sends a ATH1 to your modem so
callers will get a busy signal when trying to
call in.
DOS NOT BUSY - This option will exit to DOS but will NOT send
an ATH1 to the modem. Any users trying to call
in will see the "RING" message from their ter-
minal software but will not be answered.
FNFILER - This option takes you into the FNFILER util-
ity. See the FeatherNet PRO! Utilities sec-
tion for more information on this and other
utilities included with your FeatherNet PRO!
package. FNFILER may also be accessed from
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 21.03
╔═══════════════════════════════════════════════════════════════╗
║ RUNNING FEATHERNET PRO! - Waiting For Call Screen - Continued ║
╚═══════════════════════════════════════════════════════════════╝
within the BBS, with or without a caller on-
line.
VIEW CALLER LOGS - This option will simply let you view the
entries in the caller logs in reverse order,
last user first.
FNETSM - This takes you into the FNETSM utility. See
the FeatherNet Utilities section for more
information on this and other utilities
included with your FeatherNet PRO! package.
FNETSM may also be accessed from within the
BBS, with or without a caller on-line.
PRINTER ON Yes/No- This option simply toggles the CALLER LOG
printer output on and off. You must have set
a parallel port in FNCFG for this option to
work. MAKE SURE that your printer is TURNED
ON if you toggle this to ON otherwise you will
lockup with a printer retry error. You may
also toggle this from within the BBS, with or
without a user on the system.
FNCFG - This option takes you into the FNCFG utility.
See the FeatherNet Utilities section for more
information on this and other utilities
included with your FeatherNet PRO! package.
FNCFG may also be accessed from within the
BBS, with or without a caller on-line.
SYSOP PAGE Yes/No- This option toggles the SysOp page availabi-
lity on and off. This option may also be
toggled from within the BBS, with or without
a caller online.
NODE MONITOR - This option will let you view the status of
other nodes currently running.
PAGE BEEP Yes/No - This will toggle the System Sounds (such as
the PAGE BEEP) on and off. This option may
also be toggled from within the BBS, with or
without a caller online.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 21.04
╔═══════════════════════════════════════════════════════════════╗
║ RUNNING FEATHERNET PRO! - Sysop Functions Within The BBS ║
╚═══════════════════════════════════════════════════════════════╝
During normal operation of your BBS, FeatherNet PRO! continually
scans for SysOp key presses. These functions are listed below.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G25: The SysOp Help Screen (F10)
Here are the functions of each function key:
<F1> - Toggles SysOp Chat Availability.
<F2> - Toggles Page Bell (Beep) Status.
<F3> - SysOp Breaks into chat mode to type to a user.
<F4> - Quickly LOGOFF the caller. Recycle the modem if
nobody is on-line.
<F5> - Raise/Lower the Caller's security level. This is
a permanent change and will be saved when user
exits to DOS or logs off.
<F6> - Access the SysOp Maintenance Utility or upgrade
the caller on-line.
<F7> - Adds 1 minute to user's allowed time (Current
Logon Only).
<F8> - Subtracts 1 minute from user's allowed time
(Current Logon Only).
<F9> - Local Drop to DOS. Type "EXIT" to return.
<F10> - Displays a "Help" screen for the SysOp.
<Alt><C> - This key combination which will capture the
current screen into a file named "FNET.IMG". The
file is maintained in each node directory. It
is an appended ASCII file and is "added to" with
each capture.
<Alt><P> - This key combination toggles the printer on/off.
(If on, prints caller log output)
<SPACE> - Aborts most Menus/Messages/Text files.
<ESC> - Exit chat.
"CALL" - View Caller Logs. This can only be performed
from the Main Menu Prompt!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 22.01
╔═══════════════════════════════════════════════════════════════╗
║ MAIN MENU ║
╚═══════════════════════════════════════════════════════════════╝
Below is a sample MAIN Menu. A user is always placed at the MAIN
MENU of CONFERENCE 0 immediately following the default logon
sequence (which may include reading personal mail and the
$$LOGON.BAT).
From the main menu the user can access five (5) other menus plus
a number of other functions which are discussed below provided
they have sufficient security.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G26: SAMPLE MAIN MENU
The commands available at the main menu are in [ ] brackets.
Note that most of these commands can be restricted by security
levels covered earlier in this documentation.
The [*] command performs a "global" scan for new messages. This
includes public and private, addressed to them or not, that a
user is allowed to read. All conferences a user has "flagged"
(with the [U] command from the Message Menu) for reading will be
scanned for new mail. The user may abort at anytime by pressing
the SPACEBAR. Command is based on user's SECURITY LEVEL and is
defined in FNCFG.
The [B] command allows the user to go to the BULLETIN MENU.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [C] command allows the user to Leave the SysOp a Comment.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [D] command allows the user to go to the DOOR MENU. Command
is based on user's SECURITY LEVEL & is defined in FNCFG.
DOORS within this menu are subject to additional security level
and/or password restrictions. Command is based on CONFERENCE
SECURITY LEVEL as defined in FNCFG CONFERENCE SETUP.
The [F] command allows the user to go to the FILE MENU. Command
is based on user's SECURITY LEVEL & is defined in FNCFG.
The [G] command will log a user off the BBS. This is also known
as the Good-bye command.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 22.02
╔═══════════════════════════════════════════════════════════════╗
║ MAIN MENU - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The [H] command displays a "Help" file for the main menu
commands {MAIN.HLP}. MAIN.HLP can be edited by the SysOp and is
located in the HELP sub directory. If the SYSOP desires, add-
itional HELP files may be available for a number of reasons.
Users can view these by entering "H <Filename>" where "FILENAME"
is the actual DOS name of the help file to be viewed. Any files
to be used as additional HELP files must be located in the "HELP"
sub-directory. Command is based on user's SECURITY LEVEL & is
defined in FNCFG.
The [I] command allows users to view or change some of their user
Information:
Security Password
City/State
Default File Transfer Protocol
Telephone Number
If the user logged in has SysOp status, more information is
available to be edited. This option will allow the SysOp to
scroll through user records, edit most user information, delete
/undelete users, set conference flags, Co-SysOp Flag and Personal
Private File transfer Flag. Command is based on user's SECURITY
LEVEL & is defined in FNCFG.
The [J] command allows the user to Join another Conference area.
The user always starts in Conference 0 at logon. Command is
based on user's SECURITY LEVEL & is defined in FNCFG.
The [M] command allows the user to go to the MESSAGE MENU.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [N] command will list the "Node" status; who is on-line on
each node and what they are currently doing. This command also
allows the user to optionally enter 2 line or Group Chat. While
in 2 line or Group chat the user may get help with the H command
which displays the file CHAT.HLP located in the HELP sub-direct-
ory. The CHAT.HLP file is SysOp editable.
The [NEWS] command will re-display the NEWS display file to the
user.
The [O] command allows the user to page the SysOp Operator for a
chat. Command is based on user's SECURITY LEVEL and is defined
in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 22.03
╔═══════════════════════════════════════════════════════════════╗
║ MAIN MENU - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The [P] command allows users to set the Page Length of their
Terminal Screen. This command has no effect in RIPscrip Mode.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [Q] command allows the user to go to the QUESTIONNAIRE MENU.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [S] command toggles Screen Mode Color ANSI Graphics ON or
OFF. This command has no effect in RIPscrip Mode. Command is
based on user's SECURITY LEVEL & is defined in FNCFG.
The [T] command will display a listing of Today's callers.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [TODAY] command allows users to view the contents of the ANSI
or ASCII files produced by a "TODAY" program (as discussed in
the FNCFG section of this documentation). Command is based on
user's SECURITY LEVEL and is defined in FNCFG.
The [U] command will display a list of active Users on the BBS.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [V] command allows the user to View selected user infor-
mation and statistics contained in the display file "USRSTAT".
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
See the FILE STRUCTURES section for more information on this and
other display files.
The [VER] command will show users the current VERsion of the
FeatherNet PRO! software being used. Command is based on user's
SECURITY LEVEL and is defined in FNCFG.
The [W] command will display the Welcome (HELLO) files again.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [X] command toggles eXpert Mode (menus off) or Novice Mode
(menus on). Command is based on user's SECURITY LEVEL & is
defined in FNCFG.
The [CALL] command may ONLY be used by persons with SysOp status.
This displays the CALLer log file in reverse chronological order.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 23.01
╔═══════════════════════════════════════════════════════════════╗
║ MESSAGE MENU ║
╚═══════════════════════════════════════════════════════════════╝
Below is a sample MESSAGE MENU. From this menu all of the
messaging functions can be accessed provided the user has
sufficient security. From the selections available here, users
can capture messages for downloading, read mail, scan messages,
enter messages to other users, search messages for specific text,
flag conferences to be scanned and adjust high message read
pointers. All commands are discussed below.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G27: SAMPLE MESSAGE MENU
The [*] command performs a "global" scan for new messages
(public and private) a user is allowed to read. All conferences
a user has "flagged" for reading will be scanned for new mail.
The user may abort at anytime by pressing the SPACEBAR. Command
is based on user's SECURITY LEVEL and is defined in FNCFG.
The [A] command allows users to Archive mail for downloading.
The user can either archive the currently joined conference or
select all conferences he has flagged for scanning. The mail
will be archived using either the ZIP, ARC, ARJ or LHA
archive methods. Command is based on user's SECURITY LEVEL and
is defined in FNCFG.
The [E] command allows users to ENTER a message to another user.
Command is based on CONFERENCE SECURITY LEVEL as defined in FNCFG
CONFERENCE SETUP.
The [F] command allows a user to go to the FILE MENU. Command is
based on user's SECURITY LEVEL and is defined in FNCFG.
The [G] command will log a user off the BBS. This is also know
as the Good-bye command.
The [H] command displays a "Help" file for the Conference Area
(MSG.HLP). MSG.HLP can be edited by the SysOp and is located
in the HELP sub directory. If the SYSOP desires, additional HELP
files may be available for a number of reasons. Users can view
these by entering "H <filename>" where "filename" is the actual
DOS name of the help file to be viewed. Any files to be used as
additional HELP files must be located in the "HELP" sub
directory. Command is based on user's SECURITY LEVEL and is
defined in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 23.02
╔═══════════════════════════════════════════════════════════════╗
║ MESSAGE MENU - Continued ║
╚═══════════════════════════════════════════════════════════════╝
MSGR.HLP (Message Read Help), CLRD.HLP (Message Read
(currently displayed message) Help and FNVISUAL.HLP
(FeatherNet PRO!'s Visual Full Screen Editor Help) can
also be accessed by the Help command depending on where the
user is within the Message area and are all SysOp editable
files.
The [J] command allows users to Join another Conference area.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [K] command allows the user to Kill Messages left by him.
Those with SysOp or sufficient security level may kill other
messages. Command is based on user's SECURITY LEVEL & is defined
in FNCFG.
NOTE: This option is NOT shown on the Sample Menu.
The [L] command allows users to reset the Level of the high
message read pointer for either the currently joined conference
or ALL conferences. The currently joined conference pointer can
be set to ANY valid number while ALL conferences may be set to
either the low or high message number.
The [N] command allows users to read any NEW mail. This NEW
mail is any message numbers higher than the user's current high
message read pointer. Of course a user MUST have a sufficient
security level to read a given message.
The [Q] command allows the user to Quit to the MAIN MENU.
The [R] command allows users to Read any messages they have a
sufficient security level for. Command is based on CONFERENCE
SECURITY LEVEL as defined in FNCFG CONFERENCE SETUP.
The [S] command performs a message header Scan of the currently
joined conference. Information displayed is FROM, TO, SUBJECT,
DATE & TIME, MESSAGE STATUS. and the FIRST LINE OF THE MESSAGE.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [SS] command performs a brief message header Super Scan of
the currently joined conference. Information displayed is FROM,
TO, SUBJECT, DATE & TIME of Message and MESSAGE STATUS. Command
is based on user's SECURITY LEVEL & is defined in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 23.03
╔═══════════════════════════════════════════════════════════════╗
║ MESSAGE MENU - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The [T] command allows users to perform a TEXT search in
messages. The currently joined conference or all flagged conf-
erences may be included in this search. If a user has ANSI
capability FeatherNet will HIGHLIGHT the "found" text.
The [U] command allows users to Update flagged conference status
to be used in global message scans. Conferences flagged are
included when a [*] global new message read is performed and may
be used when archiving mail if the user so desires. Command is
based on user's SECURITY LEVEL and is defined in FNCFG.
The [X] command allows users to toggle eXpert mode - menus on or
off. Command is based on user's SECURITY LEVEL & is defined in
FNCFG.
NOTE: On the Sample Message Menu you see the command [MAIL].
This is not a Message Menu function, but rather a CALL
FILE name which calls an external DOOR program (See the
DOOR MENU section for more details on this) in this case
calling the .QWK Mail External Door Program.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 24.01
╔═══════════════════════════════════════════════════════════════╗
║ FILE MENU ║
╚═══════════════════════════════════════════════════════════════╝
Below is a sample File Transfer Area Menu. From the selections
available here, users can list/search files and descriptions,
view archives and perform manipulations such as reading files
with an archive and downloading specific files from the archive,
test archives for integrity and having them scanned for viruses,
download/upload files, perform personal private file transfer
functions if authorized by the SysOp and change default transfer
protocol.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G28: SAMPLE FILE MENU
The [D] command allows users to Download a file from the BBS.
Download means to receive a file from a remote system (BBS).
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [F] command shows the user the current FILE DIRECTORY
LISTING of all available file download directories in the
CURRENT CONFERENCE. This corresponds to the display file DIR0
which is a SysOp editable ASCII/ANSI/RIP file. From the
DIRECTORY LISTING SCREEN the user may select a single directory,
several directories or a range of directories to list. See the
FILE STRUCTURES section for more information on this and
other display files. Command is based on user's SECURITY LEVEL
and is defined in FNCFG.
The [G] command will log a user off the BBS. This is also know
as the Good-bye command.
The [H] command displays a "Help" file for the File Transfer
Area. Command is based on user's SECURITY LEVEL and is defined
in FNCFG.
The [J] command allows the user to Join a new Conference area.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
The [L] command provides a means of Listing the currently logged
(or last directory listed) file directory. This command
displays a single directory listing (DIRxx display file). See
the FILE STRUCTURES section for more information on this and
other display files. Command is based on CONFERENCE SECURITY
LEVEL as defined in FNCFG CONFERENCE SETUP.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 24.02
╔═══════════════════════════════════════════════════════════════╗
║ FILE MENU - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The [M] command allows the user to go to the MESSAGE MENU of the
CURRENT CONFERENCE.
The [N] command allows users to search for New files in the
CURRENT CONFERENCE by date range. The last search date is
maintained in the users file. Command is based on user's
SECURITY LEVEL and is defined in FNCFG.
The [P] command allows users (the SysOp has granted authoriza-
tion to) to perform personal PRIVATE file transfers. A user can
send a private file to another AUTHORIZED user and only that
user may see the name of the file and its one line description.
ONLY that user may download a personal PRIVATE file. Of course
the SYSOP has complete control of the BBS files when he is at
the computer the BBS is run on. Command is based on user's
SECURITY LEVEL and is defined in FNCFG. Command is also based on
a SysOp Set Flag and may not be accessed without BOTH qualifiers
being satisfied,
The [Q] command allows the user to QUIT to the MAIN MENU.
The [TEST] command allows users to TEST an archive for Integrity
to determine if the archived file is intact and capable of being
de-archived to disk. ULTESTER (used during this test) also uses
the SysOp's selected virus scan program to check all files in
the archive for known viruses.
The [TP] command allows users to change the users currently
defines file Transfer Protocol. Command is based on user's
SECURITY LEVEL and is defined in FNCFG.
The [U] command allows users to Upload a file to the BBS. Upload
means to send a file to a remote system (BBS). Command is based
on user's SECURITY LEVEL and is defined in FNCFG. Command is
based on CONFERENCE SECURITY LEVEL as defined in FNCFG CONFERENCE
SETUP.
The [V] command allows users to View the contents of archives.
Additionally users may read text files within an archive & down-
load specific files from within an archive. The user's file ratio
is maintained when downloading files from within an archive and
the SysOp controls the number of lines a user may read from a
text file via set parameters set in FNCFG. Command is based on
user's SECURITY LEVEL and is defined in FNCFG. Command is based
on CONFERENCE SECURITY LEVEL as defined in FNCFG CONFERENCE SETUP
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 24.03
╔═══════════════════════════════════════════════════════════════╗
║ FILE MENU - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The [X] command allows users to toggle eXpert mode - menus on or
off. Command is based on user's SECURITY LEVEL and is defined in
FNCFG.
The [Z] command allows users to perform a Zippy text search of
the file descriptions in the CURRENT CONFERENCE. This will
locate filenames or text in the descriptions. No wildcards
(*.*, ?.?) are allowed, nor are they necessary.
Searches may be done using OR (|) {pipe symbol} or AND (&)
operators as well as a single text string search. The below
examples are all assuming you are already at the file transfer
area.
"OR" SEARCH: Enter text to search using the "|" operator between
the text strings.
EXAMPLE: COMMAND: S "SEARCH"
SEARCH FOR WHAT TEXT: RON | FEATHER "ron OR feather"
DIRECTORIES TO SEARCH? A "ALL"
RESULT: Displays file descriptions or filenames in all direct-
ories containing the text "RON" OR the text "FEATHER".
This could also be input from the command line "stacked"
EXAMPLE: S RON | FEATHER A
"AND" SEARCH: Enter text to search using the [&] operator
between the text strings.
EXAMPLE: S RON & FEATHER A "SEARCH"
"ron AND feather"
"ALL"
RESULT: Displays all file descriptions and filenames in all
directories containing the text "RON" AND the text
"FEATHER".
The only thing changed is the search operators.
Directory numbers may be entered on the command line as always.
Command is based on user's SECURITY LEVEL & is defined in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 25.01
╔═══════════════════════════════════════════════════════════════╗
║ BULLETIN MENU ║
╚═══════════════════════════════════════════════════════════════╝
The BULLETIN MENU allows the SysOp to group together important
news or display files he want the users to have access to at all
times from within the CURRENT CONFERENCE. Among these files
might be the rules of the BBS or CONFERENCE, membership
information, door game scores and/or other informational reading.
The SysOp may have up to 999 Bulletins within EACH and EVERY
CONFERENCE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G29: SAMPLE BULLETIN MENU
From the bulletin menu the user will have several choices to
choose from. These options are defined as follows:
The [A] command allows the user to read All bulletins, one after
another.
The [D] command allows the user to Download bulletins. The
bulletin files MUST be in a download path in order to be
download able. The user may download one or more bulletins.
The [N] command allows the user to read only those bulletins
which are New or updated since his last logon.
The [T] command allows the user to do a Text search through all
the bulletins for a specific text string. This works exactly
like the FILE MENU [T]ext search command. If the text string is
found, the entire bulletin will be displayed with the text
string highlighted for the user (If the user is in ANSI or RIP
mode).
The [#] command simply lets a user type the bulletin number they
wish to view. The user may view more than one bulletin at a
time by separating bulletin numbers with a space.
NOTE: You will notice on the SAMPLE Bulletin Menu screen above
that the command line states that there are only bullet-
ins 1-3 available to be viewed. The SysOp has not yet
set access to bulletins 4 and 5 in FNCFG even though the
display file shows they are there. Regardless of the
display file, if a user tries to view bulletins 4 or 5
the system will tell them they don't have access to them.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 26.01
╔═══════════════════════════════════════════════════════════════╗
║ QUESTIONNAIRE MENU ║
╚═══════════════════════════════════════════════════════════════╝
The questionnaire menu allows the SysOp to display a listing of
questionnaires available to be answered within the CURRENT
CONFERENCE. Among these questionnaires might be scripts to
update user information, visiting SysOp information, user
interest scripts, etc.
The SysOp may define up to 999 Questionnaires in EACH and EVERY
CONFERENCE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G30: SAMPLE QUESTIONNAIRE MENU
The users have two options from this menu.
The [#] command allows the user to type the number of a question-
naire they wish to fill out.
The [Q] command allows the user to Quit back to the MAIN MENU.
NOTE: The number of questionnaires available in each conference
must be set in that conferences configuration screen
within FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 27.01
╔═══════════════════════════════════════════════════════════════╗
║ DOOR MENU ║
╚═══════════════════════════════════════════════════════════════╝
The DOOR menu is a SysOp definable display file which allows the
SysOp to show their users the "DOOR" programs that are available
for use, provided that they have the necessary security level
and/or passwords within the CURRENT CONFERENCE. Among these
external door programs might be BBS lists, games, files might be
the rules of the BBS, membership information, door game scores
and/or other informational reading.
The SysOp may define up to 999 DOORS within EACH and EVERY
CONFERENCE.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G31: SAMPLE DOOR MENU
Door programs may be entered in one of two ways from the door
menu. A user may enter the # of the door if you display it by
number or the user may enter the NAME of the call file as you
have defined it in the DOORS.LST editor within FNCFG.
EXAMPLE 1: Door #1 can be accessed by the user via entering a:
1 [ENTER]
EXAMPLE 2: Door 1 can also be accessed by the user typing: MAIL
[ENTER] This assumes that the CALL FILE defined in
your DOORS.LST file for door 1 is called MAIL (The
CALL FILE is the file that is called by FeatherNet
PRO!, copied to a file called DOOR.BAT and then run
to access the external program)
NOTE: External DOOR programs can also be called from the MAIN,
MESSAGE, and FILE menus by simply typing the CALL FILE
NAME defined in the DOORS.LST file within FNCFG. i.e.
If you setup a door in the DOORS.LST section of FNCFG which you
called the run file "CONNECT", you could then place the "CONNECT"
command on the FILE, MSG, or MAIN menus and if the user typed
"CONNECT" they would be taken into the door. Some SysOps use a
single letter instead of a word, however, if you do this, make
sure it does not conflict with any other letter on ANY MENU!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 28.01
╔═══════════════════════════════════════════════════════════════╗
║ VISUAL EDITOR ║
╚═══════════════════════════════════════════════════════════════╝
The Visual Editor is a full screen, easy to use, message editor.
A full help file is provided to users who are working with in it.
A brief explanation of it follows.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G32: SAMPLE VISUAL EDITOR SCREEN
Before PC Keyboard and CTRL command processing is available with
in the visual editor to allow for the broadest user base being
able to work with it.
┌─────────────────────────┐ ┌───────────────┐ ┌──────────────┐
│ Cursor Movement │ │ PC Keyboard │ │ Control Keys │
└─────────────────────────┘ └───────────────┘ └──────────────┘
Move Left a Character Left Arrow Ctrl-S
Move Right a Character Right Arrow Ctrl-D
Move Left to Previous Word Ctrl-Left Arrow Ctrl-A
Move Right to Next Word Ctrl-Right Arrow Ctrl-F
Move To Next Tab Stop Tab Key Ctrl-I
Move To Start of Line Home Key Ctrl-W
Move To End of Line End Key Ctrl-P
Move Up a Line Up Arrow Ctrl-E
Move Down a Line Down Arrow Ctrl-X
Move to Bottom of Screen Ctrl-End Ctrl-L
Move to Top of Screen Ctrl-Home Ctrl-K
Move Up a Page PgUp Key Ctrl-R
Move Down a Page PgDn Key Ctrl-C
┌─────────────────────────┐ ┌───────────────┐ ┌──────────────┐
│ Edit Function │ │ PC Keyboard │ │ Control Keys │
└─────────────────────────┘ └───────────────┘ └──────────────┘
Toggle Insert Mode Ins Key Ctrl-V
Reformat Paragraph Ctrl-B Ctrl-B
Delete a Line Ctrl-Y Ctrl-Y
Delete Char Del Key Ctrl-G
Delete Char to the Left Backspace Ctrl-H
Delete Word to the Right Ctrl-T Ctrl-T
Delete to End of Line Ctrl-N Ctrl-N
Insert a Line Ctrl-Enter Ctrl-Enter
Insert a Text File ALT-I (Local Mode Only)
┌────────────────────────┐ ┌───────────────┐ ┌──────────────┐
│ Special Functions │ │ PC Keyboard │ │ Control Keys │
└────────────────────────┘ └───────────────┘ └──────────────┘
Exit Full Screen Editor ESC Ctrl-U
Quote or List Original Ctrl-Q Ctrl-Q
ReDisplay Screen Ctrl-O Ctrl-O
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 28.02
╔═══════════════════════════════════════════════════════════════╗
║ VISUAL EDITOR - Continued ║
╚═══════════════════════════════════════════════════════════════╝
Using the above keystrokes, all systems should be able to use the
Control Key method of performing the above functions (press and
hold the <CTL> key while typing the letter key that follows it
in the above table).
The more familiar PC Keyboard keys, such as the arrow keys, will
work while on locally. They will also work if your users comm-
unications program is capable of either sending the actual key-
stroke (keyboard scan code) or an ANSI escape code equivalent
through to the host system.
An example would be calling in from remote using Telix or Qmodem
to connect to FeatherNet PRO! If utilitizing the "Doorway Mode",
keystrokes will be passed directly on to FeatherNet PRO!
INSERT MODE:
While in "Insert Mode" it should be noted that characters to the
right of the cursor will be pushed one character to the right as
each letter is typed. Pressing the <ENTER> key while in Insert
Mode will cause a new line to be inserted.
NOTE FOR SYSOPS WITH NON-PC KEYBOARD USERS!
Some modems and packet switch environments will filter out <CTL>
<S> keystrokes and interpret them to mean "Stop SendingData". In
these environments pressing <CTL><S> will not move the cursor as
expected - in fact it will appear to do nothing.
Your user will need to press <CTL><Q> to get going again. If you
have a number of non-PC users you should make this clear to
them.
You can work around this by using <CTL><A> which means move left
to previous WORD rather than moving a character to the left.
Those of you who can send either an <ESC>, then [D] or the PC
scan code for the Left Arrow will not encounter this problem and
will never have to worry about it.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.01
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - General ║
╚═══════════════════════════════════════════════════════════════╝
Every person who has ever written a BATCH file has their ideas as
to how they should be written, how they should be configured and
what should and should not go into them. It would be impossible
to cover all the billions of workable batch files that could be
created with FeatherNet PRO!. We have attempted to make batch
files as generic as possible to cover almost any situation in
installation of FeatherNet PRO! on a single or multinode system.
We can not begin to cover the principals of BATCH file
programming or batch file structure in this documentation. There
are many fine programs, tutorials, and examples available on the
bulletin board systems around the world, not to mention vast
resources in books at your local book store or public library.
We have attempted to keep the batch files a simple as possible
while maintaining usefulness.
We also can not begin to express how important your batch file
programming is. Batch files can make a system spin like a top or
crash like a lead weight dropped from a hundred feet. The
example batch files included with your FeatherNet PRO! package
will run your system as is and need no modifications. You will
find that in the near future you will want to add items into your
batch files to run programs on user recycle or upon booting up
your system. We strongly recommend that you have a good grasp of
batch file programming before attempting modifications or seek
the advice of a local person that is familiar with batch program-
ming. One further piece of advice before you proceed; " MAKE A
BACK-UP of the BATCH FILE BEFORE EDITING IT"! This will save you
time and money in the long run if your changes do not work.
REQUIRED BATCH FILES FOR FEATHERNET PRO!:
SFN.BAT - Main BBS Control Batch File
ARCMZS.BAT - Mail Archive Batch File for PKZIP
ARCMJS.BAT - Mail Archive Batch File for ARJ
ARCMLS.BAT - Mail Archive Batch File for LHA
ARCMAS.BAT - Mail Archive Batch File for PKPAK
FNETTEST.BAT - File Upload Testing Batch File
┌───────────────────────────────────────────────────────────────┐
│ THESE FILES MUST BE LOCATED IN YOUR MAIN BBS DIRECTORY AND BE │
│ MARKED "READ ONLY" │
└───────────────────────────────────────────────────────────────┘
See the following pages for examples of each of these batch file
types.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.02
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - SFN.BAT ║
╚═══════════════════════════════════════════════════════════════╝
SFN.BAT is the batch file which starts and controls FeatherNet
PRO! There is an unlimited amount of possible configurations for
this file, thus we could not even begin to print them. What we
have included is a batch file that may reside in your MAIN BBS
Directory and be used by all nodes (You must call it from the
node's "Home" directory which you want to start however). This
file "MUST" be "READ ONLY"!
(See "Setting Attributes" in your DOS manual).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.03
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - SFN.BAT - Continued ║
╚═══════════════════════════════════════════════════════════════╝
-----------------------------------------------------------------
@ECHO OFF
:Begin
SET NODE=1
SET FNDRV=C:
SET FNNODE=\FNET\NODE%NODE%
CLS
ECHO SETTING UP NODE #%NODE%
%FNDRV%
CD%FNNODE%
IF EXIST EVENT.BAT IF NOT EXIST PCBOARD.SYS DEL EVENT.BAT
FNET /C:%1 %2
IF ERRORLEVEL 255 GOTO End3 (Echo mail Entered)
IF ERRORLEVEL 254 GOTO ReStart (Fax Call Detected)
IF ERRORLEVEL 3 GOTO ReStart (Wait for new caller)
IF ERRORLEVEL 2 GOTO End3 (Reload front-end mailer)
IF ERRORLEVEL 1 GOTO End2 (DOS)
%FNDRV%
CD%FNNODE%
IF EXIST EVENT.BAT COMMAND /C EVENT.BAT
IF EXIST EVENT.BAT DEL EVENT.BAT
IF EXIST DOOR.BAT DOOR.BAT
%FNDRV%
CD%FNNODE%
ECHO SETTING UP NODE #%NODE%
SFN.BAT
:ReStart
%FNDRV%
CD%FNNODE%
ECHO SETTING UP NODE #%NODE%
SFN.BAT
:End2
ECHO OFF
DEL PCBOARD.SYS
DEL DOOR.BAT
CLS
ECHO FeatherNet PRO! Terminated!
ECHO Have a Nice Day!
:End3
ECHO Re-Loading Front-End Mailer!
-----------------------------------------------------------------
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.04
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - ARCMxS.BAT ║
╚═══════════════════════════════════════════════════════════════╝
The ARCMxS.BAT files are what FeatherNet PRO! uses to archive
messages for downloading when a user requests it from the MESSAGE
MENU. These "MUST" be located in the MAIN BBS Directory
(typically \FNET) and be "READ ONLY". There is one ARCMxS.BAT
file for each achieve method currently supported by FeatherNet
PRO! (ZIP/ARJ/LHA/PAK). The format of these files is as follows;
@ECHO OFF - Turns ECHO OFF
%FNDRV% - Changes to NODE WORK DIRECTORY DRIVE
CD %FNNODE%\WORK - Changes to NODE WORK DIRECTORY
PKZIP -ex -a %2 %1 - ARCHIVER NAME and "ADD FILES TO ARCHIVE"
command followed by %2 and %1 parameters
which are passed to the batch file by
FeatherNet PRO! with necessary
information.
CD %FNNODE% - Change to NODE DIRECTORY
The following are examples of each Mail Archive Batch File
needed:
REM ---------- ARCMZS.BAT ----------
@ECHO OFF
%FNDRV%
CD %FNNODE%\WORK
PKZIP -ex -a %2 %1
CD %FNNODE%
REM ---------- ARCMJS.BAT ----------
@ECHO OFF
%FNDRV%
CD %FNNODE%\WORK
ARJ a %2 %1
CD %FNNODE%
REM ---------- ARCMLS.BAT ----------
@ECHO OFF
%FNDRV%
CD %FNNODE%\WORK
LHA a %2 %1
CD %FNNODE%
REM ---------- ARCMAS.BAT ----------
@ECHO OFF
%FNDRV%
CD %FNNODE%\WORK
PKPAK -a %2 %1
%FNDRV%
CD %FNNODE%
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.05
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - FNETTEST.BAT ║
╚═══════════════════════════════════════════════════════════════╝
FNETTEST.BAT controls how the uploads to your system are handled.
Included with your FeatherNet PRO! system is ULTESTER, a
commercial quality upload tester and conversion program.
FeatherNet Software markets this program for other BBS packages
at a cost of $20.00 but for our FeatherNet PRO! SysOps it is FREE
OF CHARGE! You should not have to modify this batch file in any
manner UNLESS you wish to run a different upload tester.
FeatherNet PRO! is completely compatible with other fine upload
processors such as TRANSCAN.
Below is the Batch File which will run ULTESTER. Modifications
to this batch file while running ULTESTER are discouraged. This
file should reside in your MAIN BBS Directory and MUST be READ
ONLY.
REM ---------- FNETTEST.BAT ----------
@ECHO OFF
%FNDRV%
CD %FNDIR%\ULT
ULTESTER ULT%NODE%.CFG %1 %2 %3 %4
%FNDRV%
CD %FNNODE%
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.06
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - Running Multiple Nodes ║
╚═══════════════════════════════════════════════════════════════╝
Running multiple nodes with FeatherNet PRO! is not difficult. If
you wish to install more than one node, you will have to perform
the following;
MAKE FNET.EXE "READ ONLY".
When you make any file "READ ONLY" you take the responsibility
away from DOS's "SHARE" which no longer has to monitor it. None
FeatherNet PRO!'s .EXE files are written to by any utilities and
thus can and should be changed to "READ ONLY" status.
MAKE A NEW NODE DIRECTORY FOR THIS NODE TO USE.
NOTE: DO NOT confuse the BBS "MAIN" directory with the BBS
"NODE" directories.
The BBS's MAIN directory (ie: \FNET) is where the majority of the
SHARED BBS program files reside. The BBS's NODE directories are
where the individual nodes are started from ( where the node
configuration is stored and where the node is started from. Each
node "MUST" have it's OWN SEPARATE directory.
COPY THE FOLLOWING FILES INTO THE NEW NODE DIRECTORY.
NOTE: Some files are not required in the NODE directory unless
they are NODE SPECIFIC.
$$LOGON.BAT - MUST BE IN THE MAIN DIRECTORY
$LOGOFF.BAT - MUST BE IN THE MAIN DIRECTORY
SRCONFIG - MUST BE IN EACH NODE DIRECTORY
Copy your SRCONFIG file from your original NODE1
directory or any other node that you have already
setup to the new node directory for editing.
NOTE: This assumes that you are running identical conference
setups on all nodes. If you are NOT then you must have a
separate directory structure for each node that varies
from your NODE1 setup.
You "MUST" run FNCFG FROM THE NEW NODE DIRECTORY and edit the
NODE PATH and WORK DIRECTORY and any other information which
might vary from your NODE1's configuration.
Make sure that you CAREFULLY check all the paths and filenames in
the FILE LOCATION screens for proper configuration. Most errors
in setting up multiple nodes stems from overlooking these
screens!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.07
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - Running Multiple Nodes - Continued ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────────────┐
│ MAKE SURE THAT YOU SAVE THE SRCONFIG FILE AFTER EDITING! │
│ THIS WILL VERIFY/CREATE ALL PATHS AND FILES AS REQUIRED │
└───────────────────────────────────────────────────────────────┘
Setup your multi-tasker or network to handle the new node or
nodes. A later section has a small overview on quickly setting
up DESQview for use with running FeatherNet PRO! multi-line.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.08
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - Tips & Troubleshooting ║
╚═══════════════════════════════════════════════════════════════╝
┌─────────────────────┐
│ Questions & Answers │
└─────────────────────┘
You should not have any problems getting FeatherNet PRO! up and
running if you have followed the INSTALFN procedure and the
setup/configuration instructions. However, there are some folks
who perhaps will still have difficulty. Here are some additional
troubleshooting items that will hopefully provide the informa-
tion you will need for a smooth installation.
Q: When I try to run FNET.EXE I get a "fatal" error and the
program recycles continuously. What's going on?
A: Check the SET statements in your "SFN.BAT" and confirm
that all paths are correct. Also check all paths you may
have added both in the "SFN.BAT" file and the SRCONFIG
file for the node which you are setting up.
Also, ensure you have edited the com port/node setup in
FNCFG.EXE. If you are running a single node BBS, the
node MUST be "1".
Q: FeatherNet PRO! loads and waits for a call but when I
call the BBS, it doesn't answer. What's wrong?
A: Run "FNCFG.EXE" and check your modem initialization
string. DO NOT put "ATZ" anywhere in it unless you
are sure your modem has the proper string saved in NRAM
(non-volatile ram).
Remember, your modem must send verbal response codes and
that auto-answer MUST be DISABLED. Run MODEMSET and
reinitialize your modem.
┌──────┐
│ Tips │
└──────┘
If you have any trouble getting FeatherNet PRO! running, run
"FNCFG.EXE". Ensure ALL items are edited/verified. Then SAVE the
setup.
NOTE: A single Node BBS MUST be identified as Node 1.
The Node home directory MUST be identified as well. If this is a
single node board, the FeatherNet PRO! Main directory (ie: \FNET)
and the Node directory may be the same DOS directory, but it is
"NOT RECOMMENDED".
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.09
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - Tips & Troubleshooting - Continued ║
╚═══════════════════════════════════════════════════════════════╝
Double check the paths in "SFN.BAT" and the other ".BAT" files
which are included. Ensure they are correct for your system
setup.
If you have extended or expanded memory available, a virtual
(RAM) disk setup as your "WORK" directory will increase perform-
ance and dramatically reduce hard disk access. It is especially
beneficial to use a RAM disk for loading your FNETTEXT prompt
file.
For the same reasons in #3 above, if you have extended or expand-
ed memory available, install a disk cache.
If your modem has Non-Volatile Ram (NVR, NRAM, etc.) you should
enter the modem initialization string into the modem's NVRAM and
ONLY use "ATZ" in your FeatherNet PRO! modem initialization
string. If your modem is a US Robotics HST or Dual Standard (or
any other high speed modem) you should have the com port initial-
ized at the opening baud rate (i.e. 19200, 38400, etc.) before
saving the initialization string into the modem's NRAM with the
"AT&W" command.
NOTE: You do NOT have to put in a modem initialization string if
the NODE is being handled by a "Front End Mailer Program",
however, you must still provide all other information.
If there are any problems not mentioned here which are keeping
FeatherNet PRO! from operating properly, please call FeatherNet
PRO! Support. Voice calls will be accepted on a LIMITED basis
for unregistered SysOps. Registered SysOps, please keep in mind
that we will always be more than happy to help you with any
aspect of setting up and operating the FeatherNet PRO! system.
We can only offer limited help when dealing with the operation of
third party programs.
┌──────┐
│ Tips │
└──────┘
Please contact the authors of third party programs before calling
FeatherNet Technical Support. Your cooperation is most apprec-
iated in this matter.
Anyone may make use of the FeatherNet Echo mail conference via
LinkUSA. There you will find many FeatherNet PRO! SysOps who read
the echo and are more than willing to give you a hand setting up
and running your FeatherNet PRO! system.
The following files should be obtained by you and placed some-
where in your PATH. FeatherNet PRO! uses these files for file
transfer functions and archive manipulations.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.10
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - Tips & Troubleshooting - Continued ║
╚═══════════════════════════════════════════════════════════════╝
PKUNZIP.EXE
PKZIP.EXE
PKUNPAK.EXE
PKPAK.EXE
LHA.EXE
ARJ.EXE
DSZ.COM (or .EXE) or GSZ.EXE (Renamed DSZ.EXE)
Other Optional External Protocol Drivers
Ensure that your modem initialization string TURNS ON DTR and
ENABLES hardware flow control.
Ensure that your modem initialization string DISABLES AUTO
ANSWER.
FeatherNet PRO! handles the ring detect and gives the "ATA"
answer command to the modem.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 29.11
╔═══════════════════════════════════════════════════════════════╗
║ BATCH FILES - Error Codes ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! has built-in error handling which intercepts
potential problems before they generate a "fatal" error. In the
unlikely event of a fatal error when a user is logged onto the
BBS, FeatherNet PRO! will recycle and the user will remain on-
line and in control of the BBS. If you have an unlikely error
which prevents the BBS from running, the cause is one of a few
possible situations. Please check the following for possible
glitches:
A corrupted message file or message index file. Run FNPACK or
PROPACK to attempt to repair the message file. Run FNPACK with
the "/IN" (index pack) command line.
If you receive an error #76 the cause is that a file exists with
the name you attempted to give to a sub-directory in FNCFG. You
will need to check for an existing filename in which you have
specified in FNCFG to be a sub-directory. DOS does not know how
to handle a file named with the same name as the sub-directory it
is in (i.e. The filename TEMP in a directory called /TEMP). You
probably have noticed by now there are very few files used by
FeatherNet PRO! with file extensions. You must take some care
that you do not name a filename the same as a directory name or
you will receive a DOS error.
If you edit ANY of the FeatherNet PRO! data file by hand, you
must use EXTREME CARE. There are no cases in which this procedure
is necessary! One note for all of you who will try and manually
edit your files anyway, is that all data and configuration files
used by FeatherNet PRO! can NOT have a blank line between the
last line of the file and the EOF marker or you will receive an
error. It is HIGHLY recommended you only edit these files with
the provided configuration editor utilities!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 30.01
╔═══════════════════════════════════════════════════════════════╗
║ SYSOP UTILITIES - General ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet Software, Inc. has included with FeatherNet PRO! a
number of utilities to handle various aspects of managing your
system. Among these are FNETSM, the system manager, FNFILER, the
file base and file description manager, LOCALUP, an enhanced
local upload file handler, FNPACK a message base packer, FN-NET a
message pointer update utility for echo mail conferences, and
MODEMSET, a utility to help you setup your modem for use with
FeatherNet PRO!
We have included these utilities to enhance the quality of your
BBS and to save you time and trouble in the running of your
board as a hobby or business. Unlike some other BBS software
companies, we include these utilities for your use free of
charge and will continue to develop quality utilities as the
need arises to enhance our product and your enjoyment.
If you have an idea for a utility that would benefit FeatherNet
PRO! SysOp's, we encourage you to leave a note to us on the
FeatherNet HQ BBS telling us about it and we will see what we
can do. We have a vast resource of information available and
the utility may already exist by a third party programmer. If
we don't have the utility, we will definitely consider writing
it if we have enough requests.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.01
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - FeatherNet PRO!'s System Manager ║
╚═══════════════════════════════════════════════════════════════╝
Like most other FeatherNet PRO! utilities (FNCFG, FN-NET, etc.)
FNETSM must be run from a node "Home" directory.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G33: SAMPLE FNETSM MAIN SCREEN
Moving around in the FeatherNet PRO! system manager is just like
most of the other editors. Simply move the field bar with your
up and down arrow keys until you are on your choice and press
[ENTER]. You may also press the <ESC> key to exit back to DOS or
wherever you called FNETSM from.
[A] EDIT USERS - Lets you edit Information in your
user's records including financial &
conference availability
[B] CREATE USER INDEX - RE-writes the user index files
[C] PACK USERS - Purges deleted users from the users
file
[D] PURGE USERS - Purges user who have not called in x
number of days
[E] DEFINE EDITORS - Lets you set your favorite editors for
use in FNCFG
[F] FNCFG - Takes you into FNCFG & returns you here
when completed
[G] FNFILER - Takes you into FNFILER and returns you
when completed
[H] PRINT USER RECORDS - Lets you print out the records of your
users
[I] SORT USER RECORDS - Let's you sort your user base by a
number of methods
[J] STANDARDIZE FORMATS - Checks and standardizes the format of
all phone #'s in the user records
[K] ABOUT FEATHERNET - Displays a Information about Feathernet
Software, Inc., their authors and
addresses and the node version you
currently have.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.02
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users ║
╚═══════════════════════════════════════════════════════════════╝
[A] EDIT USERS:
FNETSM handles a lot of record management for you. When a new
user logs onto your system FeatherNet PRO! it asks all the
questions it needs to keep track of each user and handle the
account. The System Manager user edit area will let you edit
and manipulate that data, take care of all the user financials
for you, and allow you to manage each user on an individual
level.
Below are explanations on each items you may encounter:
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G34: SAMPLE USER EDITOR SCREEN ONE
<F1> Help - Display the Help screen
<F2> Toggle - Go to 2nd page of users record
<ALT A> Add User - Add a user to the users file
<ALT B> Bottom Record - Go to last user record on file
<ALT C> Clear Record - Clear this user record
<ALT D> Delete Record - Delete this user record
<ALT F> User Finance - Go to users financial screen
<ALT L> Repeat Last Search - Search for information in all
user records
<ALT M> Conf Registration - Go to users conference regis-
tration screen
<ALT R> Restore Record - Restore this record
<ALT S> Text Search - Do a text search through all
user records
<ALT T> Top Record - Go to 1st user record on file
<CTL PgUp> Rev 20 - Go back 20 users records
<CTL PgDn> Fwd 20 - Go forward 20 users records
<PgUp> Rev 1 - Go back 1 user record
<PgDn> Fwd 1 - Go forward one user record
USER'S NAME:
Enter the users Complete Name. The name may be a maximum of 25
characters long. The name must not start with a number or the
system will reject it.
CITY AND STATE USER IS FROM:
Enter the city and state the user is from. This is a "text" field
so any format you desire may be used.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.03
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
USER'S SECURITY PASSWORD:
This may be up to 12 characters. It is "Strongly" recommended
you do NOT let users use an easy password such as their first or
last name. Sometimes it is good to have a bulletins explaining
the importance of unique passwords and the rules about sharing
their account and passwords with others.
BUSINESS/DATA PHONE NUMBER:
This should be the user's "Work" or "Data" phone number. Any
format may be used. You may standardize phone numbers with FNETSM
option [J] at the main menu.
VOICE PHONE NUMBER:
This should be the user's "Voice" (Home Phone) number. Any format
may be used. You may standardize phone numbers with FNETSM option
[J] at the main menu.
USER'S SECURITY LEVEL:
Enter the users security level. This may range from 0 to 255.
The security level entered must have been set up in the
FeatherNet PRO! configuration editor's (FNCFG) PWRD file located
on the file location's one screen. Otherwise, the next time the
user logs in, he/she will be dropped to whatever security level
you have set up for newuser status.
DELETED USER FLAG:
Enter a "Y" to have the users account deleted. When you pack your
user base the next time, such as in your system event.
An alternate method to mark this user for deletion is to press
the <ALT D> keys.
EXPIRATION DATE:
If operating in subscription mode, enter the user's expiration
date in "yymmdd" format.
EXAMPLE: 911225
LAST DATE ON SYSTEM:
Enter the date the user last logged onto the BBS. Utilize the
"mm/dd/yy" format.
EXAMPLE: 04/18/91
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.04
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
TIME USED TODAY:
Enter the time to be charged to the users maximum allowed time
for Today. If you set this field to "0" and the user calls back
during the same day, the user will have the full amount of time
as defined in the PWRD file for his/her security level.
USER'S TEXT PAGE LENGTH:
Enter the user's screen height. This setting controls the number
of lines in a file or message that will be displayed before a
"More" prompt is sent. 24 is recommended for most users.
TIMES LOGGED ONTO BBS:
Enter the number of times the user has logged onto the BBS.
FILE TRANSFER PROTOCOL:
Enter the letter which signifies the default file transfer
protocol to use. This letter "Must" match one specified in the
"FNETPROT.DAT" file.
FILES DOWNLOADED TODAY:
Enter the number of files this user has "Downloaded Today". This
number is reset to zero at midnight.
NUMBER OF UPLOADS:
Enter the Number of Files the user has "Uploaded" to your BBS.
NUMBER OF DOWNLOADS:
Enter the number of files the user has "Downloaded" from your
BBS.
BYTES DOWNLOADED TODAY:
Enter the total number of bytes the user has "Downloaded" from
your BBS today.
BYTES UPLOADED TO BBS:
Enter the total number of bytes the user has "Uploaded" to your
BBS.
BYTES DOWNLOADED FROM BBS:
Enter the total number of bytes the user has "Downloaded" from
your BBS.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.0 Documentation Page 31.05
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
ALLOWED TO USE THE [P]RIVATE FILES FUNCTION:
Enter "Y" if you want this user to be able to use the private
file transfers command from the file transfer area. Persons who
use this command may send private files to any user who also has
authorization to use the [P] command.
PRIVATE FILES AWAITING DOWNLOAD:
Enter "Y" if you want to flag this user's account to indicate
"Private" files are waiting to be downloaded.
This allows the SysOp to make files available for users who are
allowed to use the "Private" upload and download functions
Private files uploaded by one user to another will cause this
bit to be set automatically.
Press <F2> to toggle between the 1st and 2nd page of the users
record.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G35: SAMPLE USER EDIT SCREEN TWO
USER'S NAME:
Enter the users complete name. The name may be a maximum of 25
characters long. The name must not start with a number or the
system will reject it.
NOTE: This is carried over from the user record - page one.
USERS ALIAS NAME:
Enter the users alias or nickname. This name will be allowed to
be used in place of the users real name based on your configura-
tion setup. (FNCFG.EXE)
USERS STREET ADDRESS #1:
Enter the users street address #1. This would normally be the
physical street address. Use street address #2 for post office
boxes, apartment numbers suite numbers, etc.
USERS STREET ADDRESS #2:
Enter the users street address #2. Normally this is the post
office box, apartment number, suite number, etc.
Use street address #1 for the "Physical Street" address.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.06
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
USERS CITY:
Enter the city from where the caller is actually calling from.
USERS ZIPCODE:
Enter the users postal zip code. This may be either in the 5 or
in the 5+4 code format.
EXAMPLE: "12345" or "12345-6789"
NUMBER OF MESSAGES THE USER HAS LEFT:
This number reflects the number of messages the user has left
whether private or public.
USERS DATE-OF-BIRTH:
Enter the users Date-Of-Birth. The format is "mm/dd/yy".
NOTE: The "/" will automatically be placed between the proper
fields.
USERS SEX:
Enter "F" for female or "M" for male.
USERS PERSONAL COMMENT:
This reflects the users personal comment that was entered when
logging on. This may be edited by the user. If this field is
not filled in by the user a default line of "I LOVE COMPUTERS"
will be inserted.
NOTE: This field may be displayed with the @UCOMMENT@ macro in
a display screen.
SYSOPS USER COMMENT:
This field is used for the SysOp to store any information about
the user. note: this information is private and may only be
seen by the SysOp in FNETSM.
USERS STATE OR PROVINCE:
Enter the state or province the user is actually calling from.
USERS COUNTRY:
Enter the country the user is calling from.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.07
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
CLEAR SCREEN "BETWEEN" MESSAGES:
Enter a "Y" to clear the screen "Between" messages.
Entering an "N" in this field will allow the screens to "Scroll",
including the header.
SCROLL SCREEN WHILE READING MESSAGES:
Entering a "Y" will cause the screen to scroll normally.
Entering an "N" will "Lock" the message header at the top of the
screen while the message text scrolls.
USE THE HI-LITED FLAG AND/OR VIEW OPTION:
Entering a "Y" will allow the user to use the hi-lighted file
marking method when viewing or flagging files. User must have
ansi capabilities to use this feature. Normal operation is used
if an "N" is entered.
Press <ALT><F> for the users financial record screen.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G36: SAMPLE USER FINANCIAL SCREEN
When running in subscription mode you can charge users by the
hour. FeatherNet PRO! has simplified this sometime bothersome,
tedious, and time consuming task for you. In most cases all you
must do is enter the amount of money received and how much you
are charging that particular user for an hours worth of time.
AMOUNT RECEIVED (SysOp Edit):
Enter the amount of funds you have received from this user to be
credited to his account. This amount will be used to calculate
the total amount of money received and the total number of hours
purchased. To clear the entry before leaving this field, press
the <ALT><C> key combination.
TOTAL MONEY RECEIVED (Calculated Field):
You do not enter any information in this field. FeatherNet PRO!
will show the total money received from the user here. This field
is updated each time you add to the money received field.
COST PER HOUR (SysOp Edit):
Enter the cost for one hour of system use to this user. This
figure combined with any prior balance determines the amount of
time a user has "Bought". The figure you enter is immediately
used to recalculate any remaining balance.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.0 Documentation Page 31.08
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: Altering this value permanently changes the subscription
time remaining for this user and adjusts the account's
balance automatically.
CURRENT MONEY USED (Calculated Field):
This field is calculated by cost per hour multiplied by the time
used and shows how much the user has spent.
AMOUNT OF BALANCE (Calculated Field):
This field is calculated by total money received minus the money
used and shows the users current balance of spendable money.
HOURS PURCHASED (Calculated Field):
This field is calculated by total money received for the cost per
hour and shows how many total hours the user has ever purchased.
CURRENT HOURS USED (Calculated Field):
This field is calculated by current money used and cost per hour
and shows how many hours the user has used to date.
CURRENT HOURS AVAILABLE (Calculated Field):
This field is calculated by amount of balance and cost per hour
and shows how many hours the user has left on account.
DAYS BEFORE EXPIRE (Calculated Field):
This field is calculated by current hours available and
hours available per day (set in PWRD file) and give you an idea
of how long before the users subscription runs out. This field
is also used to determine when the expired warning file will be
displayed to the user as his account comes close to expiring.
LAST PAYMENT DATE (Calculated Field):
This field is calculated by the last time you entered a payment
into the amount received field. Each time you edit the amount
received field the date will record here.
Press <ALT M> for users conference registration screen.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G37: SAMPLE CONFERENCE REGISTRATION SCREEN
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.09
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Edit Users - Continued ║
╚═══════════════════════════════════════════════════════════════╝
This area lets you override a users access to the conferences of
your BBS. You may give access to a conference a user usually
would not have access to or in fact make him a Co-SysOp of that
conference if you wish. Care should be used when editing the
user's available conferences.
CONFERENCE REGISTRATION FLAG:
Enter an "X" to register a user in a conference or press the
[SPACEBAR] to UNregister a user in a private or public conf-
erence. Note that a user "Must" be registered by the SysOp to
have access to a private conference.
A user not already registered in a public conference "Must" have
a security level equal to or greater than that required to read
messages in the conference in order to join the conference unless
the SysOp manually registers the user using this utility.
CO-SYSOP CONFERENCE REGISTRATION FLAG:
Enter an "X" to designate a user as a Co-SysOp for a conference.
Use the [SPACEBAR] to deny the user access to Co-SysOp priv-
ileges.
The user "Must" meet the normal criteria to join a conference
(Private or Public) to be recognized access as a Co-SysOp by the
FeatherNet PRO! software. A user with Co-SysOp privileges can do
the following in a conference:
Read Any Mail - Public or Private
Delete - (Kill) Any Message
Edit Any Message
NOTE: The use of this should be done with caution, and only
those whom you trust should be granted Co-SysOp status.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.10
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Create Users Index ║
╚═══════════════════════════════════════════════════════════════╝
[B] CREATE USER INDEX FILES:
This function will very quickly sort the users file and creates
26 individual updated user index files which the system uses to
create user records. It is recommended that you use this after
you do work within the edit user section of FNETSM.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.11
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Pack Users Filebase ║
╚═══════════════════════════════════════════════════════════════╝
[C] PACK USERS FILEBASE:
This function will delete all user records that have been tagged
for deletion in the users record by you in the edit user section
of FNETSM in the purge user by call date section. This function
is irreversible! Make SURE that there are no records that should
be kept are "Tagged for Deletion" before you run this. It is
recommended that you use the print user records option before
packing the user base. When this function finishes it will then
automatically re-index your user files (Option B).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.12
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Purge Users ║
╚═══════════════════════════════════════════════════════════════╝
[D] PURGE USERS BY CALL DATE:
This function will search through all the user records and search
for all records with a "last called" date older than that which
you specify and a "Security Level" lower than you specify. If any
records are found meeting the criteria they will be tagged for
deletion when the user base is next packed. It is recommended
that you verify the users records "Tagged for Deletion" in the
edit user section before packing your user base.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.13
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Define Text & Graphic Editors ║
╚═══════════════════════════════════════════════════════════════╝
[E] DEFINE TEXT AND GRAPHICS EDITORS:
Enter the full path and filename of your favorite text editor.
EXAMPLE: C:\DOS\EDIT.EXE
Enter the full path and filename of your favorite ansi editor.
EXAMPLE: C:\ANSI\THEDRAW.EXE
This will allow you to edit menus and batch files that are
defined in various configuration editors in FeatherNet PRO! with-
out leaving the configuration editor. Most of the FeatherNet PRO!
configuration editors will allow you to edit the ascii or ansi
files by simply pressing <F2>(ascii) or <F3>(ansi). You will see
a highlighted bar at the bottom of the editor screen which will
tell you the "F" key(s) to press to edit the file whose name is
being edited.
Some files only allow a ascii editor to be used when there is no
ansi version of the file to be created. When ansi versions of
menus and text files are to be edited, you must keep in mind
that the length of the file name *MUST* be 4, 5, 7 or fewer
characters depending on the type of screen it is (check the
display file list for further information) and there *MUST NOT*
be a file extension on the file name.
A "G" should be appended to the ansi version of a file you wish
to maintain both ansi and ascii versions of and an "R" to RIP
versions of the file (you can not enter RIPaint from any
FeatherNet PRO! configuration editors). The "G" or "R" should
not be reflected in the name that you enter into the configura-
tion editor, but only in the name you give the physical file.
FeatherNet PRO! will allow you to use one xcode file for menus
and text files versus having you maintain one ascii and one ansi
version. Simply name your display file without a "G" appended
to it and if the user has ansi turned off, FeatherNet PRO! will
strip color xcodes from the file before it is display to them.
FeatherNet PRO! uses "PCBoard" designated color xcode system.
When you press either key while your field selection bar is on
the defined path and filename the configuration editor will call
your favorite editor and load the filename for you to edit. When
you are done editing the file, simply exit the program and you
will be returned to the same place you were in the configuration
editor.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.14
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - System Configuration (FNCFG) ║
╚═══════════════════════════════════════════════════════════════╝
[F] SYSTEM CONFIGURATION (FNCFG):
This calls and allows you to work in the FeatherNet PRO! config-
uration editor and returns you here when you leave FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.15
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - File Directory Utility (FNFILER) ║
╚═══════════════════════════════════════════════════════════════╝
[G] FILE DIRECTORY UTILITY (FNFILER):
This calls and allows you to work in the FeatherNet PRO! file
utility FNFILER and returns you here when you leave FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.16
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Print User Records ║
╚═══════════════════════════════════════════════════════════════╝
[H] PRINT USER RECORDS
This function will allow you to print out a list of the users on
your system and their information.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G38: SAMPLE PRINT USER RECORDS SCREEN
FNETSM will ask you which records you want to print:
Enter record to start printing at: Example: 1
Enter record to end printing at: Example: 12
FNETSM will then determine which format of information you want
printed (A,B,C):
[A] Short Format (one line) - Name, city & state, security
level, voice phone
[B] Long Format (multiple lines) - Complete users record info
[C] Expiration Date (one line) - Name, voice phone number,
expiration date
FNETSM will ask you where you want the information printed:
Parallel port: EXAMPLE: 1
FNETSM will then proceed to print out the information that you
have requested. It is suggested that you use this function once
in a while and before packing your user base in case you accid-
entally delete a user and need to re-enter their information into
the system by hand.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.17
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Purge By CallIndex ║
╚═══════════════════════════════════════════════════════════════╝
[I] SORT USER RECORDS:
FNETSM will allow you to sort your user records in a number of
ways. This allows you to run data checks on your users in a
matter of seconds! Check for multiple users using the same pass-
word or home phone number, calculate how many users you have by
city or find out in an instant who is entering messages and who
isn't. This function is one of FNETSM's most powerful features
and we think that you will find it one of the most useful util-
ities included in the FeatherNet PRO! package!
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G39: SAMPLE USER RECORD SORT SCREEN
SORTING THE USER RECORDS:
Use your up and down arrow keys or press the letter to select you
preferred sorting method.
[A] Name - Sort by user names,ascending or
descending
[B] Password - Sort by passwords, ascending or
descending
[C] Voice Phone - Sort by voice numbers, ascending or
descending
[D] Data Phone - Sort by data numbers, ascending or
descending
[E] City / State - Sort by city/state, ascending or
descending
[F] Registration Expiration - Sort by expiration date, ascending
or descending
[G] Security Level - Sort by security level, ascending
or descending
[H] Date-Of-Birth - Sort by date of birth, ascending or
descending
[I] Messages Left - Sort by messages left, ascending or
descending
After choosing a sort method, FNETSM will ask whether you want
the records sorted in ascending or descending order. FNETSM will
then sort the user files and then update your user index files
automatically.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.18
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Standardize Phone Formats ║
╚═══════════════════════════════════════════════════════════════╝
[J] STANDARDIZE PHONE FORMATS
This function simply goes though all your user records and puts
all phone numbers into the " xxx xxx-xxxx" format which provides
meaning to the SORT BY PHONE NUMBER option.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.19
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - About FeatherNet Software ║
╚═══════════════════════════════════════════════════════════════╝
[K] ABOUT FEATHERNET SOFTWARE:
This option gives you information about the software you are run-
ning.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 31.20
╔═══════════════════════════════════════════════════════════════╗
║ FNETSM.EXE - Command Line Operation ║
╚═══════════════════════════════════════════════════════════════╝
FNETSM supports a limited command line mode of operation which
allows you to perform INDEXing, SORTing and PACKing from the
command line. This will typically be used during a system EVENT.
The command line options MUST be preceded with a "/" (forward
slash.
PACK and INDEX options expect "ONLY" /PACK and /INDEX respect-
ively.
SORT, on the other hand, is a little more involved. There are
nine sort options. Sorting may be performed in ascending
(default) or descending order.
SORTING OPTIONS:
(1) Sort by User Name
(2) Sort by Password
(3) Sort by Voice Phone
(4) Sort by Data/Business Phone
(5) Sort by City/State
(6) Sort by Registration Expiration Date
(7) Sort by Security Level
(8) Sort by Date of Birth
(9) Sort by Number of Messages Left
The command line for the SORT option is:
FNETSM /SORT <option> <direction>
Where <option> is 1-9 above and <direction> is 0 for ascending
order and 1 for descending order.
EXAMPLE 1: FNETSM /INDEX
The above command will create new FNPNDX.x user record index
files.
EXAMPLE 2: FNETSM /PACK /SORT 1 1
This command line first performs a PACK of the USERS file
followed by a SORT on the name field (#1 in the selection list
above) in DESCENDING order (reverse alpha order).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.01
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - General ║
╚═══════════════════════════════════════════════════════════════╝
FNFILER is the FeatherNet PRO! SysOp's file directory manager.
It will move or copy, files and descriptions from any of your
conference file directories to any other specified conference
directory path and DIRxx file respectively. It will also delete
unwanted files from any of your conference file directories and
delete the entry from your DIRxx file. In addition to these
actions FNFILER allows the SysOp to edit a file description list-
ing file (DIRxx) and [V]iew archives and read text files within
them.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G40: SAMPLE FNFILER MAIN MENU SCREEN
Upon running FNFILER for the first time, you must chose option
[E] and answer the questions posted. This will insure that
FNFILER is properly configured for your system and with your pre-
ference in DIRxx handling.
[A] EDIT DIR FILES - This allows you to edit your file
descriptions.
[B] LOCATE FILE ON DISK - This will allow you to locate a
particular file that is/might be
on your hard drive.
[C] LOCATE FILE IN DIR FILES - This will allow you to locate a
file description with your DIR
files.
[D] LOCATE TEXT IN DIR FILES - This will locate the text you
input with the filebase, either in
the DIR file or the filename
itself.
[E] EDIT FNFILER DEFAULTS - This will allow you to edit the
standard defaults for FNFILER.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.02
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - General ║
╚═══════════════════════════════════════════════════════════════╝
EDIT DIRxx FILES:
This is the main function selection of FNFILER. Within this area
you handle all file manipulations and DIRxx file edits. Upon
selection of this function, FNFILER will present you with a
listing of all of the conference areas set up for your BBS.
Use your up and down arrow keys to move the selection bar to the
conference which you want to edit and press <ENTER>.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.03
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - Selecting A Conference & Directory ║
╚═══════════════════════════════════════════════════════════════╝
Once you have selected your conference, you will be presented a
file directory screen listing all the file directories within
the current conference plus your upload and private upload areas
within that conference. Again, use your up and down arrow keys
to select the file directory and corresponding DIRxx file that
you wish to work with and press <ENTER>.
FNFILER will now bring you into the FNFILER editor screen and
load the DIRxx file for that file directory, if it exists.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.04
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - DIR File Editing Key Controls ║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G41: SAMPLE FNFILER EDIT SCREEN WITH FILE DESCRIPTION
From the FNFILER editor you can perform just about any manipula-
tion you could hope for. Below some of these are discussed in
detail. When the FNFILER editor loads you will the first descrip-
tion in the DIRxx file, if the file is not in the correct format
and you try to leave it, the editor will beep a warning to you.
You may use the editor to re-write the description, color the
description, draw ansi boxes or lines, and much more. The follow-
ing commands are available:
<F1> Help - This will give you a brief reminder
of the commands available
<F2> View - View the contents of the currently
displayed file. (zip/arj/lha)
<F3> Delete - Toggle delete flag for file & desc-
ription currently displayed
<F4> Copy - Toggle copy flag for file & desc-
ription currently displayed
<F5> Drive Space - Obtain free space on any disk drive
on your system
<F6> Find Text - Do a text search of entire DIRxx
file you are currently working with.
<F7> Repeat Search - Continue last text search in current
DIRxx file.
<F8> Restore - Restore original description before
editing.
<F9> EOF - Go to end of description
<F10> Justify - Justify file description (make all
lines even)
<PgUp> Page Down - Go back one record
<PgDn> Page Up - Go forward one record
Arrow Up ─┐
Arrow Down ├> Use these keys to move your
Arrow Left │ cursor around the screen
Arrow Right ─┘
<ALT A> Add - Add a file description
<ALT B> Bottom - Go to last file in DIRxx
<ALT C> Case - Proper name case description
<ALT I> Insert - Insert line in file description
<ALT J> Jump - Drop to a DOS shell
<ALT M> Move - Toggle the move flag on this file
<ALT S> Sort - Sort the DIR file being edited
<ALT T> Top - Go to top of DIRxx file
<CTL R> Repeat - Select last copy/move settings
<CTL T> Del Word - Delete word where cursor is
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.05
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - DIR Editing Key Controls - Continued ║
╚═══════════════════════════════════════════════════════════════╝
<CTL Y> Del Line - Delete line where cursor is
<CTL-R.Arrow>Move Right - Move word right
<CTL-L.Arrow> Move Left - Move word left
<CTL PgDn> Fast Forward - Go forward 20 files
<CTL PgUp> FastBack - Go backward 20 files
<CTL End> Del EOL - Delete all characters to the EOL
<CTL Home> Goto Top - Go to the upper left of the DIRxx
<Shift F1> ┌ ─┐
<Shift F2> ┐ │
<Shift F3> └ │
<Shift F4> ┘ │
<Shift F5> ─ │
<Shift F6> | │
<Shift F7> ├ │
<Shift F8> ┤ │
<Shift F9> ┴ │
<Shift F10> ┬ ├ Used for line drawing
<Ctl F1> ╔ │
<Ctl F2> ╗ │
<Ctl F3> ╚ │
<Ctl F4> ╝ │
<Ctl F5> ═ │
<Ctl F6> ║ │
<Ctl F7> ╠ │
<Ctl F8> ╣ │
<Ctl F9> ╩ │
<Ctl F10> ╦ ─┘
<Tab> Tab - Tab Forward
<Shift Tab> Tab Back - Tab Reverse
<Del> Delete - Delete Char at Cursor
<Home> Jump 1 - Move to Column 1
<Enter> New Line - New Line & Insert "|"
<End> Move Right - Move to RightMost Column
<Bksp> Backspace - Delete Char to Left
<Ins> Insert - Toggle Insert Mode
<Esc> Quit - Quit File and Make Changes
LOCATE FILE ON DISK:
This function allows you to search all paths listed in your
dlpath.lst and DIR.LST files. It will not search your index
file. Wildcards are allowed.
LOCATE FILE IN DIRxx FILE:
This function allows you to search all of your DIRxx files for a
specific file name.
LOCATE TEXT IN DIRxx FILE:
This function allows you to search for any text string within all
of your DIRxx files.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.06
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - DIR Editing Key Controls - Continued ║
╚═══════════════════════════════════════════════════════════════╝
EDIT FNFILER DEFAULTS:
This function allows you to set memory allocation for your system
and certain preferences. The following questions will be asked
when you enter this function:
Sort Method (1,2,3):
Sort by Filename
Sort by File Size
Sort by File Date
Once you chose a method it will ask:
Sort in ascending or descending order:
Enter your choice.
Determine memory allocation:
Use EMS/XMS memory if available:
Enter "Y" or "N"
The use of EMS/XMS is strongly recommended as it speeds up pro-
cessing of large DIRxx files tremendously!
Determine file security:
Make backup files before processing:
Enter "Y" or "N"
It is highly recommended you set this to "Yes" to ensure that in-
case of system failure or mistakes, you have a backup of the
DIRxx file.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.07
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - Exiting ║
╚═══════════════════════════════════════════════════════════════╝
Upon exiting FNFILER, if any changes in file locations (ie:
moved, deleted) have taken place, a file called FRESHEN.BAT
(located in the MAIN BBS directory) will be executed (if it
exists).
Use FRESHEN.BAT to update your conference files indexes (if
used).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 32.08
╔═══════════════════════════════════════════════════════════════╗
║ FNFILER.EXE - Command Line Switches ║
╚═══════════════════════════════════════════════════════════════╝
There are two command line options that can be used with FNFILER.
These options are /LIST and /SORT. These options are useful
during the nightly events to update your Master Files Lists and
to update the sort your conference DIR files.
The /LIST command is used to create your Master Files List(s).
The command line parameters are as follows:
FNFILER /LIST <path & name of filelist> <conference #(s)>
When entering the conference numbers, you may enter individual
numbers or group them. If the conferences are consecutive you
may enter your first and last conferences numbers with a "dash"
in between. (ie: 0-3)
If you do not have consecutive conferences, you may seperate the
conference number with a "comma". (ie: 8,22)
You may also combine these types of conference numberings.
(ie: 0-3,8,22)
EXAMPLE:
FNFILER /LIST D:\FNET\CF0000\FILES\DL001\ALLFILES.LST 0-3,8,22
In the above example, a master file list called ALLFILES.LST
will be created in the D:\FNET\CF0000\FILES\DL001 file directory
of all the files within conferences 0 thru 3, 8 and 22.
The /SORT option is used to Sort your conference(s) DIR files.
The command line parameters are as follows:
FNFILER /SORT <conference #(s)>
The conference number(s) follow the same number sequence as does
the /LIST option.
The order of sort may be configured from FNFILER's Main Menu.
EXAMPLE: FNFILER /SORT 0-3,8,22
In the above example, the DIR files within conferences 0 thru 3,
8 and 22 will be sorted in the order that was configured within
FNFILER.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 33.01
╔═══════════════════════════════════════════════════════════════╗
║ MKFNTEXT.EXE - Prompt Editor ║
╚═══════════════════════════════════════════════════════════════╝
Because we realize that all SysOps are different and have varying
degrees of ideas on how items should be presented to a caller, we
have included MKFNTEXT.EXE with your FeatherNet PRO! package.
FeatherNet PRO!'s MKFNTEXT is a prompt editor which allows you,
the SysOp, to customize your prompts to meet your needs & tastes.
The command line to activate this utility is:
MKFNTEXT [prompt filename]
EXAMPLE: MKFNTEXT FNETTEXT
This will bring up the prompt editing screen as show below.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
G42: SAMPLE MKFNTEXT PROMPT EDIT SCREEN
Because all instructions are provided on-screen, we will not go
into a lot of detail here on the utility. However, we will point
out a few items of importance:
<F1> RESETS ALL PROMPTS IN FILE TO DEFAULT! (SEE NOTE)
<F2> Will allow you to quickly search through your prompt file
and find all occurrences of a words or text string and
allow you to edit them.
<F4> Resets only the prompt you are looking at to original.
(SEE NOTE)
<ESC> Quits and Saves
NOTE: FeatherNet PRO! has a built in "Original" copy of the de-
fault prompt file. At any time you may restore defaults
to the original FeatherNet PRO! prompts by pressing the
<F1> or <F4> keys.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 34.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCHK.EXE - Upload Integrity Checker ║
╚═══════════════════════════════════════════════════════════════╝
OVERVIEW:
Verifying newly uploaded files is now a "Way of Life" in the BBS
world. The threat and widespread distribution of computer
"Viruses" have made a dramatic impact on SysOps. Most SysOps now
use some method of scanning newly uploaded files for virus
infection. Doing this certainly reduces the likelihood of
receiving infected files and inadvertently allowing them to be
distributed to other computer system once downloaded by users.
FeatherNet PRO! employs FNCHK.EXE to aid in verifying the
integrity of uploaded files. FNCHK performs several tasks. It
first reads a configuration file (FNCHK.CFG). It determines the
number of archive "Testers", their default archive format file
extension (ZIP, LZH, ARJ, etc.) and each archiver's testing
commands (PKUNZIP -t, ARJ t, etc.) are read from FNCHK.CFG. A
SysOp may choose not to define testers in the FNCHK.CFG file if
his/her external program to test archives (discussed below)
handles these tests.
Once FNCHK has read its configuration file it checks the node's
WORK directory and retrieves the filenames of all newly uploaded
files. It then calls "FNETTEST.BAT" to verify the uploads with
any external upload verification utility the SysOp chooses to use
(if any). If ULTESTER is used for upload verification, FNCHK
calls "FNETTEST.BAT" for each file name otherwise "FNETTEST.BAT"
is called once.
Then FNCHK will perform archive testing as directed by the SysOp
in "FNCHK.CFG" and update the "CALLER.LOG" and "TRANSFER.DAT"
files.
After the testing is completed FNCHK will move all files which
tested good from the WORK directory to the UPLOAD directory.
Note: You should configure your "external" archive testing
program to move any files which test bad (no viruses) to the HOLD
directory as defined in the FeatherNet PRO! FNCFG setup. This
allows all partial uploads to be resumed if a user takes
advantage of a file transfer protocol which allows resumption of
an aborted transfer.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 35.01
╔═══════════════════════════════════════════════════════════════╗
║ FNCHK.CFG - Upload Integrity Checker Configuration ║
╚═══════════════════════════════════════════════════════════════╝
FNCHK.CFG must reside in the MAIN BBS directory with FNCHK.EXE.
Its purpose is two-fold:
1) It let's the SysOp state if he is going to use the
"ULTESTER" utility by FeatherNet Software.
2) It allows the SysOp to define the archive testers he
wants FNCHK to use after the external archive testing
program has completed its job
A sample "FNCHK.CFG" file and comments follow:
Y "Y" if using ULTESTER otherwise enter an "N"
1 (See Note Below)
3 Number of Archive testers you will use (0 - 25)
ZIP File extension first archiver uses by default
PKUNZIP -t Command needed to test archives with ZIP
extension
LZH File extension first archiver uses by default
LHA t Command needed to test archives with LZH
extension
ARJ File extension first archiver uses by default
ARJ t Command needed to test archives with ARJ
extension
NOTE: The "1" in the 2nd line of FNCHK.CFG means you do want to
swap FNCHK to EMS, XMS or to DISK when shelling out to
the archive testing program (ULTESTER). This will
free up about 64k (all but 2k of the memory FNCHK was
utilizing).
If you do not want to swap FNCHK out then place a "0" on the 2nd
line.
If you wish to handle upload testing differently on
different nodes, then place the FNCHK.EXE and FNCHK.CFG file in
each node directory and change the PATH statement in the
C:\AUTOEXEC.BAT file by placing the node directory as the first
entry.
NOTE: This should "only" be done if you are running under a
network with each node being run from a separate
workstation or if you use a true multitasking operating
system which creates "virtual machines" such as OS/2.
Example: PATH=C:\FNET\NODE1;C:\FNET
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 36.01
╔═══════════════════════════════════════════════════════════════╗
║ FNETTEST.BAT - Upload Testing Batch File ║
╚═══════════════════════════════════════════════════════════════╝
FNETTEST.BAT - FEATHERNET PRO! UPLOAD EXTERNAL TESTING BATCH FILE
"FNETTEST.BAT" is the last file to be mentioned in the UPLOAD
testing procedure. It is completely up to the SysOp to determine
what goes in this file as it controls the external testing of
uploads by a program other than FNCHK.EXE.
If you are not familiar with any of the external upload file ver-
verification utilities such as "ULTESTER" then create one line in
your FNETTEST.BAT stating ":END" (no quotes).
FNCHK.EXE shells to FNETTEST.BAT as mentioned above. If there are
any problems processing commands in FNETTEST.BAT then FNCHK.EXE
will resume operation once control is returned by FNETTEST.BAT.
To utilize an FNETTEST.BAT file to call an archive test program
such as ULTESTER, you must ensure FNETTEST.BAT has the correct
command line for the program being called.
NOTE: FeatherNet PRO! passes two parameters to the FNETTEST.BAT
file:
1) File path & filename
2) The letter "T" if this is a test function Only
During a TEST, FeatherNet PRO! lets the archive test
program provide the interaction and test progress inform-
ation to the user. ULTESTER is aptly suited for this
function.
For ULTESTER, the below "Sample" command line is appropriate.
A sample FNETTEST.BAT file:
@ECHO OFF
CD C:\FNET\ULT
ULTESTER ULT%NODE%.CFG %1 %2 %3 %4
CD C:\FNET\NODE%NODE%
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 37.01
╔═══════════════════════════════════════════════════════════════╗
║ LOCALUP.EXE - Local Upload Utility ║
╚═══════════════════════════════════════════════════════════════╝
LOCALUP is designed to take a command line parameter of a DOS
directory containing new files you wish to locally upload into
the FeatherNet PRO! DIRxx files. The actual files will be moved
into the corresponding DOS directory for the DIRxx file as
specified in the configuration and the DIR.LST (type) file.
If desired, you can choose to move a file to any directory path
listed in a DLPATH.LST file.
LOCALUP allows you to view any non-binary file. You may also
view the contents of a ZIP, ARJ, LHA, or ARC file (PKUNPAK only).
Self extracting archives are also supported as archive type is
determined by signature, not file extension.
Each file is processed immediately upon the description being
entered or the file_id.diz file description being used by
pressing the INS key.
PRE-CONDITIONS:
The following programs must be in your system's path.
PKUNZIP.EXE
ARJ.EXE
LHA.EXE
PKUNPAK.EXE
If any of these programs are not in the path, archive viewing
and file_id.diz operations are disabled for the affected archive
format.
Archive contents viewing is internal for ZIP, ARC, and LHA
archives. This does not include extracting the file_id.diz file
or reading files within an archive.
Operation usage is:
"LOCALUP [drive/path of files to upload] [DIR.LST control file"
EXAMPLE: LOCALUP C:\TMPFILES DIR.LST DLPATH.LST <DIZ>
Where: "C:\TMPFILES" is a DOS directory with some files
stored in it which you want to add descriptions
to the BBS DIRxx files and make available for
downloading
"DIR.LST" is the name of the directory listing
file you wish to use for selecting the appropriate
DIRxx files and DOS directories.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 37.02
╔═══════════════════════════════════════════════════════════════╗
║ LOCALUP.EXE - Local Upload Utility - Continued ║
╚═══════════════════════════════════════════════════════════════╝
"DLPATH.LST" is the name of the download paths
listing file you wish to use to provide additional
paths to move files into.
"DIZ" causes LOCALUP to check for a file_id.diz
description file within an archive. If present,
you will be prompted to press <INS> to insert the
file_id.diz file and add process the file.
All parameters above except "DIZ" are mandatory.
FEATURES:
The actual DOS directory a file will be moved to and free space
remaining is displayed when selecting a directory category for a
file. Keep in mind even though the assigned DOS directory for a
file is at minimum space remaining, you may choose any DLPATH.LST
directory (if configured) for the file to be moved into.
* You may select the DIRxx file for a description to go into and
also choose to send the file to be uploaded locally to one of
the DLPATH.LST file directories (if configured).
* Press LEFT/RIGHT arrow keys to skip to the previous/next file.
* Code has been added to verify that the destination file does
not exist.
* Code has been added to verify that a file is not being
"copied" onto itself.
* FILE_ID.DIZ supported.
* Viewing archives and reading text files within archives sup-
port supported.
* Displaying (reading) of any (non binary) file supported.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 38.01
╔═══════════════════════════════════════════════════════════════╗
║ FNPACK.EXE - Message Packing Utility ║
╚═══════════════════════════════════════════════════════════════╝
FNPACK is a new message file packing utility. It currently does
up to 2 functions:
PACK THE MESSAGE FILE:
This removes deleted messages, preserving the low message number
and renumbers the message file with a new low message number
ranging from 1 to 9,990,000. To run FNPACK you just need to be
in the directory where the message files are. FNPACK.EXE needs
to be located somewhere in your DOS path.
The command line is: FNPACK
MSGFILE OPTIONS EXAMPLE: FNPACK MSGS /RE:15000
This example will pack the message file named "MSGS" and will
change the starting message number to 15000. "/RE:" is
currently the *only* option available for repacking. a "plain"
repack just removed deletes messages from the file, while a
(/RE:) renumber removes deleted messages and renumbers all
messages.
If you renumber messages, user's high message read pointers will
be affected. The pointers will either be reduced to the low
message number, raised to the high message number or be located
somewhere in between. If you renumber messages, be sure to
leave users some "News" and advise them to use the [L] command
after joining a conference to adjust their high message read
pointers as required.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 39.01
╔═══════════════════════════════════════════════════════════════╗
║ FN-NET.EXE - Message Pointer Utility ║
╚═══════════════════════════════════════════════════════════════╝
The program FN-NET.EXE is included for the SysOps who are running
echomail conferences which handle echo mail such as FIDONet,
LinkUSA, etc.
Place FN-NET.EXE in your path.
Go to any of your node directories and run:
FN-NET [drive & path to FNET Main BBS directory]
NOTE: The parameter only should be run the first time you run
FN-NET after importing echo mail. Once run with the para-
meter, you do not need to run it again with the parameter.
FN-NET should be run directly after you import any echo
mail into your message bases from an echo mail network.
The command line for this program is simply:
FN-NET [no parameters]
This will update all message pointers and set all "Mail Waiting"
flags in the echo mail conferences.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 40.01
╔═══════════════════════════════════════════════════════════════╗
║ MODEMSET.EXE - Modem Setup Utility ║
╚═══════════════════════════════════════════════════════════════╝
MODEMSET is a utility to assist you in "Installing" your modem.
It has initialization and setup parameters for many popular
modems.
MODEMSET expects you to specify the serial port to use and the
baud rate to open the serial port at. If using serial port 3 or
4 or if using a non-standard base address or IRQ, the IRQ and
serial port base address must be included on the command line.
EXAMPLE: MODEMSET 1 38400
This tells MODEMSET you will use serial port "1" which will be
opened at 38400 baud.
EXAMPLE: MODEMSET 4 57600 15 &h3f8
This tells MODEMSET you will use serial port #4 and want to open
the port at 19200 baud. additionally, you are specifying IRQ
#15 and a serial port base address of 3f8 (&h3f8).
NOTE: The format for the serial port base address must be spec-
ified, if in the format above, with "&h" as the first 2
characters.
MODEMSET will give you two menu options:
Select Modem
Quit
Selection "1" allows you to view the available modems in alpha-
betical order pausing at each screen full. Once you see the modem
you use and answer "N" to the "More" query, you may enter the
number adjacent to the your modem. You will be presented with
some initialization parameters for your modem and you may have
the initialization process performed by pressing <ENTER>.
If you choose to initialize the modem with the listed settings,
your modem is sent the commands you see on the screen if it has
NRAM (non-volatile ram).
If initialization is successful, the initialization string of
"ATZ" is placed in SRCONFIG for a modem with nram. for non-nram
modems, the recommended initialization string shown on the
screen is written to SRCONFIG. Consult your modem manual if you
have problems with calls not being answered.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 41.01
╔═══════════════════════════════════════════════════════════════╗
║ BUILDNDX.EXE - File Index Compiler ║
╚═══════════════════════════════════════════════════════════════╝
With the advent of CD-ROM technology and the scramble to add
huge amounts of information to bulletin board systems with high
capacity, low cost hard drives, many found themselves with a
problem. Their BBS software couldn't handle dealing with CD-ROM
drives due to not being able to write to those directories. Slow
transfer times and the huge amount of files would bog down the
system while the software searched through the physical director-
ies and read the names of each of thousands of files on the hard
drive. Even now, a lot of BBS software can only "deal" with
CD-ROM drives but do not allow you to manipulate files on them.
FeatherNet PRO!'s BUILDNDX handles all this and more. If you are
using CD-ROM drives with your BBS you should read this section
carefully. Be sure to take advantage of the "File To Run Before
And After File Transfer" option setup in FNCFG.
BUILDNDX is a utility to build an index file of all the file
names on your system. When you run your system using an index
file instead of the DIR.LST parameters, FeatherNet PRO! ignores
your DIR.LST paths during file searches and instead searches
your index file for the filename. If not found, it then searches
your DLPATH.LST for alternate file download directories to
search. This allows fast file searching and eliminates the need
to search huge DIRxx description files and physical searches of
your CD-ROM drives or hard drives.
FeatherNet PRO! will search through a typical index file with
approximately 30,000 files on a 486 machine in under a second and
then verify the physical file still exists in the place the index
file has it recorded as being (this time depends on the seek time
of your CD-ROM drive but is usually also under 1 second).
A sample of an index file transfers is similar to this:
USER REQUEST: Searches INDEX file -IF EXIST GOTO FOUND
Searches DLPATH.LST -IF EXIST GOTO FOUND ELSE
NOT
FOUND: Checks the users sec
lev against that which
is recorded for the
file dir -IF OK GOTO SLOW DRIVE IF
BAD GOTO NOT
NOT: Tells user that file is not on disk or his
security level is too low.
SLOW DRIVE: Is drive listed as a
slowdrive? -IF YES GOTO MOVE ELSE GOTO
BAT
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 41.02
╔═══════════════════════════════════════════════════════════════╗
║ BUILDNDX.EXE - File Index Compiler - Continued ║
╚═══════════════════════════════════════════════════════════════╝
MOVE: Copies file from slow
drive to hard drive - GOTO BAT
BAT: If you specified a batch file to run before and
after a file transfer it will be done now. this
allows you to strip BBS ads or zip comments from
files on your CD-ROM before transfering it to your
user, however, this will take a few extra seconds.
DL: The file is sent to your user.
┌────────────┐
│ IMPORTANT! │
└────────────┘
This is not a batch file and only shown here to give you refer-
ence to how indexed file transfers are handled!
As you can see, this allows you complete and total control over
every file on your system, including the files on your CD-ROM
drives. Setting up your index configuration file is fairly
simple. Once completed, it can be used over and over again with
minimal maintenance.
BUILDNDX.EXE should be located in your path or in the directory
you are compiling your index file in. Before you can compile
your file index, you must create an index configuration file.
This file simply lists a file listing, the path to the direct-
ories you wish to index, and the security level needed to obtain
files in that directory.
On the following page is a sample setup of an index configuration
file:
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 41.03
╔═══════════════════════════════════════════════════════════════╗
║ BUILDNDX.EXE - File Index Compiler - Continued ║
╚═══════════════════════════════════════════════════════════════╝
_________________________________________________________________
C:\ZIP\,40
C:\FILES\,100
C:\FILES\ARCHIVE\,40
C:\FILES\BATCH\,40
C:\FILES\BBSAPPS\,40
C:\FILES\BBSLISTS\,40
G:\001A\,40
G:\002A\,40
G:\004A\,40
G:\005A\,40
G:\006A\,40
G:\007A\,40
H:\010A\,40
H:\011A\,40
H:\012A\,40
H:\013A\,40
H:\015A\,40
H:\016A\,40
H:\017A\,40
I:\COMPRESS\,40
I:\DBASE\,40
I:\DIAG\,40
I:\DOOR\,40
I:\DRIVER\,40
I:\EDITOR\,40
I:\EDUCATE\,40
I:\FONT\,40
_________________________________________________________________
In the above sample, C:\ is a hard drive with the file to index
(all available file directories can be listed) and G:\, H:\, and
I:\ are all CD-ROMs. The setup is as follows:
[drive and path],[security level needed to access]
EXAMPLE: C:\FILES\ANSI\,100
In the above example, the path is C:\FILES\ANSI\.
NOTE: You must have a trailing backslash, then a comma ","
then the security level of 100 which means that the
user accessing must have a security level of 100 or
greater to download, view or test files in this area.
Please also note that there may be NO SPACES in the
file.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 41.04
╔═══════════════════════════════════════════════════════════════╗
║ BUILDNDX.EXE - File Index Compiler - Continued ║
╚═══════════════════════════════════════════════════════════════╝
Once this file is created, you can run the compiler with the
following command line:
BUILDNDX [file in] [file out]
EXAMPLE: BUILDNDX DIR.PTH CONF0001.NDX
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 42.01
╔═══════════════════════════════════════════════════════════════╗
║ CNAMES40.EXE - PCBoard's CNAMES.@@@ Utility ║
╚═══════════════════════════════════════════════════════════════╝
With compatibility in mind, and since we have a number of feat-
ures in FeatherNet PRO! that are PCBoard compatible, we created
CNAME40.EXE. This utility will create a PCBoard v14.5 compatible
CNAMES, CNAMES.@@@, and PCBOARD.DAT file. This will allow
FeatherNet PRO! to use many utilities and doors already designed
for PCBoard.
The CNAMES and CNAMES.@@@ file may be shared if all your nodes
that have identical conference information.
CNAME40.EXE must be run from the directory in which your
FNCONF.@@@ file resides.
EXAMPLE COMMAND LINE: CNAME40
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 43.01
╔═══════════════════════════════════════════════════════════════╗
║ FNODEMON.EXE - Node Monitoring Utility ║
╚═══════════════════════════════════════════════════════════════╝
FNODEMON enables you to view a list of who is currently online
and what they are doing on the system. The list shown on your
screen is updated every few seconds.
If you are running a multi-node BBS via a network, FNODEMON will
interface with "Network" monitoring utilities (such as The
Network Eye by Artisoft). You may "Pop-In" on one of the nodes
that is displayed on your FNODEMON screen by arrowing down and
pressing enter once the node monitoring utility is installed.
In order to accomplish this, you will need to create a batch file
called "NODE.BAT" in your BBS's Main directory (ie: \FNET). This
file MUST be called NODE.BAT and be "Read-Only" once created.
Below is the necessary contents of the NODE.BAT file:
@ECHO OFF
REM - NODE.BAT NETWORK MONITORING INTERFACE BATCHFILE -
TNE-USE %1 %2 >NUL
The variables above (following TNE-USE) represent the following:
%1 - Node# (where # = node number)
%2 - The actual node number
The node number in the batch file is represented two times. This
may seem redundant but is necessary.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 44.01
╔═══════════════════════════════════════════════════════════════╗
║ FRESHEN.BAT - Update Your Conference Files Index File ║
╚═══════════════════════════════════════════════════════════════╝
FNFILER is hard coded to execute FRESHEN.BAT to freshen/update
your conference files index file(s). If you do not want this
automated method to take place you will need to rename
FRESHEN.BAT to xxxxxxxx.BAT (where xxxxxxxx = any legal dos
filename).
Keep in mind however, if you are using file indexing and move or
delete ANY file within your filebase, your index file will need
to be updated. If this is NOT done and your user selects the
filename to download that you moved or deleted, the file will
NOT be found.
If you are using multiple index files (separate index files for
seperate conferences) you should include and update line in the
FRESHEN.BAT file for EACH SEPERATE INDEX FILE.
FRESHEN.BAT uses FeatherNet PRO!'s BUILDNDX.EXE to accomplish
this indexing.
For more information on BUILDNDX see page 41.01.
EXAMPLE FRESHEN.BAT FILE:
@ECHO OFF
%FNDRV%
CD %FNDIR%
BUILDNDX C:\FNET\CF0000\CF0000.PTH C:\FNET\CF0000\CF0000.NDX
BUILDNDX C:\FNET\CF0009\CF0009.PTH C:\FNET\CF0009\CF0009.NDX
CD %FNDIR%
Two index files will be created in the example above. CF0000.NDX
will be created in the C:\FNET\CF0000 directory using
CF0000.PTH. Likewise, CF0009.NDX will be created in conference
9's directory.
The CF0000.PTH file is ASCII text file with the drive and
path (ending in a backslash), a "comma" followed by the minimum
security level to download from that directory for EACH
directory that is to be downloaded from.
EXAMPLE xxxxxxxx.PTH FILE:
C:\FNET\CF0000\FILES\DL001\,10
C:\FNET\CF0000\FILES\DL002\,50
C:\FNET\CF0000\FILES\DL003\,50
C:\FNET\CF0000\FILES\DL004\,50
C:\FNET\CF0000\FILES\DL004\,70
C:\FNET\CF0000\FILES\DL005\,50
C:\FNET\CF0000\FILES\DL006\,50
C:\FNET\CF0000\FILES\DL007\,50
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.01
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - UPSEC ║
╚═══════════════════════════════════════════════════════════════╝
This file is not required by FeatherNet PRO! but is described for
those who will run ProDoor.
C:\UPLOADS\,*.EXE,100, - Path, file name info, access required
C:\UPLOADS\,*.TXT,100, - Path, file name info, access required
C:\UPLOADS\,*.ZOO,100, - Path, file name info, access required
C:\ANSI\*.*,30, - Download Path, filename info, access
level required etc...
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.02
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - DIRxx ║
╚═══════════════════════════════════════════════════════════════╝
Use a text editor to edit the various directories listing files.
You must use the file names you have specified in the file
directory configuration when you edited the List File (DIR.LST)
in FNCFG.
There MUST be at least two non-description line in the file
before the actual file directory information begins in order for
the search to properly work. The first of the non-descriptive
lines may be a call for a file header (See below).
This is the format and a sample FeatherNet PRO! File Listing
Directory file;
0 1 1 2 2 3 3 7
1----------2 5-----1 4------1 4-----------------------------9
NAME OF FILE SIZE DATE DESCRIPTION OF FILES
( May be Multiple Lines )
1) File Name is positions 1-12.
2) Size is positions 15-21 right justified.
3) Date is positions 24-31.
4) Description text is positions 34-79.
5) A "|" character is at position 32 for each multiple
description line.
A sample entry for a DIRxx file might look like this:
MC-VISA.ZIP 1202640 10-28-93 Master-Card Visa Sysops, use
|Credit Cards on your BBS
|Uploaded by: JOE TESTER
The format is provided as a guide to properly format the
directory entries. ALL fields MUST begin at the start positions
indicated in the sample except for the SIZE field. It should END
at position 21 and begin at position 15 or higher.
You may add a header to the top of your DIRxx file. To do this,
simply add a line to the FIRST LINE of your DIRxx file in this
format;
%[PATH][FILENAME]
% directs FeatherNet PRO! to read the file pointed to in the PATH
and FILENAME statement.
The filename you specify should have 7 or less characters as it
will look for the specified filename with an appended "G" if the
user is in ANSI or an appended "R" if the user is in RIPscrip
mode. You may have 3 versions of the header file in the path you
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.03
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - DIRxx - Continued ║
╚═══════════════════════════════════════════════════════════════╝
specify. In the below example, we user the filename HDR-STD,
this would be the name of the ASCII version of your header. In
the same path you may also have HDR-STDG for ansi users and
HDR-STDR for RIPscrip users.
This line MUST be followed by a BLANK LINE then start your DIRxx
entries.
%C:\FNET\DISP\HDR-STD
MC-VISA.ZIP 1202640 10-28-93 Master-Card Visa Sysops, use
|Credit Cards on your BBS.
|Uploaded by: JOE TESTER
┌────────────┐
│ IMPORTANT! │
└────────────┘
The DIRxx files MUST have a minimum of 2 lines in the header for
proper operation and to prevent possible lockups due to the
extreme speed of the FeatherNet PRO! routines used for text
and/or date searches.
NOTE: There are a number of utilities that make short work of
DIRxx list maintenance. Among them are DFMS, RWDIR and
WGM-DMS. They can be found (along with a ton other DIR
utilities) on most BBSes. Another valuable utility is
WGM-MAKE which will read all the files in your directory,
extract any FILE_ID.DIZ's found, and create a complete
DIRxx file for you. All you need to do is add your
header!
The directory listing files are configured in the conference
configuration section in FNCFG. The names of the listing files
are contained in the DIR.LST type file along with the category or
name of the directory listing, security level and a DOS path
where FeatherNet PRO! should look for the actual files (See also
DLPATH.LST and File INDEXing).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.04
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - FNETPROT.DAT ║
╚═══════════════════════════════════════════════════════════════╝
On of the biggest complaints we hear from SysOps is that their
BBS software does not allow external protocols, does not allow
enough external protocols, or that protocols such as ZModem were
built into the BBS an could not be updated to newer versions.
When we developed FeatherNet PRO! we took a look at this problem
and decided that a separate, single control file for all the
transfer protocols was preferable to building them into the soft-
ware. We think that you will find this to be an easier method
for transfer protocol installation and maintenance.
This is an ASCII text file that must be EDITED BY THE SYSOP which
contains external protocol information that FeatherNet PRO! uses
to display the available file transfer protocols and to create
the "on the fly" batch files for file transfers.
A sample FNETPROT.DAT file and its format description is given
below.
1
Z110Zmodem with Resume Capability - (Still the best!)
DSZ handshake slow port %1 pB4096 sz -s -m
DSZ handshake slow port %1 pB4096 rz -m -r
Breakdown of the entry
1 Number of external protocols available
Z Letter (HOTKEY) to select this protocol
1 Use a 1 if the protocol can resume an aborted upload as
Zmodem can. 0 if it can not.
1 Enter a 1 if the protocol supports batch transfers. 0 if
it can not.
1 Enter a 1 if the protocol supports Bi-Directional trans-
fers. 0 if it can not
Zmodem with Resume Capability = Protocol desc (40 Char Limit)
DSZ ha sl port 2 pB4096 sz -s -m = This is the send command line
DSZ ha sl port 2 pB4096 rz -m -r = The receive command line
The above is a DSZ (Zmodem) command line. For further informa-
tion, refer to the documentation for the external protocol you
are configuring for use.
On the next page is an actual FNETPROT.DAT file for your
reference.
On the following page is an actual FeatherNet PRO! PROT.DAT file
configured for serial port #1.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.05
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - FNETPROT.DAT - Continued ║
╚═══════════════════════════════════════════════════════════════╝
6
Z110Zmodem with Resume Capability - (Still the Best!)
DSZ handshake both port %1 pB4096 sz -s -m
DSZ handshake both port %1 pB4096 rz -m -r
P110Puma Protocol with Resume Capability
Puma LC:\FNET\NODE1\DSZLOG p%1 x+ s
Puma LC:\FNET\NODE1\DSZLOG p%1 x+ r+ r
G010Ymodem-G Batch (Error Correcting Modems ONLY!!)
DSZ handshake both port %1 sb -k -g -s
DSZ handshake both port %1 rb -g -p
O000Xmodem-1k
DSZ handshake both port %1 sx -ks
DSZ handshake both port %1 rx -c -k -y
C000Xmodem CRC and Checksum
DSZ handshake both port %1 sx
DSZ handshake both port %1 rx -c
H111HS/Link (Bi-Directional / Start 2-Way Transfers as D/L!)
C:\HSLK\HSLINK -P%1 @C:\FNET\NODE1.CFG
C:\HSLK\HSLINK -P%1 @C:\FNET\NODE1.CFG
YOU DO NOT NEED TO MAINTAIN A SEPARATE FNPROT.DAT FILE FOR EACH
NODE. THE SERIAL PORT INFORMATION IS PASSED TO THE FILE THROUGH
THE %1 DOS VARIABLE.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.06
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - SRCONFIG ║
╚═══════════════════════════════════════════════════════════════╝
This is the main BBS configuration file. It is straight ASCII
and it is created by FNCFG in each NODE directory. A sample
SRCONFIG file with a short description of the contents follows:
ENTRY LINE DESCRIPTION
───────────────────────── ──── ─────────────────────────────────
The BBS 1 Name of your BBS
JOE SYSOP 2 Sysop's name
C:\FNET 3 BBS program main directory
1 4 Number of this node
C:\FNET\NODE1 5 This node home directory
140 6 Max messages per archive run
115 7 Userfile edit access (remote sysop
access
1 8 Lock com port at opening baud rate
1=yes, 0=no
COM1 9 Comport for this node (com1-4)
ATZ 10 Modem reset string
57600 11 Baud rate which to open com port
30 12 New user's access level
1 13 Questionnaires used? 1=yes, 0=no
25 14 Secs for modem to wait to connect
C:\FNET\NODE1\WORK\ 15 Node work directory (all deleted)
3 16 Number of questionnaires available
1200 17 Lowest baud rate to allow onto BBS
1 18 Use the Today function? 1=yes,0=no
000000.00 20 Zip comments added to u/l's?
1=yes, 0=no
1000 21 Min K-bytes on U/L drive for U/Ls
8 22 Number of bulletins available
23 - unused -
24 - unused -
30 25 Days before subscription expired
warning file displayed
10 26 Expired sec level when subscrip-
tion expires)
1 27 Subscription mode desired?
1=yes, 0=no
0 28 Ringback option desired?
1=yes, 0=no
45 29 Seconds to wait for ringback?
0 30 Frontdoor program is used?
1=yes, 0=no
0 31 Running under DESQview?1=yes, 0=no
1 32 "Uploaded By:"in file description?
1=yes, 0=no
0 33 Want high ASCII filter? 1=yes,0=no
C:\FNET\SECMSGS\ 34 Location of security files
0 34 Minutes before modem is reinitial-
ized
C:\FNET\FILES\CF0000\HOLD 36 Duplicate U/L hold directory path
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.07
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - SRCONFIG - Continued ║
╚═══════════════════════════════════════════════════════════════╝
30 37 Sec lev required to D/L files
30 38 Sec lev required to U/L files
30 39 Sec lev to enter Files area
1 40 Graphics at local logon?
1=yes, 0=no
0 41 Force users into door at logon?
1=yes, 0=no
1.5 42 Upload time credit factor.
43 - unused -
1 44 Warn if files flagged at logoff?
1=yes, 0=no
1 45 Ask to set msg pointers at logoff?
1=yes, 0=No
46 - unused -
47 - unused -
48 - unused -
49 - unused -
Y 50 Permit swapping to EMS/XMS/Disk?
1=yes, 0=no
50 51 Sec lev to list users?
52 - Unused -
1 53 Allow private personal transfers?
1=yes, 0=no
C:\FNET\FILES\CF0000\UPL 54 Private personal file xfer file
directory path
0 55 3 second pause after connect=<2400
0=yes, 1=n0
50 56 Sec lev to archive and D/L msgs
1 57 Enable split screen chat?
1=yes, 0=no
1 58 Always ask users to select xfer
protocol? 1=yes, 0=no
2 59 Number of nodes configured for
1 60 Enable auto-ANSI detect at logon?
1=yes, 0=no
0 61 Default subscription in days
(0-999) for new users
00:00 62 Sysop available start time (page)
23:59 63 Sysop available stop time (page)
0 64 Allow one name users (handles)?
1=yes, 0=no
0 65 Allow login as sysop from remote?
1=yes, 0=no
F F 1^m 66 1/10 shifted F-keys - defined
67 2/10 shifted F-keys - defined
68 3/10 shifted F-keys - defined
69 4/10 shifted F-keys - defined
70 5/10 shifted F-keys - defined
71 6/10 shifted F-keys - defined
72 7/10 shifted F-keys - defined
73 8/10 shifted F-keys - defined
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.08
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - SRCONFIG - Continued ║
╚═══════════════════════════════════════════════════════════════╝
74 9/10 shifted F-keys - defined
J 0 R-^M 75 10/10 shifted F-keys - defined
1 76 Enforce the above sysop availiab-
ility for chat? 1=yes, 0=no
77 Path/name of program to run before
& after transfers
&H3F8 78 Serial port base address
&H4 79 IRQ number to use
C:\FNET\FNSYS\FNETTEXT 80 Path/name of the "FNETTEXT" file
0 81 - unused -
1010 82 Number of lines users allowed to
read from archive
255 83 Sec lev req'd to kill own message
255 84 Sec lev req'd to list [T]odays
callers
100 85 Sec lev req'd to carbon copy msgs
C:\FNET\MENU\MM 86 Path/name of Main menu file
C:\FNET\MENU\CM 87 Path/name of Conference menu file
C:\FNET\MENU\FM 88 Path/name of File menu file
C:\FNET\QUES\QUEM 89 Path/name of Script questionaire
menu
C:\FNET\DISP\PRELOG 90 Path/name of Prelogin welcome file
C:\FNET\DISP\NEWS 91 Path/name of News file
C:\FNET\HELLO1 92 Path/name of After login Welcome
file
C:\FNET\DISP\NEWUSER 93 Path/name of New User welcome file
C:\FNET\DISP\CLOSED 94 Path/name of text file shown to
new users if system is private
C:\FNET\LOGS\CALLER1 95 Path/name of Caller log file
C:\FNET\DISP\EXPWARN 96 Path/name of Expired subscription
Warning file
C:\FNET\DISP\EXPIRED 97 Path/name of Expired Subscription
lapse notice file
C:\FNET\QUES\SCRIPT.0 98 Path/name of New user script
questionaire file
C:\FNET\\DISP\LOGOFF 99 Path/name of Logoff file
(shown after the [G]oodbye)
C:\FNET\DISP\TODAY 100 Path/name of "TODAY" text file
(if used)
C:\FNET\DISP\PREDL 101 Path/name of PreDownload Warning
file
C:\FNET\DISP\PREUL 102 Path/name of PreUpload Warning
file
C:\FNET\DISP\USRSTAT 103 Path/name of the User Statistics
Information file
255 104 Sec lev req'd to Kill any message
255 105 Sec lev req'd to Edit any message
110 106 Sec lev req'd to enter @ macro
messages
255 107 Sec lev req'd to [R]ead any msg
110 108 Sec lev req'd to view callers log
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.09
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - SRCONFIG - Continued ║
╚═══════════════════════════════════════════════════════════════╝
50 109 Sec lev req'd to user [VER]
command
100 110 Sec lev req'd to edit own messages
110 111 Sec lev req'd to edit user info
50 112 Sec lev req'd to view [B]ulletins
50 113 Sec lev req'd to leave a [C]omment
50 114 Sec lev req'd to use [D]oors
50 115 Sec lev req'd to view [H]elp files
50 116 Sec lev req'd to [J]oin a conf
50 117 Sec lev req'd to [L]ist files
50 118 Sec lev req'd for [N]ew file dir
scan
50 119 Sec lev req'd to page [O]perator
50 120 Sec lev req'd to change [P]age
length
110 121 Sec lev req'd for unlimited time
50 122 Sec lev req'd to answer [Q]ues-
tionnaries
50 123 Sec lev req'd for [S/SS]can/super
scans
50 124 Sec lev req'd to [S]elect msg scan
50 125 Sec lev req'd to toggle [S]creen
color mode
50 126 Sec lev req'd for [TP], transfer
protocol
50 127 Sec lev req'd to [V]iew user's
statistics
50 128 Sec lev req'd to [V]iew archive
50 129 Sec lev req'd to view [W]elcome
file
50 130 Sec lev req'd to toggle e[X]pert
mode
50 131 Sec lev req'd for [Z]ippy scan
70 132 Sec lev req'd for [*] global new
messages read
1 133 Show bulletin menu if new Bltns?
1=yes, 0=No
10 134 Suspend callers before event
(in minutes)
C:\FNET\USRNDX\ 135 Path to the "FNPNDX.x" user index
files
C:\FNET\DISP\CL 136 Path/name of conf listing file
C:\FNET\HELP\ 137 Path to "Custom" help files
C:\FNET\COSYSOP.BIT 138 Path/name of the COSYSOP bitmap
file
1 139 Ask "Do you want color at logon?"?
1=yes, 0=no
1 140 Number of "rings" before sending
modem answer command
C:\FNET\FNSYS\PWRD 141 Path/name of the "PWRD" file
C:\FNET\FNSYS\RATIO 142 Path/name of the "RATIO" file
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.10
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - SRCONFIG - Continued ║
╚═══════════════════════════════════════════════════════════════╝
-1 143 Load FNETTEXT into memory?(faster)
-1=yes, 0=no
1 144 Confirm the [G] (logoff) command?
1=yes, 0=no
70 145 Sec lev required to U/L attached
file
HIJ 146 Slow drive letters
Y 147 Take modem off-hook during event
C:\FNET\QUES\ 148 Location of script questionnaires
0 149 0=Open system, -1= Closed system
0 150 Use sysops real name? -1=yes, 0=no
151 - unused -
152 - unused -
1 153 Parallel printer port assigned
C:\FNET\FNSYS\FNUSERS.INF 154 Path/name of "FNUSERS.INF" file
C:\FNET\FNSYS\CUSSWRN 155 Path/name of the Profanity Warning
file
C:\FNET\DISP\QUOTES.BBS 156 Path/name of BBS quotes file
1 157 Display USRSTAT at logon: 1=y,0=n
C:\FNET\DISP\POSTUL 158 Path/name of Post Upload file
C:\FNET\DISP\POSTDL 159 Path/name of Post Download file
C:\FNET\DISP\FAILUL 160 Path/name of Failed Upload file
C:\FNET\DISP\FAILDL 161 Path/name of Failed Download file
C:\FNET\CHAT\ 162 Location of Chat files
C:\FNET\DISP\CHTM 163 Path/name of Group Chat menu
6 164 Maximum number of rooms available
in group chat
1 165 Verify callers city/state at logon
0=yes, 1=no
C:\FNET\MENU\CLS 166 Path/name of sysop message menu
C:\FNET\MENU\MM 167 Path/name of sysop main menu
C:\FNET\MENU\FMS 168 Path/name of sysop file menu
1 169 Force mail to be read at logon?
1=yes, 0=no
C:\FNET\FNSYS\FNCONF.@@@ 170 Path/name of "FNCONF.@@@" file
C:\FNET\FNSYS\FNCONF.LST 171 Path/name of "FNCONF.LST" file
C:\FNET\FNSYS\USERS 172 Path/name of "USERS" file
C:\FNET\FNSYS\FNEXTUSR 173 Path/name of "FNEXTUSR" file
150 174 Maximum number of lines allowed in
message editor
C:\FNET\FNETPROT.DAT 175 Path/name of "FNETPROT.DAT" file
F 176 "A"=Async serial driver,"F"=Fossil
C:\FNET\FILES\FREE 177 Location of "FREE" D/L files
0 178 Charge users time for D/L Free
files? 1=yes, 0=n
50 179 Sec lev for "*" Quick logon
C:\FNET\FNSYS\TRASH 180 Path/name of "TRASH" file
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.11
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - USERS ║
╚═══════════════════════════════════════════════════════════════╝
The 26 USERS file "quick" index files are automatically generated
by the BBS when the file is packed in the filename format of
FNPNDX.x - where "x" is a letter from A-Z. These index files
contain the names of all registered system callers, sorted
alphabetically by last name. Each file contains a caller's
record number and their complete username. Each record in the
file is 27 bytes long. The first two bytes as the caller's
record number in the main USERS file, and the last 25 bytes
contain the caller's first and last names.
1,25 ASCII First & Last Name
26,24 ASCII City & State
50,12 ASCII Password
62,13 ASCII Business/Data Phone Number
75,13 ASCII Voice/Home Phone Number
88,6 ASCII Last Date on in (yymmdd) format
94,5 ASCII Last Logon Time in (hh:mm) format
99,1 ASCII Expert Mode (y or n)
100,1 ASCII Protocol Type
101,1 (Space) (- Reserved for future use- )
102,6 ASCII Last DIR look date (yymmdd) format
108,1 chr$ Sec Lev
109,2 MKI$ Number of times on System
111,1 chr$ Page Length
112,2 MKI$ Number of Uploads
114,2 MKI$ Number of Downloads
116,8 MKD$ Daily Download Bytes so Far
124,25 ASCII Alias Name
149,4 MKL$ Messages left in long integer format.
154,29 ASCII Sysop Maintained Comment
183,1 BITMAP Bit 0 is Private File Transfers allowed. Bit 1
is Private File(s) waiting to be D/L
{0 = No Access/No Files Waiting}
184,2 MKI$ Elapsed Time on System for that Day
186,6 ASCII Subscription Registration Date (yymmdd)
192,1 chr$ Subscription Expired Sec Lev
193,1 chr$ Conference the user last joined
194,5 BitMap Area Registration Information (1-39)
199,5 BitMap Used to indicate conferences with personal mail
204,5 BitMap User Message Areas "I want to scan"
209,8 MKD$ Total Bytes Downloaded - all calls
217,8 MKD$ Total Bytes Uploaded - all calls
225,1 ASCII Delete Flag (y or n)
226,4 MKS$ Last Read Message Area 0 (Main)
230,156 MKS$ This range of bytes contain the last message
read pointers for all the conference message
bases (1-39). Each message base pointer uses 4
bytes to store its number. In other words, the
last read pointer for message base 1 is located
at position 230 for 4 bytes. For message base
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.12
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - USERS - Continued ║
╚═══════════════════════════════════════════════════════════════╝
16, the information would be located at position
290 for 4 bytes, etc.
386,2 MKI$ Pointer to FNEXTUSR/FNUSERS.INF/COSYSOP.BIT recs
388,2 MKI$ Birthdate crunched into an integer.
390,11 (Space) (- Reserved for future use -)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.13
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - USERNET.DAT ║
╚═══════════════════════════════════════════════════════════════╝
A random access file located in the FeatherNet PRO! main
directory. Used internally to maintain node chat status. The
file is composed of one 53 byte "record" for each node the sysop
has defined.
START POS/LEN DESCRIPTION
───────────── ──────────────────────────────────────────────────
1,2 # of opposite Node CHAT (if one-on-one chat) or:
[A] Available for chat
[U] Node is Unavailable (Down for Maintenance)
[D] Opened a Door
[E] Entering a message
[T] File Transfer
[G] In Group CHAT
[ ] (2 spaces) if no caller on-line for node
3,2 # of the Node requesting the CHAT, or
[R ] chat request sent
5,25 Name of User in the node
30,24 City and State the user is from
MESSAGE BASE FILE FORMATS (128 BYTES PER BLOCK)
Header Block of Message Base for each Area
1,4 MKS$ High Message Number (0 to 9,999,999)
5,4 MKS$ Low Message Number (0 to 9,999,999)
9,4 MKS$ Number of Active Messages (0 to 32767)
13,4 MKS$ Number of System Callers (0 to 9,999,999)
17,6 ASCII "LOCKED" when message is being written to disk
23,105 Space (Reserved for future use)
First Block of Each Actual Message
1,1 ASCII Status Flag
2,4 MKS$ Message Number (1 to 9,999,999)
6,4 MKS$ Reference Message Number (1 to 9,999,999)
10,1 chr$ Number of 128 byte blocks in the message
11,8 ASCII Date of message as (mm-dd-yy)
19,5 ASCII Time of Message as (hh:mm)
24,25 ASCII Who the Message is For
49,4 MKS$ Date of reply message as (yymmdd)
53,5 ASCII Time of last reply message
58,1 ASCII The letter "R" if an "ALL" msg. has reply(s)
59,25 ASCII Who the Message is From
84,25 ASCII The Subject of the Message
109,12 ASCII Password of the Message (Not Used)
121,1 ASCII chr$(225) for active or chr$(226) for inactive
122,1 ASCII The letter "E" if message is to be echoed
123,2 MKI$ (Record in the Conf attach database for file)
125,4 Space (Reserved for future use)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.14
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - USERNET.DAT - Continued ║
╚═══════════════════════════════════════════════════════════════╝
The message base index files for each message base in use are
created in the format <message base filename>+".NDX". This file
is pre-formatted to a size of 4096 bytes times the number of
message base blocks defined per section of the board (1 block =
1024 messages). Each 4 byte record is the "address" of the
respective message number starting block location in the message
base (a "single precision" number in MKS$ format). Since the
index file must be able to access a very large message base (in
excess of 3 meg is possible), addresses are stored as single
precision numbers. If there is no message, a "0" is written to
the file. If the message has been killed, the address is a
negative number. Under this format, the index automatically
"floats" - based on the low message number and the number of
defined blocks.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.15
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - PCBOARD.SYS ║
╚═══════════════════════════════════════════════════════════════╝
This is the exit to DOS information FeatherNet PRO! uses to
maintain a caller's stats and the system's configuration upon
exit to DOS when running a DOOR, during file transfers, or
viewing some archives
START POS SAVED
& LENGTH AS DESCRIPTION OF DATA
───────── ────── ────────────────────────────────────────────
1, 2 ASCII "-1" always used by FeatherNet PRO!
3, 2 ASCII " 0" always used By FeatherNet PRO!
5, 2 ASCII "-1" if page allowed or 0 if not.
7, 2 ASCII User Number in Users file
9, 1 ASCII "Y" if Expert or "N"if Not
10, 2 ASCII "-1" if Error Correcting modem, "0" if not
12, 1 ASCII "Y" if Graphics Mode or "N" if Not
13, 1 ASCII "A" is always placed here by FeatherNet PRO!
14, 5 ASCII The DTE speed or PC to Modem baud rate
19, 5 ASCII The connect baud rate:"300-38400" or "Local"
24, 2 MKI$ User's Record # in "USERS" file
26, 15 ASCII User's FIRST Name padded with spaces
41, 12 ASCII User's Password
53, 2 MKI$ Time user logged on in Mins: (60 x Hr)+Mins
55, 2 MKI$ User's Time on today in minutes
57, 5 ASCII Time user logged on in HH:MM format.
Ex: "12:30"
62, 2 MKI$ Time user allowed today in minutes
64, 2 ASCII Daily D/L Limit from pwrd file
66, 1 Chr$ Conference the user has last joined
67, 5 Bitmap Areas user has been in
72, 5 Bitmap Areas user has scanned
77, 2 MKI$i An mki$(0) used by FeatherNet PRO!
79, 2 MKI$ Currently a value of 0 is here (MKI$(0))
81, 4 ASCII 4 Spaces are placed here
85, 25 ASCII User's Full name placed here.
110, 2 MKI$ Number of minutes user has left today
112, 1 chr$ Node user is on (actual character)
113, 5 ASCII Scheduled EVENT time
118, 2 ASCII A "-1" if EVENT is active or a " 0"
120, 2 ASCII " 0" is Placed here by FeatherNet PRO!
122, 4 MKS$ Time of day in secs format when user is on
126, 1 ASCII The Com port this node uses (0 - 8)
127, 2 ASCII Flag to let FNET PRO! know type of file xfer
129, 1 CHAR Ansi Detected Flag - Char[0] or Char[1]
130, 13 ASCII Unused by FeatherNet PRO! - SPACE filled
143, 2 MKI$ Last Area User was in (0 - 32766 possible)
145 BITMAP Not Currently Used by FeatherNet PRO!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.16
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - DOORS.LST ║
╚═══════════════════════════════════════════════════════════════╝
This is the information that is generated in the DOORS.LST file
upon saving the DOORS.LST configuration.
TYPE Doorcfg
Doorname AS STRING * 8 'Name of door (8 characters max)
DoorPas AS STRING * 12 'Password to use door
DoorSec AS STRING * 3 'Security level required for door
DoorSys AS STRING * 1 '"Y" to create a DOOR.SYS file
DoorPath AS STRING * 24 'Path to DOOR batch file
DoorLogin AS STRING * 1 'Is this a Login door? (Y/N)
DoorShell AS STRING * 1 'Shell/Swap this door? (Y/N/S)
DoorRip AS STRING * 1 'Is this a RIP door? (Y/N)
Unused AS STRING * 9 '( -Reserved for future use- )
END TYPE
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.17
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - DOOR.SYS ║
╚═══════════════════════════════════════════════════════════════╝
This is the "generic" door control file. A DOOR.SYS will be
created when a door program is executed if the Sysop has entered
a "Y" under the "DOOR.SYS" column when editing a conference's
door information in FNCFG. The file is a straight ASCII file with
each line ending with a CR/LF.
COM1: Comm Port - COM0: = LOCAL MODE
2400 Baud Rate - 300 to 57600
8 Parity - 7 or 8
1 Node Number - 1 to 999 (Default to 1)
19200 DTE Rate. Actual BPS rate to use. (300-115200)
Y Screen Display - Y=On N=Off (Default to Y)
Y Printer Toggle - Y=On N=Off (Default to Y)
Y Page Bell - Y=On N=Off (Default to Y)
Y Caller Alarm - Y=On N=Off (Default to Y)
Joe User User Full Name
Anywhere, USA Calling From
555 555-1212 Home Phone
555 555-1213 Work/Data Phone
PASSWORD Password
110 * Security Level
1456 Total Times On
03/14/93 Last Date Called
7560 Seconds Remaining THIS call
126 Minutes Remaining THIS call
GR Graphics Mode GR=ANSI Graphics,
NG=ASCII Non-Graphics, RIP=RIPscrip Mode
23 Page Length
Y User Mode - Y = Expert, N = Novice
1,2,3,4,5,6,7 Conferences/Forums Registered In
7 Conference Exited To DOOR From
01/01/99 User Expiration Date (mm/dd/yy)
1 User File's Record Number
Y Default Protocol - X, C, Y, G, I, N, Etc.
0 Total Uploads
0 Total Downloads
0 Daily Download "K" Total
999999 Daily Download Max. "K" Limit
10/22/88 Caller's Birth date
C:\FNET Path to MAIN directory (Where USERS file is)
C:\FNET Path to the GEN directory
Bob Sysop's Name (name BBS refers to Sysop as)
Whasmaname Alias name
00:05 Event time (hh:mm)
Y If its an error correcting connection (Y/N)
N ANSI supported & caller using NG mode (Y/N)
Y Use Record Locking (Y/N)
14 BBS Default Color (IBM color code, ie: 1-15)
10 * Time Credits In Minutes (positive/negative)
07/07/90 Last New Files Scan Date (mm/dd/yy)
14:32 Time of This Call (hh:mm)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.18
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - DOOR.SYS - Continued ║
╚═══════════════════════════════════════════════════════════════╝
07:30 Time of Last Call (hh:mm)
6 Maximum daily files available
3 Files d/led so far today
3456 Total "K" Bytes Uploaded
76329 Total "K" Bytes Downloaded
A Piece of Work User Comment
0 Total Doors Opened
0 Total Messages Left
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.19
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - FNCONF.@@@ ║
╚═══════════════════════════════════════════════════════════════╝
This is the conference "control" file. It contains configuration
information for each conference on the system. The file begins
with a 2 byte header (signed integer) which indicates the length
of each conference record. The number of records is obtained by
dividing the size of the file minus 2 by the conference record
size. As an example we read the first two bytes of FNCONF.@@@
into an integer (ConfRecSize). Currently, this will equal 600.
Checking the size of out FNCONF.@@@ file we find it to be 1202
bytes. To determine the number of conferences we divide (1202 -
2) by the ConfRecSize integer (600) and realize we have two (2)
conferences configured. The following is a breakdown of the
FNCONF.@@@ file used with FeatherNet PRO!
ConfRecSize AS Integer ' Header Record - First 2 bytes of
file
TYPE ConfNames
Maildir AS STRING * 40 'Path/name of conf message file
Bname AS STRING * 25 'Name of conference
Xfer AS STRING * 35 'Dir listing file name ("DIR.LST")
DpathNm AS STRING * 30 'DLPATH.LST file name
UpathNm AS STRING * 30 'Public U/L file directory path
PrivPathNm AS STRING * 30 'Private U/L directory path
UlDirFile AS STRING * 30 'Public U/L dir listing file name
PrivDirFile AS STRING * 30 'Private U/L dir listing file name
DirMenFile AS STRING * 30 'Dir listing menu file name
IsEcho AS STRING * 1 'Is this conf to be echoed?
(char 0=no; 1=yes)
AccLvl AS STRING * 1 'Sec Lev req'd to enter conference
(0-255)
RepLvl AS STRING * 1 'Sec Lev req'd to reply to message
(0-255)
WritLvl AS STRING * 1 'Sec Lev req'd to enter a message
(0-255)
IsPub AS STRING * 1 'Is this a public conference?
(char 0= no; 1=yes)
NumMblks AS STRING * 1 'Number of message blocks
(1 block=1024 msgs)
UpDirlvl AS STRING * 1 'Public u/l director Sec Lev
PrivDirlvl AS STRING * 1 'Private u/l directory Sec Lev
IndexFile AS STRING * 30 'Path/name of dir index file
(if any)
DoorMen AS STRING * 30 'Path/name of door menu file
DoorData AS STRING * 30 'Path/name of door data file
BltnMen AS STRING * 30 'Path/name of bulletin menu file
BltnLst AS STRING * 30 'Path/name of bulletin list file
PrivateOnly AS STRING * 1 'Private mail ONLY conference
(char 0= no; 1=yes)
ConfNewsFile AS STRING * 30 'Conference intro file
PubLicOnly AS STRING * 1 'Public mail only conference
(char 0= no; 1=yes)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.20
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - FNCONF.@@@ - Continued ║
╚═══════════════════════════════════════════════════════════════╝
AttachToDir AS STRING * 30 'Directory where files "attached"
to msgs are "located" after an U/L
CoSysOpName AS STRING * 25 'Co-SysOp's name (if any) for SysOp
mail
GraphicsQ AS STRING * 1 'Graphics Quoting
Cussing AS STRING * 30 'Path/name of Cusword file
AliasOK AS STRING * 1 'Alias Name OK in this conference
ReceiptSec AS STRING * 1 'Return receipt security level
Future AS STRING * 42 'Future growth room (v5.0/PRO!v1.0)
END TYPE
NOTE: Each 1 byte STRING is a character representing a value
(0-255)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.21
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - FNCONF.SEC ║
╚═══════════════════════════════════════════════════════════════╝
This binary file contains the security level and public status
for each conference. The format is 2 byte (integers) written for
each conference's Sec Lev (0-255) and PUBLIC status (1 = PUBLIC,
0=PRIVATE). It is written in the sequence: sec1,pub1,sec2,pub2,
etc...
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.22
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - FNEXTUSR ║
╚═══════════════════════════════════════════════════════════════╝
IF more than 40 total conferences are configured (main board plus
39 conferences), a file called FNEXTUSR is created by FNCFG.
This file maintains conference information for each user which
includes the high message read pointer, mail waiting flag, Joined
flag and conference scan flag. To calculate the size of a record
the following is done.
ExtraConfs = No.Confs - 40 ;Determine how many extended confs
HiMsgSize = ExtraConfs * 4 ;Determine bytes for Hi Msg Read
Pointers
BitChars = ExtraConfs \ 8 ;Determine how many bytes are nec-
essary for each BITMAP
IF ExtraConfs MOD 8 <> 0 THEN ;If number of confs divided by 8
BitChars = BitChars + 1 ;if not zero, we add a character
END IF
TotalBitChars = BitChars * 3 ;Total BITMAP bytes needed
ExtRecSize = HiMsgSize + TotalBitChars ;Total FNEXTUSR record
length
The file's records are in parallel with the BBS' USERS file - A
user having record number one in USERS also has record one in
FNEXTUSR.
Once the record size is calculated and that number of bytes is
read from the record offset in FNEXTUSR, the information is then
converted to the high message read pointers and the appropriate
conference flags.
The high message read pointers use 4 bytes for each conference
from the TotalBitChars. The 4 bytes per conference for high
message read pointers are MBF (Microsoft Binary Format (MSBIN)
Single Precision Reals.
The remaining bytes (TotalBitChars) are the conference BITMAP
flags. For each BITMAP (Scan, Mail Waiting, Joined) a BITMAP of
BitChars numbers of bytes is available (they are in this order,
too).
Determine the BITMAP flags in the following sequence:
1) All the Conference scan flags (user wants to scan these
conferences)
2) All mail Waiting flags (user has mail waiting in these
conferences)
3) All Joined Conference Flags (user has/can joined these
conferences)
Bit Flags: If a bit is non zero it is considered ON.
A zero bit is OFF.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.23
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - COSYSOP.BIT ║
╚═══════════════════════════════════════════════════════════════╝
This file contains co-sysop status bit flags. Each user has a
128 byte record to accommodate the 1024 possible conferences.
Each byte contains 8 bit flags (0-7) which are either ON (user
has co-sysop status) or OFF (user does not have co-sysop status).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.24
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - % Syntax ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! looks for the "%" syntax imbedded within display,
menu, and other files. When FeatherNet PRO! encounters a
%PATH\FILENAME syntax it will immediately suspend what it is
currently displaying and run or display the FILENAME on the %
syntax specified.
NOTE: Files may be "chained" by adding a "%FileName" to an
existing file.
EXAMPLE: If you started your Main Menu Display File with a;
%C:\FNET\DISP\UPDATE.TXT
@WAIT@
@CLS@
[REGULAR MAIN MENU]
FeatherNet PRO! would display the contents of UPDATE.TXT which
might be a new command you have added, wait for the user to Press
enter, then clear the screen and proceed to display the normal
Main Menu Display File.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.25
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - Remote Mode Doors ║
╚═══════════════════════════════════════════════════════════════╝
In remote mode, a DOOR requires a SERIAL port for proper
execution. The DOORS are created like those in local mode, but
further manipulation is necessary. REMOTE Mode DOORS are
handled in three ways:
1) The Serial port routines may be written directly into the
"DOOR" program. This provides greatest control, but the most
work.
2) Communication routines to init-
iating the DOOR application. A
sample batch file to initiate @ECHO OFF (No DOS echo)
such door with the CTTY command CTTY COM1: (COM1 output)
is to the right. The caller TYPE MYTEXT (function)
sees any host or local node CTTY CON (Output to scrn)
that is displayed such as the SFN.BAT (Load BBS)
display. MYTEXT
┌────────────┐
│ IMPORTANT! │
┌───────────────────────┴────────────┴──────────────────────┐
│ IT IS VERY DANGEROUS TO USE THIS TYPE ROUTINE UNLESS YOU │
│ HAVE A BREAK COMMAND DISABLE PROGRAM AND A CARRIER DETECT │
│ PROGRAM. IF A USER DROPS CARRIER IN A COMM ROUTINE LIKE │
│ THIS THE NEXT CALLER COULD LOG IN TO YOUR DOS! IF A USER │
│ BREAKS OUT OF THIS, HE COULD BE SITTING IN YOUR DOS DIR- │
│ ECTORY AND EXECUTE A "FORMAT C:" COMMAND! │
│ │
│ BE VERY CAREFUL! │
└───────────────────────────────────────────────────────────┘
3) Instead of using the CTTY command, a program called "DOORWAY"
may be used (and is recommended). It also redirects screen
output and keyboard input through the Serial Port, but prov-
ides many additional features that add reliability, further
compatibility and SECURITY.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 45.26
╔═══════════════════════════════════════════════════════════════╗
║ CONTROL FILES - Downloadable Files ║
╚═══════════════════════════════════════════════════════════════╝
The Sysop can place a file inside one of the directories
specified in DIR.LST or DLPATH.LST to make it available for
download. This doesn't provide a listing for the file. It only
places the file in the directory and only users aware of its
existence can download it. To add a file listing that includes
the filename, date, and description, the Sysop has several
options:
As previously discussed in the FNCFG DIR.LST section, the DIR.LST
file holds the names and paths of several DIRx text files. Each
file represents a different directory which contains the names of
files available for downloading within that directory. Among
others, the DIR.LST file consists of DIR Text Filename & Path and
Hard Disk Sub-directory fields.
1a) Run FNCFG to edit the DIR.LST file. (Conference Configura-
tion Section)
b) Add definitions for the new DIR file or locate an existing
DIR file that will eventually hold the file to download.
c) Make note of the Hard Disk Sub-directory and the DIRxx file
name.
d) Then exit FNCFG.
e) At the DOS prompt, copy the file to the Hard Disk Sub-
directory listed in the DIR.LST file for the directory in
which the file will be stored.
f) Use the FNFILER utility to edit the DIRxx file. (See
FNFILER in the SYSOP UTILITIES SECTION).
2a) Use the LOCALUP utility to add the file to a DIRxx file
and have the file itself placed in an appropriate Hard Disk
Directory. (See the SYSOP UTILITIES SECTION)
3a) Place the file in any of your alternate directory paths
(DLPATH.LST) and let the users know it is there.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 46.01
╔═══════════════════════════════════════════════════════════════╗
║ FILE STRUCTURES ║
╚═══════════════════════════════════════════════════════════════╝
Below you will find a listing of ALL the files that FeatherNet
PRO! v1.0 uses/creates. Now for a description of the column
headings:
1) FILENAME - The actual filename
2) ANSI - The name of the associated ANSI screen
(if applicable)
NOTE: Remember, if using XCodes, there will only
one file for both color & mono. This file
will be a color XCode screen but named the
same as the monochrome screen, ie: no "G"
appended to the end of the filename.
3) RIP - The name of the associated RIP screen.
4) S - Can this file be "Security Specific"?
5) TYPE - The "Type(s)" this file may be
6) LOC - The directory location of this file
NOTE: Remember, "Main" represents the \FNET
directory (where all the .EXE files are
located). The "Node" directory may also
be known as the "Home" directory.
7) CREATR - Tells you Who "Makes" the file.
╔════════════╤════════╤════════╤═╤═══════════════╤═══════╤══════╗
║ FILENAME │ ANSI │ RIP │S│ TYPE │ LOC │CREATR║
╠════════════╪════════╪════════╪═╪═══════════════╪═══════╪══════╣
║### │###G │###R │Y│ASC/ANS/XCD/RIP│SECMSG │SYSOP ║
║ARCMAS.BAT │--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║ARCMJS.BAT │--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║ARCMLS.BAT │--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║ARCMZS.BAT │--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║BADFILES.LST│--------│--------│-│ASC TEXT │ULT │SYSOP ║
║BLT.LST │--------│--------│-│DATA │BLTS │FNCFG ║
║BLT01 │BLT01G │BLT01R │N│ASC/ANS/XCD/RIP│BLTS │SYSOP ║
║BLTM │BLTMG │BLTMR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║CALLER1 │--------│--------│-│LOG FILE │LOGS │FNET ║
║CALLFIX.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║CHTM │CHTMG │CHTMR │ │ASC/ANS/XCD/RIP│MENU │FNETSM║
║CHAT.DEF │--------│--------│-│DATA │MAIN │FNET ║
║CHAT.HLP │--------│--------│-│HELP │HELP │SYSOP ║
║CL │CLG │CLR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║CL.HLP │--------│--------│-│ASC/XCD │HELP │SYSOP ║
║CLR.HLP │--------│--------│-│ASC/XCD │HELP │SYSOP ║
║CLRD.HLP │--------│--------│-│ASC/XCD │HELP │SYSOP ║
║CLOSED │CLOSEDG │CLOSEDR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║CM │CMG │CMR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║CNAME40.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
╚════════════╧════════╧════════╧═╧═══════════════╧═══════╧══════╝
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 46.02
╔═══════════════════════════════════════════════════════════════╗
║ FILE STRUCTURES - Continued ║
╚═══════════════════════════════════════════════════════════════╝
╔════════════╤════════╤════════╤═╤═══════════════╤═══════╤══════╗
║ FILENAME │ ANSI │ RIP │S│ TYPE │ LOC │CREATR║
╠════════════╪════════╪════════╪═╪═══════════════╪═══════╪══════╣
║COMMENT │COMMENTG│COMMENTR│N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║COSYSOP.BIT │--------│--------│-│DATA │FNSYS │FNCFG ║
║CUSSWRN │CUSSWRNG│CUSSWRNR│N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║CUSWORD │--------│--------│-│DATA │FNSYS │SYSOP ║
║DIR001 │AUTOMATC│--------│-│ASC TEXT │FILES │SYSOP ║
║DIR.LST │--------│--------│-│DATA │FILES │FNCFG ║
║DIRLST.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║DIRM │DIRMG │DIRMR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║DLPATH.LST │--------│--------│-│DATA │FNSYS │FNCFG ║
║DOORCVT.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║DOORS.LST │--------│--------│-│DATA │DOORS │SYSOP ║
║DORM │DORMG │DORMR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║EVENT.LST │--------│--------│-│DATA │EVENTS │FNCFG ║
║EXPIRED │EXPIREDG│EXPIREDR│N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║EXPWARN │EXPWARNG│EXPWARNR│N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║FAILDN │FAILDNG │FAILDNR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║FAILUP │FAILUPG │FAILUPR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║FM │FMG │FMR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║FN-NET.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNCFG.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNCFG.HLP │--------│--------│-│XCD │MAIN │F.S.I.║
║FNCFG.NDX │--------│--------│-│DATA │MAIN │FNCHK ║
║FNCHK.CFG │--------│--------│-│DATA │MAIN │SYSOP ║
║FNCHK.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNCONF.@@@ │--------│--------│-│DATA │FNSYS │FNCFG ║
║FNCONF.LST │--------│--------│-│DATA │FNSYS │FNCFG ║
║FNCONF.SEC │--------│--------│-│DATA │FNSYS │FNCFG ║
║FNECHO.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNET.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNET.IMG │--------│--------│- ASC TXT │NODE │SYSOP ║
║FNETPROT.DAT│--------│--------│-│ASC TEXT │SYS │SYSOP ║
║FNETSM.CFG │--------│--------│-│DATA │MAIN │FNETSM║
║FNETSM.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNETSM.HLP │--------│--------│-│DATA │MAIN │F.S.I.║
║FNETSM.NDX │--------│--------│-│DATA │MAIN │FNETSM║
║FNETTEST.BAT│--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║FNETTEXT │--------│--------│-│DATA │FNSYS │SYSOP ║
║FNEXTUSR │--------│--------│-│DATA │MAIN │FNET ║
║FNFILER.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNINDEX.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNODEMON.EXE│--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNPACK.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FNP102.DOC │--------│--------│-│ASC TEXT │DOCS │F.S.I.║
║FNUSERS.INF │--------│--------│-│DATA │USERNDX│FNETSM║
║FNVISUAL.HLP│--------│--------│-│ASC/XCD │HELP │SYSOP ║
║FNZIPCMT.EXE│--------│--------│-│PROGRAM │MAIN │F.S.I.║
║FT.HLP │--------│--------│-│ASC/XCD │HELP │SYSOP ║
║HELLO1 │HELLO1G │HELLO1R │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
╚════════════╧════════╧════════╧═╧═══════════════╧═══════╧══════╝
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page 46.03
╔═══════════════════════════════════════════════════════════════╗
║ FILE STRUCTURES - Continued ║
╚═══════════════════════════════════════════════════════════════╝
╔════════════╤════════╤════════╤═╤═══════════════╤═══════╤══════╗
║ FILENAME │ ANSI │ RIP │S│ TYPE │ LOC │CREATR║
╠════════════╪════════╪════════╪═╪═══════════════╪═══════╪══════╣
║INTRO │INTROG │INTROR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║LOCALUP.EXE │--------│--------│-│PROGRAM │MAIN │F.S.I.║
║LOGOFF │LOGOFFG │LOGOFFR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║MAIN.HLP │--------│--------│-│ASC/XCD │HELP │SYSOP ║
║MKFNTEXT.EXE│--------│--------│-│PROGRAM │FNSYS │F.S.I.║
║MM │MMG │MMR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║MODEMSET.DAT│--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║MODEMSET.EXE│--------│--------│-│PROGRAM │MAIN │F.S.I.║
║MODEMSET.PTR│--------│--------│-│DATA │MAIN │F.S.I.║
║MSGPRIV.TXT │--------│--------│-│ASC/XCD │DISP │SYSOP ║
║NEWS │NEWSG │NEWSR │Y│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║NEWUSER │NEWUSERG│NEWUSERR│N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║FNPNDX.A--Z │--------│--------│-│DATA │USERNDX│FNETSM║
║PERSONAL │--------│--------│-│ASC/XCD │DISP │SYSOP ║
║POSTDN │POSTDNG │POSTDNR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║POSTUP │POSTUPG │POSTUPR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║PREDN │PREDNG │PREDNR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║PRELOG │PRELOGG │PRELOGR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║PREUP │PREUPG │PREUPR │N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
║PRIV.DAT │--------│--------│-│DATA │FNSYS │USER ║
║PRIVUL.TMP │--------│--------│-│DATA │MAIN │FNET ║
║PRIVUTIL.EXE│--------│--------│-│PROGRAM │MAIN │F.S.I.║
║PWRD │--------│--------│-│DATA │FNSYS │FNCFG ║
║QUES │QUESG │QUESR │Y│ASC/ANS/XCD/RIP│MENU │SYSOP ║
║README.1ST │--------│--------│-│ASC TEXT │DOCS │F.S.I.║
║SCRIPT.0 │--------│--------│-│ASC TEXT │QUES │SYSOP ║
║SFN.BAT │--------│--------│-│ASC TEXT │MAIN │SYSOP ║
║SRCONFIG │--------│--------│-│ASC TEXT │NODE │FNCFG ║
║SYSOP.HLP │--------│--------│-│XCD │MAIN │F.S.I.║
║TRASH │--------│--------│-│ASC TEXT │FNSYS │SYSOP ║
║ULT.CFG │--------│--------│-│DATA │ULT │SYSOP ║
║ULTCFG.EXE │--------│--------│-│PROGRAM │ULT │F.S.I.║
║ULTCFG.HLP │--------│--------│-│DATA │ULT │F.S.I.║
║ULTESTER.DOC│--------│--------│-│ASC TEXT │ULT │F.S.I.║
║ULTESTER.EXE│--------│--------│-│PROGRAM │ULT │F.S.I.║
║USERDATE │--------│--------│-│DATA │MAIN │FNET ║
║USERNET.DAT │--------│--------│-│DATA │FNSYS │FNET ║
║USERS │--------│--------│-│DATA │USERNDX│FNETSM║
║USRSTAT │USRSTATG│USRSTATR│N│ASC/ANS/XCD/RIP│DISP │SYSOP ║
╚════════════╧════════╧════════╧═╧═══════════════╧═══════╧══════╝
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-A01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX A - Running With A Front-End Loader ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! supports the capability for a SysOp to utilize a
"front-end" program to load the BBS and control the events such
as net mail exporting and importing.
If you desire to use a "front-end" loader, you will have to
answer "Y" to the "Using a front-end to load BBS" question in
FNCFG's Modem Set Up Section. This will cause FeatherNet PRO!
to return to DOS after each call. Your front-end batch file
will then be able to take control of communications and events
until another call is received.
Parameters which MUST be passed to FeatherNet PRO! by the
frontend program are BAUDRATE and /ERR (If error correcting
connection is made). Any baud rate may be passed to FeatherNet
PRO! by using the baud rate on the command line as in: /C:2400
/C:9600 /C:14400 etc. FeatherNet PRO! handles baud rates up to
115200. These items are passed to FeatherNet PRO! as shown:
FNET /C:BAUDRATE /ERR
The following two parameters may also be passed to FeatherNet
PRO!:
/C:0 (Local Logon)
/C:9 (SysOp Logon)
Since a good percentage of FeatherNet PRO! SysOps are using
FrontDoor 2.02 we have inserted a few FrontDoor tips here on set
up. These actually apply to all front-end mailers but each
mailer handles them in different ways. This is not intended to
be a manual on setting up a front-end loader, thus these
examples are not meant to be complete, just give you an idea of
what it is that you need to do to get a caller from FrontDoor to
your BBS. These examples will not go into tossing or packing
mail. Below you will find some samples of the batch files that
are needed to run FrontDoor 2.02 with FeatherNet PRO!
A sample MAILER.BAT file which runs FrontDoor and calls the BBS
will be shown on the following page:
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-A02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX A - Running With A Front-End Loader - Continued ║
╚═══════════════════════════════════════════════════════════════╝
REM ---------- START MAILER.BAT SAMPLE ----------
@ECHO OFF
REM - SFN.BAT CONTROLLING FNET & FRONTDOOR W/ALL MAIL ROUTINES -
REM -- BATCH FILE USES FRONTDOOR-FNET-VPURGE-INTERPCB-PROPACK --
REM --- LOAD X00.SYS IN YOUR CONFIG.SYS FILE BEFORE STARTING ---
REM ---- SET ALL SYSTEM VARIABLES ----
C:\DV2\DVANSI
SET NODE=1
SET MAILDRV=C:
SET FNDRV=C:
SET FNDIR=\FNET
SET FNNODE=\FNET\NODE1
SET LINK=C:\LINK
SET DSZLOG=C:\FNET\NODE1\DSZLOG
SET FD=C:\FD
SET GE=C:\GE 3
:START
C:
CD \FD
IF ERRORLEVEL 255 GOTO INTERPCB
FD -NOUNPACK
REM ---------- FD EXIT WITH ERRORLEVEL ? ----------
IF ERRORLEVEL 100 GOTO MAILIN
IF ERRORLEVEL 60 GOTO EXEBBS
IF ERRORLEVEL 20 GOTO NODE_MAINT
IF ERRORLEVEL 10 GOTO DONE
REM ---------- END ERRORLEVELS & START ROUTINES ----------
:MAILIN
C:
CD \GE
IF EXIST C:\FD\FILES\*.SU? GOTO IMPORT
IF EXIST C:\FD\FILES\*.MO? GOTO IMPORT
IF EXIST C:\FD\FILES\*.TU? GOTO IMPORT
IF EXIST C:\FD\FILES\*.WE? GOTO IMPORT
IF EXIST C:\FD\FILES\*.TH? GOTO IMPORT
IF EXIST C:\FD\FILES\*.FR? GOTO IMPORT
IF EXIST C:\FD\FILES\*.SA? GOTO IMPORT
GOTO NODE_MAINT
:IMPORT
C:
CD \GE
GECHO TOSS IMPORT
GOTO INTERPCB
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-A03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX A - Running With A Front-End Loader - Continued ║
╚═══════════════════════════════════════════════════════════════╝
:INTERPCB
CD \FD\STP
CALL MAIL %LINK% ADMIN
CALL MAIL %LINK% AUTOS
REM ---------- ECHOS DELETED FOR BREVITY -----------
CALL MAIL %LINK% FNET
CALL MAIL %LINK% RIP
C:
CD\FNET\NODE1
FN-NET
GOTO MAILOUT
:MAILOUT
C:
CD \GE
GECHO SCAN -FORCE -HOLD -FLAGS
GOTO NODE_MAINT
:NODE_MAINT
C:
CD \FD\FILES
IF EXIST NODEDIFF.* GOTO NODELIST
:TIC
C:
CD \FD\FILES
IF EXIST *.TIC GOTO TIC2FNET
:FILES
C:
CD \FD\FILES
IF EXIST *.ZIP GOTO FILESIN
:DEL
C:
CD \FD\FILES
IF EXIST *.ZIP DEL *.ZIP
GOTO START
:TIC2FNET
C:
CD \FD
TIC2PCB TIC2FNET.CFG /BELL
GOTO FILES
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-A04
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX A - Running With A Front-End Loader - Continued ║
╚═══════════════════════════════════════════════════════════════╝
:NODELIST
C:
CD\FD\NODELIST
PKUNPAK C:\FD\FILES\NODEDIFF.*
MERGENL -K -F
CD \FD
FDNC /F
GOTO TIC
:FILESIN
C:
CD \FD\WRK
COPY C:\FD\FILES\*.ZIP C:\FD\TEMP
WGM-MAKE /dC:\FD\TEMP /fC:\FD\WRK\TEMP1 (continued next line)
/cC:\FD\WRK\COMMENT.FNP COPY C:\FILES\RESDESC
C:\FD\WRK\TEMP COPY TEMP+TEMP1 C:\FILES\RESDESC
COPY C:\FD\TEMP\*.ZIP C:\FILES\CF0000\UPLPV
DEL C:\FD\TEMP\*.ZIP
DEL C:\FD\WRK\*
GOTO DEL
:EXEBBS
DOBBS
:DONE
ECHO ATH1 > COM2
GOTO END
:END
REM ---------- END MAILER.BAT SAMPLE ----------
A sample DOBBS.BAT which is created by FrontDoor would look like
this:
EXEBBS 14400 2 1093 /ARQ/V42b
Bat File Baud P Event Error Inf.
EXEBBS - Batch file to call to determine information to pass
on to the BBS
BAUD - The Baud rate that FrontDoor connected with
P - Port (Com Port) Information
EVENT - Time until next event in minutes
ERROR INFO - Information passed if both modems connected in Error
Correcting Mode
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-A05
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX A - Running With A Front-End Loader - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: At this time, FeatherNet PRO! does not accept passed "time
until next event parameter", this will be written into the
next version. Port information does not need to be passed
to FeatherNet PRO! as all Port information is already rec-
orded in your SRCONFIG data file.
A Sample EXEBBS.BAT file would look something like this:
REM ---------- START SAMPLE EXEBBS.BAT ----------
@ECHO OFF
REM - %1=BAUDRATE %2=PORTINFO %3=UNTILEVENT %4=ERROR_CORRECTING -
REM - FEATHERNET PRO! DOES NOT ACCEPT TIME UNTIL NEXT EVENT YET -
REM --- FEATHERNET PRO! HAS THE PORT INFORMATION IN SRCONFIG! ---
SET CONTYPE=/ERR
IF "%1"=="300" SET BAUD=300
IF "%1"=="1200" SET BAUD=1200
IF "%1"=="1275" SET BAUD=1275
IF "%1"=="2400" SET BAUD=2400
IF "%1"=="4800" SET BAUD=4800
IF "%1"=="7200" SET BAUD=7200
IF "%1"=="9600" SET BAUD=9600
IF "%1"=="12000" SET BAUD=12000
IF "%1"=="14400" SET BAUD=14400
IF "%1"=="19200" SET BAUD=16800
IF "%4"=="/NONE" SET CONTYPE=
IF "%4"=="" SET CONTYPE=
CD C:\FNET\NODE1
CALL SFN.BAT %BAUD% %CONTYPE%
C:
CD \FD
MAILER.BAT
REM ---------- END SAMPLE EXEBBS.BAT ----------
A Sample SFN.BAT would look like this;
REM ---------- START SAMPLE SFN.BAT ----------
@ECHO OFF
CLS
ECHO SETTING UP NODE #%NODE%
%FNDRV%
CD%FNNODE%
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-A06
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX A - Running With A Front-End Loader - Continued ║
╚═══════════════════════════════════════════════════════════════╝
IF EXIST EVENT.BAT IF NOT EXIST PCBOARD.SYS DEL EVENT.BAT
FNET /c:%1 %2
IF ERRORLEVEL 255 GOTO End3
IF ERRORLEVEL 254 GOTO ReStart
IF ERRORLEVEL 3 GOTO ReStart
IF ERRORLEVEL 2 GOTO End3
IF ERRORLEVEL 1 GOTO End2
%FNDRV%
CD%FNNODE%
IF EXIST EVENT.BAT COMMAND /C EVENT.BAT
IF EXIST EVENT.BAT DEL EVENT.BAT
IF EXIST DOOR.BAT DOOR.BAT
%FNDRV%
CD%FNNODE%
ECHO SETTING UP NODE #%NODE%
SFN.BAT
:ReStart
%FNDRV%
CD%FNNODE%
ECHO SETTING UP NODE #%NODE%
SFN.BAT
:End2
@ECHO OFF
IF EXIST EVENT.BAT DEL EVENT.BAT
DEL PCBOARD.SYS
DEL DOOR.BAT
CLS
ECHO FeatherNet PRO!
Terminated!
:End3
@ECHO OFF
IF EXIST EVENT.BAT DEL EVENT.BAT
DEL PCBOARD.SYS
DEL DOOR.BAT
CLS
ECHO RE-LOADING FRONT DOOR!
REM ---------- END SAMPLE SFN.BAT ----------
For more information on setting up your mailer, please contact
the author of your particular front-end mail system.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-B01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX B - Running Under DESQview ║
╚═══════════════════════════════════════════════════════════════╝
DESQview, from Quarterdeck Office Systems, provides an excellent,
low-cost, software platform for SysOps wanting multiple nodes on
a single PC. DESQview has continued to be a proven environment
for multitasking over the years where so many others have flound-
ered and it is because of this that we have included and area
here for some setup tips.
BASIC HARDWARE CONSIDERATIONS:
If your computer has only 640k, you will be limited to a single
node when using DESQview. If however, your computer has 1 MB or
more of EMS memory, DESQview is capable of supporting up to 8
nodes on a single computer. Providing 2 nodes is simple. Going
beyond two nodes will require special software and hardware.
This appendix describes both approaches.
Multiple-node operation will require an EMS/XMS memory manager.
DESQview has some limitations in a PC or AT, unless you can
reduce the motherboard memory to 64k, 128k or 256k. The amount
of memory on our motherboard will affect the size of your 2nd,
3rd, etc. windows. This limitation is described in the DESQview
documentation. These limitations do not apply if you use an
80386 or higher class computer. Therefore, we recommend at least
an 80386 as the best choice for a multi-node host computer. If
you plan to use an 80386 or 80386/SX computer, we suggest you
purchase DESQview/386, which includes the QEMM memory manager.
This memory manager allows DESQview to use regular 80386 Extended
memory in the same manner as EEMS memory. The QEMM memory manager
may be purchased separately if you already own DESQview.
Before you continue, make certain you have read and thoroughly
understand the instruction manual provided with your copy of
DESQview.
MODIFICATIONS TO DOS CONFIG.SYS AND FEATHERNET PRO! BATCH FILES:
The first step in using DESQview with FeatherNet PRO! is setting
up your CONFIG.SYS file. FILES=40 is probably the most critical
value. This value tells DOS how many files may be open at the
same time. This value may need to be increased if you intend to
run more than 2 nodes.
A typical CONFIG.SYS file should include the following:
FILES=40
BUFFERS=40
If you use a disk cache at least 1mb in size, it is recommended
the BUFFERS be reduced to 4 as the disk cache is more efficient
than the DOS BUFFERS in handling repeated disk reads.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-B02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX B - Running Under DESQview - Continued ║
╚═══════════════════════════════════════════════════════════════╝
DESQVIEW SETUP DEFAULT SETTINGS:
The first step in configuring DESQview for use with FeatherNet
PRO! is specifying the default settings for DESQview. DESQview
has a setup program that may be invoked from within DESQview
called DVSETUP.
Enter DESQview and open the DVSETUP WINDOW. After the DESQview
setup program loads, you may press a letter for editing the
corresponding section or ESC for "simple setup". See the
graphic on the next page.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
GX: SAMPLE DESQview MAIN SETUP SCREEN
PRESS [P] for Performance defaults. Here is an example of
recommended settings:
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
GX: SAMPLE DESQview MAIN SETUP SCREEN
Task Processing Time (in Clock Ticks): Optimum Fore/Background
varies between 1 - 5. These settings depend on your CPU speed
and number of nodes running. You may need to experiment with
different settings to find the optimum setup for your system.
Optimize Communications (Y/N): N
Select "Y" if you're operating only 1-node.
Select "N" if you are running multiple nodes and/or if
you are using a FOSSIL drive such as BNU or X00 to cont-
rol your communications ports.
Manage printer contention? (Y/N): N
Always select "N" here or DESQview will try and give
equal time to your parallel ports and slow your machine
down considerably.
NOTE: NEVER indicate more clock ticks for Background processing
than you are using for the Foreground processing. DESQ-
view will automatically increase the amount of Background
clock ticks whenever there is reduced demand for Fore-
ground processing. This will be the case when running
FeatherNet PRO! in the background and doing other tasks in
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-B03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX B - Running Under DESQview - Continued ║
╚═══════════════════════════════════════════════════════════════╝
the foreground. This feature cannot function properly if
Background clock ticks are set higher than the Foreground
clock ticks.
Press ENTER to go back to the MAIN SETUP MENU and then PRESS [S].
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
GX: SAMPLE DESQview SWAPPING SETUP SCREEN
┌──────────┐
│ WARNING! │
└──────────┘
Make sure that you DO NOT allow DESQview to swap programs in and
out of memory or you will find that your BBS may be put on the
back burner while you are doing something memory intensive in
the foreground.
Press ENTER to go back to the MAIN SETUP MENU then PRESS [N].
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
GX: SAMPLE DESQview NETWORK SETUP SCREEN
These questions need only be answered if you are running under a
NOVELL or LANtastic network. The defaults are shown in the
screen above and should be left untouched if not running in a
network environment.
ADDING FEATHERNET PRO! TO DESQVIEW'S "OPEN WINDOW" MENU:
Refer to "Adding Your Own Program" in the DESQview manual. You
will need to "Add a Program" for each node of FNET you intend to
operate on your system. You only need call a single batch file
in the FeatherNet PRO! main BBS directory called SFN.BAT. In
these examples we show the passing of the NODE # parameter which
is caught by the SFN.BAT file and interpreted as to which node
should be brought up. Use the following settings for each node
you install with the exceptions of those noted below.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
GX: SAMPLE DESQview STANDARD OPTION SETUP SCREEN
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-B04
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX B - Running Under DESQview - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: The parameter option has a "2" in it. This is passed to
the SFN.BAT file as a parameter and tells the SFN.BAT file
that it is to start node 2. The reason we pass this para-
meter is that this way you only need one batch file to run
FeatherNet PRO!
PRESS <F10> TO TOGGLE TO THE SECOND HALF OF THE SETUP.
┌───────────────────────────────────────────────────────┐
│ Artwork shown here in Registered Users Printed Manual │
└───────────────────────────────────────────────────────┘
GX: SAMPLE DESQview ADVANCED OPTION SETUP SCREEN
The SFN.BAT file will need to include a line reading:
C:\DV\DVANSI (Assuming that C:\DV is your DESQview directory)
This is the START of a sample DESQview aware SFN.BAT file for
running multiple nodes:
@ECHO OFF
SET NODE=%1 <----- Sets the node as that passed from DESQview
CLS
ECHO SETTING UP NODE #%NODE%
C:
CD \FNET\NODE%NODE%
IF EXIST EVENT.BAT IF NOT EXIST PCBOARD.SYS DEL EVENT.BAT
FNET /C:%1 %2
IF ERRORLEVEL 255 GOTO ReStart
IF ERRORLEVEL 254 GOTO FaxIn
IF ERRORLEVEL 3 GOTO ReStart
IF ERRORLEVEL 2 GOTO ReStart
IF ERRORLEVEL 1 GOTO End2
C:
CD \FNET\NODE%NODE%
IF EXIST EVENT.BAT COMMAND /C EVENT.BAT
IF EXIST EVENT.BAT DEL EVENT.BAT
IF EXIST DOOR.BAT DOOR.BAT
C:
CD \FNET\NODE%NODE%
ECHO SETTING UP NODE #%NODE%
SFN.BAT
:ReStart
C:
CD \FNET\NODE%NODE%
ECHO SETTING UP NODE #%NODE%
SFN.BAT
---------- BATCH FILE CLIPPED FOR BREVITY ----------
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-B05
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX B - Running Under DESQview - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: The above are "recommended" settings and have worked
well on many systems. Due to the nature of DESQview
and the extremely varied nature of computer hardware,
you may find that your optimum settings are different.
Please refer to the DESQview documentation for further
information.
There are numerous motherboard manufacturers of "CLONES". Some
are more "perfect" and closer to the IBM PC than others. It is
anticipated some users will run into hardware conflicts when
attempting to run a BBS under DESQview. This is not a fault of
DESQview or the FeatherNet PRO! software. If you find yourself
in this situation, it is recommended you either (1) try a dif-
ferent motherboard/CPU, (2) purchase a LAN to run multiple nodes
from workstations or (3) try different serial cards or modem
cards (if using an internal modem(s)).
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-C01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX C - Using "RING BACK" Mode ║
╚═══════════════════════════════════════════════════════════════╝
If you desire to use "Ring Back" mode, you will have to answer
"Y" to the appropriate question in FNCFG in the "Modem / Node /
Subscription configuration. Then enter the amount of time (in
seconds) for the BBS to wait for the "ring back" call after the
initial call triggers the ring back alert. A recommended
"waiting" period is 60 seconds.
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-D01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX D - Macros ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! supports a wide array of macros for conveniently
displaying information about the caller and the system, control-
ling the display and user input and addressing messages.
A "SysOp" level user can enter a message to a users having
specific security level or to users who fall within a range of
security levels:
@70@ (level 70 ONLY) or @70-100@ (Level 70 through level 100)
A message addressed to a security level will result in the
message being treated as a NEW personal message to any user
whose security level is being addressed and the user will be
notified of new mail waiting at logon.
A "SysOp" level user may also address a message to @USER@. A
message addressed to @USER@ will result in the message being
treated as a NEW personal message to all users and they will be
notified of new mail waiting at logon.
FeatherNet PRO! is unique with this mail waiting notification in
that it needs to perform no search at logon to notify the user
of new mail. The conference(s) having mail waiting are included
in the notification. A user may choose to read new personal
mail at the time of notification or wait until later (Unless the
SysOp has the "FORCE Users to read waiting Mail" option turned
on!).
Many MENU and DISPLAY sample files are included in your
FeatherNet PRO! package and will serve as prime examples of how
to use the FeatherNet PRO! macros within them.
With the exception of 9 macros, all may be included in text
files, menus, bulletins and messages. The macros not supported
within messages are:
@BEEP@ @MORE@ @QON@
@CLS@ @PON@ @QOFF@
@HANGUP@ @POFF@ @WAIT@
On the following page are the macros which are now supported and
a short description of what they do.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-D02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX D - Macros - Continued ║
╚═══════════════════════════════════════════════════════════════╝
INFORMATION ABOUT THE CALLER:
@ALIAS@ = User's "ALIAS" name
@BAL@ = BALANCE in user's hourly subscription account (hr)
@BLEFT@ = User's BYTES LEFT for download today
@BLIMIT@ = Daily BYTE LIMIT on downloads
@BRATIO@ = Download BYTE RATIO
@BDATE@ = User's BIRTHDATE
@BDAY@ = Download BYTES TODAY
@CITY@ = CITY the caller is from (from FNUSERS.INF file)
@CTYSTATE@ = CITY & STATE the caller is from (from USERS file)
@DLEFT@ = DAYS LEFT for hourly subscription
@BLIMIT@ = Daily BYTE LIMIT on downloads
@BRATIO@ = Download BYTE RATIO
@BDATE@ = User's BIRTHDATE
@BDAY@ = Download BYTES TODAY
@CITY@ = CITY the caller is from (from FNUSERS.INF file)
@CTYSTATE@ = CITY & STATE the caller is from (from USERS file)
@DLEFT@ = DAYS LEFT for hourly subscription
@EXPDATE@ = EXPIRATION DATE for non-hourly subscription
@EXPDAYS@ = EXPIRATION DAYS left for non-hourly subscription
@FDT@ = FILES Downloaded TODAY
@FIRST@ = FIRST name (first letter capitalized)
@FIRSTU@ = FIRST name (all caps)
@FRATIO@ = Download FILE RATIO
@KBLEFT@ = K BYTES LEFT (= @bytesleft@ / 1024)
@KBLIMIT@ = K BYTE LIMIT (= @bytelimit@ / 1024)
@LDATE@ = LAST DATE on
@LNEW@ = LAST "NEW files search" date
@LTIME@ = LAST amount of TIME on
@MAXBATCH@ = MAXIMUM Number of files in a BATCH file transfer
@MAXBR@ = MAXIMUM allowed BYTE RATIO
@MAXB@ = MAXIMUM number of BYTES allowed to download
@MAXF@ = MAXIMUM number of FILES allowed to download
@MAXFR@ = MAXIMUM allowed FILE RATIO
@MSGLEFT@ = Number of MESSAGES LEFT (Written)
@TIMESON@ = Number of TIMES ON
@PLTR@ = Default PROTOCOL LETTER
@PDESC@ = Default PROTOCOL DESCRIPTION
@SEC@ = SECURITY level
@STATE@ = STATE caller is from (from FNUSERS.INF file)
@TLEFT@ = TIME LEFT today
@TLEFT@ = TIME LEFT today
@TLIMIT@ = TIME LIMIT
@TDB@ = TOTAL DOWNLOADED BYTES
@TDF@ = TOTAL DOWNLOADED FILES
@TUB@ = TOTAL BYTES UPLOADED
@TUF@ = TOTAL FILES UPLOADED
@UCOMMENT@ = USER's *Public* personal information COMMENT
@USER@ = USER's full name (all caps)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-D03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX D - Macros - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: The following three MACROS will be activated AFTER v1.0 is
released.
@COMPANY@ = User's COMPANY name
@MEMOA@ = MEMO field A
@MEMOB@ = MEMO Field B
ADDRESSING MESSAGES (Placed In The "TO:" Field Within A Message):
@USER@ = Addresses a message to EVERYONE
@##@ = Messages are addressed to users of the security
level specified by "##".
@##-##@ = Messages are addressed to users of the security
level specified by a range of numbers ##-##.
NOTES: Messages addressed to a user using the above macros are
protected so that only persons with SysOp privileges may
delete the message.
Also, messages that are addressed using the @##@ codes
are treated as PRIVATE messages so that only those users
having the security level(s) specified may read the
message. The message is protected from being viewed by
anyone else.
SYSTEM INFORMATION:
@BBSNAME@ = BBS NAME
@CONFNAME@ = Current CONFERENCE NAME joined
@CONFNUM@ = Current CONFERENCE NUMBER joined
@CMSGS@ = Current CONFERENCE total active MESSAGES
@EVENT@ = Time next EVENT "Window" opens
@FVER@ = FEATHERNET VERSION running (ex: v1.0)
@HMR@ = User's HIGH MESSAGE READ
@HMSG@ = HIGH MESSAGE number in current conference
@LMSG@ = LOW MESSAGE number in current conference
@NODE@ = NODE Number
@NUMBLT@ = NUMBER of BULLETINS
@PREVCALL@ = Name of the PREVIOUS CALLER on this node
@SDATE@ = Current SYSTEM DATE
@SFIRST@ = SYSOP's FIRST name only
@SNAME@ = SYSOP's full real NAME
@STIME@ = Current SYSTEM TIME
@TCALLS@ = TOTAL number of CALLS the system has received
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-D04
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX D - Macros - Continued ║
╚═══════════════════════════════════════════════════════════════╝
SYSTEM AND DISPLAY CONTROLS:
@BEEP@ = Sends a <CTL><G> (ASCII BELL character) to the
caller but is not heard on the local machine un-
less the Page Beep is turned on.
@CLS@ = Clear the entire screen (must start in column 1)
@HANGUP@ = Hangs the caller up (ONLY may placed in a file,
not a message and must start in column 1)
@MORE@ = Cause a "more?" prompt to be displayed
@POFF@ = Turns Prompts OFF (disables "More?" prompt)
@PON@ = Turns Prompts ON (enables "More?" prompt)
@QOFF@ = Disables CTRL-X/CTRL-K checking (display abort)
@QON@ = Enables CTRL-X/CTRL-K checking (display abort)
@WAIT@ = Display a "Press Enter to Continue" prompt
SPECIAL SCREEN AND CURSOR CONTROLS:
@CBUP:##@ = Cursor back-up ## places on a line. Requires ANSI
Support (should *only* be used in files)
@CLREOL@ = Clear to End-of-Line. Requires ANSI Support.
(Should *ONLY* be used in files)
@CPOS:####@ = Locates the cursor to the position implied but the
(####) value. A user *MUST* have ANSI capability
(not necessarily in graphics mode) for this func-
tion to proceed. The function expects a strictly
formatted number indicating the row and column to
locate the cursor to.
As for example: @CPOS:1235@ would cause the cursor
to be located to row 12, column 35 on both the
local and remote (if caller is connected) comp-
uters. The maximum row allowed is 23 and the
column 80. The numbers are based 1-based. 01-23
and 01-80 are valid numbers for this function.
@DELAY:###@ = Stops program execution for (###) tenths of a sec-
ond. An approximate maximum delay of 25.5 seconds
is possible.
@DOFF@ = Cancels the delayed print mode.
@DON:#@ = A teletype-like printing function. Causes text to
be printed as though it is being typed. Currently,
the # should be 1 or 2 (max.!). This is a "delay-
ed" print function. You should restrict its use to
files only.
NOTE: This macro will only work for a full line
(or lines). It can not be used to print
"part" of a line at one speed and another
"part" of the *SAME* line at a different
speed. Different lines may use the command
to change the speed.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-D05
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX D - Macros - Continued ║
╚═══════════════════════════════════════════════════════════════╝
@FIRST:20C@ = Added support for "ALL Data Related Macros" to
include Centering, and Left/Right justification of
the text the macro produces. You use the normal
macro (as our example), followed with the ":##?"
all prior to the ending "@" terminator. The "?"
may be "C" for center, "R" for right justify or
nothing to left justify. The number after the ":"
indicates the designated space the macros is to
fill. Based on the output method (Centered, Right
or Left justified), blanks are used to exactly
fill the desired portion of the screen. If a var-
iable length is equal to or greater than that
specified as the "field" length, the request is
ignored.
@PNODE@ = The Node being paged for chat
@POS:##@ = Positions the cursor "forward" on the same line to
the (##) position. The new location can not be
less than the current position of the cursor.
@SNODE:##@ = STATUS of NODE(xx) and Caller Information (Similar
to FNODEMON's information)
@BAN:##@ = Scrolls a line of text through a designated line
length ("window") on a single line as a BANNER.
The window size must be less than 78 characters
and must not exceed 78 plus the current position.
The "##" is the window length. You may use a
single line of text following the macro or you may
display the contents of a file (entire contents)
by having a "%" followed by the path and filename
of a file to use immediately following the macro.
(Ex: @BAN:45@%C:\FNET\PARTY.TXT)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-E01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX E - Color Macros ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! employs a fast internal ANSI driver. This reduces
the urge to employ the popular @Xfb macros in text files and
menus. However, the @Xfb macros have an advantage in that they
can be used in a single file with no graphics version of that
file necessary. A caller in non-graphics mode will see the con-
tents of the file as pure ASCII with no color added, because
FeatherNet PRO! will automatically strip the @Xfb codes out for
them. A user in color graphics mode will see the colors design-
ated by the @Xfb macros.
The color codes are: @Xfb, where "f" is the Foreground color
and "b" is Background color.
┌────────────┐
│ IMPORTANT! │
└────────────┘
The following codes are case-sensitive. All color macros MUST BE
IN CAPITAL LETTERS. @XFB will work, @xfb will not.
╔═════════════╤═════════════╤═════════════╤═════════════════╗
║ Background │ Foreground │w/Blinking FG│ Hi-Intensity FG ║
╠═════════════╪═════════════╪═════════════╪═════════════════╣
║ 0 = Black │ 0 = Black │ 8 = Black │ 8 = Black ║
║ 1 = Blue │ 1 = Blue │ 9 = Blue │ 9 = Blue ║
║ 2 = Green │ 2 = Green │ A = Green │ A = Green ║
║ 3 = Cyan │ 3 = Cyan │ B = Cyan │ B = Cyan ║
║ 4 = Red │ 4 = Red │ C = Red │ C = Red ║
║ 5 = Magenta │ 5 = Magenta │ D = Magenta │ D = Magenta ║
║ 6 = Yellow │ 6 = Yellow │ E = Yellow │ E = Yellow ║
║ 7 = White │ 7 = White │ F = White │ F = White ║
╚═════════════╧═════════════╧═════════════╧═════════════════╝
EXAMPLES
╔═══════╤═══════╤═══════════════════════╗
║ Code │ BG │ FG ║
╠═══════╪═══════╪═══════════════════════╣
║ @X1F │ Blue │ Bright White ║
║ │ │ ║
║ @X2E │ Green │ Bright Yellow ║
║ │ │ ║
║ @XCF │ Red │ Blinking Bright White ║
╚═══════╧═══════╧═══════════════════════╝
NOTE: Blinking foreground colors are supported. To use them,
choose both your FOREGROUND and BACKGROUND colors from the
high intensity chart. Example: @XDFHELLO
This will produce a blinking white HELLO on a magenta background.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-F01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX F - Aborted Download Credits ║
╚═══════════════════════════════════════════════════════════════╝
The vast majority of file transfers will be done successfully,
however, there are some that will be aborted in midstream for
various reasons (i.e. carrier loss, noisy phone lines, user
abort, etc.). FeatherNet PRO! has an additional function that
reads the file "DSZLOG" (MUST be located in each NODE directory)
after each download. If the download was aborted, this will be
indicated in "DSZLOG" and the caller will not be charged for a
download.
The file "DSZLOG" is created by external protocol drivers (DSZ,
PUMA, ETC). You must use the protocol driver's instructions for
specifying a log file in order to create a "DSZLOG" file in each
NODE directory.
For DSZ, placing the following command in your SFN.BAT file will
cause DSZ to create a DSZLOG during each file transfer.
"SET DSZLOG=C:\FNET\NODE1\DSZLOG" (you must edit this according
to your setup)
If a download is aborted but FeatherNet PRO! can't find a file
called "DSZLOG" in the current node directory, the user will be
charged for the download as if it was a successful transfer.
Consequently, it is in your user's best interest to enable this
feature.
NOTE: FeatherNet PRO! also looks for the "DSZLOG" after running
a DOOR. Because this feature is read after the use of a
DOOR FeatherNet PRO! will update a users personal file
with upload/download credits if s/he made use of a CD-ROM
DOOR or another type of transfer DOOR.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-G01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX G - Configuring & Running Multiple Events ║
╚═══════════════════════════════════════════════════════════════╝
An "EVENT" is a means of unattendedly 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.
Events can be set to run on specific days of the week, every day
of the week or on any specific date. Multiple events can be set
to run as Expedited (non-sliding) or Sliding. The events are
each set to run within a specified time period ("window"). (See
"EVENT CONFIGURATION" in the "FNCFG" section)
A "Condensed" sample FNCFG EVENT.LST Editor screen follows.
Batch Begin End Last
Act Mod File Time Time Date Date Day
SMTWTFS
--- --- -------- ----- ----- -------- -------- -------
1) Y S PROGINN 02:15 02:45 YYYYYYY
2) Y E LEAPING 01:30 03:00 02-29-00 NNNNNNN
3) Y S CHRSTMAS 03:15 04:30 12-25-00 YYYYYYY
4) Y E MONTHLY 04:00 05:30 00-01-00 YYYYYYY
<ESC>=Exit <Alt><I>=Insert a Line
<Alt><R>=Repeat a Line <Alt><D>=Delete a Line
Explanation for each field follows:
ACT = Active Y/N
MOD = Event Execution Mode (Expedite, Sliding).
BATCH FILE = Name of the batch file for the event.
(w/o the ".BAT").
BEGIN TIME = The time the event should begin.
END TIME = Latest time event will be allowed to run.
DATE = Specific date on which the event is to be run.
LAST DATE = Date event was last run. (updated by FeatherNet)
DAYS = Sunday through Saturday - days of the week to
run event.
The Begin Time and End Time create a "window" in which the event
is to be run. FeatherNet PRO! will run the event right at the
Begin Time if possible, however, should the BBS be busy handling
a file transfer, running a door, or out to DOS, it will still
run the event if control is returned to FeatherNet PRO! before
the End Time has been reached.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-G02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX G - Configuring & Running Multiple Events - Continued║
╚═══════════════════════════════════════════════════════════════╝
In SAMPLE EVENT #1: The event is ACTIVE as the "Y" in the "Act"
column specifies. It is a SLIDING event as indicated by the "S"
in the "Mod" field. The batch file to be run during the event is
"PROGINN.BAT". The Begin Time is "02:15" and the latest the
event will be run is "02:45". No specific date is given and the
event will be run every day continuously since each "Days" field
has a "Y" specifying to run the event on that day.
In SAMPLE EVENT #2: The event is ACTIVE as the "Y" in the "Act"
column specifies. It is a EXPEDITED event as indicated by the
"E" in the "Mod" field. The batch file to be run during the
event is "LEAPING.BAT". The Begin Time is "01:30" and the latest
the event will be run is "03:00". It is *only* run on February
29, during Leap Year. Since the event is "expedited", users will
have time allowed on the system temporarily adjusted by
FeatherNet PRO! (if necessary) while it attempts to run the event
promptly at the Begin Time. Since a specific date (including
dates with wildcards, FeatherNet PRO! considers "00" in a date
month or year field to be a wild-card) is specified, FeatherNet
PRO! ignores the "Days" field.
In SAMPLE EVENT #4: The event is ACTIVE as the "Y" in the "Act"
column specifies. It is a EXPEDITED event as indicated by the
"E" in the "Mod" field. The batch file to be run during the
event is "MONTHLY.BAT". The Begin Time is "04:00" and the latest
the event will be run is "05:30". It is *only* run on the first
day of *each* month. Since the event is "expedited", users will
have time allowed on the system temporarily adjusted by
FeatherNet PRO! (if necessary) while it attempts to run the event
promptly at the Begin Time. Since a specific date is specified,
FeatherNet PRO! ignores the "Days" field.
An "EVENT.BAT" file is created by FeatherNet PRO! when the event
is run. EVENT.BAT contains one word - the name of the batch
file to run for this event. Your event batch files MUST have a
".BAT" file extension! SAMPLE FILE: "MYEVENT. BAT" follows:
@ECHO OFF
CD C:\FNET\TODAY
TODAY23 NOPAUSE PAINT64577 >TODAYG.TXT
TODAY23 NOPAUSE >TODAY.TXT
CD C:\FNET
CALL PACK.BAT
CD C:\FNET\NET
EXPORT NODELIST
CD C:\TELIX
TELIX STELIX
CD C:\FNET\NET
IMPORT
DEL EVENT.BAT
CD C:\FNET
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-G03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX G - Configuring & Running Multiple Events - Continued║
╚═══════════════════════════════════════════════════════════════╝
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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-H01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX H - Allowing "FREE" Downloads ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! has a means for the SysOp to allow "FREE" down-
loaded files. This is useful for letting users download specific
files without being charged for them. This will enable your users
to download specific files regardless of their file transfer
ratio.
To allow "FREE DOWNLOAD" files, you must go into the "FILE
LOCATIONS" section of "FNCFG" and set the PATH and directory
name of your "FREE DOWNLOAD DIRECTORY".
"FREE DOWNLOAD" files must be placed in the indicated directory.
Once you place files there the users will not be charged against
their BYTE or FILE ratio for those files, nor would they be
charged against a total file count, if downloaded.
Some files that you might consider placing in this directory are:
1) The rules of your BBS
2) The RIP icons for your BBS
3) A complete listing of files available on your BBS
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-I01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX I - Duplicate Uploads Protection ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! has "duplicate upload" detection through the
file "FNCHK.EXE". Upon completion of the upload, FNCHK.EXE
performs testing of all uploads to ensure their integrity. The
files uploaded are then checked against the files already in the
upload directory. If there are files with the same name in the
UPLOAD directory, the newly uploaded files will be moved into
the SysOp's "duplicate uploads" directory for evaluation
/disposition.
The "Duplicate Uploads" directory is specified in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-J01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX J - Shelling to Archive Manipulations ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! allows the SysOp to choose between "shelling"
and "swapping" to DOS for archive manipulations. 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.
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.
You need to ensure these batch files are edited to cause the
archive extraction and compression is performed in the node's
"work" directory.
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 dir-
ectory. 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.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-K01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX K - Script Questionnaire Instructions ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! supports script questionnaires. Set them up as
follows.
1) If scripts questionnaires are activated, you MUST make
a script for new users to answer. The name for the new
user questionnaire is "SCRIPT.0"
2) Additional script questionnaires may be added (up to 99
per node) as desired. The name for each of these is
"SCRIPT.x" where "x" is the number of the questionnaire
from the questionnaire menu.
3) The questionnaire menu is "QUESsssi" (must exist if more
than one script) where "sss" is the optional security
level needed to view the file and "i" is the optional
graphics identifier "G" or "R".
4) On the first line of each question place ONLY a ";" for
an optional question or a ":" if the user MUST answer the
question.
5) On the 2nd line place a number on a line by itself indi-
cating how many lines of text are in the forthcoming
question.
6) Type in a question. DO NOT use more lines of text for a
question than have been specified. IF THIS OCCURS, YOUR
QUESTIONNAIRE WILL BOMB.
7) DO NOT PUT ANY BLANK LINES IN THE FILE!
8) Answers to SCRIPT.0 are found in the file "SCRIPT.ANS".
Answers to other script files are found in "SCRIPTx.ANS"
where x is the number of the script.
SAMPLE NEW USER SCRIPT QUESTIONNAIRE:
-----------------------------------------------------------------
:
8
Welcome to the FeatherNet HQ BBS! In order to establish an
account for you here we will need some information to satisfy
our records. If you are a Registered User of any FeatherNet
BBS Software Product your account will be upgraded within 24
hours. If not you will have general access to most of the system.
Please fill out these questions as completely as you can so that
we may track demographics and other such things.
ARE YOU THE "SYSOP" OF AN OPERATING BBS? (ENTER BBS NAME OR NO):
;
1
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-K02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX K - Script Questionnaire Instructions - Continued ║
╚═══════════════════════════════════════════════════════════════╝
ENTER YOUR COMPANY NAME (RETURN IF NONE):
;
1
ENTER YOUR TITLE (RETURN IF NONE):
;
1
ENTER YOUR BUSINESS TELEPHONE NUMBER (RETURN IF NONE):
:
16
THE RULES ON THE FeatherNet HQ BBS:
1) Act and be responsible for your own actions.
2) Do not upload any (C)opyrighted files with the express
notation of being "Non-Transferable" or any Commercial
release programs/files. Failure to abide by this will
void your technical support agreement, you will be locked
from this system and your name will be reported to the
Software Publishers Association (S.P.A.).
3) No vulgar language is allowed on the system.
4) The use of multiple accounts on the system won't be toler-
ated. Each user has a set time limit and many users need
access to the system. Use of multiple accounts are unfair
to the others and will get you a "NO STATUS" flag.
5) The use of an alias is allowed ONLY IN the ALIAS Conference!
ENTER "YES" IF YOU'VE READ THE ABOVE AND AGREE TO IT, ELSE NO:
:
15
THE ELECTRONIC PRIVACY ACT:
It is required that you, the user, are informed of the follow-
ing; There are NO private messages on this system. Although the
system will allow you to post messages that are flagged
"private", the SysOps, certain Co-SysOps and the Officers of
FeatherNet Software, Inc. can and will read them. Please be
assured that any message that is thusly marked private will be
treated in the strictest confidence and only the person to whom
the message is addressed will know anything about it outside the
few in our company. Also all messages that are over 30 days
old, whether read or not will be deleted. We can not be resp-
onsible for undelivered mail. If you do not agree with these
policies then you have the option NOT TO POST SUCH MESSAGES and
there will be no problems.
ENTER "YES" IF YOU'VE READ THE ABOVE AND AGREE TO IT, ELSE NO:
:
17
LIMITED WARRANTY:
This is a PRIVATE Electronic Information System maintained for
the express purpose of supporting registered FeatherNet Software
users and SysOps. In exchange for the privilege of using and
downloading from this system, you are expressly promising the
following:
A: To assume all risks of your downloads or use; and,
B: That your uploads are neither;
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-K03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX K - Script Questionnaire Instructions - Continued ║
╚═══════════════════════════════════════════════════════════════╝
a: Virused, Trojaned, or Tampered with; and
b: Infringing the owner's (C)opyright;
All digitally encoded information on this system is provided "AS
IS" with all faults and defects. We disclaim all express and
implied warranties including MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, INCIDENTAL and/or CONSEQUENTIAL DAMAGES.
If you do not agree to this your account will be erased in the
next system event.
ENTER "YES" IF YOU HAVE READ THE ABOVE AND AGREE TO IT, ELSE NO:
:
2
The following questions will round out your account information:
FOR LATER VERIFICATION, ENTER YOUR MOTHER'S MAIDEN NAME:
;
1
ENTER YOUR COMPUTER TYPE:
;
1
ENTER YOUR OPERATING SYSTEM TYPE AND VERSION:
;
1
ENTER YOUR TERMINAL PROGRAM NAME:
:
3
PLEASE TELL US WHERE YOU LEARNED ABOUT THE FeatherNet HQ BBS.
IF YOU FOUND THE NUMBER IN ONE OF OUR PROGRAMS, PLEASE TELL
US WHERE YOU DOWNLOADED THE PROGRAM FROM:
----------------------------------------------------------------
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-L01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX L - Private "Personal" File Transfers ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! includes a feature which permits the SysOp to
allow designate users the ability to perform private file
transfers with other authorized users.
A flag is set and the user is automatically notified during the
logon process if any private files for him/her are waiting to be
downloaded. After a successful download the file is flagged as
received and will not be listed to the user again.
Users WILL see only files meant for them to be downloaded. No
user may download a file even if he enters the filename unless
it is in the private file transfer database with his/her name
attached.
1) To enable the private file transfers (from user to user) the
SysOp must run "FNCFG.EXE" and set the option to "Y" under
the "General Information 2" heading. Then the SysOp MUST
define a DOS file path where the private files will be stored
in the "file locations" (1) section. This should ONLY be
available to the private file transfer function. Do not
place this path in any conference's DLPATH.LST (type) file.
This would compromise the security afforded by this feature.
Ensure you save the configuration with the "Y" answer and the
private file directory will be created for you.
2) Ensure the file "PRIVUTIL.EXE" is in your main BBS directory.
PRIVUTIL.EXE
RUN from the BBS HOME directory to "ADD" files to or
"DELETE" files from the database.
Command Line: PRIVUTIL
3) The SysOp MUST manually turn on a user's "private" file
transfer flag using FNETSM. When the SysOp uses "PRIVUTIL"
to make a private file available to a user, that user is
automatically authorized private transfers and the private
file waiting flag is turned on for the user.
4) An authorized user selects the private file transfer option
by using the (P) command from the file transfer command
prompt.
Then s/he may:
[1] Download any files waiting for himself
[2] List a directory of any files waiting for himself
[3] Upload a file(s) to another authorized user
[Q] Quit to the main file transfer menu
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-L02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX L - Private "Personal" File Transfers - Continued ║
╚═══════════════════════════════════════════════════════════════╝
NOTE: You MUST ensure you have the command "SET DSZLOG=
C:\FNET\NODE1\DSZLOG" (where C:\FNET\NODE1\DSZLOG
will be your BBS NODE directory and the text file
"DSZLOG") in your "SFN.BAT" file or in a batch file
which calls "SFN.BAT" to load FeatherNet PRO!.
Without this setting downloads cannot be verified and
files will continue to be listed to the user even
after a successful download.
5) "PRIV.DAT" will be created in the BBS HOME directory when the
1st private file is transferred to another user.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-M01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX M - Attaching Files to Messages ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! allows files to be uploaded and "attached" to
messages. This is done by saving a message with the [SA] command
instead of the regular [S] command. Only users with sufficient
security level may use the [SA] command and upload a file atta-
ched to the message.
Each conference has a flag to allow ATTACHED files to be uploaded
when saving a message. If ATTACHED files are disallowed in a
conference the [SA] message save command is processed as an [S]
and no upload is solicited.
Procedure for "ATTACHING" a file to a message.
1) Write a message and save with the [SA] command. Prior to the
message actually being saved, user will be prompted for a
file name to UPLOAD. Only one file will be processed during
an "attached" upload - ensure users are aware of this. No
description of the file is solicited (nor is one necessary).
2) Once the file is uploaded, it is processed as any uploaded
FNCHK handles the testing of the upload, running the batch
file FNETTEST.BAT and adding a successfully upload to the
appropriate conference #.ATT attachment database (where # is
the number of the conference (1 -High Conf#)). When control
is returned to FeatherNet PRO!, it checks for a file named
"ATTACH.INF" which is in the attachment directory for the
joined conference. If the information in ATTACH.INF ind-
icates a successful upload, the record number in the conf-
erence attachment database is then written to positions 126
and 127 of the message header as it is saved. This record
number is what FeatherNet PRO! uses when reading a message
to determine if a message has an attached file.
3) Database File Maintenance is automatic in that whenever a
message is deleted which has an attached file record number
in the header, that record number is blanked in the attach-
ment database. Files in each attachment directory are never
deleted. This is a function the SysOp must manually do
since he may want to keep some files after the messages they
were "attached" to have been deleted.
Attached files can be uploaded "locally" as can any file. It is
strongly recommended you do not CARBON COPY messages with files
attached. Once a message is deleted the record in the database
is blanked. FNCHK searches for blank records in the database
when adding a file. If there are multiple copies of a message
with the same attached file and file record # in the database, a
user deleting the message could unknowingly delete the database
entry for a newer attached file.
Please advise your users allowed to attach files of this pot-
ential problem.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-M02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX M - Attaching Files to Messages - Continued ║
╚═══════════════════════════════════════════════════════════════╝
You may delete the database from the attachment directory at any
time without creating any problem.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPScrip Screens ║
╚═══════════════════════════════════════════════════════════════╝
With your purchase of the FeatherNet PRO! BBS package you have
received a full set of RIP MENUS and some other assorted display
files that you can use forever or as a temporary set until you
develop your own.
Below you will find a complete set of instructions on how to
manipulate these menus to suit your own needs without purchasing
the RIPaint program and with out using any other RIP program. All
you will need to do this is an straight ASCII text editor such
as DOS's EDIT, QEdit or the equivalent.
WHAT IS RIP?
RIP (Remote Imaging Protocol) scrip is a new way to transmit
graphics to your users based on a Base 36 coding which makes
transmission of files about 3-4 times faster than ANSI.
RIPscrip was developed by Telegrafix Communications, INC and has
taken the BBS community by storm. They have made available, as a
FREEWARE program, the RIPterm program and also are the developers
of RIPaint, the RIP screen development package.
The RIPaint program costs $200.00 (+CA tax if applicable) from
Telegrafix and will allow you to create your own screen or alter
the ones provided to you with your FeatherNet PRO! BBS Package.
WHERE CAN I GET IT RIPaint?
Telegrafix Communications, Inc.
16548 Bolsa Chica #15
Huntington Beach, CA 92649
(714) 379-2131 Voice
(714) 379-2132 Fax
(714) 379-2133 BBS
CHECK - M.O. - C.C.
As a special offer, LinkUSA, the official Support Echo Mail
Network of the FeatherNet PRO! BBS has a special FeatherNet SysOp
deal where you, as a FeatherNet SysOp may purchase the same
RIPaint program through them at a significantly reduced price of
only $159.95 (+5% MA tax if applicable).
LinkUSA - NorthEast Division
P.O. Box 857
Leominster, MA 01453
(508) 537-6554 Voice
(508) 537-0152 Fax
(508) 537-4007 BBS
CASH - CHECK - M.O.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
LinkUSA is also the official support network of FeatherNet
Software. With over 40 echo mail conferences you get a variety
of mail from across the country for your users. You can get an
up to date information packet on LinkUSA by calling 508-537-4007
V32b V42b HST/DS and downloading LINKmmyy.ZIP (i.e.:
LINK1293.ZIP)
There are also a number of third party programs hitting the
streets every day such as Dead Paint, Casket Paint, WinRIP,
WinRIP Utilities, Tombstone and more, I am sure. As these
products become available you will see more and more advances in
RIPscrip and also a fall in prices for the paint programs. You
will also see more and more BBS's using the RIP technology and
competing for the best looking menus.
MANIPULATING RIPSCRIP WITH AN ASCII EDITOR:
You HAVE to have a straight ASCII text editor. You SHOULD have
at least the DEMO copy of RIPaint. With the demo copy of RIPaint
you can load a RIP file and look at it and actually play with it,
but you can not SAVE it! The DEMO version of RIPaint is good for
looking at your changes to make sure that you have done them
correctly though.
If you have the DEMO of RIPaint, boot it up and look at the
default menus provided. All RIP Menus and Files will end in "R".
EXAMPLES: MM - No Color
MMG - ANSI Color
MMR - RIPscrip
It is important to remember that if you have a REGISTERED version
of RIPaint, that the menu's are created to the user as they were
originally drawn, this is to say that if you make a circle on the
bottom of the screen then a square at the top, this is how the
user will see it displayed/redrawn. To further this point, if
you don't like a button the way it was created, change it from
the text editor, NOT RIPaint. The reason for this is, if you
delete a button in RIPaint then make a new one, the user will see
a "hole" where the button would have been until the complete
screen is redrawn/displayed and then it is filled in at the end.
Not pretty.
These are the files that have been provided to you to use. You
MUST rename them if needed to what you call the display file and
place them where you have them configured in FNCFG.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
┌───────┐
│ MENUS │ WHAT
└───────┘ ──────
MMR Main Menu
CMR Message Menu
FMR File Menu
┌──────────┐
│ SUBMENUS │ WHAT
└──────────┘ ──────
QUESR Questionnaire Menu
BLTMR Bulletin Menu
DORMR Doors Menu
CLR Listing of Conferences before Message Menu
┌───────────────┐
│ DISPLAY FILES │ WHAT
└───────────────┘ ──────
PRELOGR File displayed to callers before login
HELLO1R Hello screen to callers
NEWSR News bulletin screen
USRSTATR Users Statistics file
DIR0R Listing of File Areas for Main Conf
PREUPR File displayed before upload
PREDNR File displayed before download
EXPWARNR File displayed to users about to expire
EXPIREDR File displayed to users who have expired
INTROR File displayed when joining a NON-ECHOed conf
F_INTROR File displayed when joining a FidoNet ECHOed conf
L_INTROR File displayed when joining a LinkUSA ECHOed conf
LOGOFFR Goodbye screen.
┌───────────────────┐
│ NON-DISPLAY FILES │ WHAT
└───────────────────┘ ──────
RIP-36 Shows all Base 36 codes
RIP-CMD Shows all RIP commands
FNETICN.ZIP A complete ICONS package for your users to down-
load to use all the RIP MENU and DISPLAY files
that you have here.
┌─────────┐
│ WARNING │
┌──────────────────────────┴─────────┴──────────────────────────┐
│ YOU MUST PROVIDE THE SUPPLIED ICONS TO YOUR USERS IN ORDER TO │
│ USE THESE MENUS AND DISPLAY FILES OR ELSE THEY WILL SEE JUNK │
│ AND YOU WILL GET ALL SORTS OF COMPLAINTS FROM THEM! PLEASE │
│ PUT THIS ICONS FILE, FNETICONS.ZIP, IN WITH YOUR VERSION OF │
│ RIPTERM SO THEY GET THE ICONS AT THE SAME TIME THEY GET RIP- │
│ TERM! YOU PROBABLY SHOULD ALSO LOOK INTO ONE OF THE MANY GOOD │
│ ICON UPDATER DOORS AVAILABLE THAT CAN BE RUN FROM YOUR │
│ $$LOGON.BAT FILE. │
└───────────────────────────────────────────────────────────────┘
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N04
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
┌───────────────────────────────────────────────────────────────┐
│ THESE DISPLAY AND MENUS FILES WERE CREATED WITH RIPAINT V1.54 │
│ AND USERS WILL GET ERRORS IF USING A VERSION OF RIPTERM THAT │
│ IS LOWER THAN 1.54. IF A USER SAYS THAT TEXT IS OVER WRITING │
│ OTHER TEXT, TELL HIM/HER TO GET A NEWER VERSION OF RIPTERM OR │
│ UPDATE THEIR VERSION OF QMODEM PRO/TELIX. │
└───────────────────────────────────────────────────────────────┘
┌────────────┐
│ IMPORTANT! │
└────────────┘
┌───────────────────────────────────────────────────────────────┐
│ THESE SAMPLES MAY VARY FROM WHAT HAS ACTUALLY BEEN PROVIDED │
│ IN THIS RELEASE. AS RIPScrip HAS CHANGED AND FeatherNet PRO! │
│ HAS BEEN DEVELOPED, WE HAVE CONTINUOUSLY UPDATED THE RIP │
│ SCREENS THUS SOME ITEMS MAY BE DIFFERENT IN THE DOCS THAN │
│ WHAT ACTUALLY APPEARS IN THE DEFAULT FILES. THESE SAMPLES ARE │
│ INTENDED AS A GUIDE ONLY! │
└───────────────────────────────────────────────────────────────┘
THIS IS THE MAIN MENU "MMR" in RIPscrip
!|1K|*|Y00000100|1B0000020PVK030F000F080300000F07000000|1U0504HI1
S0000<><>
!|1B0000020PHC030F00080F0100000F07000000|1U0A08HD1O0000<><>|W00|=
00000001
!|1B0000020PVK030F000F080300000F07000000|1U0520HI8W0000<><>
!|1B0000020PHC030F00080F0100000F07000000|1U0A24HD8S0000<><>|c0F|L
0F848R84
!|LH82K9V2K|A8R7O7IA00K|A9V302I500K|L9B309B7O|LH8289128|A912O2I50
0K|L8H2O8H7C
!|A7X7C7IA00K|L7X7S0F7S|S0103|L0F7S0F84|LH828H82K|c08|F8U5B0F|LH8
289128
!|L8H2O8H7C|L0F7S7X7S|L0F7S0F84|A7X7C7IA00K|A912O2I500K
!|1B0000020PHC030F000F080300000F07000000|1U0F88FF8O0000<><>
!|1B0000020PHC030C000F080300000F07000000|1UFK88H88O0000<>SSG'93<>
!|1B0000020PHC0304000F080300000F07000000|1U0F288C2O0000<>M A I N
M E N U<>
!|1U9G7OH8840000<>A U X I L A R Y C O M M A N D S<>
!|1B00000201EE0300000F080300040F07000000
!|1U9L74H37G0000<>Today In History<>TODAY^M
!|1U9L6KH36W0000<>QWK Mail Pick-Up & Drop-Off<>D 1^M
!|1U9L60D76C0000<>Global MSG Read<>*^M|1UDH60H36C0000<>Welcome
File<>W^M
!|1U9L5GD75S0000<>Todays Callers<>T^M|1UDH5GH35S0000<>User
Listing<>U^M
!|1U9L4WD7580000<>Edit Settings<>I^M|1UDH4WH3580000<>Your
Stats<>V^M^M^M
!|1U9L4CD74O0000<>Page Length<>P^M|1UDH4CH34O0000<>Toggle
Color<>S^M
!|1U9L3SD7440000<>HELP FILE<>H^M|1UDH3SH3440000<>Expert
Mode<>X^M|c0F|LH82OH830
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N05
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
!|LH8309G30|LH82O9V2O|A9V302I500G|FBE2V0F|c08|A9V302I500G|LH82O9V
2O
!|1B0000020PHC0300000F080300000F07000000|1U9G34H83K0000<><>|c01
!|@9R2RCONFERENCE:|@9R39TIME LEFT : @TLEFT@|@CF2R@CONFNAME@
!|1B0000020TQU0300000F080300040F07000000|1U0U3000000000FN-
JOIN.ICN<><>J^M
!|1U3M3000000000FN-FILE.ICN<><>F^M|1U693000000000FN-
DOOR.ICN<><>D^M
!|1U0U4O00000000FN-BULL.ICN<><>B^M|1U3M4O00000000FN-
QUES.ICN<><>Q^M
!|1U694O00000000FN-CHAT.ICN<><>n^M|1U0U6C00000000FN-
COMM.ICN<><>C^M
!|1U3M6C00000000FN-PAGE.ICN<><>o^M|1U696C00000000FN-
BYE.ICN<><>G^M|c03
!|Y02000400|@0P44CONFERENCES FILE MENU DOORS
!|@0P5S BULLETINS QUESTIONAIRES NODE CHAT
!|@0K7GLEAVE COMMENT PAGE SYSOP GOODBYE\!|c00|Y00000100
!|@0L8C(C)opyright 1993 FeatherNet Software. (813) 249-8322
Voice Line|c0E
!|Y07000500|@0N08@BBSNAME@|w0012271400|#|#|#
BREAKING IT ALL DOWN
!|1K|*|Y00000100|1B0000020PVK030F000F080300000F07000000|1U0504HI1
^ S0000<><>
|
Resets all graphics and text windows
!|1B0000020PHC030F00080F0100000F07000000|1U0A08HD1O0000<><>|W00|=
^ 00000001
|
Tells RIP that it is the beginning of a COMMAND LINE
!|1B0000020PVK030F000F080300000F07000000|1U0520HI8W0000<><>
^ ^
Plain Button
!|1B0000020PHC030F00080F0100000F07000000|1U0A24HD8S0000<><>|c0F|L
0F848R84
!|LH82K9V2K|A8R7O7IA00K|A9V302I500K|L9B309B7O|LH8289128|A912O2I50
0K|L8H2O8H7C
!|A7X7C7IA00K|L7X7S0F7S|S0103|L0F7S0F84|LH828H82K|c08|F8U5B0F|LH8
289128
!|L8H2O8H7C|L0F7S7X7S|L0F7S0F84|A7X7C7IA00K|A912O2I500K
!|1B0000020PHC030F000F080300000F07000000|1U0F88FF8O0000<><>
!|1B0000020PHC030C000F080300000F07000000|1UFK88H88O0000<>SSG'93<>
^ ^
Plain button with text
!|1B0000020PHC0304000F080300000F07000000|1U0F288C2O0000<>M A I N
M E N U<>
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N06
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
!|1U9G7OH8840000<>A U X I L A R Y C O M M A N D S<>
!|1B00000201EE0300000F080300040F07000000
EDITABLE FIELDS:
!|1U9L74H37G0000<>Today In History<>TODAY^M
!|1U9L6KH36W0000<>QWK Mail Pick-Up & Drop-Off<>D 1^M
!|1U9L60D76C0000<>Global MSG Read<>*^M|1UDH60H36C0000<>Welcome
File<>W^M
!|1U9L5GD75S0000<>Todays Callers<>T^M|1UDH5GH35S0000<>User
Listing<>U^M
!|1U9L4WD7580000<>Edit Settings<>I^M|1UDH4WH3580000<>Your
Stats<>V^M^M^M
!|1U9L4CD74O0000<>Page Length<>P^M|1UDH4CH34O0000<>Toggle
Color<>S^M
!|1U9L3SD7440000<>HELP FILE<>H^M|1UDH3SH3440000<>Expert
Mode<>X^M|c0F|LH82OH830
You may edit the above fields between the <> & <> Marks. You
will notice that the Command is right after the second <> and is
followed by a "^M" which is the command for ENTER.
You could change this line:
!|1U9L6KH36W0000<>QWK Mail Pick-Up & Drop-Off<>D 1^M
To:
!|1U9L6KH36W0000<>Trade Wars 2002!<>D 3^M
Use some caution when redoing buttons as you do not want to make
the text to long or you will over write other buttons and text,
you may in any case go to a smaller text line as we have made all
buttons CENTER the text you insert.
!|LH8309G30|LH82O9V2O|A9V302I500G|FBE2V0F|c08|A9V302I500G|LH82O9V
2O
!|1B0000020PHC0300000F080300000F07000000|1U9G34H83K0000<><>|c01
!|@9R2RCONFERENCE:|@9R39TIME LEFT : @TLEFT@|@CF2R@CONFNAME@
^ ^ ^
Variable Variable
^ = Shows where to start text
You may replace the @CODES shown on any screen with new ones that
suit your tastes. Remember that there is a certain amount of
room and only the number of original lines may be replaced, in
this case, 2 lines.
You could change this from:
!|@9R2RCONFERENCE:|@9R39TIME LEFT : @TIMELEFT@|@CF2R@CONFNAME@
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N07
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
To:
!|@9R2RSecurity :|@9R39Name : @USER@|@CF2R@SECURITY@
!|1B0000020TQU0300000F080300040F07000000|1U0U3000000000FN-
JOIN.ICN<><>J^M
!|1U3M3000000000FN-FILE.ICN<><>F^M|1U693000000000FN-
DOOR.ICN<><>D^M
!|1U0U4O00000000FN-BULL.ICN<><>B^M|1U3M4O00000000FN-
QUES.ICN<><>Q^M
!|1U694O00000000FN-CHAT.ICN<><>n^M|1U0U6C00000000FN-
COMM.ICN<><>C^M
!|1U3M6C00000000FN-PAGE.ICN<><>o^M|1U696C00000000FN-
BYE.ICN<><>G^M|c03
!|Y02000400|@0P44CONFERENCES FILE MENU DOORS
!|@0P5S BULLETINS QUESTIONNAIRES NODE CHAT
!|@0K7GLEAVE COMMENT PAGE SYSOP GOODBYE\!|c00|Y00000100
These fields may NOT be edited unless you have a registered
version of RIPaint or similar RIP painting program as they deal
with specific ICONS of specific sizes. If you decide to play
with them you may destroy or at least make the menu unusable.
┌──────────┐
│ WARNING! │
└──────────┘
Always make a backup copy before you alter ANY RIP screen!
!|@0L8C(C)opyright 1993 FeatherNet Software. (813) 249-8322
Voice Line|c0E
^
You may edit this line to suit your needs.
WARNING: Make sure that it is NO LONGER than it is here!
!|Y07000500|@0N08@BBSNAME@|w0012271400|#|#|#
^ *
^ = Inserts your board's name into the header of the menu.
┌──────────────────────────────┐
│ IMPORTANT FOR RIPAINT OWNERS │
└──────────────────────────────┘
It is important to note here that when you save a file in RIPaint
with the NO TEXT WINDOW OPTION it will just add a; |#|#|# to your
file, you will find that you will need to add a "|w000000000000"
command to make all prompts invisible or a "|w0012271410" to send
the cursor to the Bottom of the screen and not the top where it
will over write your graphics.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N08
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
A FEW NOTES:
As you look at some raw RIP files you may see some misc "\"
symbols in weird spots. These are markers for split command
lines and other purposes.
┌──────────┐
│ WARNING! │
└──────────┘
DO NOT DELETE them.
If an actual "\" is used, it will show up in the raw RIPscrip
text as "\\".
Also included with your FeatherNet BBS software are two files
which will help further your understanding of the raw RIP code,
on is called RIP-CMD, which is a listing of the RIP commands (The
letters that immediately follow the | sign) and the other, RIP-36
is a listing of all the Base 36 structure which RIPscrip is based
on.
THIS IS THE CONFERENCE LISTING MENU "CLR"
!|1K|*|Y07000500|1B0000020PVK030F000F080300000F07000000|1U0504HI8
40000<><>
!|1B00000200LC030C000F080100000F07000000|Y00000100
!|1U0F0CH80O0000<>LinkUSA Conference Menu<>
!|1B00000201DY030F000F080100040F07000000|1U0F0W4B180000<>Main<>0^
M
!|1U0F1G4B1S0000<>Autos<>1^m|1U0F204B2C0000<>BBS Ads<>2^M
!|1U0F2K4B2W0000<>BBS Help<>3^M|1U0F344B3G0000<>Careers<>4^M
!|1U0F3O4B400000<>Chatter<>5^m|1U0F484B4K0000<>Computer Q&A<>6^M
!|1U0F4S4B540000<>Cooking<>7^M|1U0F5C4B5O0000<>Cycles<>8^M
!|1U0F5W4B680000<>Dear SPECTRE<>9^m|1U0F6G4B6S0000<>DOS
Help<>10^M
!|1U0F704B7C0000<>FNet BBS<>11^M|1U0F7K4B7W0000<>Gamers<>12^M
!|1U4Q0W8M180000<>GAP BBS<>13^M|1U4Q1G8M1S0000<>Gripes<>14^M
!|1U4Q208M2C0000<>Hobbies<>15^M|w0010271610|1U4Q2K8M2W0000<>Jobs<
>16^M
!|1U4Q348M3G0000<>Jokes<>17^M|1U4Q3O8M400000<>Law/Legal<>18^M
!|1U4Q488M4K0000<>Modems<>19^M|1U4Q4S8M540000<>Music<>20^M
!|1U4Q5C8M5O0000<>OS/2<>21^M|1U4Q5W8M680000<>PCBoard BBS<>22^M
!|1U4Q6G8M6S0000<>Pets<>23^M|1U4Q708M7C0000<>Politics<>24^M
!|1U4Q7K8M7W0000<>Rehab<>25^M|1U910WCX180000<>Religion<>26^M
!|1U911GCX1S0000<>RIP
Graphics<>27^M|1U9120CX2C0000<>Roots/Genealogy<>28^M
!|1U912KCX2W0000<>R.P.G.<>29^M|1U9134CX3G0000<>SALE<>30^M
!|1U913OCX400000<>Shareware<>31^M|1U9148CX4K0000<>Sports<>32^M
!|1U914SCX540000<>Star Trek<>33^M|1U915CCX5O0000<>SysOps<>34^M
!|1U915WCX680000<>Teens<>35^M|1U916GCX6S0000<>Wildcat\! BBS<>36^M
!|1U9170CX7C0000<>Windows
Help<>37^M|1U917KCX7W0000<>Writers<>38^M
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N09
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
!|1UDC0WH8180000<><>?^M|1UDC1GH81S0000<><>?^M|1UDC20H82C0000<><>?
^M
!|1UDC2KH82W0000<><>?^M|1UDC34H83G0000<><>?^M
!|1B00000200LC030F000F080400000F07000000|1UDC3OH8400000<>ADULTS
ONLY<>
!|1B00000201DY030F000F080400040F07000000|1UDC48H84K0000<>Adults<>
44^M
!|1UDC4SH8540000<>Love Boat<>45^M|1UDC5CH85O0000<>Swingers<>46^M
!|1UDC5WH8680000<><>?^M|1UDC6GH86S0000<><>?^M
!|1B00000200LC030F000F080200000F07000000|1UDC70H87W0000<><>
!|1B00000201EE0300000F080A00040F07000000|1UDM78GY7O0000<>CONTINUE
<>^M
!!|w000000000000|#|#|#
BREAKING IT ALL DOWN
!|1K|*|Y07000500|1B0000020PVK030F000F080300000F07000000|1U0504HI8
40000<><>
!|1B00000200LC030C000F080100000F07000000|Y00000100
!|1U0F0CH80O0000<>LinkUSA Conference Menu<>
^
Plain button, change the name to reflect Local Conferences,
or whatever your EchoMail networks name is.
These CONFR files can be linked together if you need more than
one screen of conference buttons like this;
COPY CONFR CONFR1 ; Edit for first conf screen
COPY CONFR CONFR2 ; " " " " "
(Repeat as needed)
DEL CONFR
(Edit CONF1 accordingly for your first conference screen)
(Edit CONF2 accordingly for your second conference screen)
(Repeat as needed)
COPY CONFR1+CONFR2 CONFR
(This joins the two or more screens together into one)
Make sure to edit the text of the first <>MESSAGE MENU<> prompt
to say <>MORE<> so your users know there is another screen.
!|1B00000201DY030F000F080100040F07000000|1U0F0W4B180000<>Main<>0^
M
!|1U0F1G4B1S0000<>Autos<>1^m|1U0F204B2C0000<>BBS Ads<>2^M
WARNING: You may not have ANY RIP COMMAND LINE over 79
characters!
You may break a Command Line at any "|" (Pipe) symbol as shown
here:
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N10
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
!|1U0F1G4B1S0000<>Autos<>1^m
!|1U0F204B2C0000<>BBS Ads<>2^M
Notice that when the Command line is broken at the "|" you must
insert a "!" at the beginning of the new line to tell RIP that it
is now a Command line.
!|1U0F2K4B2W0000<>BBS Help<>3^M|1U0F344B3G0000<>Careers<>4^M
^ ^ ^ ^
These may be edited with your conference name and command
parameter. ie:
!|1U0F2K4B2W0000<>New Wave<>3^M|1U0F344B3G0000<>Mother's<>17^M
!|1U0F3O4B400000<>Chatter<>5^m|1U0F484B4K0000<>Computer Q&A<>6^M
!|1U0F4S4B540000<>Cooking<>7^M|1U0F5C4B5O0000<>Cycles<>8^M
!|1U0F5W4B680000<>Dear SPECTRE<>9^m|1U0F6G4B6S0000<>DOS
Help<>10^M
!|1U0F704B7C0000<>FNet BBS<>11^M|1U0F7K4B7W0000<>Gamers<>12^M
!|1U4Q0W8M180000<>GAP BBS<>13^M|1U4Q1G8M1S0000<>Gripes<>14^M
!|1U4Q208M2C0000<>Hobbies<>15^M|w0010271610|1U4Q2K8M2W0000<>Jobs<
>16^M
!|1U4Q348M3G0000<>Jokes<>17^M|1U4Q3O8M400000<>Law/Legal<>18^M
!|1U4Q488M4K0000<>Modems<>19^M|1U4Q4S8M540000<>Music<>20^M
!|1U4Q5C8M5O0000<>OS/2<>21^M|1U4Q5W8M680000<>PCBoard BBS<>22^M
!|1U4Q6G8M6S0000<>Pets<>23^M|1U4Q708M7C0000<>Politics<>24^M
!|1U4Q7K8M7W0000<>Rehab<>25^M|1U910WCX180000<>Religion<>26^M
!|1U911GCX1S0000<>RIP
Graphics<>27^M|1U9120CX2C0000<>Roots/Genealogy<>28^M
!|1U912KCX2W0000<>R.P.G.<>29^M|1U9134CX3G0000<>SALE<>30^M
!|1U913OCX400000<>Shareware<>31^M|1U9148CX4K0000<>Sports<>32^M
!|1U914SCX540000<>Star Trek<>33^M|1U915CCX5O0000<>SysOps<>34^M
!|1U915WCX680000<>Teens<>35^M|1U916GCX6S0000<>Wildcat\! BBS<>36^M
^
┌──────┐
│ NOTE │ Note that RIPscrip is saying that this "!" is NOT the
└──────┘ beginning of a Command line but part of the text by
using the SINGLE "\" command in front of it.
!|1U9170CX7C0000<>Windows
Help<>37^M|1U917KCX7W0000<>Writers<>38^M
All the buttons above may be edited. Make sure you put the TEXT
between the two <> and also the command number before the ^M.
(The ^M meaning a carriage return)
!|1UDC0WH8180000<><>?^M|1UDC1GH81S0000<><>?^M|1UDC20H82C0000<><>?
^M
!|1UDC2KH82W0000<><>?^M|1UDC34H83G0000<><>?^M
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N11
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
These are just blank mouse buttons that return a "?" or relist
screen command if pressed. You may edit them to reflect a
conference name and replace the "?" with a Conference Number.
!|1B00000200LC030F000F080400000F07000000|1UDC3OH8400000<>ADULTS
ONLY<>
^
This is a Header button which denotes the following conferences
are for adult's only, you may edit this to say RESTRICTED
or PRIVATE if you prefer.
!|1B00000201DY030F000F080400040F07000000|1UDC48H84K0000<>Adults<>
44^M
!|1UDC4SH8540000<>Love Boat<>45^M|1UDC5CH85O0000<>Swingers<>46^M
!|1UDC5WH8680000<><>?^M|1UDC6GH86S0000<><>?^M
You may edit these as in the previous section.
!|1B00000200LC030F000F080200000F07000000|1UDC70H87W0000<><>
!|1B00000201EE0300000F080A00040F07000000|1UDM78GY7O0000<>MESSAGE
MENU<>^M
^
If you "CHAIN" this menu with more CONFR menu's, change this to
read "MORE" then you -= MUST =- insert, on a BLANK line, the
following command AFTER this line;
!|w000000000000|#|#|#
@WAIT@
If you do NOT insert the @WAIT@ the menus will just keep going
until it hits the Message Menu!
OK, I GIVE UP!:
I have tried to do this and I just can't get it! Everything gets
messed up and I don't have the time, patience or money to buy
RIPaint and learn ANOTHER package... What do I do now?
SOLUTION #1:
Take all the RIP menus and screens off your BBS. This way your
users don't ever see them and then you don't have to worry about
it. If RIP is detected when the caller logs in they will get a
the default RIP ANSI instead.
SOLUTION #2:
Contact another SysOp in your area that has RIP on his/her BBS to
help you and/or give you some tips. They may let you come over
and use their computer and show you where you have erred. There
are also A LOT of SysOps offering to make screens for a profit
advertising in a lot of the echo conferences.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-N12
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX N - Manipulating The Default RIPscrip Screens - Cont.║
╚═══════════════════════════════════════════════════════════════╝
NOTE: The use of Commercial Software on more than one computer
is an infringement of copyrights and is considered PIRACY.
Please do not, under any circumstances "borrow" a copy of
any commercial software for use with a FeatherNet Software
product.
SOLUTION #3:
You can send your "G" screens to FeatherNet Software and we will
custom make them for you. We will not change the looks of the
default menus, but we will change all buttons to reflect your
options. We can also change the BUTTON colors for you.
If you choose this option, we will do this for you at a slight
charge to cover the time it takes our RIP person to make the
changes for you.
MAIN, MESSAGE or FILE MENUS ................. $15.00 ea
CONF LISTING, DOOR, BULLETIN,
or QUESTIONNAIRE MENUS ...................... $10.00 ea
INDIVIDUAL DISPLAY FILES, CONF HEADERS,
FILE AREA HEADERS, ETC. .......................... $ 5.00 ea
(These files may be custom designed to reasonable specifications)
ALL MENUS AND DISPLAY FILES FOR
YOUR BBS USING THE DEFAULT DESIGN ............... $100.00
COMPLETE CUSTOM RIP MENUS TO YOUR SPECS CAN BE QUOTED ON AN
INDIVIDUAL BASIS, IF YOU WOULD LIKE MORE INFO ON ANY OF THESE
SERVICES.
Please Contact BETH at:
FeatherNet Software, Inc.
Graphics Department
(813) 249-8322 [voice]
Monday - Friday 5PM - 9PM
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-O01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX O - Converting from PCBoard ║
╚═══════════════════════════════════════════════════════════════╝
We have received several requests for information on "Converting"
from other BBS packages to the all new FeatherNet PRO! v1.0.
The BBS package that's most easily converted from is Clark Dev-
elopment's PCBoard 14.5 - 15.x.
The biggest fear in converting BBS packages is the loss of the
userbase and filebase. You may rest assured that when convert-
ing from PCBoard to the all new FeatherNet PRO! v1.0, this will
NOT be a problem.
The following pages will cover the necessary steps you will have
to take in order to convert to FeatherNet PRO! v1.0 from PCBoard
14.5 -15.x.
As you go through these steps, you will undoubtedly notice how
similar PCBoard's file structures are to FeatherNet PRO!'s. We
have designed featherNet PRO! to make use of nearly all of the
existing PCBoard utilities on the shareware circuit today. This
means you will not have to register a whole new set of utilities
when setting up your new FeatherNet PRO! system.
With that said, let us move forward and get your files and data
converted.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-O02
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX O - Converting from PCBoard - Conferences ║
╚═══════════════════════════════════════════════════════════════╝
Unfortunately FeatherNet PRO! uses exclusive conference control
files, and will not use PCBoard's CNAMES.@@@ file. You will need
to manually configure all conferences FIRST!
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-O03
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX O - Converting from PCBoard - Userbase ║
╚═══════════════════════════════════════════════════════════════╝
The userbase conversion is basically a 4 step process as follows
1) COPY THE USERS FILE:
PCBoard uses a file called USERS for the user list and
PCBNDX.x for it's user index (where x= A through Z). These
files are normally maintained in the \PCB\MAIN directory.
In FeatherNet PRO! the USERS file's default location is the
\FNET\FNSYS directory while the users indexed files are
located in the \FNET\USERNDX directory.
The main difference in these files are just in the naming.
The USERS file is exactly the same. For FeatherNet PRO!
v1.0, the index files are called FNPNDX.x (where x= A
through Z).
Copy your USERS file from PCBoard to the \FNET\FNSYS dir-
ectory.
EXAMPLE: COPY C:\PCB\MAIN\USERS C:\FNET\FNSYS
2) COPY & RENAME THE PCBNDX.x FILES:
Copy and rename your PCBoard PCBNDX.x files to the
FeatherNet PRO! v1.0 \FNET\USERNDX directory as FNPNDX.x.
This can be performed with one command by following the
example below:
EXAMPLE: COPY C:\PCB\MAIN\PCBNDX.? C:\FNET\USERNDX\FNPNDX.?
NOTE: Substitute the drive letter and directories accord-
ingly.
3) RUN FEXTFIX.EXE
┌────────────┐
│ IMPORTANT! │
└────────────┘
It is "EXTREMELY" important that the "FIRST" function you
perform is to insure that FEXTFIX.EXE is in your \FNET\FNSYS
directory (or the directory that your USERS file is in) and
run it.
You must now change to one of your "Node" directories and
run FeatherNet PRO!'s System Manager program (FNETSM).
3) RUN FNETSM & SORT:
┌────────────┐
│ IMPORTANT! │
└────────────┘
It is "EXTREMELY" important that the "SECOND" function you
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-O04
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX O - Converting from PCBoard - Userbase - Continued ║
╚═══════════════════════════════════════════════════════════════╝
perform at this point is "Sort Your Userbase" (selection [I]
on the FNETSM Main Menu) It makes no difference which method
you select for the sorting, just that you DO "sort". This
creates other necessary files for your userbase.
4) RUN FNCFG & SAVE:
Once this is completed, exit out. You should still be in
the "Node" directory. Run FeatherNet PRO!'s Configuration
program (FNCFG). You only need to enter, then save the
configuration file at this point. This will create/update
the necessary files for your userbase.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-O05
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX O - Converting from PCBoard - Filebase ║
╚═══════════════════════════════════════════════════════════════╝
Like PCBoard, there are three principal files that are used for
maintaining the filebase. One is normally called DIR.LST which
is the list of paths and filenames of the DIRxx files and the
actual directory that the files are located in. The second file
is normally called DLPATH.LST. This file is the paths of all the
directories that contain files that you allow to be downloaded
for that conference. The third is the INDEX file (if used). This
file contains all the paths and names of the files on slow drives
such as CD-ROMS.
NOTE: There ARE differences between the PCBoard and FeatherNet
PRO! files. The DIR.LST file is 66% compatible but the
DLPATH.LST file and INDEX can NOT be used.
Copy the PCBoard DIR.LST file to the area you have configured
for your Main FeatherNet PRO! conference (ie: \FNET\CF0000).
Change to your "Node" directory (ie: \FNET\NODE1) and run FNCFG,
FeatherNet PRO!'s Configuration program.
Select [A] for conference configuration, then the number of the
conference you are setting up (in this case 0 for the Main conf-
erence.
Move down to the Path & Name of List File for Directories and
press <F2>. This will take you into the DIR.LST file for edit-
ing.
You will notice that ALL your DIR paths & filenames are already
there with the Hard Disk Subdirectories.
You will need to enter the 3rd column (SEC header) and set the
minimum security level allowed to download from this file direct-
ory.
Once this is completed, press <ESC> and save your edits.
Move to the Alternate D/L Paths Listing and enter the full path
and filename for a new DLPATH.LST file. Press <F2> to edit the
DLPATH.LST file. Enter all alternate download paths and security
level information. (See DLPATH.LST in the FNCFG section of these
DOCS)
Once this is completed, press <ESC> and save your edits.
If you make use of file INDEXing, you will have to re-INDEX your
drives with FeatherNet PRO!'s BUILDNDX program. For more infor-
mation on this, please see the chapter on BUILDNDX in the SysOp
Utilities section.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-O06
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX 0 - Converting from PCBoard - Doors ║
╚═══════════════════════════════════════════════════════════════╝
PCBoard uses a file called DOORS.LST to control access to all the
doors within each conference.
Copy PCBoard's DOORS.LST to the FeatherNet PRO!'s Main conference
directory (ie: \FNET\CF0000)
EXAMPLE: COPY C:\PCB\MAIN\DOORS.LST C:\FNET\CF0000\DOORS.LST
You "MUST" now edit the DOORS.LST file with a GOOD text editor
(such as SemWare's QEdit) and place a comma "," at the END of
EACH line.
Once you have completed and saved your edits, you will need to
run the conversion program FNPDRCVT.EXE, which is found in the
\FNET (the FeatherNet PRO!'s Main) directory, followed by the
path and filename of the DOORS.LST file.
EXAMPLE: C:\FNET\FNPDRCVT.EXE C:\FNET\CF0000\DOORS.LST
NOTE: Once the conversion program has been used you may delete
this file as it will no longer be needed.
Change to the "Node" directory and run FeatherNet PRO!'s Config-
uration program (FNCFG).
From FNCFG's Main Menu select [A] for conference configuration.
Select the conference you wish to edit (this case the Main BBS,
conference 0).
Move down to the Path & Name of List File for Doors. Enter the
full path and filename for the DOORS.LST file (which should
already exist at this point). Now press <F2> to edit the
DOR.LST file.
You will notice that the ONLY item that needs to be changed is
under the RIP column. This tells FeatherNet PRO! if the door
supports RIP graphics.
Once the RIP column is satisfied, press <ESC> and save your
edits.
NOTE: The conversion functions for files conversion listed above
MUST be performed for "Each" conference that will have
files available within it.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page A-P01
╔═══════════════════════════════════════════════════════════════╗
║ APPENDIX P - Stuffing the keyboard ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! has the ability to stuff the keyboard when
returning from doors and/or external programs. A file called
FNSTUFF.KBD in the node directory will be read and the contents
"STUFFED" into the keyboard to emulate characters being entered
from the users terminal.
An example of where this might be used is when a user is
returning from a callback verifier to the main board. You might
want them to be forced to read a bulletin outlining the rules
and regulations of your BBS. Let's say this is bulletin #3.
In the batch file used to execute the callback verifer, when
returning to the board after execution, you would use a copy
command to copy a .TXT file to a file called FNSTUFF.KBD in the
node's home directory. The contents of this .TXT file would be
"B 3".
EXAMPLE CONTENTS OF A .TXT FILE FOR KEYBOARD STUFFING: B 3
In the example above, this would be what a user would type to
view Bulletin #3.
EXAMPLE VERIFIER BATCH FILE:
@ECHO OFF
CD \FNET\DOORS\VERIFYER
VERIFY VERIFY1.CFG
%FNDRV%
CD %FNDIR%
COPY C:\READBLT3.TXT %FNDRV%%FNDIR%\FNSTUFF.KBD
SFN
In the example above, once the user has returned to the main
board, the system would have copied the contents of the
READBLT3.TXT file to a file in the node's home directory called
FNSTUFF.KBD. This would automatically force "B 3" to be typed
at the main prompt once returned to the BBS, forcing the user to
read bulletin #3.
This is only one possiblity of the powerful keyboard stuffing
function.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page B-001
╔═══════════════════════════════════════════════════════════════╗
║ REGISTRATION ║
╚═══════════════════════════════════════════════════════════════╝
Thousands of hours and tremendous effort have been invested in
FeatherNet PRO! to make it as user-friendly, dependable, and
flexible as possible. If you do choose FeatherNet PRO! as your
BBS package of choice, please show your appreciation for a
quality product by registering it.
To register FeatherNet PRO! and become one of an ever-growing
number of SysOps utilizing this powerful, yet most affordable BBS
package, fill out and mail the licensing agreement found on the
LAST page of this documentation. Registration enables you to
operate 1-250 nodes, up to 1024 conferences, 1024 doors per
conference and removes all delays and UNREGISTERED TEST DRIVE
notices. By registering FeatherNet PRO! you are supporting the
most affordable and "support oriented" marketing system existing
in software today.
REGISTRATION is only 299.99* for the full 250 node version and
includes registration for all utilities included with FeatherNet
PRO!, a quality set of printed DOCS, and 1 years voice and BBS
support.
REGISTRATION is easy! Just fill out the registration form and
send it with your check or money order (US FUNDS ONLY) to;
FeatherNet Software, Inc.
P.O. Box 260666
Tampa, FL 33685-0666
* Plus shipping and handling. Florida residents please add
applicable State and County Sales Tax. All prices are
subject to change without prior notice. Please also note
that there will be a $29.99 fee for returned checks as
applicable under Florida law.
BONUS: The FIRST ONE THOUSAND (1000) Entities that register
FeatherNet PRO! will receive a 1/3 DISCOUNT! That's right
save $100.00! All you have to do to get this DISCOUNT
is follow these simple steps.
Evaluate FeatherNet PRO! and decide you want to register! Call us
voice at (813) 249-8322 and ask for the PRO! BONUS. If you are
within the first 1000 to register you will receive a BONUS
number.
We must receive your completed registration forms within seven
(7) business days to guarantee your BONUS. If not, your BONUS
number will be issued to another entity. If your registration is
received after the seven (7) business days but there are still
bonus slots, you will receive the discount. If all the BONUS
discounts have been taken then you will be notified by U.S. MAIL
stating so with your returned check.
NOTE: Does not include upgrades.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page C-001
╔═══════════════════════════════════════════════════════════════╗
║ SUPPORT ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet Software, Inc. offers some of the most comprehensive
support available to it's users. We offer you advantages that
other small time BBS authors only dream of! Non-registered users
may take advantage of the Unregistered support conference for
questions and answers on the FeatherNet HQ BBS system.
Registered users have the advantage of both Voice and data
support via an expert Technical Support staff here at FeatherNet
Software, Inc.
FeatherNet PRO! voice support number: (813) 249-8322
Monday-Friday 9:00-5:00
Eastern Standard Time
FeatherNet PRO! Support Echo via LinkUSA National EchoNet System.
(For information on LinkUSA download the current LINK????.ZIP
file from the FeatherNet HQ BBS)
Registered users are eligible to carry the FeatherNet Software
Support Echos on their BBS which cover all aspects of BBSing.
(For more information on carrying the FeatherNet Software Echos,
download FN-ECHOS.ZIP from the FeatherNet HQ BBS)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page D-001
╔═══════════════════════════════════════════════════════════════╗
║ UPGRADES ║
╚═══════════════════════════════════════════════════════════════╝
The following is the upgrade schedule for FeatherNet PRO! v1.0.
All upgrades include one (1) year free Technical support as
outlined above. NOTE: This does NOT include free bug fixes.
Upgrading from FeatherNet BBS v4.2 to PRO! v1.0 $50.00 #,@
Bug Fixes x.x"X" FREE
(User downloads from the FeatherNet HQ BBS)
Minor Upgrades x."X"x
(User downloads from the FeatherNet HQ BBS) $20.00 #,@
(FeatherNet Software, Inc. mails upgrade to you) $25.00 #,@
Major Upgrade "X".xx $50.00 #,@
(Upgrade mailed to user with new documentation)
FeatherNet Auto Upgrade Plan (FAUP) $50.00 #,@
(User mailed all minor upgrades to user for one
(1) year FREE of charge)
# - Plus shipping and handling.
@ - Florida residents must add State and County sales tax as
applicable.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page E-001
╔═══════════════════════════════════════════════════════════════╗
║ REGISTRATION AGREEMENT / APPLICATION ║
╚═══════════════════════════════════════════════════════════════╝
Date: ____/____/19____
I, _________________________________, hereby apply for a license
to operate the following FeatherNet Software, Inc. products.
QTY DESCRIPTION PRICE EXTENDED
───── ──────────────────────────────────── ────────── ───────────
[ ] FeatherNet PRO! v1.02 (250 Node) $299.99 ___________
[ ] FeatherNet PRO! v1.02 (250 Node) $199.99* ___________
[ ] FeatherNet PRO! v1.02 (Single Node) $129.00 ___________
* BONUS NUMBER: [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]
[ ] Upgrade from FeatherNet v4.2a $50.00 ___________
[ ] FeatherNet Auto Update Plan (FAUP) $50.00 ___________
[ ] 1 Yr Access to the FeatherNet HQ BBS $35.00 ___________
(FREE w/above)
Add Florida State and County Sales Tax (If applicable)___________
SHIPPING & HANDLING FOR EACH PACKAGE
────────────────────────────────────
[ ] U.S. MAIL or U.P.S. GROUND $ 5.00 ___________
[ ] U.P.S. ORANGE (Third Day) $10.00 ___________
[ ] U.P.S. BLUE (Second Day) $15.00 ___________
[ ] U.P.S. RED (Over Night) $25.00 ___________
Total U.S. Funds submitted ___________
I understand that the registration fee entitles me to free bug
fixes until the next MINOR release and that any bug fixes must be
downloaded at my expense from the FeatherNet HQ BBS.
Furthermore, as a registered SysOp, I understand that I will have
continuous use of the FeatherNet HQ BBS free of charge. It is
agreed that I may choose to subscribe to the FAUP at anytime
during the first year or during an active support period. If I
do not subscribe to the FAUP during an active support period, I
may not do so until I upgrade to the most current version of the
Software.
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page E-002
╔═══════════════════════════════════════════════════════════════╗
║ REGISTRATION AGREEMENT / APPLICATION - Continued ║
╚═══════════════════════════════════════════════════════════════╝
THE FOLLOWING INFORMATION IS MANDATORY TO PROCESS YOUR ORDER.
PLEASE MAKE SURE ALL INFORMATION IS TYPED OR PRINTED CLEARLY AS
SOME INFORMATION IS USED TO PROCESS YOUR FEATHERNET PRO!
REGISTRATION CODE!
______________________________________________________
NAME^
(MUST BE "EXACTLY" AS YOU HAVE IT TYPED IN THE FEATHERNET PRO!
CONFIGURATION)
______________________________________________________
STREET ADDRESS^
______________________________________________________
CITY, ST, ZIP^
DAYTIME PHONE (V) ( ) ______ - ________
EVENING PHONE (V) ( ) ______ - ________
BBS PHONE LINE (D) ( ) ______ - ________
______________________________________________________
BBS NAME^
(MUST BE "EXACTLY" AS YOU HAVE IT TYPED IN THE FEATHERNET PRO!
CONFIGURATION)
5 DIGIT "DEMOG" CODE FOUND IN YOUR README.1ST FILE:
[ ] [ ] [ ] [ ] [ ]
__________________________________
Signed:^
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page F-001
╔═══════════════════════════════════════════════════════════════╗
║ BUG REPORT - Software ║
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! has been tested and retested for "Bugs" by our
Beta Team. However, we all know that this is NOT a perfect
world. There is no way that we could have tested FeatherNet PRO!
under each and every possible hardware/memory configuration.
"Just In Case" of a "Bug", we have included this page to assist
you in "Finding The Answer".
Check the appropriate box below of the area of the BBS that is in
question, followed with the date and time of the .EXE file.
FeatherNet PRO! version:
[ ] FNET.EXE Date: _____________ Time: ___________
[ ] FNCFG.EXE Date: _____________ Time: ___________
[ ] FNETSM.EXE Date: _____________ Time: ___________
[ ] FNFILER.EXE Date: _____________ Time: ___________
The information you furnish to us on these forms will assist us
in helping solve your difficulties. Please respond to each
question (if known) and be as thorough as possible with your
explanations.
If an item's response requires additional space to complete,
please use a separate page that letter (i.e. "Page A").
You may send these pages in any of the following methods:
1) Upload it as a Message or File to the FeatherNet HQ BBS
at the number below:
2) Mail the completed forms to the address listed below:
FeatherNet Software, Inc.
P.O. Box 260666
Tampa, FL 33685-0666
(813) 249-9422 [BBS/Fax]
(813) 249-8322 [Voice]
Describe the nature of the problem. Be specific. If known,
describe the exact sequence of events leading to discovery of
the problem.
________________________________________________________________
________________________________________________________________
________________________________________________________________
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page F-002
╔═══════════════════════════════════════════════════════════════╗
║ BUG REPORT - Software - Continued ║
╚═══════════════════════════════════════════════════════════════╝
We need some information about your computer system. Please
answer all applicable questions:
1) SYSTEMBOARD:
a) Type of System (286/386/486): __________________________
b) Brand of Computer (CLONE/IBM/ZEOS, Etc): _______________
c) Computer Motherboard Manufacturer: _____________________
d) Motherboard BIOS Manufacturer: ________ Version: ______
e) Enter your BIOS Serial #: ______________________________
(Usually displayed on screen during System START-UP).
2) OPERATING SYSTEM / ENVIRONMENT:
a) Operating System - Enter the applicable number or
specify if unlisted:
(1) DOS 3.30 (5) OS/2 v1.x
(2) DOS 4.01 (6) OS/2 v2.0
(3) DOS 5.0 (7) OS/2 v2.1
(4) DOS 6.0 (8) WIN nt v3.1
Enter number from above list or specify if other:_______
b) Running under Desqview (Y/N): ___ Version: ___________
c) Running under Windows (Y/N) : ___ Version: ___________
3) CD-ROM:
a) Using a CD-ROM (Y/N): ___
Manufacturer: _____________________________________
Model: ____________________________________________
d) Using Soundblaster (Y/N): ___
e) Using another Sound Generator (Y/N): ___
Manufacturer: _____________________________________
4) HARD DISK:
a) Model: _________________________________________________
b) Manufacturer: __________________________________________
c) Size (in Megabytes): ___________________________________
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page F-003
╔═══════════════════════════════════════════════════════════════╗
║ BUG REPORT - Software - Continued ║
╚═══════════════════════════════════════════════════════════════╝
5) CONTROLLER:
a) Hard Disk Controller Manufacturer: ____________________
b) Hard Disk Controller Model: ____________________________
6) RAM:
a) Amount of RAM available on your System (in Megs): ______
7) I/O:
a) Manufacturer: __________________________________________
b) Number of Serial Ports available: ______________________
c) Are Non-Std IRQ's & BASE Addresses supported (Y/N): ___
d) Does serial card have 16550 UART(s) installed(Y/N): ___
e) If a Non-Std serial port BASE address or IRQ is used:
Port Base Address (i.e. 03e8) : _______________________
IRQ used by this port (i.e. 4): ________________________
8) VIDEO:
a) Type of Video Adapter (VGA/CGA/MGA/SVGA, etc.): ________
b) Manufacturer: __________________________________________
c) Model: _________________________________________________
d) Memory ([Megabytes] 256k = 1/4 M/B): __________________
9) MODEM:
a) Manufacturer: __________________________________________
b) Model: _________________________________________________
c) Highest Opening Speed Allowed: _________________________
d) Your Opening Speed: _______________ (Set in FNCFG.EXE)
e) Are you LOCKing the port (Y/N): ___ (Set in FNCFG.EXE)
f) Serial Port # you are using: ______ (Set in FNCFG.EXE)
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page F-004
╔═══════════════════════════════════════════════════════════════╗
║ BUG REPORT - Documentation ║
╚═══════════════════════════════════════════════════════════════╝
If you have found any misprints, errors, or incorrect information
in the documentation, we would be gratefully appreciative if you
would let us know. This is not a requirement, only a request.
You may follow the same instructions as found on page 199.
1) Page number: _______
2) Section: _____________________________________________________
3) Brief description: ___________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝
FeatherNet PRO! v1.02 Documentation Page G-001
╔═══════════════════════════════════════════════════════════════╗
║ YOUR NOTES ║
╚═══════════════════════════════════════════════════════════════╝
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
─────────────────────────────────────────────────────────────────
╔═══════════════════════════════════════════════════════════════╗
╚═══════════════════════════════════════════════════════════════╝