home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
PHREQ13B.ZIP
/
PHREQ.DOC
< prev
next >
Wrap
Text File
|
1995-01-15
|
14KB
|
230 lines
============================== PHreq!.DOC ===============================
Version 1.3beta
PHreq! is a TriBBS door program which allows a sysop to provide anonymous
file transfers of selected files using various protocols. PHreq! can be
configured to allow the caller to download any/all of the listed files or
only a preset number of files (up to 26 files). PHreq! allows the use of
descriptive "magic" names which can be up to 20 characters long. Also new
in this version are one line file descriptions (max. 70 characters). In the
unregistered version a maximum of 3 files can be downloaded per session.
The program supports an optional intro screen which can be of any
length (line length should not exceed 256 characters) and will be displayed
to the caller 22 lines at a time. The door can make use of either DSZ or
GSZ Zmodem protocol (Omen Technology, seperate registration required),
any of TriBBS's internal protocols (TTPROT.EXE) or HS/Link (Samuel H. Smith,
seperate registration required) bi-directional protocol for transfers.
HS/Link is set to block any attempted uploads since the sysop will have no idea
where these files came from. PHreq! now also supports any protocols defined
in TriBBS's EXTPROT.MNU, including protocols which use redefined hotkeys
for TriBBS's internal protocols. If you have an error correcting protocol
available, but TriBBS does not detect an error correcting modem then the
protocol choice will not appear in the protocol list.
The door will also write a summary of the callers actions into the
CALLERS.LOG file so the sysop can easily see what files where downloaded and
when. A 3 line message can also be left for the sysop (enter "*" as the
first file selection), which will be displayed to the sysop as a logon
message (appended to existing 1.bbs or creates a new 1.bbs file). A caller
can also specify a single file to be downloaded by entering a "!" in front
of the magic name (eg. !PHREQ_BETA). This will cause the program to search
for the named file (the search is NOT case-sensitive) and if it exists it
will start the download and log the caller out in the normal fashion (I have
included this feature so that people can use an automated script for their
terminal program to call and ask for a file by name rather than having to look
through a list and find a file by it's letter). If the file is not found it
will notify the caller and wait for further input - either reenter the magic
name, choose a file(s) by letter or press <ENTER> to hangup without downloading.
The "*" and "!" options can be used together but the "*" must come first. The
file descriptions are accessed by pressing "?" at the prompt. In query mode,
you simply press the letter preceding the file you want the description for, and
it will be displayed at the bottom of the screen - you do not need to press
<ENTER>. You may continue to query files for their descriptions as often as you
like. When you are finished looking at the file descriptions, press "?" again
to return to file selection mode.
After the file transfer is complete the door will either hang up the modem
and reinitialize TriBBS to await the next caller or return to the BBS - depending
on how you have configured the door. The program will also update the "Today's
Downloads" line on the TriBBS "Waiting for Caller" screen. This door may also work
with other BBS's that are capable of running user specific logon batch files. If
used on other BBS software, the door will give error messages when it tries to write
to the log file, but the transfers should take place correctly. Phreq should also
hang up on the caller properly, but it will not reset the BBS - the sysop will have
to ensure that this takes place by some other means. I have not tested PHreq on any
other systems, so I would appreciate any feedback from anyone who might try this.
This door is perfect for software developers and sysops who want to be able
to provide public access to commonly requested files without making the
caller fill out all the new user information. This is especially important
if the person is calling long distance with the express purpose of getting
a file that they know you have available.
The most likely setup for this door is to include it in a SECxxxx.BAT
file which gets run as soon as the caller logs onto the BBS. You will need
to create a dummy account which you will use to access the SECxxxx.BAT file
- something like username PHREQ FILES, password GUEST. Make sure you assign
a security level to this account that is unique, so that no regular users
will accidentally get into the door. I would suggest setting it up with a
security level lower than your new user logon security level. Since the sole
purpose of the door is for anonymous transfer, and the caller will never
access the BBS, there is no need for a higher level of security for the BBS.
Also if the caller should ever happen to break in to the BBS through the
door, they will have very limited access to the features of your BBS
(remember.... they are an anonymous caller). As an additional security
measure, you should create a xxxxSEC.BBS screen that includes the @HANGUP@
command which will have the effect of logging the caller off, if they should
somehow get past PHreq!'s internal logoff function.
Phreq! can also be run as a door from the BBS to provide access to files
that you might want to make available off of a particular menu (eg. you might
want to offer a selection of mail readers that callers can download off of
your message menu or offer a special list of files to visiting sysops, etc.)
To run PHreq! as a door from within the BBS, you need to make the appropriate
changes to the PHREQ.CFG file - put "N" (or any other character except "Y")
on the line for logoff after download and as an option you can allow the
caller to select the protocol to use (same protocols as listed above) by
entering "U" on the line for the protocol to use (U=user defined). You can
also configure the door so that it will give back the time that was used while
in downloading files. In effect this makes them free downloads since they are
not counted into the total bytes downloaded, and their time is not reduced for
having downloaded the files. To set this option enter a "Y" in the phreq.cfg
file on the line which asks if you want to "Give back the time used.....".
INSTALLATION (for Anonymous logins)
------------
1. Create a directory to hold all the PHreq! files. Move into the newly
created directory.
2. Unzip all of the files contained in the PHreq! archive into the PHreq!
directory.
3. Modify the PHREQ.CFG file following the instructions listed at the
bottom of the configuration file. Make sure that you have the trailing
backslash on the directory path where indicated.
4. If you want to run the door as a SECxxxx.BAT file, edit the sample
SEC1.BAT file (or write your own) and rename it using the security level
that you want to use. Move this file to your TriBBS main directory.
If you have multiple nodes, you will have to copy this batch file to
the main directory of each node you wish to have access the door.
5. Create a dummy account on your system which will be used to access the
door. Remember to assign a unique security level to this account. The
security level you enter for this account must match the number in the
filename used in step 4 (i.e. if you created a SEC1.BAT file in step 4
you must assign a security level of 1 to the dummy account). Create a
xxxxSEC.BBS file (in the display directory) which includes the @HANGUP@
command. This is simply as an added safety precaution -see text above.
6. Edit the PHREQ.LST file to include all of the files you would like to
make available for anonymous download. You may include any number of
files up to a maximum of 26 files (the unregistered version will only
allow a user to d/l a maximum of 3 files). Each line MUST contain a
magic name for the file and the full path to the file. The magic name
can be up to 20 characters long, and can include any characters except
spaces (use underlines instead of spaces). There must be at least one
space between the magic name and the path\filename. See the sample file
included in this archive.
7. If desired, create an optional introduction screen which could list
instructions, file limits, specifics about what certain files contain,
or any other information you might like to provide to anonymous callers.
The file must be called PHREQ.ANS or PHREQ.BBS and be located in the
PHreq! directory. The screen supports the use of escape codes but NOT
@ codes.
8. Copy the file SYSDAT2.DAT from the TriBBS main directory to the PHreq
directory. If you don't use TriBBS don't worry about this part.
INSTALLATION ( as a door within the BBS)
----------------------------------------
1. Complete instructions 1-3 and 6-8 from above.
2. Change line 9 of the PHREQ.CFG file to "N", so that the door
will not hang up and reset the board, but return to the BBS.
3. Modify the appropriate menu to add the PHreq! door. If you are adding
it to the DOORS.MNU file you should have something like this:
T,TEXT,PHREQ.BAT,100
Where: T=type of drop file to use (check TriBBS manual for values)
TEXT=text that will appear on default menus
PHREQ.BAT=name of the batch file that will call PHreq!
100=the minimum security level to access this option
If you are adding Phreq! to any other menu you will have to add a line
to the appropriate menu such as the following:
!,!,TEXT,100
Where: !,!= the hotkey you want to use to access the door
TEXT=the text you want to appear on the default menus
100=the minimum security level to access the door
The name of the batch file you will create to run the PHreq! door will
be dependent on what menu you have added it to. Check the TriBBS manual
for the proper name to use (ex. MESSO.BAT to run a door off the message
menu using the "O" hotkey, MAIN1.BAT to run door from the main menu with
the hotkey "1"). The batch file should look similar to the following.
Make the appropriate changes to directory names and irq value (replace
[non-standard irq] with the appropriate value if required.
CD \TRIBBS\DOORS\PHREQ
PHREQ PHREQ.CFG [non-standard irq]
CD \TRIBBS
BOARD
INSTALLATION ( in logon.bat or newuser.bat file)
------------------------------------------------
Set up PHreq! following the instructions for anonymous logons, but skip the
section where you create the dummy account and the SECxxxx.BAT file. Simply
add the appropriate lines to the LOGON.BAT or NEWUSER.BAT file (use included
batch file as an example). This will cause the door to be run as part of the
logon process so that you can offer up special files for download (i.e. ripterm)
before the caller finishes logging into the board.
If you followed the steps above, the door should be installed properly,
and should work without any problems, providing that you have the Zmodem
program in your DOS path somewhere. TTPROT should already be in the path
since it is located in the TriBBS main directory. Any protocols defined in
your EXTPROT.MNU file should work properly since their batch files have to
be in the TriBBS main directory and are also therefore in the DOS path.
If you want to check to see if the door is functioning properly, you can
log in locally by switching to the PHreq directory and using the following
command line:
C:\> PHREQ PHREQ.CFG LOCAL
You will get an error message when you finish a local logon, because the
program tries to update the DOORS.TMP file, which only exists if a caller
is online and running a door, so just ignore the error message - it's OK.
Also, when run locally the door will still write to the temporary
callers.log file - this means that the next time you have a caller online
you will get a bunch of extra lines added to the permanent callers.log file
which reflect your local test. To avoid this, simply remove the temporary
callers.log file from the \TRIBBS\NWORK directory when you are done the
local session - BE SURE YOU DELETE THE FILE FROM THE CORRECT NODE!!
The following special keys are available to the sysop while the door is
running, to allow access to a variety of functions.
HOME Toggle between User status window and Sysop special keys window.
F6 Takes 5 minutes away from callers time - only applies to time in
the door program - not to time on the BBS.
F7 Adds 5 minutes to the callers time - only applies to time in the
door program - not to time on the BBS.
F9 Quits the door and returns the caller to the BBS.
F10 Enter Chat mode. Exit chat mode by pressing ESC.
ALT+D Drop to DOS. Type EXIT at the DOS prompt to return to the door.
ACKNOWLEDGEMENT
---------------
This program is written in Turbo C++ using the TDoor and TBAPI libraries,
both of which are written by Mark Goodwin (author of TriBBS).
These libraries are easy to work with and greatly simplify the work of 3rd
party authors in providing seamless integration with TriBBS.
THANKS MARK!!
CONTACTING THE AUTHOR
---------------------
If you have any questions or comments about this, or any of my other programs
I can be reached through the following:
WME conferences - BBS Doors, C/C++ Programming, BBS Utilities, TriBBS Support
PHONE (807) 767-4155,
BBS (807) 767-1185
Mail: Peter Hanmore
265 Cascade Cres.
Thunder Bay, ON
CANADA P7B 6H9