home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.barnyard.co.uk
/
2015.02.ftp.barnyard.co.uk.tar
/
ftp.barnyard.co.uk
/
cpm
/
walnut-creek-CDROM
/
CPM
/
BBSING
/
RBBS
/
RBBS37-1.LBR
/
RBBSINST.HQP
/
RBBSINST.HLP
Wrap
Text File
|
2000-06-30
|
11KB
|
301 lines
1*
The value for DSK$ is pre-assigned in the program to Drive A:
on this drive are the following files: BOOTPWD, BULLETIN, INFO,
HELP, NEWS, ENTERCPM, MENURBBS, and DATETIME.DAT. These are the
files having the minimum of security required. As the SYSOP you
can select which drive contains other files created and used by
RBBS37. Remember they can all be on the same disk drive, the
idea behind breaking up the files was to allow this program to
be used on systems having small disk density (90K etc.)
You are now being asked to select the DSK2$ drive. On this drive
are contained the files PWDS, COUNTERS, SUMMARY, MESSAGES, and
COMMENTS. These are the files which will grow the fastest as
messages and comments are left by the callers. You will also
note that the file called PWDS is written in lowercase to provide
additional protection from being viewed by someone who may have
entered the system.
**
2*
Like DSK2$ there are additional files stored on drive DSK3$.
These are the files LASTCALR, CALLERS, and USERS. The USERS
file is one of the files that should be protected as it will
contain all the passwords of all your system users. Now you
can select the drive that the DSK2$ files will be stored on.
-Remember- that all the files will be located in the same
user area, but on different drives, or you can use drive A:
for all drives.
A default is written into the program and this is the A: drive,
if any of the password files are not found, the system will
default to the pre-programmed default values.
**
3*
When ever you log on as the SYSOP, you might also want to be
notified if there are any other messages for you directed to
your REAL name. So enter in this your FIRST name that you
will be using on this RBBS system.
This creates the value for SYS1$
**
4*
This is the LASTNAME you as the SYSOP will be using on the
system. The last value and this one are used to flag you
when logged in as the SYSOP that there are messages for you
directed to your REAL name.
This creates the value for SYS2$
**
5*
This value in the password files is used to provide the name
of your RBBS37 system. It can be in Upper/lower case characters
of any discription as long as it is on one single line.
This is the VERS1$ value and is printed on entry to your RBBS
system.
**
6*
This value called P1$ is the password for direct entry to CP/M
thru the RBBS system. When asked for your first name upon system
entry you use this password, you will skip over the RBBS message
system and be allowed direct entry to CP/M. This password should
probably be the most complicated of all your passwords. If it is
found out, you have no way of keeping that caller out of your
operating system, other then protections that you might be using
provided to the system by NZCPR, ZCMD, or ZCPR2.
Select this password carefully, use a combination of letters and
numbers to provide additional difficulty of guessing it.
**
7*
This is the P2$ password, it is the LASTNAME you use when you use
the firstname of SYSOP to enter the RBBS program as the SYSOP. It
is another important password, and should be selected with care,
so that it will be difficult for someone to guess. A combination
of letters, and numbers will help to provide additional difficulty
in guessing the password.
**
8*
This is the Validation password VAP$, it is a special password that
is requested whenever you validate a new user. If there are more
than one SYSOP on the system, this provides a way for the main SYSOP
to be the only one allowed to validate new users to the system.
Like all other passwords select it with care !!
**
9*
This is a question that a caller is asked before allowed entry to
CP/M using the J command from RBBS37. This question is not needed
if you are allowing entry to CP/M without a password, or not allowing
any entry to CP/M.
It was originally used as a way of keeping non CP/M users from
entering the system. Questions relating to CP/M would usually be
asked, and you could assume that anyone knowing the answer would
have some knowledge of CP/M.
This is the PC$ entry.
**
10*
This is the answer to the question in the previous menu, it is
the answer you must enter to get into the CP/M system. IF you
don't want to require a password for CP/M entry than use an
answer in this file of NOPASS, using that will delete the need
for a CP/M entry password or answer to the PC$ question.
This is the value for P3$.
**
11*
Some RBBS systems may want to have more than one SYSOP on the
board, if this is what you would like then enter the proper
answer. When there are more then one SYSOP, then folllowing
the correct entry of SYSOP (First name) and lastname, the
SYSOP will be questioned as to which SYSOP he/she is. This
will allow the SYSOP to leave messages on the message system
that have a more personal identification of the SYSOP instead
of the name SYSOP. You could be SYSOP DENNIS or SYSOP NR1,
whatever you enter in the Which SYSOP question will be tagged on
the SYSOP name.
This is the setup of MSYS.
**
12*
Here is your chance to set up the timing loop used by the RBBS
program when the SYSOP is paged for CHAT. This is a value that
is between 1 and 32000, when in the Compiled mode, you need to
choose a value in excess of 10000, while in the MBASIC mode you
can pick a value of less then 500 or so to see how it works.
This is the value for BEEP.
**
13*
You can control the number of lines in messages that are entered
on the message system. This is the SIZE value in the program, and
you can enter the number of lines you want to limit the callers
to leave on the message system. A good starting value is 20.
**
14*
This value is for the number of NEWS files that are on the system.
These are files which you create using a word processor that provide
information about various topics. If you enter a value of 0 then
the program will know that there is only 1 NEWS file, and it will
contain whatever information you want. If the value is 1 or greater,
then the NEWS file should contain a menu of the other NEWS files you
have put on the system. The additional news files are named NEWS1,
NEWS2, etc. depending upon the number you have selected with this
entry.
This is the value for NNUM.
**
15*
This value is for the number of HELP files that are on the system.
These are files which you create using a word processor that provide
information or help on various topics. If you enter a value of 0
then the program will know that there is only 1 HELP file, and it
contain whatever information you want. If the value is 1 or greater,
then the HELP file should contain a menu of the other HELP files you
have put on the system. The additional HELP files are named HELP1,
HELP2, etc. depending upon the number you have selected with this
entry.
This is the value for HNUM.
**
16*
Upon entry to the RBBS system the caller can be notified which was
the last message he read. This does require that whenever you do
a purge of the message base using RBBSUTIL.COM you do not renumber
the messages. If the messages are renumbered each time than this
information stored in the users file is of no use. If you plan on
making use of the 'Last Message read' message then enter the correct
answer to the question.
This is the value for SKIP.
**
17*
Well this won't keep them out of the system unless you tag the caller
as a TWIT. If you select to keep TWITS off the system then whenever
the TWIT calls using the name you have TWITED from the password
validation portion of the RBBS program he will be hung up on. The
TWIT is given a chance to leave you a COMMENT before being droped off
the system. This may make for some interesting comments from the
person, but it does provide a way for them to appologise or let you
know his opinions too. The drawback is that he can call in using a
new name and start all over again. An alternative to TWITING is to
change the password of an unwanted caller instead. This also will
keep them off the system. The other advantage of setting a caller to
TWIT is that he/she will not be allowed access to any functions. If
you select to keep them off or just limit their abilities you can do
it with this function.
This is the value for TWIT$
**
18*
The system can be protected from those folks who like to leave nasty
or obscene messages. You can set up the system to allow only validated
users to leave messages on the public board, or with this menu you can
select to let anyone leave messages on the public board. You may want
to allow them to CP/M but you may not want to take a chance of letting
a new caller leave a public message.
This is the value for LMSG.
**
19*
Here is your chance to determine who will have access to the CP/M
operating system. Using a combination of this menu and the menu
for password entry to CP/M you can create a number of various ways
to allow or not allow entry to CP/M.
E> will allow everyone to enter CP/M except a TWIT, if you have
decided to require a password, then one will be required.
V> will allow only validated users to enter CP/M, a password may or
may not be required depending upon how you set up the CP/M entry
password requirements earlier in this program.
N> Will allow No One to enter CP/M at all, except for the SYSOP or
a SUPER user of the system.
This is the value for GOCPM.
**
20*
As a way of providing a Date/time function for the RBBS program,
there is a section of the code that will go out and read a file
from DSK$ called DATETIME.DAT. You can manually enter date and
time information into this file or let the system do it each time
the BYE program answers the phone. This is an awkward way to do
this, but one that can be made universal from the compiled version
of RBBS37. If you don't have a file to be read then so indicate,
and the program will work in the same old fashion as it has in the
past.
This is the value for DATIM$.
**
21*
Sometimes callers wonder why the message count is larger than
what they can see on the board, or the report says there are
more messages than they are able to read. In these cases the
messages they are trying to read are private and they are not
allowed to read them. One way to fix this is to set SCAN to
YES, and this will allow validated callers to see the private
messages whenever they do a SCAN of the message base. They
cannot read any of them, but just see that there really is a
messge with that number. This is the value for SCAN$.
**
22*
Now this program will write the two password files BOOTPWD and
PWDS in the proper disk drive as you have selected earlier in the
installation program.
I hope this has provided a simple way to configure the RBBS37
program for your own requirements.
Any comments or suggestions are appreciated. Thank you !!
Dennis Recla
**