home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 15
/
CD_ASCQ_15_070894.iso
/
vrac
/
fnp110a.zip
/
FNP110-B.DOC
< prev
next >
Wrap
Text File
|
1994-05-16
|
217KB
|
4,773 lines
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 80 ║
╚════════════════════════════════════════════════════════════════════════════╝
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:
Insure that your modem is properly installed. If it is an external 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 applicable. The most difficult task is often
finding the correct modem initialization string. As SysOps report their
functioning modem strings, we try to incorporate them in to the MODEMSET modem
setup program. If your modem is not represented in the MODEMSET program and
you have a working string, please, send it to us so that we can include it in
a future update.
BBS FILES:
Insure that FNET.EXE is in your BBS HOME directory (i.e. \FNET) or somewhere
in the DOS PATH and that FNCFG.EXE, FNCHK.EXE, FNETSM.EXE, and FNFILER.EXE are
also in your BBS HOME directory. If you are running the SHAREWARE /10-node
version or a registered multi node version, insure that you have SHARE loaded
before running the BBS. Placing SHARE in your CONFIG.SYS or AUTOEXEC.BAT file
is a good idea. If you are running multi node software, you should also
double check to make sure that all the shared .EXE files in the BBS HOME
directory (FNET.EXE) are READ ONLY.
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: Insure 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 some 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 already have 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, you can then make the modifications to your SFN.BAT to encompass
your front end mailer and reset the option to "Y".
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 81 ║
╚════════════════════════════════════════════════════════════════════════════╝
THE ORDER OF DISPLAY:
When a user logs onto your system the display files shown to them are in a
specific order. This order may include/exclude some files depending on
whether or not they are a new user and whether or not you have specific
security level only files. Notations that start with a * are prompts shown by
the system.
*System Info/Registration Number
*# of the Current Caller
Language List - Available language Prompts the user has to chose from.
Prelog - display file if available
*Users first name
*Users last name
NEW USER Questionaire if new user
*Password
*Bithdate verification - if configured
*Phone number verification - if configured
SEC - display file if available
HELLO1 - HELLO99 - display files if available
NEWS - display file if available and user has not seen it before.
QUOTE - display file if offered
$$LOGIN.BAT - batch file if available.
TODAY - display file, if available.
USERSTAT - display file if configured in FNCFG.
*New BULLETIN prompt. You may configure FEATHERNET PRO! to force users into
the bulletin menu if new bulletins within FNCFG.
*Personal mail waiting prompt. You may configure FEATHERNET PRO! to force
users to read new personal mail from within FNCFG.
Main Menu - display file.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 82 ║
╚════════════════════════════════════════════════════════════════════════════╝
FEATHERNET PRO! - Waiting For Call Screen
Options are selected with the Up/Dn/Left/Right arrow keys and executed the
command by Pressing [ENTER].
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 the BBS name as configured in the
FEATHERNET PRO! configuration editor.
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/TOTAL - The CALLS field show the total number of calls to the system.
CALLS/TODAY - The TODAY field show the total number of calls to the system
since midnight.
NEXT EVENT - The NEXT EVENT field shows how much time until the next event.
NOTE: If there is no event scheduled before midnight this field will show
NONE!
SYSOP MAIL - The SYSOP MAIL field shows if you have unread mail waiting.
DATE - The DATE field shows the current date.
TIME - The TIME field shows the current time as set in your systems internal
clock.
The Current Date and Time are read from your PC's internal clock. All are
here for your convenience.
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:
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 83 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 reference about
what each of the option fields do as you move through them with the arrow
keys.
SYSOP OPTION FIELDS ON THE WAITING FOR CALL SCREEN:
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 information 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
terminal software but will not be answered.
FNFILER - This option takes you into the FNFILER utility. See the FEATHERNET
PRO! Utilities section for more information on this and other utilities
included with your FEATHERNET PRO! package. FNFILER may also be accessed
from 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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 84 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 availability on and
off. This option may also be toggled from within the BBS, with or without a
caller on-line.
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 on-line.
SYSOP OPTION FIELDS FROM THE WAITING FOR CALL SCREEN (NOT SHOWN ON SCREEN):
The waiting For Call Screen (WFC) has a number of ERRORLEVELS built into it
for using SHIFTED F-KEYS. These can be useful for shelling out to another
program like you favorite terminal program or a caller log analyzer utility.
In any case, you may use these ERRORLEVELS as shown here. See your DOS manual
for more information on using ERRORLEVELS in Batch File Programming.
SHIFTED F1 - ERRORLEVEL 84
SHIFTED F2 - ERRORLEVEL 85
SHIFTED F3 - ERRORLEVEL 86
SHIFTED F4 - ERRORLEVEL 87
SHIFTED F5 - ERRORLEVEL 88
SHIFTED F6 - ERRORLEVEL 89
SHIFTED F7 - ERRORLEVEL 90
SHIFTED F8 - ERRORLEVEL 91
SHIFTED F9 - ERRORLEVEL 92
SHIFTED F10 - ERRORLEVEL 93
SYSOP OPTION WHILE A CALLER IS ONLINE:
During normal operation of your BBS, FEATHERNET PRO! continually
scans for SysOp key presses. These functions are listed below.
This screen will be shown if your press F10.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 85 ║
╚════════════════════════════════════════════════════════════════════════════╝
Here are the functions of each function key:
NOTE: ALL <F10> SYSOP FUNCTIONS ARE AVAILABLE FROM WITHIN THE BBS.
<F1> Toggles SysOp Chat Availability.
<F2> Toggles Bell (Beep) Status.
<F3> SysOp Breaks into chat mode to type to a user.
<F4> Quickly LOGOFF the caller, or 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><H> This key combination toggles the 2 line status bar at the bottom of
the sysop's screen scrolling through the current users information.
<Alt><P> This key combination toggles the printer on/off. (If on, prints
caller log output)
<Alt><V> This key combination toggles the sysops screen into and out of 43
line EGA mode. EGA Mode shows only on the local monitor and lets
the sysop view all of the current users information at once.
<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.10 Page 86 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 six (6) other menus plus a number of
other functions which are discussed below provided they have sufficient
security.
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.
The [H] command displays a "Help" file for the main menu commands {MMH.}.
MMH 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 & is defined in FNCFG.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 87 ║
╚════════════════════════════════════════════════════════════════════════════╝
The [HIDE] command toggles STEALTH Mode on and off.
The HIDE command is only operational for those users specifically flags for
using STEALTH Mode by the SysOp in FNETSM on an individual basis. STEALTH
mode is the ability for a user to sign onto the board placing a "/" in front
of thier name and being invisible to all other nodes. Users with STEALTH
technology may also toggle it on or off using the hide command.
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 [L] command allows the user to change the LANGUAGE prompt file.
The user may change from the prompts they chose at login or previously from
the main menu using the "L" command. (ALSO SEE: MKFNTEXT.EXE)
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 directory. 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.
The [P] command allows users to set the 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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 88 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 [QWK] command allows users to go into the QWK Mail Menu.
User may upload a .REP packet or download a .QWK packet. The QWK command is
available from any of the three main menu's, MAIN, FILE, and MESSAGE. Users
may also use the "QWK U" or "QWK D" stacked command to auto start an upload or
download respectively.
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 information and statistics contained in
the display file "USRSTAT". Command is based on user's SECURITY LEVEL & is
defined in FNCFG.
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.10 Page 89 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
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 [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
Logs 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.
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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 90 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 [QWK] command allows users to go into the QWK Mail Menu.
User may upload a .REP packet or download a .QWK packet. The QWK command is
available from any of the three main menu's, MAIN, FILE, and MESSAGE. Users
may also use the "QWK U" or "QWK D" stacked command to auto start an upload or
download respectively.
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.
The [T] command
Allows users to perform a TEXT search in messages. The currently joined
conference or all flagged conferences may be included in this search. If a
user has ANSI capability FeatherNet will HIGHLIGHT the "found" text.
No wildcards (* or ?) 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
message menu area.
"OR" SEARCH: Enter text to search using the "|" operator between the text
strings.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 91 ║
╚════════════════════════════════════════════════════════════════════════════╝
EXAMPLE: COMMAND: S "SEARCH"
SEARCH FOR WHAT TEXT: RON | FEATHER "ron OR feather"
AREAS TO SEARCH? A "ALL"
RESULT: Displays messages in all conferences 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 PIERCE & DAVID PLACE
"SEARCH" "ron pierce AND david place"
RESULT: Displays all messages in the selected conference(s) containing the
text "RON PIERCE" AND the text "DAVID PLACE".
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.
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 is also used by the internal QWK system for which conference
areas will be scanned when building a QWK packet for downloading. This is the
same as the "S" command from within the QWK menu. A user may also use the "S
##" command to start selecting at a particular conference number. This is
useful if only one conference is to be updated. 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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 92 ║
╚════════════════════════════════════════════════════════════════════════════╝
FILE 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.
NOTE: The RIPscrip menus are available anywhere a normal graphics display or
menu file is available and this one was just to show you what a default menu
looked like.
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. 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). Command is based on CONFERENCE SECURITY LEVEL as defined in
FNCFG CONFERENCE SETUP.
The [M] command
Allows the user to go to the MESSAGE MENU of the CURRENT CONFERENCE.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 93 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 authorization 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 [QWK] command allows users to go into the QWK Mail Menu.
User may upload a .REP packet or download a .QWK packet. The QWK command is
available from any of the three main menu's, MAIN, FILE, and MESSAGE. Users
may also use the "QWK U" or "QWK D" stacked command to auto start an upload or
download respectively.
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 & download 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.10 Page 94 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 directories 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.10 Page 95 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 512 Bulletins within EACH and EVERY CONFERENCE for a
maximum of 2,097,152 bulletins within the BBS. From the bulletin menu the user
will have several options to choose from. They 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 bulletins 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.10 Page 96 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 99 Questionnaires in EACH and EVERY CONFERENCE for
a maximum or 405,504 within the BBS. The users have two options from this
menu.
The [#] command
Allows the user to type the number of a questionnaire 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.10 Page 97 ║
╚════════════════════════════════════════════════════════════════════════════╝
QWK MENU
The .QWK Menu allows users to perform a number of functions dealing with
uploading and downloading mail packets to be read offline. The internal QWK
feature is a little different from other menu option as the QWK menu may be
accessed from any of the three major menus, MAIN, FILE, and MESSAGE Menu's.
User may call the QWK menu with any command found on it in a stacked manner,
such as, QWK DG which would perform a QWK Download with immediate logoff after
completion. The following commands are available of the QWK menu.
The [?] command:
The ? will redisplay the QWK display menu.
The [C] command:
The C ommand will bring up the QWK configuration menu. From the configuration
menu users may set up to "only receive messages addressed to them" and/or
whether to "recieve messages addressed to ALL" or not.
The [D] command:
The D command simply allows users to start a download of a QWK packet.
The [DG] command:
The DG command simply allows users to start a download of a QWK packet then
FEATHERNET PRO! will immediately log them off the system.
The [H] command:
The H command will bring up a help menu for the QWK command structure.
The [P] command:
The P command will allow you users to set thier message pointers just like the
L command of the message menu.
The [Q] command:
The Q command will Quit to the previous menu.
The [S] command:
The S command will allow users to set the flags of the conferences they wish
to recieve messages from and also at the same time set the message pointers
for the conferences selected. A user may use the "S ##" command to start
selecting at a particular conference number. (i.e. "S 34" would start the user
at conference number 34)
The [U] command:
The U command simply allows users to start a upload of a REP packet.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 98 ║
╚════════════════════════════════════════════════════════════════════════════╝
The [UG] command:
The UG command simply allows users to start a download of a REP packet then
FEATHERNET PRO! will immediately log them off the system.
The [X] command:
The X command toggle eXpert mode on and off. This simply means the menu is or
is not shown to the user. The user still may get the menu by using the ?
command.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 99 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 1024 DOORS within EACH and EVERY CONFERENCE for a
maximum 4,194,304 of within the BBS.
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.EXE.
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.10 Page 100 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
PC Keyboard and CTRL command processing are available within 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)
Justify Paragraph Ctrl-J Ctrl-J
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
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 communications program is capable
of either sending the actual keystroke (keyboard scan code) or an ANSI escape
code equivalent through to the host system.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 101 ║
╚════════════════════════════════════════════════════════════════════════════╝
An example would be calling in from remote using Telex or QModem to connect to
FEATHERNET PRO! If utilizing 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 Sending Data". 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.10 Page 102 ║
╚════════════════════════════════════════════════════════════════════════════╝
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).
A Sample SFN.BAT;
@ECHO OFF
CLS
SET NODE=1
ECHO SETTING UP NODE #%NODE%
SET FNDRV=D:
SET FNDIR=\FNET\NODE%NODE%
SET DSZLOG=%FNDRV%%FNDIR%\DSZLOG
:BEGIN
%FNDRV%
CD %FNDIR%
FNET.EXE %1 %2
IF ERRORLEVEL 255 GOTO DoMail
IF ERRORLEVEL 254 GOTO Fax
IF ERRORLEVEL 93 GOTO F10
IF ERRORLEVEL 92 GOTO F9
IF ERRORLEVEL 91 GOTO F8
IF ERRORLEVEL 90 GOTO F7
IF ERRORLEVEL 89 GOTO F6
IF ERRORLEVEL 88 GOTO F5
IF ERRORLEVEL 87 GOTO F4
IF ERRORLEVEL 86 GOTO F3
IF ERRORLEVEL 85 GOTO F2
IF ERRORLEVEL 84 GOTO F1
IF ERRORLEVEL 3 GOTO ReStart
IF ERRORLEVEL 2 GOTO End3
IF ERRORLEVEL 1 GOTO End2
IF EXIST EVENT.BAT CALL EVENT.BAT
IF EXIST DOOR.BAT DOOR.BAT
(Continued next Page)
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 103 ║
╚════════════════════════════════════════════════════════════════════════════╝
ECHO RETURNING TO FEATHERNET
SFN.BAT
:DoMail
GOTO BEGIN
:Fax
GOTO BEGIN
:F10
GOTO BEGIN
:(F9-F1 same as F10)
:ReStart
GOTO Begin
:End2
ECHO OFF
IF EXIST DOOR.BAT DEL DOOR.BAT
CLS
ECHO FeatherNet Terminated!
ECHO Have a Nice Day!
:End3
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 104 ║
╚════════════════════════════════════════════════════════════════════════════╝
BATCH FILES - FNP*.BAT
The FNP*.BAT files are what FEATHERNET PRO! uses to archive
messages for downloading when a user requests it from the QWK
Menu. These "MUST" be located in the MAIN BBS Directory
(typically \FNET).
FNPQWK
FNPQWK handles the archiving of QWK packets in the archive format
the user choses.
@echo off
IF %1 == Z PKZIP -ex -a %3 %2
IF %1 == J ARJ a -y %3 %2
IF %1 == L LHA a /m %3 %2
IF %1 == A pkPAK -a %3 %2
:END
%FNDRV%
CD %FNDIR%
FNPREP
FNPREP handles the unarchiving of received REP packets in the
archive format the user choses.
@echo off
IF %1 == Z PKUNZIP -o %2
IF %1 == J ARJ e -y %2
IF %1 == L LHA e /m %2
IF %1 == A PKUNPAK -r %2
:END
%FNDRV%
CD %FNDIR%
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 105 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
NOTE: This batch file assumes that when you set up ULTester that your ULTester
configuration files are named "ULT1.CFG", "ULT2.CFG" etc. and correspond to
node1, node2, etc.
REM ---------- FNETTEST.BAT ----------
@ECHO OFF
%FNDRV%
CD\FNET\ULT
ULTESTER ULT%NODE%.CFG %1 %2 %3 %4
%FNDRV%
CD %FNDIR%
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 106 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 ALL .EXE FILES IN YOUR \FNET DIRECTORY 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 of 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 (i.e.: \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.
SRCONFIG - MUST BE IN EACH NODE DIRECTORY
FN.PTR
FNET.IMG
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 such as log file information.
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!
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.10 Page 107 ║
╚════════════════════════════════════════════════════════════════════════════╝
Edit your SFN.BAT file as follows;
@ECHO OFF
CLS
---------- EDIT THIS PART ----------
REM SET NODE=1 REM THIS OUT!
SET NODE=%1
---------- END EDIT ----------
ECHO SETTING UP NODE #%NODE%
SET FNDRV=D:
SET FNDIR=\FNET\NODE%NODE%
SET DSZLOG=%FNDRV%%FNDIR%\DSZLOG
%FNDRV%
CD %FNDIR%
:BEGIN
FNET.EXE
IF ERRORLEVEL 255 GOTO DoMail
IF ERRORLEVEL 254 GOTO Fax
--- CUT FOR BREVITY - SEE SFN.BAT FOR MORE DETAILS ON THE SFN.BAT FILE ---
Now when you start FEATHERNET PRO! from your node directory, simply include
the node number as a parameter!
Example: SFN 3 Will start FEATHERNET PRO! as node3 assuming it has a node 3
configured. SFN 234 Will Start FEATHERNET PRO! as node 234 assuming it has a
node 234 configured.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 108 ║
╚════════════════════════════════════════════════════════════════════════════╝
BATCH FILES - Tips & Other 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
information 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". Make sure that RECORD ONE of FNETSM matches
EXACTLY the name in the FNCFG SysOp's Name field!
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. If modemset does not
have your modem init string in it, call us, we may have one for you. If you
have a working string that is not listed, leave a message with it so we can
support your modem.
Tips
If you have any trouble getting FEATHERNET PRO! running, run "FNCFG.EXE".
Insure ALL items are edited/verified. Then SAVE the setup. You may also want
to get the program SFLCHK from the FeatherNet HQ BBS and run it. This program
will check all the paths specified in your SRCONFIG file and make sure the
files are, in reality, there.
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".
Double check the paths in "SFN.BAT" and the other ".BAT" files which are
included. Insure they are correct for your system setup.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 109 ║
╚════════════════════════════════════════════════════════════════════════════╝
If you have extended or expanded memory available, a virtual (RAM) disk setup
as your "WORK" directory will increase performance 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 stated above, if you have extended or expanded memory
available, install a disk cache sucha as SMARTDRV.EXE or PC-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 initialized 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 such as comm port information etc.
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 but we will try when time and knowledge allow us to.
Tips
Please contact the authors of third party programs before calling FeatherNet
Technical Support with questions about them and setting them up. Your
cooperation is most appreciated in this matter. We can only supply limited
support in this matter and most likely only on the FEATHERNET PRO! side of
integration.
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.
Insure that your modem initialization string TURNS ON DTR and ENABLES hardware
flow control.
Insure that your modem initialization string DISABLES AUTO ANSWER.
FEATHERNET PRO! handles the ring detect and gives the "ATA" answer command to
the modem.
Note: You should ensure the comm port speed (baud rate) in use when the
modem configuration is written to NVRAM with MODEMSET.EXE (or manually
with a terminal program) is the port opening speed you specify in
FNCFG's Modem/Node/Subscription configuration speed.
Likewise, if using a FOSSIL driver, the fossil driver *must* be LOCKED
at this speed.
If this is not done, the bbs may not answer calls. Call FeatherNet
Technical Support at (813) 249-8322 if you encounter problems with
your modem NOT answering calls and linking correctly.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 110 ║
╚════════════════════════════════════════════════════════════════════════════╝
The following files should be obtained by you and placed somewhere in your
PATH. FEATHERNET PRO! uses these files for file transfer functions and
archive manipulations. Each of these files are SHAREWARE and you should takes
steps to register them and support the authors of these programs if used.
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
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 111 ║
╚════════════════════════════════════════════════════════════════════════════╝
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. One
more possible reason you may get an ERROR #76 is that the BBS is trying to
access a file that is not in the proper place, has been marked "READ ONLY", or
does not exist. This is particularly true with DATA files and LOG files.
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.10 Page 112 ║
╚════════════════════════════════════════════════════════════════════════════╝
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, FNPACK a message base packer, FN-NET a message pointer update utility
for echo mail conferences and the internal QWK processor, ULTester, an upload
processor and Virus checker, 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 who charge upwards of $100 extra for
message and file utils, and then add a third party Upload checker ($45.00) and
maybe a QWK Mail door ($35.00), 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.10 Page 113 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNETSM - FEATHERNET PRO!'s System Manager
Like most other FEATHERNET PRO! utilities (FNCFG, FN-NET, etc.) FNETSM must be
run from a node "Home" directory.
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.
FNETSM - 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 financial for
you, and allow you to manage each user on an individual level.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 114 ║
╚════════════════════════════════════════════════════════════════════════════╝
Below are explanations on each items you may encounter:
<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 registration 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.
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 bulletin 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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 115 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 new user 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
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. (SysOp Screen Has 1 More Status Line Than The
Users Screen. 1 Line Scroll Locally Is Normal.)
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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 116 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
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.
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 configuration setup. (FNCFG.EXE)
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 117 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 118 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
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.
STEALTH:
Allow user to use STEALTH MODE. Entering a "Y" here will allow this user to
enter the BBS in STEALTH mode. This may be done by placing a / (forward
slash) before their name when logging on or using the HIDE command from the
main menu to toggle STEALTH on or off. When in STEALTH mode the user will be
STEALTHed from all other users on the system. When a node status is displayed
it will not show who is on the STEALTHed node. Placing a "N" here will
disable this function for this user.
SUBSCRIPTION MODE:
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.
Press <ALT><F> for the users financial record screen.
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.
AMOUNT TO DEBIT (SysOp Edit):
Allows the SysOp to make corrections and/or deduct monies recieved from the
total amount. Will be added to the monies used column.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 119 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
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.
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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 120 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONFERENCE FLAGGING
Press <ALT M> for users conference registration screen.
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 conference. 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 privileges. 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.
LISTING USERS
MISC. NOTES: When entering USER EDIT you will be presented with a listing of
users, you may scroll through this list and PRESS ENTER to edit that users
record which is highlighted. You can also get this user listing when exiting
from any of the four previous areas, User Edit Screen 1 or 2, Conference
Registration Screen, or the User Financial Page, you will be brought to a
screen that asks if you want to Quit to the menu or get a USER LISTING. The
USER LISTING will give you a brief list of current users, city and state where
they are from, their security level, and the last call date.
FNETSM - 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.10 Page 121 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNETSM - Pack Users File Base
[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).
FNETSM - 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.
FNETSM - 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
configuration editor, but only in the name you give the physical file.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 122 ║
╚════════════════════════════════════════════════════════════════════════════╝
FEATHERNET PRO! will allow you to use one @Xcode or ANSI 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.
FNETSM - System Configuration (FNCFG)
[F] SYSTEM CONFIGURATION (FNCFG): This calls and allows you to work in the
FEATHERNET PRO! configuration editor and returns you here when you leave
FNCFG.
FNETSM - 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.
FNETSM - 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.
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 accidentally delete a user and need to re-enter
their information into the system by hand.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 123 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNETSM - Sort User Records
[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 password 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
utilities included in the FEATHERNET PRO! package!
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
[J] Last Date Called - Sort by Date Users Last called.
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.
FNETSM - 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.10 Page 124 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNETSM - 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 respectively.
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.10 Page 125 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNFILER - 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 listing file
(DIRxx) and [V]iew files within archives, view GIF and PCX files, import files
from your sub directories and auto search them for FILE_ID.DIZ's and build a
DIRxx file automatically, show you which files are missing from the disk and
read text.
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 preference in DIRxx handling. See the section a
little later on about editing the FNFILER defaults.
[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.
FNFILER - Edit
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>.
FNFILER - 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>.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 126 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNFILER will now bring you into the FNFILER editor screen and load the DIRxx
file for that file directory, if it exists.
FNFILER - DIR File Editing Key Controls
From the FNFILER editor you can perform just about any manipulation you could
hope for. Below some of these are discussed in detail. When the FNFILER
editor loads you will the first description 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 following
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 & description currently displayed
<F4> Copy - Toggle copy flag for file &description 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> Down - Go back one record
<PgDn> 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
<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
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 127 ║
╚════════════════════════════════════════════════════════════════════════════╝
<Shift F1>
<Shift F2>
<Shift F3>
<Shift F4>
<Shift F5> Shift F1-10 and CTRL F1-F10 Are used for Line Drawing Within Your
<Shift F6> DIRxx file. Please see the "F1" Help in FNFILER for the Exact
<Shift F7> Functions of these keys.
<Shift F8>
<Shift F9>
<Shift F10>
<Ctl F1>
<Ctl F2>
<Ctl F3>
<Ctl F4>
<Ctl F5> Shift F1-10 and CTRL F1-F10 Are used for Line Drawing Within Your
<Ctl F6> DIRxx file. Please see the "F1" Help in FNFILER for the Exact
<Ctl F7> Functions of these keys.
<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
You will also notice that an "L" is sometimes placed in the FNFILER "EDIT"
screen header. This means that the file you are currently using can not be
located in the specified directory. Double check you physical file location.
(Note: If you are using a CD-ROM drive and INDEX files then this is acceptable
and the file will be found by a user looking for it.)
FNFILER will, if you wish, import all files in the directory you chose that
are not listed in the DIRxx file. Upon doing this it will check for
FILE_ID.DIZ files within each archive found. If found, the FILE_ID.DIZ
discription will be imported automatically into the DIRxx file. If a
FILE_ID.DIZ can not be located then a "No Discription Available" is placed in
the discription area.
If a discription can not be found within an archive, you may look for one with
the View Command. The view command will allow you to open the archive and
read a TEXT (ASCII) file within to acertain the files purpose. A GIF/PCX
viewer can also be added to your defaults to allow you to view a picture type
file and then add a discription based on what you see.
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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 128 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
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 processing 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.
Path and Name of Archive utility: Enter the path and name of your favorite
Archive utility such as SHEZ. The archive utility MUST be able to accept a
path and file name as a parameter to be compatible.
Path and name of Graphics Viewer utility: Enter the path and name of your
favorite graphics viewer such as VPIC. The graphics viewing utility you chose
must be able to accept a path and file name as a parameter to be compatible.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 129 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNFILER COMMAND LINE OPTIONS
As many SysOps like to do file mantainence during nightly events we have built
into FEATHERNET PRO!'s FNFILER utility a few commands that are much in demand.
Among these are the ability to SORT your DIRxx files and an option to create
an ALLFILES listing. Additional configuration settings are available to allow
unique sort parameters for the public and private upload DIR files. The all
other DIR files will be sorted in the mode specified for the DIR files.
The command line FNFILER expects for sorting the dir files of a conference is:
FNFILER /SORT 0-4,10
The above command line will cause FNFILER to sort all the DIR files in
conferences 0 through 4 and conference 10. Separate each non-inclusive
conference with a COMMA as is done in the sample above.
To create an ALLFILES list use a command line:
FNFILER /LIST E:\FREE\ALLFILES 0,1
This would create an allfiles list named "E:\FREE\ALLFILES" for the DIR files
of conferences 0 and 1.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 130 ║
╚════════════════════════════════════════════════════════════════════════════╝
MKFNTEXT - 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. This program will let you create you LANGUAGE FILES to
be chosen by your users when logging on or at the MAIN menu with the "L"
command.
The command line to activate this utility is: MKFNTEXT [prompt filename]
EXAMPLE: MKFNTEXT FNETTEXT or MKFNTEXT FNETTEXT.ext
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 default prompt
file. At any time you may restore defaults to the original FEATHERNET PRO!
prompts by pressing the <F1> or <F4> keys.
MOST any prompt may be re-directed to a DISPLAY file. To do this, simply
remove the default prompt from the edit box and replace it with a "%"
redirection command followed with the path and filename of the file you wish
to display.
Example: After remove the prompt "NO MAIL WAITING" you could then place a
"%C:\FNET\DISP\NOMAIL" which could contain a larger ANSI display stating that
the users mail box was empty.
NOTE: SOME PROMPT FILES CONTAIN DATA FIELDS USED BY FEATHERNET PRO! You must
be very careful when editing these fields or format fields, make sure to
thoroughly check all changes before users re-enter the BBS!
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 131 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNCHK - 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" has 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.10 Page 132 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.10 Page 133 ║
╚════════════════════════════════════════════════════════════════════════════╝
ULTESTER - Upload Processing & Virus Checker
ULTester will test archives for integrity, Scan for virus' using any scan
utility, such as McAfees SCAN.EXE (or other quality virus detection utility),
and will optionally test your GIF files for integrity and ensure files meet
your age requirements.
Among some of the major features of this product we draw your attention to the
following;
FEATURES
* Identifies and processes all ZIP, ARJ, LHA, GIF and TD0 files regardless of
the actual file extension. This includes self-Extracting archives.
* Supports the use of FILE-ID.DIZ and DESC.SDI description files in an
archive. ULTester will replace the description with the contents of
FILE_ID.DIZ or DESC.SDI respectively.
* Moves all Virus Infected programs into a Virus Holding directory the Sysop
has defined.
* Will save descriptions of rejected files in the current conf.'s PRIVATE
upload description file.
* Will delete all files names located in a text file if those names appear in
the archive.
* Optionally will test GIF and TD0 files for integrity using the file tester
available for Teledisk'd files (TDCHECK.EXE). GIF testing is performed
internally.
* Optionally Inserts the number of files in the archive, OLDest file date and
NEWest file date into the file description. Adds .GIF resolution to .GIF
file descriptions (on the 1st line if possible or last line/new line).
* ULTester will optionally SWAP itself to EMS, XMS or DISK when running the
archive and swap utilities to make as much room as possible available for
these programs. When swapped, ULTester will leave a 2k Kernel in DOS Ram.
* Includes an easy to use and informative configuration program. (ULTCFG.EXE)
* Allows the SysOp to append a 7 line display file to the bottom of the
ULTester caller display information screen.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 134 ║
╚════════════════════════════════════════════════════════════════════════════╝
SETTING UP ULTester
ULTester will test archives for integrity, Scan for viruses using McAfee's
SCAN.EXE or other quality virus scanner, optionally test .GIF files for
integrity and ensure files meet your age requirements, among other things
which were listed above.
When running ULTCFG.EXE the file "ULTCFG.HLP" should be in one of two
locations:
(1) In the Directory from which ULTCFG.EXE was started
(2) In the directory in which the .CFG file resides or will be created
You must include a complete path and name to the .CFG file when starting
ULTCFG.EXE.
Example: Say I am in the C:\FNET directory. My ULTCFG.HLP file happens to be
in the C:\ULT directory. A normal command-line to run ULTCFG and create or
re-edit the .CFG file named "ULT1.CFG" would be:
ULTCFG C:\ULT\ULT1.CFG
Remember that ULTCFG.HLP must be in either the directory where the .CFG file
is located or in the directory from which you run ULTCFG.EXE.
ULTCFG has complete built in HELP files accessed by pressing the F1 key.
Since all information is provided with the F1 Help files we will not go into
the configuration options in these docs. You will find that the information
provided in the F1 help files will assist you in getting each item configured,
with a minimal amount of brain damage.
1: Run "ULTCFG.EXE" to create a configuration file. ULTCFG will edit an
existing configuration file.
Enter: "ULTCFG <CONFIG FILE NAME> to start ULTCFG.EXE.
It DOES NOT DEFAULT to ANY file name.
Example: ULTCFG ULT1.CFG
See the following section on Configuring ULTCFG
2: Make sure that your FNETTEST.BAT files is properly configured. A sample
FNETTEST.BAT file is shown here. It is assumed that you have set the NODE
environment variable; SET NODE=# where "#"=the node currently operating, in
your BBS' start up batch file.
@ECHO OFF
C:
CD \FNET\ULT
ULTESTER ULT%NODE%.CFG %1 %2 %3 %4
C:
CD\FNET
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 135 ║
╚════════════════════════════════════════════════════════════════════════════╝
3: ULTester reads the configuration file (ULT1.CFG in the above samples) and
determines the node directory where SRCONFIG is located and retrieves all
necessary information.
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
The files in the WORK directory specified for ULTester in the configuration
file for ULTester are ALL DELETED. Insure this WORK DIRECTORY is ONLY used by
ULTester. The BBS work directory MUST NOT be specified as the ULTester work
directory. Additionally, the ULTester WORK directory may have recursed
sub-directoried created during file extraction and scanning. These
sub-directories and the ULTester work directory are all KILLED by ULTester
prior to its termination. Then the ULTester work directory is recreated.
4: If you *DO NOT* allow a particular archive format or want to just restrict
acceptable uploads to a particular archive format use the "Y" or "N" as
indicated above to ALLOW or NOT ALLOW an archive type.
5: All extensions or archive formats NOT ALLOWED will be tested if they are in
a supported archive format.
6: All files - allowed or not - are SCANNED for Virus infection.
7: Files found having virus are moved to the Virus hold directory.
8: Files not allowed are moved to the holding directory specified in the
configuration program for ULTester.
9: The swap to EMS/XMS/Disk works fine with ULTester for users of MS/PC-DOS
and OS/2. If you have enough memory you do not need to Swap ULTester.
10: ULTester requires about 65k of ram when running.
11: It is recommended you make a separate directory for ULTester to be run
from.
12: Each BBS node *MUST* have a separate configuration file and work
directory.
13: Insure you rectify any missing file warnings received when running ULTCFG.
14: For local operation outside the BBS use the normal command line syntax
followed by " /L":
Example: ULTESTER ULT1.CFG C:\TEMP\TEST.ZIP TEST C:\FNET\UPDESC.1 /L
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 136 ║
╚════════════════════════════════════════════════════════════════════════════╝
SETTING UP ULTCFG
Configuring ULT is basically a straight forward proceedure. In a future
version this will be incorporated into the FNCFG proceedure but for now it is
external. We will go step by step through the questions within ULTCFG and
tell you what they mean.
ENTER: ULTCFG ULT#.CFG (Where # is the node number of the configuration file
you are editing)
ENTER THE SYSOP'S (YOUR) NAME
Enter your name here.
ENTER THE BBS NODE DIRECTORY PATH
This is the directory where the SRCONFIG file is located. Example Directory:
C:\FNET\NODE1
ENTER A "WORK" DIRECTORY FOR ULTESTER
This MUST be a unique directory which is use by no other program. The files
ULTESTER places in this WORK directory are routinely deleted. It MUST NOT be
the work directory for FEATHERNET PRO! BBS! The WORK directory path/name
"MUST" be at least 5 characters in length and MUST be in the format
"C:\WORKDIR" or "C:\FNET\ULT\WORK1".
NOTE: If running more than one node EACH node MUST have a separate WORK
directory. SAMPLE Work Directory: C:\FNET\ULT\WORK or C:\FNET\ULT\WORK3
ENTER THE HOLD DIRECTORY FOR REJECTED FILES THAT ARE "NOT" VIRUSED
This should be the same as the FEATHERNET PRO! holding directory in order for
aborted uploads to be resumed. Example Hold Directory: C:\FNET\FILES\HOLD
ENTER A "HOLD" DIRECTORY FOR VIRUSED FILES
This directory should "NOT" be the same as the HOLD directory for other
rejected files. Example Virus Hold Directory: C:\FNET\ULT\VIRUSED
ENTER THE DOS PATH WHERE PKZIP.EXE AND PKUNZIP.EXE ARE LOCATED
Enter ONLY THE PATH and NOT the complete path and filename. Example archive
directory path: C:\UTIL\
ENTER A "Y" IF YOU "WILL" ACCEPT FILES COMPRESSED WITH PKZIP.EXE
Enter an "N" if you do not want to accept these files. All PKZIP archived
files will be tested and scanned prior to being moved to the appropriate HOLD
directory if you do not want to accept files of this archive format. NOTE:
Self- extracting PKZIP archives which have the .EXE file extensions are also
tested and scanned.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 137 ║
╚════════════════════════════════════════════════════════════════════════════╝
ENTER THE DOS PATH WHERE THE FILE LHA.EXE IS LOCATED
Enter ONLY THE PATH and NOT the complete path and filename. Example archive
directory path: C:\UTIL\
ENTER A "Y" IF YOU WILL ACCEPT FILES COMPRESSED WITH LHA.EXE
Enter an "N" if you do not want to accept these files. All LHA archive files
will be tested and scanned prior to being moved to the appropriate HOLD
directory if you do not want to accept files of this archive format. NOTE:
Self-extracting LHA archives which have the "EXE" extensions are also tested
and scanned.
ENTER THE DOS PATH WHERE THE FILE ARJ.EXE IS LOCATED
Enter ONLY THE PATH and NOT the complete path and name of the file. Example
archive directory path: C:\UTIL\
ENTER A "Y" IF YOU WILL ACCEPT FILES COMPRESSED WITH ARJ.EXE
"N" if you do not want to accept these files. All ARJ archive files will be
tested and scanned prior to being moved to the appropriate HOLD directory if
you do not want to accept files of this archive format. Example archive
directory path: C:\UTIL\
ENTER A "Y" IF YOU WILL ACCEPT GIF UPLOADS
All ".GIF" files will be tested prior to being moved to the appropriate "HOLD"
directory if you do not desire to accept GIF files. NOTE: Your .GIF test
program must return a DOS ERRORLEVEL if a GIF file is corrupt.
ENTER THE PATH AND NAME OF YOUR TDCHECK FILE
You MUST enter the COMPLETE PATH AND NAME of the TDCHECK program! Leave this
line blank if you do NOT want to test uploads created using the TELEDISK
program. Example path and filename: C:\UTIL\TDCHECK.EXE
ENTER A "Y" IF YOU WILL ACCEPT TELEDISK UPLOADS (.TD0)
NOTE: All .TD0 files will be tested and moved to the appropriate HOLD
directory if you do not desire to accept these files.
ENTER THE COMPLETE PATH AND FILENAME OF YOUR VIRUS SCAN UTILITY
It doesn't matter which scan utility you use as long as it is a quality virus
detection scanning utility. Example scan path and filename: C:\UTIL\SCAN.EXE
ENTER THE COMMAND LINE PARAMETERS TO USE WITH YOUR VIRUS SCANNER
You must enter /NOPAUSE /NOEXPIRE /NOBEEP to prevent SCAN.EXE from waiting
for a local keyboard response if your SCAN.EXE is outdated or for some other
reason a keypress is required.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 138 ║
╚════════════════════════════════════════════════════════════════════════════╝
ENTER A "Y" IF YOU WANT TO SWAP TO EMS, XMS OR DISK WHEN TESTING
ULTESTER uses about 80k of ram. Some archive utilities use 300k of ram when
in the archive mode. If your memory situation is critical and you have enough
EMS or XMS available, it is recommended that you DO SWAP testing uploads. IF
you do not have EMS or XMS, you can swap to disk which only takes a couple of
seconds when testing archives. The exact SWAP method used is determined by
ULTESTER.
ENTER THE OLDEST FILE YOU WILL ACCEPT IN DAYS
All files within an uploaded archive are examined for the date stamp. If ANY
file has a date stamp OLDER than the number of days you enter the OVERAGE file
count is incremented. If the percentage of OVERAGED files is greater than the
number you specify in the configuration item below, the uploaded file is
rejected. These files WILL still be scanned for virus. The maximum number of
days allowed is 9999. Example entry: 180 In this example, all files more than
180 days will be added to the OVERAGE count.
ENTER THE MAXIMUM % OF OLDER FILES IN AN ARCHIVE YOU "WILL" ACCEPT
For example, if 730 (two years) is your old age limit and the uploaded archive
has 20 files and you allow 20% of them to exceed the old age restraints, then
no more than 4 files in the archive can be older than 199001.
ENTER "Y" TO ACCEPT FILES OTHER THAN THE ARCHIVE FORMATS SUPPORTED
If you answer "Y" to the above question, files which are not of the archive
formats supported (ARJ, GIF, LHA, TD0 or ZIP ) would be Passed and Scanned
only. This will allow any file extension to be uploaded to your BBS. Enter
an "N" to restrict uploads to the archive formats you have chosen earlier in
the configuration.
ENTER THE PATH AND FILENAME OF A FILE YOU WANT TO ADD TO UPLOADS
This may be an Advertisement for your BBS or any file you desire for that
matter. Leave this line blank if NO file is to be added to the new archive.
Example: C:\FNET\ULT\MYBBS.COM
ENTER THE COMPLETE PATH AND FILENAME OF A THE FILE WHICH CONTAINS THE NAMES
OF FILES YOU WISH TO BE "DELETED" FROM ANY ARCHIVES UPLOADED TO YOUR SYSTEM.
This MUST be a text file with only one name per line in UPPER CASE. This is
convenient for deleting unwanted BBS ads and other "NUISANCE" files. Leave
blank if no files are to be deleted. Example: C:\FNET\ULT\BADFILES.LST
ENTER THE SERIAL PORT ADDRESS TO USE
If you will be using the "STANDARD" Port Address for COM Ports 1 or 2 then you
may skip this question. Examples: &h3F8 or &h2F8
ENTER THE IRQ NUMBER YOUR COM PORT WILL USE
If you will be using a "STANDARD" IRQ for COM ports 1 or 2 then you may skip
this question. Example: 4 (for COM Port #1)
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 139 ║
╚════════════════════════════════════════════════════════════════════════════╝
SERIAL DRIVER SELECTION
Enter the serial driver mode you desire to use. Selections available are (A)
ASYNC, (F) FOSSIL and (M) Intelligent DigiBoard. Normally ASYNC will be
selected. FOSSIL could be selected in situations where an ASYNC driver might
have problems such as under a software multitasker such as DESQview. You must
have a FOSSIL DRIVER such as X00 or BNU loaded if you select (F). You MUST
have a DigiBoard Intelligent MultiPort Board to utilize the "M" option.
ENTER "Y" IF YOU WANT TO "CREATE" AND ADD A FILE_ID.DIZ FILE
If you select "Y", ULTESTER will use the description the user entered for an
uploaded file and make a file_id.diz file, then add it to the archive. Enter
"N" if you do NOT wish to CREATE a file_id.diz.
SELECT AN ARCHIVE TYPE TO CONVERT ALL FILES TO
ULTESTER will extract ALL files from an uploaded archive (including recursed
directories). After scanning, the file(s) will be re-archived with this
default IF the "convert to" archive type is different than that which was used
on the uploaded file.
ENTER A "Y" TO HAVE ULTESTER CONVERT FILES OTHER THAN ZIP/ARJ/LZH
Selecting "Y" will cause *ALL* files uploaded to be converted to the specified
default archive type.
ENTER A "Y" TO ADD A ZIP OR ARJ COMMENT TO THE ARCHIVE HEADER
Enter "N" if you do NOT wish the header comment added to the archive. This is
naturally dependant upon the archive type(s) you allow uploaded to your
system.
ENTER THE PATH AND FILENAME OF A "FOOTER" FILE TO BE ADDED TO THE BOTTOM OF
THE ULTESTER TESTING SCREEN.
ULTESTER will attempt to control screen output of lines 19 through 25 for the
footer file, therefore limit this file to "7" screen lines to avoid the screen
scrolling. NOTE: You should have 2 files! (1) An ASCII one whose path & file
name you should enter above and (2) an ANSI file which *MUST* have a "G"
appended to the name entered above. Example: C:\FNET\ULT\FOOTER (Include a
FOOTERG file for ANSI)
ENTER A "Y" IF YOU WOULD LIKE ULTESTER TO ADD THE TOTAL FILES RECEIVED IN AN
ARCHIVE FOLLOWED BY THE NEWEST AND OLDEST FILE DATES IN THE ARCHIVE.
ULTESTER counts the total number of files in an uploaded archive, including
all files in imbedded archives and those which might be in recursed
sub-directories. If you enter "Y" for this item, ULTESTER will make an entry
in the file description stating the number of files, the newest file date in
the archive and the oldest file date found in the archive.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 140 ║
╚════════════════════════════════════════════════════════════════════════════╝
ENTER THE MINIMUM GIF RESOLUTION ALLOWED. YOU MUST ENTER IT IN THE FORMAT OF
###x###x###.
IF you do not enter a MINIMUM GIF Resolution, ULTESTER will bypass the
resolution verification. DO NOT enter any spaces in the minimum resolution.
It MUST be in the format depicted above. Example: 640x480x256
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 141 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNETTEST.BAT - Upload 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 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 information 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
%FNDRV%
CD C:\FNET\ULT
ULTESTER ULT%NODE%.CFG %1 %2 %3 %4
%FNDRV%
CD C:\FNET\NODE%NODE%
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 142 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNPACK - Message Packing Utility
FNPACK is a message file packing utility. It currently performs 3 functions:
PACK THE MESSAGE FILE: FNPACK <CONF#>
Example: FNPACK 34
FNPACK #### - 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 need to be in a NODE directory. FNPACK.EXE
needs to be located somewhere in your DOS path.
RENUMBER THE MESSAGE FILE: FNPACK <CONF#>
/RE:<STARTING MSG#>
Example: FNPACK 34 /RE:15000
This example will pack conference #34 and will change the starting message
number to 15000. "/RE:" is currently the *only* option available for
repacking. a "plain" repack just removes 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.
REBUILD THE CONFERENCE FILE INDEX: FNPACK <CONF#> /IN
Example: FNPACK 34 /IN
FNPACK will attempt to rebuild the conferences INDEX file if the conference
has been corrupted. Depending on how badly the conference has become it may
or may not succeed.
RESIZE THE CONFERENCE MESSAGE FILE: FNPACK <CONF#>
/MAX:#
Example: FNPACK 34 /MAX:500
FNPACK will resize the conference message base to the last "X" number of
messages entered. This is a good way to keep you message bases small or to
trim them before lowering the number of message blocks allocated in FNCFG.
Remember, 1 message block will hold upto 1024 messages.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 143 ║
╚════════════════════════════════════════════════════════════════════════════╝
FN-NET - Message Pointer Utility
The program FN-NET.EXE is included for the SysOps who are running echo mail
conferences which handle echo mail such as FIDONet, LinkUSA, etc. FN-NET will
also update mail waiting pointers after an upload to the system of a .REP
packet from the QWK Mail menu.
Place FN-NET.EXE in your path.
Go to any of your node directories and run:
FN-NET <Path to your FNET directory>
NOTE: The parameter only should be run the first time you run FN-NET after
importing echo mail. Once run with the parameter, 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. There is a 3 second pause after the program runs so
that you can see the results. You may append a QWK parameter to the command
line to disable the 3 second pause.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 144 ║
╚════════════════════════════════════════════════════════════════════════════╝
MODEMSET - 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 specified, 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 alphabetical 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.10 Page 145 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 directories 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
or Floptical 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).
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 146 ║
╚════════════════════════════════════════════════════════════════════════════╝
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
If NOT FOUND, Tell User that file is not on disk or his security level is
too low.
FOUND:
Checks the users security level against that which is recorded for the file
directory
IF OK GOTO SLOW DRIVE
IF BAD, Tell User that file is not on disk or his security level is too low.
SLOW DRIVE: Is drive listed as a slow drive?
IF YES GOTO MOVE ELSE GOTO BAT
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 transferring 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 reference 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 directories 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.10 Page 147 ║
╚════════════════════════════════════════════════════════════════════════════╝
The following is what the contents of the .PTH file should look like,
referencing all Hard Drive and Slow Drive's and thier PATHS with downloadable
files.
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.
Once this file is created, you can run the compiler with the following command
line:
BUILDNDX [file_in.PTH] [file_out.IDX]
EXAMPLE: BUILDNDX DIR.PTH CONF0001.IDX
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 148 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONFUTIL - FEATHERNET PRO! Conference Utility
The conference utility will perform a few operations on existing conferences.
The FEATHERNET PRO! Conference Utility (CONFUTIL.EXE) enables you to perform
several operations on your existing conference configuration.
The options are:
1: Move a Conference - Move to another Conference's Position.
2: Copy a Conference - *replaces* the target conference #.
3: Blank Conferences - Disables a range of conferences by "BLANKING" the
conference name and resetting all user message pointers for the affected
conferences to null.
4: Swap two Conferences - Swaps the position of two conferences.
5: Delete Conferences - Deletes a range of conferences. Resets all user
message pointers for the affected conferences to null.
6: Insert Conferences - Inserts a specified number of conferences unless the
total number of conferences would exceed 4096. Moves all user message
pointers as necessary. All user message pointers for the INSERTED
conferences are nulled.
IMPORTANT! The numbering of conferences on the command line is from 0 to the
highest conference # you have configured. This is exactly the same method used
by FeatherNet (FNET.EXE) and FNCFG.EXE. The maximum conference number allowed
on the command-line is 4095.
Now that you have an indication of what this utility can do, be forewarned! -
it is extremely powerful and caution must be exercised. Much care and testing
has been done to this point, however it is possible under certain
circumstances things could go wrong without warning. It is most advisable you
back up these files (.ZIP, TAPE, FLOPPY, etc) prior to starting Confutil:
USERS
FNCONF.@@@
FNCONF.SEC
FNCONF.LST
FNEXTUSR (if More than 40 total conferences are present).
COSYSOP.BIT
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 149 ║
╚════════════════════════════════════════════════════════════════════════════╝
Running CONFUTIL.EXE
Confutil operates from the DOS command line. There is no user interface or
menu. Before running confutil ensure you have performed a CHDIR to a
FeatherNet node sub-directory (where an SRCONFIG file is located). To start
Confutil, enter "confutil" followed by the command line parameters necessary
to perform the task you want completed. Examples of command lines follow:
Confutil 0 5 /COPY ; Copies Conf #0 to #5 (Conf #0 remains).
Confutil 5 12 /BLANK ; Blanks out 12 Conferences starting at #5
Confutil 5 845 /SWAP ; Swaps Confs #5 and #845.
Confutil 105 17 /DELETE ; Deletes 17 Conferences starting at #105
Confutil 1 5 /MOVE ; Moves Conf #1 TO Conf #5.
Confutil 5 10 /INSERT ; Inserts 10 Conferences starting at #5
Confutil does minimum Syntax checking on the passed command line. It will not
function is a conference number less than 0 or a conference number greater
than the highest existing conference is passed. Confutil will prompt you if
you wish to continue before it begins working on any files. This is your last
opportunity to avoid permanent changes to the existing files mentioned above.
Confutil does backup each file prior to modifying the original files. You
would be wise to check the affected files listed above after *each* time
Confutil is allowed to run its course.
Confutil Function Details
Copying
confutil x y /COPY
When the /COPY parameter is seen on the command line Confutil prepares to
perform one of its most simple functions. Copying will read conference "x"
from FNCONF.@@@ and replace conference "y" with an exact duplicate of
conference "x".
Swapping
confutil x y /SWAP
When the /SWAP parameter is seen on the command line Confutil prepares to
perform another its simple functions. Swapping will read conferences "x" and
"y" from FNCONF.@@@ and swap their positions.
Delete
confutil x y /DELETE
When the /DELETE parameter is seen on the command line Confutil prepares to
work a bit harder. Deleting a conference means all conferences beyond the
deleted conferences will be shifted left "y" places in the FNCONF.@@@ file.
The end result is "y" fewer conference.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 150 ║
╚════════════════════════════════════════════════════════════════════════════╝
Blank
confutil x y /BLANK
When the /BLANK parameter is seen on the command line Confutil prepares works
with enthusiasm. Blanking conferences removes the names from the FNCONF.@@@
file for all conferences from "x" to "y". This signals to FeatherNet to
ignore this conference as it is inactive. Additionally, all user message
pointers are nulled in the "blanked" conferences.
Move
confutil x y /MOVE
When the /MOVE parameter is seen on the command line Confutil prepares to
perform its most intense task. Moving a conference involves placing
conference "x" into conference "y"'s position. In order to do this all the
affected conferences from "x" to "y" must be shifted as necessary to complete
the move.
For example let's say x is 20 and y is 30. When Confutil is finished records
21 - 30 have been shifted left one position to make room for the move of
conference 20 to position 30.
Insert
confutil x y /INSERT
When the /INSERT parameter is seen on the command line Confutil prepares to
get busy!. Inserting a conference(s) involves placing conference "x" into
conference "y"'s position. In order to do this all the affected conferences
from "x" to "y" must be shifted as necessary to complete the Insertion.
For example let's say x is 20 and y is 10. When Confutil is finished records
20 - 29 will have the default MAIN BOARD settings. The original conferences
20-29 have been shifted right to make room for the new conferences. You may
never insert so many conferences so that the maximum of 4096 conferences is
exceeded.
Summary
Confutil will assist you in organizing obsolete conferences. It also provides
a simple way of inserting or deleting conferences. The "hard" work will be
updating your conference listing files (CL/CLS/CLR). It is strongly suggested
you plan ahead and make some room for insertion of future conferences by
leaving some BLANK conferences at strategic locations in your conference
planning.
Confutil is quite efficient and its speed is ultimately governed by the number
of users present in your users file and the number of conferences in use.
NOTE: You *must* run FNCFG.EXE from a node directory when you are finished
with CONFUTIL. Once FNCFG is started, be sure you exit with the "Y" response
to the "Save Configuration?" question.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 151 ║
╚════════════════════════════════════════════════════════════════════════════╝
When Confutil performs a task, each user record in the USERS, FNEXTUSR (if
more than 40 conferences configured) and the COSYSOP.BIT files must be
manipulated to reposition the bitmaps which keep users' flags and the high
message read pointers. The more users you have the longer this will take.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 152 ║
╚════════════════════════════════════════════════════════════════════════════╝
CNAMES40 - PCBoard's CNAMES.@@@ Utility
With compatibility in mind, and since we have a number of features 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.
COMMAND LINE EXAMPLE: CNAME40
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 153 ║
╚════════════════════════════════════════════════════════════════════════════╝
FNODEMON - Node Monitoring Utility
FNODEMON enables you to view a list of who is currently on-line 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.10 Page 154 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.10 Page 155 ║
╚════════════════════════════════════════════════════════════════════════════╝
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
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.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 156 ║
╚════════════════════════════════════════════════════════════════════════════╝
This line MUST be followed by a BLANK LINE then start your DIRxx entries.
%C:\FNET\DISP\HDR-STD
<Blank Line>
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.10 Page 157 ║
╚════════════════════════════════════════════════════════════════════════════╝
CONTROL FILES - FNETPROT.DAT
One 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 and 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 software. 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 port %1 handshake slow pB4096 sz -s -m
DSZ port %1 handshake slow 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 transfers.
0 if it can not,
ZModem with Resume Capability = Protocol desc (40 Char Limit)
DSZ port %1 ha sl pB4096 sz -s -m = This is the send command line
DSZ port %1 ha sl pB4096 rz -m -r = The receive command line
The above is a DSZ (ZModem) command line. For further information, refer to
the documentation for the external protocol you are configuring for use.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 158 ║
╚════════════════════════════════════════════════════════════════════════════╝
This is an actual FNETPROT.DAT file for your reference;
5
Z110Zmodem with Resume Capability - (Still the Best!)
DSZ port %1 handshake both pB4096 sz -s -m
DSZ port %1 handshake both 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 port %1 handshake both sb -k -g -s
DSZ port %1 handshake both rb -g -p
O000Xmodem-1k
DSZ port %1 handshake both sx -ks
DSZ port %1 handshake both rx -c -k -y
C000Xmodem CRC and Checksum
DSZ port %1 handshake both sx
DSZ port %1 handshake both rx -c
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.10 Page 159 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.10 Page 160 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 initiating the DOOR application. A sample batch
file to initiate such door with the CTTY command is below. The caller sees
any host or local node that is displayed such as the MYTEXT display.
@ECHO OFF (No DOS echo)
CTTY COM1: (COM1 output)
TYPE MYTEXT (function)
CTTY CON (Output to scrn)
SFN.BAT (Load BBS)
IMPORTANT! IMPORTANT! IMPORTANT! 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 DIRECTORY AND EXECUTE A
"FORMAT C:" COMMAND!
BE VERY CAREFUL!
3) Instead of using the CTTY command, a program called "DOORWAY" by Dudley
Marshall, may be used (AND IS RECOMMENDED). It also redirects screen output
and keyboard input through the Serial Port, but provides many additional
features that add reliability, further compatibility and SECURITY.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 161 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 Configuration 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) Place the file in any of your alternate directory paths (DLPATH.LST) and
let the users know it is there.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 162 ║
╚════════════════════════════════════════════════════════════════════════════╝
FILE STRUCTURES
Below you will find a listing of ALL the files that FEATHERNET PRO! v1.10
uses/creates.
REMOVED FOR SPACE RESONS FROM THE SHAREWARE DOCS. IF YOU NEED THESE FILES FOR
DEVELOPMENT REASONS, PLEASE DOWNLOAD CTLTDOCS.ZIP FROM THE FEATHERNET HQ BBS @
(813) 249-8422.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 163 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 front-end 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 <ERROR CORRECTION STRING> EVENT<MINUTES>
The following two parameters may also be passed to FEATHERNET PRO!:
/C:0 (Local Logon)
/C:9 (SysOp Logon)
Example FNET.EXE string: FNET /C:%1 %2 EVENT%3
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 164 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX B - Running Under DESQview & OS/2
DESQview, from Quarterdeck Office Systems, and OS/2 2.1, from IBM provide
excellent, low-cost, software platforms 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 floundered and IBM has provided a
reliable multitasking enviroment that does not require a DOS platform beneath
it. It is because of this that we have included on our Tech Support BBS, text
files that will help you set up your system with these multitaskers.
For OS/2 users, please download OS2-FNET.ZIP
For DESQview users, please download DV-FNET.ZIP
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 165 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX C - Macros
FEATHERNET PRO! supports a wide array of macros for conveniently displaying
information about the caller and the system, controlling 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@
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 166 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.10 Page 167 ║
╚════════════════════════════════════════════════════════════════════════════╝
NOTE: The following three MACROS will be activated AFTER v1.10 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
SYSTEM AND DISPLAY CONTROLS:
@BEEP@ = Sends a <CTL><G> (ASCII BELL character) to the caller but
is not heard on the local machine unless the 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
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 168 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 function 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) computers. 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 second. 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 "delayed" 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.
@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 variable 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.10 Page 169 ║
╚════════════════════════════════════════════════════════════════════════════╝
@CNUM:####@ = where #### is the number of a conference to for FEATHERNET
PRO! return the CONFERENCE NAME for. Example: @CNUM:0 This
would return the name of the first conference, normally
"MAIN BOARD" or something similar.
@CLW:#############@ = where the "#" characters translate to: ULRow, ULCol,
LLRow, LLCol, FGCcolor,BGColor,Intensity. This macro
REQUIRES ANSI capability on the caller's end. The color
codes are ANSI colors such as 30-37 and 40-47 where the
numbers beginning with "3" are foreground colors and those
beginning with "4" are background colors. The intensity "#"
should be set at "0" for low intensity or "1" for high
intensity. This macro clears a "window" on the screen by
filling it with spaces. Use the below "@CWIN:###@" macro
to quickly clear a portion of the screen by erasing ENTIRE
lines of text with the ANSI CLREOL code.
Example: @CLW:1015206533401@ The above example will clear
the portion of the screen starting at row 10, column 15
through row 20 column 65. It will use high intensity 30 on
40 (yellow on black). Note: ALL "#" characters must be
replaced by numbers. Use "05" instead of "5", etc.
@CWIN:####@ = which will use the ANSI CLREOL command to quickly clear a
portion of the screen by erasing entire lines of text.
Example: @CWIN:0510@ The above example clears the lines 5
through 10 of the screen. Note: ALL "#" characters must be
replaced by numbers. Use "05" instead of "5", etc.
@NEWM:####@ = will report the number of new messages in the specified
conference number for the user that is currently viewing
the macro. Example: New Message Available: @NEWM:45@
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 170 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX D - 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, because so
many display files are in existence today using the popular @Xfb macros, we
have included compatibility with FEATHERNET PRO! @Xfb codes do have an
advantage in that they can be edited quickly and easily in a text editor while
ANSI is more difficult. We should also point out here that ANSI display files
are some what quicker to display than the @Xfb codes.
Both ANSI and @Xfb coded files may be used in a single file with no graphics
version of that file necessary. A caller in non-graphics mode will see the
contents of the file as pure ASCII with no color added, because FEATHERNET
PRO! will automatically strip the ANSI or @Xfb codes out for them. A user in
color graphics mode will see the colors designated by the @Xfb macros or ANSI
codes.
TheDraw version 4.60+ has provisions to save files in either ANSI or @Xfb
coding. If you wish to use the @Xfb coding in TheDraw, simply chose [S]ave,
[@], [D].
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.10 Page 171 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX E - 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.10 Page 172 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX F - 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 indicating how many
lines of text are in the forth coming 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! If you wish to create a blank line
you must use the <ALT> 255 Key press combination. (Move to the line you want
blank and hold the <ALT> key down while you type 255 on the keypad (w/ the
number lock OFF). This will create an invisible character that the script
reader will be fooled into thinking that there really is a character there,
you MUST count these lines when totaling lines in the question.)
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.
9) You may use any @MACRO@ or @XColor Code within your script.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 173 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.
(ALT 255 CHAR)
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:
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 174 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX G - 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. Insure you save the configuration with the "Y"
answer and the private file directory will be created for you.
2) Insure 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 they may:
[1] Download any files waiting for them
[2] List a directory of any files waiting for them
[3] Upload a file(s) to another authorized user
[Q] Quit to the main file transfer menu
NOTE: You MUST ensure you have the command "SET DSZLOG=C:\FNET\NODE1\DSZLOG"
(whereC:\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.10 Page 175 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX H - 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 attached 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 indicates a successful upload, the record number in the conference
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 attachment 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 potential problem.
You may delete the database from the attachment directory at any time without
creating any problem.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 176 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX I - About 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.
In the REGISTERED Docs 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 Base36 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.10 Page 177 ║
╚════════════════════════════════════════════════════════════════════════════╝
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. 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.
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"
i.e.: 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 sent 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/re drawn. 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 re drawn/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.
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
QWKR QWK Menu
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 178 ║
╚════════════════════════════════════════════════════════════════════════════╝
DISPLAY FILES WHAT
------------- ----------------------------------------------------
BDAY File displayed on users birthday
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 Conference
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 Conference
F_INTROR File displayed when joining a FidoNet ECHOed conference
L_INTROR File displayed when joining a LinkUSA ECHOed conference
LOGOFFR Goodbye screen.
NON-DISPLAY FILES
RIP-36 Shows all Base36 codes
RIP-CMD Shows all RIP commands
FNETICN.ZIP A complete ICONS package for your users to download 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 RIPTERM!
YOU PROBABLY SHOULD ALSO LOOK INTO ONE OF THE MANY GOOD ICON UPDATER DOORS
AVAILABLE THAT CAN BE RUN FROM YOUR $$LOGON.BAT FILE.
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.
(THE REMAINDER OF THE EDITING RIPscrip FILE HAS BEEN REMOVED FROM THE SHARE-
WARE DOCUMENTATION FOR SPACE REASONS)
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 179 ║
╚════════════════════════════════════════════════════════════════════════════╝
OK, I GIVE UP!
I have tried to do RIP 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 orry 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 you come over and use thier
computer and show you where you have errored. There are also A LOT of SysOps
ring to make screens for a profit advertising in a lot of the echo
conferences.
NOTE: The use of Commercial Software on more than one computer is an
infringement of copyrights and is idered PIRACY. Please do not, under any
circumstances "borrow" a copy of any commercial software for use with atherNet
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 looks of the default menus. but
we will change all buttons to reflect your options. We can also change the ON
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 changes for you.
MAIN, MESSAGE, FILE MENUS $ 15.00 ea
CONF LISTING, DOOR, BULLETIN, QUESTIONAIRE MENUS $ 10.00 ea
INDIVIDUAL DISPLAY FILES, CONF HEADERS, FILE AREA HEADERS, ETC.
(These files may be custom designed to reasonable specs) $ 5.00 ea
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 IDIVIDUAL BASIS,
IF YOU WOULD LIKE MORE INFO ON ANY OF THESE SERVICES, PLEASE CONTACT BETH at
FeatherNet Software's Graphics Department. (813) 249-8322 VOICE, Monday -
Friday 5PM - 9PM.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 180 ║
╚════════════════════════════════════════════════════════════════════════════╝
APPENDIX J - Converting from PCBoard
We have received several requests for information on "Converting" from other
BBS packages to the all new FEATHERNET PRO! v1.10.
The BBS package that's most easily converted from is Clark Development'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 converting from PCBoard to the all
new FEATHERNET PRO! v1.10, 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.10 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.
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.
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.10+, the index files are called
FNPNDX.x (where x= A through Z).
Copy your USERS file from PCBoard to the \FNET\FNSYS directory.
EXAMPLE: COPY C:\PCB\MAIN\USERS C:\FNET\FNSYS
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 181 ║
╚════════════════════════════════════════════════════════════════════════════╝
2) COPY & RENAME THE PCBNDX.x FILES: Copy and rename yourPCBoard PCBNDX.x
files to the FEATHERNET PRO! v1.10 \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 accordingly.
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 "FIRST" function you 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.
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 conference.
Move down to the Path & Name of List File for Directories and press <F2>.
This will take you into the DIR.LST file for editing.
You will notice that ALL your DIR paths & filenames are already there with the
Hard Disk Subdirectories.
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 182 ║
╚════════════════════════════════════════════════════════════════════════════╝
You will need to enter the 3rd column (SEC header) and set the minimum
security level allowed to download from this file directory.
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 information on this, please see
the chapter on BUILDNDX in the SysOp Utilities section. BUILDNDX takes about
1.3 minutes per CD-ROM.
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 Configuration 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.10 Page 183 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 questionsand 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 The FeatherNet HQ BBS number: (813) 249-8422 - 24 Hours
(Except Zone Mail Hour)
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.10 Page 184 ║
╚════════════════════════════════════════════════════════════════════════════╝
UPGRADES
The following is the upgrade schedule for FEATHERNET PRO! v1.10. 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.10 $50.00 1,2
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) $15.00 1,2,3
(FeatherNet Software, Inc. mails upgrade to you) $20.00 1,2
Major Upgrade "X".xx $50.00 1,2,3
(Upgrade mailed to user with new documentation)
FeatherNet Auto Upgrade Plan (FAUP) $45.00 1,2
(User mailed all minor upgrades to user for one (1) year FREE of charge)
1 - Plus shipping and handling.
2 - Florida residents must add State and County sales tax as applicable.
3 - After Payment and Paperwork is recieved and cleared
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 185 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 the following pages 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. "A").
You may send these pages in either of the following methods:
1) Upload it as a Message or File to the FeatherNet HQ BBS at the number:
(813) 249-8422 [BBS]
(813) 249-8322 [Voice]
2) Mail the completed forms to the address listed below:
FeatherNet Software, Inc.
P.O. Box 260666
Tampa, FL 33685-0666
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.10 Page 186 ║
╚════════════════════════════════════════════════════════════════════════════╝
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) DOS 6.10 (9) OS/2 v1.x (13) WIN NT v3.1+
(2) DOS 4.01 (6) DOS 6.20 (10) OS/2 v2.0 (14) Chicago v4.0+
(3) DOS 5.0 (7) DOS 6.21 (11) OS/2 v2.1+
(4) DOS 6.0 (8) Novell DOS 7.0 (12) WIN v3.10+
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: ____________________________________________________________
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 187 ║
╚════════════════════════════════════════════════════════════════════════════╝
4) HARD DISK:
a) Model: ________________________________________________________________
b) Manufacturer: __________________________________________________________
c) Size (in Megabytes): ___________________________________________________
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): _____
╔════════════════════════════════════════════════════════════════════════════╗
║ FeatherNet PRO! v1.10 Page 188 ║
╚════════════════════════════════════════════════════════════════════════════╝
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.10 Page 189 ║
╚════════════════════════════════════════════════════════════════════════════╝
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 in the Software Bug Report Section.
1) Page number: _______
2) Section: _______________________________________________________________
3) Brief description: _____________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________