home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
DDMENU25.ZIP
/
DDMENU25.DOC
< prev
next >
Wrap
Text File
|
1994-12-09
|
7KB
|
167 lines
Beta Docs: For DoorDoor 2.5 Menu System
Just what is this stuff?
This is a procedure that allows a door to call a gateway to up to
19 doors, and also keep the usage statistics for the doors in the
gateway. I will refer to these doors as doordoors from here on out.
The procedure creates its own menu for the gateway from the data
file ddmenu.dat. DDmenu can call itself, thus allowing one door
to open to possible 361 doors.
The program assumes you are using a fossil driver.
Files included in ddmenu##.zip are:
ddmenu.med The doordoor execution file. (medium *)
ddmenu.slo The doordoor execution file. (slowest *)
ddmenu.exe The doordoor execution file. (fastest *)
ddmenu.cfg File with registration name.
nutedit.exe The data editor.
ddmenu##.doc This file.
readme.com This file in a screen readable form.
upgrade.doc What do do if you already have a doordoor system.
door.sys Sample door.sys file.
one.bat Sample batch files.
two.bat "
three.bat "
The ddmenu.cfg should be as follows:
Line 1: Registration name
Line 2: Sysop's name. If you want this name to not appear
on the screen updates, enter it so each word begins
with a capital letter and the other letters lower
case.
example line 2:
Jim Woodward -> would cause Jim Woodward to not appear
Jim WoodwarD -> would cause Jim Woodward to appear on screen update.
This file must be located in the c:\ (root) directory, or
the registration name will be the sysop's name.
ddmenu.dat (created and/or edited with nutedit.exe)
Each line keeps the usage data for that door,
i.e. line1 is the data for doordoor 1. and looks like
the following:
str1,str2,str3,str4,str5^
where:
str1 is the number of times that ddoor1 has been entered.
str2 is an 'a' or 'p' or 'r'. If str1 is an 'a', then
the users alias will be printed as the last user. If it is a 'p',
then a name I chose will be printed, e.g. Liz Taylor. If an 'r'
is there, then the real users name will be used.
str3 is last user's name.
str4 is the time of day the last user entered the door.
str5 is the description of the door.
Please note that a comma is between each str# and the line ends with
a caret (shift-6) . This is essential that each line be in this
form! See the sample ddmenu.dat file included.
Directions to make door# on your system a gateway to doors.
1- Unzip the ddmenu.zip file into a work directory.
2- Edit ddmenu.dat and ddmenu.cfg to your wants, then copy
ddmenu.cfg to c:\ , i.e. enter the command:
copy ddmenu.cfg c:\
after you have edited it.
3- Test the system by entering the command:
'nutedit ddmenu.dat'
and then exit the nutedit program. It will create a ddmenu.dat
file with one door. Now enter the command:
'ddmenu .'
The . in the above command tells ddmenu.exe to look for door.sys
in the present directory. Hit the '1' key several times to
try out this system. If you like what you see, then continue.
4- copy ddmenu.exe and nutedit.exe into your BBS directory,
e.g. c:\wc30.
5- Make a directory ddoor#, e.g. c:\wc30\doors\ddoor20 would be a
path to the directory if door20.bat is the bat file to the
gateway ddoor20.
e.g.: give the following commands
cd\wc30\doors
md ddoor20
6- Change to this directory and enter the command
'nutedit ddmenu.dat'
and make the ddmenu.dat file as you want it.
7- Make a one.bat file to run the first ddoor program, a two.bat
to run the second doordoor program, etc. Each line
in the ddmenu.dat file should have a *.bat file included in
this directory. The bat files MUST be named as follows:
one.bat
two.bat
three.bat
four.bat
five.bat
six.bat
seven.bat
eight.bat
nine.bat
ten.bat
eleven.bat
twelve.bat
thirteen.bat
fourteen.bat
fifteen.bat
sixteen.bat
sevnteen.bat
ateteen.bat
nineteen.bat
NO More possible, and they must be spelled as above!!
You only need as many as doors you want to run in this doordoor.
Remember 19 doors is the maximum number of doors that can be run
from Doordoor. Look into one.bat file included.
8- Edit your door#.bat file so it appears as the following
ddmenu <path to doordoor dir>
A sample door#.bat file would be:
ddmenu c:\wc30\doors\ddoor20
It is essential that the above line be in the door#.bat file
before any change in directories, i.e. the ddmenu.exe
file must find your drop file first. If your door#.bat
file doesn't open up in a directory where your drop file
is, then first change to this directory.
e.g.
c:
cd\BBS\...\node1
ddmenu c:\...\ddoor20
9- Fire up your BBS and try it, but first say a prayer and if it
doesn't work, you shouldn't get mad at me.
This utility was compiled using Borland's 3.1 C++ compiler and Brian
Pirie's Opendoor door kit (which requires a fossil driver, e.g.
X00 or BNU, be installed).
These docs were written for a Wildcat BBS. I do know that it works
in Renegade and Maximus, as well as Wildcat3.x and Wildcat4.x.
I have it running on Wildcat 4 and Maximus BBSs which share doors
and up/download files.
Addendum: Added by request are the ddmenu.slo & ddmenu.med. If the
dot (*) is moving too fast copy ddmenu.med or ddmenu.slo over
ddmenu.exe .
Jim Woodward
556 W. Main St.
Lock Haven, PA 17745-1109
Any other comments, good, bad, or indifferent are welcome, just
send to the above address.
Wildcat BBS
Woody's NutHouse
717-748-5728 (Supra 28.8 V.FAST)
Maximus 2.02 BBS
Woody's NutHouse II (ZyXEL 1496E+ V.32BIS)
717-748-1834