home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbsfiles
/
gsbbs302.arj
/
-READ.ME
next >
Wrap
Text File
|
1991-01-21
|
4KB
|
79 lines
The following items didn't make it into the documentation:
DISTRIBUTION COMRESSION.
Please distribute GSBBS only in the original .ZIP file, with
Authenticy Verification. This is something I can't get from any
other archive method, and I'd rather keep this integrity check
with my software. In fact, I'll go so far as to specifically
prohibit any distribution other than the original .ZIP file.
However, you may modify the .ZIP file COMMENT if you wish.
BAD_MAIL.EXE.
Run this periodically; it will search for mail messages sent to
or from people who no longer have accounts. It will delete any
such messages. It will also delete netmail, so be careful.
SETUP.
The first time you run S1.BAT, you'll see a bunch of error messages
about "run-time error 002", "file not found", other stuff. Don't
worry - it's just complaining because there aren't any users. After
you log on and log off, these messages should disappear the next time
you run S1.BAT.
Also, it is very important to create your message and file directories
ahead of time. Nasty fatal errors will occur if these directorie
don't exist.
DIR.BBS.
In each file section, a file named DIR.BBS is created which contains
the name and description for each file in that file area. The format
of this file is
FILE.EXT The description goes here
You can edit this file with a plain text editor. To put in comments
which are not associated with a file but which should be shown to
people requesting a directory listing, put in a line which starts with
a space character.
MESS0.BBS, TITLE0.BBS.
These files are the mail system. TITLE0.BBS contains message header
information and MESS0.BBS contains the messages in linked list form.
This is extremely compact, efficient, and fast. Message board messages
are stored in the same format.
IDS.BBS.
This contains the user information (passwords, names, addresses, etc)
and thus should be backed up often, and kept under high security.
GSBBS TRUSTS YOU.
GSBBS knows a caller can't be expected to read menus.
However, the SysOp should be expected to know what he's doing.
Therefore, though it's robust on the caller's end, it's fragile
on the SysOp's end. If you screw up, GSBBS will bite you with
nasty, incomprehensible error messages. Read the manual and
this file carefully. If you get really stuck, send me a disk
with all your configuration files, or maybe a printout.
But remember, you're supposed to know what you're doing. <grin>
I'M ONLY HUMAN.
Because of that, I've probably glaringly overlooked explaining
something in these notes. If you don't understand something or
I've left files around which you have no idea what to do with
them, just send me a note and I'll try to help. I'll also fix
the problem in future docs.
FREE REGISTRATION.
I have a few projects, such as a full-screen editor, which I'd
be willing to give a free registration to someone if they'd
return the favor by writing for me. Drop me a note if you're
interested. First ask first option.
Public service organizations may also be eligible for free
registration. Drop me a manifesto and a request.
Have fun!
Jones.