Converted from CVS

html/.cvsignore

@@ -0,0 +1 @@
+filelist index.htm basic.html upgrade.html

html/Makefile

@@ -0,0 +1,125 @@
+# Copyright (c) M Broek, 1997-2000
+# Top-level makefile for MBSE BBS html documentation.
+# $Id: Makefile,v 1.43 2007/03/01 19:12:54 mbse Exp $
+
+include ../Makefile.global
+
+H_BASE		= dist.html manual.css errcodes.html \
+		  flow.html postfix.html ups.html doors.html \
+		  intergate.html intro.html invoking.html faq.html \
+		  known_bugs.html mgetty.html routing.html nodelist.html
+
+H_FTSC		= ftsc/index.htm
+
+H_IMAGES	= images/b_arrow.png  images/magic.png        images/nodes1.png \
+		  images/connec.png   images/mbsetup0.png     images/nodes2.png \
+		  images/domains.png  images/mbsetup1.6.S.png images/nodes3.png \
+		  images/e_menu.png   images/mbsetup1.6.png   images/nodes4.png \
+		  images/emareas.png  images/mbsetup2.png     images/nodes5.png \
+		  images/nodes6.png   images/nodes7.png       images/nodes8.png \
+		  images/nodes9.png   images/nodes10.png      images/doors.png \
+		  images/emgroup.png  images/modems0.png      images/oneliner.png \
+		  images/fdb.png      images/newfiles.png     images/protocol.png \
+		  images/fegroup.png  images/newgroups.png    images/rarrow.png \
+		  images/fileecho.png images/nodelist.png     images/security.png \
+		  images/filefind.png images/nodelist1.png    images/tty.png \
+		  images/files.png    images/nodelist2.png    images/tty1.png \
+		  images/go_to.png    images/nodelist3.png    images/tty2.png \
+		  images/hatch.png    images/nodelist4.png \
+		  images/language.png images/nodelist5.png    images/uarrow.png \
+		  images/larrow.png   images/users.png        images/doors2.png \
+		  images/mbse.png     images/taskmgr.png      images/mbsebbs-s.png \
+		  images/mbsebbs.png  images/users2.png       images/hand.up.png \
+		  images/dream1.png   images/dream2.png       images/dream3.png \
+		  images/tdream1.png  images/tdream2.png      images/tdream3.png \
+		  images/route1.png   images/route2.png       images/mbmon1.png \
+		  images/mbmon2.png   images/mbmon1-tn.png    images/mbmon2-tn.png \
+		  images/nodes11.png
+
+H_LICENSE	= license/copying.html license/hydracom.html license/index.htm \
+		  license/jam.html
+
+H_MENUS		= menus/control.html  menus/index.htm     menus/menu100.html \
+		  menus/menu300.html  menus/menu500.html  \
+		  menus/menu0.html    menus/menu200.html  menus/menu400.html
+
+H_MISC		= misc/dropfile.html   misc/fileid.html     misc/index.htm \
+		  misc/jam.html        misc/semafore.html   misc/filefind.html \
+		  misc/ftpserver.html  misc/ipmailer.html   misc/outbound.html \
+		  misc/usleep.html     misc/webserver.html
+
+H_PROGS		= programs/mbfido.html     programs/mbmon.html \
+		  programs/mbtoberep.html  programs/mblogin.html \
+		  programs/index.htm       programs/mbcico.html \
+		  programs/mbfile.html     programs/mbmsg.html \
+		  programs/mbseq.html      programs/mbuser.html \
+		  programs/mbaff.html      programs/mbdiff.html \
+		  programs/mbindex.html    programs/mbout.html \
+		  programs/mbsetup.html    programs/mbuseradd.html \
+		  programs/mball.html	   programs/mbnntp.html \
+		  programs/mblang.html     programs/mbsebbs.html \
+		  programs/mbstat.html     programs/mbpasswd.html \
+		  programs/mbtask.html
+
+H_SETUP		= setup/archiver.html  setup/index.htm     setup/bbs.html \
+		  setup/language.html setup/oneliner.html \
+		  setup/emareas.html   setup/magic.html    setup/mail.html \
+		  setup/protocol.html  setup/emgroup.html  setup/chat.html \
+		  setup/fdb.html       setup/security.html setup/sitedoc.html \
+		  setup/fegroup.html   setup/modems.html   setup/softinfo.html \
+		  setup/fidonet.html   setup/tic.html      \
+		  setup/fileecho.html  setup/newfiles.html setup/filefind.html \
+		  setup/newgroups.html setup/files.html    setup/nodes.html \
+		  setup/ttyinfo.html   setup/global.html   setup/users.html \
+		  setup/hatch.html     setup/virscan.html  setup/services.html \
+		  setup/domains.html   setup/taskmgr.html  setup/route.html
+
+H_OTHER		= index.htm basic.html upgrade.html
+
+H_IN		= index.htm.in basic.html.in upgrade.html.in
+
+FILES		= $(H_IN) $(H_BASE) $(H_FTSC) $(H_IMAGES) $(H_LICENSE) $(H_MENUS) $(H_MISC) $(H_PROGS) $(H_SETUP) Makefile
+
+#########################################################################################################
+
+all depend clean depend:
+
+install:
+		@echo "Installing html documentation in ${PREFIX}/html"
+		@rm -Rf ${PREFIX}/html
+		@mkdir -p ${PREFIX}/html
+		@mkdir -p ${PREFIX}/html/ftsc
+		@mkdir -p ${PREFIX}/html/images
+		@mkdir -p ${PREFIX}/html/license
+		@mkdir -p ${PREFIX}/html/menus
+		@mkdir -p ${PREFIX}/html/misc
+		@mkdir -p ${PREFIX}/html/programs
+		@mkdir -p ${PREFIX}/html/setup
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/ftsc
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/images
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/license
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/menus
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/misc
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/programs
+		@${CHOWN} ${OWNER}:${GROUP} ${PREFIX}/html/setup
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_BASE}    ${PREFIX}/html
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_OTHER}   ${PREFIX}/html
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_FTSC}    ${PREFIX}/html/ftsc
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_IMAGES}  ${PREFIX}/html/images
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_LICENSE} ${PREFIX}/html/license
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_MENUS}   ${PREFIX}/html/menus
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_MISC}    ${PREFIX}/html/misc
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_PROGS}   ${PREFIX}/html/programs
+		@${INSTALL} -p -c -o ${OWNER} -g ${GROUP} -m 0444 ${H_SETUP}   ${PREFIX}/html/setup
+
+clean:
+		rm -f filelist
+
+filelist:	Makefile
+		BASE=`pwd`; \
+		BASE=`basename $${BASE}`; \
+		(for f in ${FILES}; \
+			do echo ${PACKAGE}-${VERSION}/$${BASE}/$$f; \
+		done) >filelist
+

html/basic.html.in

@@ -0,0 +1,287 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: basic.html.in,v 1.23 2007/10/14 13:58:22 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS basic installation.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align="right"><h5>Last update 14-Oct-2007</h5></div>
+<div align="center"><h1>MBSE BBS Basic Installation</h1></div>
+
+<h3>Introduction.</h3>
+<p>
+Before you compile and install MBSE BBS you must first setup the basic
+environment. If you don't do this, things will fail.
+<p>
+To compile and install MBSE BBS most distributions have installed all needed packages. 
+If important packages are missing then the configure script will tell you. There are also
+less important packages which if missinng still let you compile MBSE BBS, but you will miss
+some features. Here is a short list of these packages:
+<ol>
+ <li><b>Zlib</b>. On some distributions you also need <b>zlib development</b>. When you have
+     zlib installed, then in <b>mbcico</b> extra code will be compiled in the Hydra and Binkp protocol drivers
+     that will allow the PLZ extension. In the binkp protocol GZ compression will be enabled as well.</li>
+ <li><b>Bzlib</b>. On some distributions you need to install <b>bzlib2 development</b> to add 
+     support for binkp BZ2 compression.</li>
+ <li><b>GeoIP</b>. Allows logging of the origin of the network connections by country and continent.
+     You need at least GeoIP 1.4.3 to compile without errors. See
+     <A HREF="http://www.maxmind.com/app/geoip_country">www.maxmind.com</A>.
+ </ol>
+If you use Gentoo or Ubuntu, read the files README.Gentoo or README.Ubuntu. The last one may be usefull
+for Debian users too.
+<P>&nbsp;<p>
+
+<h3>Step 1: planning the filesystems.</h3>
+<p>
+MBSE BBS is default installed in <b>/opt/mbse</b>. It should be possible to install the bbs in a different
+location but this is not supported. Many have tried, and and only a few have succeeded. See
+<A HREF="http://www.pathname.com/fhs/">Filesystem Hierarchy Standard</A> for more info.
+The default filesystem layout looks like this:<br>
+<pre>
+/opt/mbse                       0775  Default MBSE_ROOT
+/opt/mbse/bin                   0770  Binaries
+/opt/mbse/etc                   0770  System configuration files
+/opt/mbse/etc/dosemu            0750  DOSemu configuration files
+/opt/mbse/ftp/pub               0755  Default FTP root for download areas.
+/opt/mbse/home                  0770  Users homedirectories
+/opt/mbse/home/bbs              0770  Newuser account
+/opt/mbse/html                  0755  HTML documentation
+/opt/mbse/log                   0770  MBSE BBS logfiles
+/opt/mbse/share/doc             0750  Generated sitedocs
+/opt/mbse/share/doc/html        0750  Generated html sitedocs
+/opt/mbse/share/doc/tags        0750  Generated area tags
+/opt/mbse/share/int             0750  Base for language files
+/opt/mbse/share/int/macro/de    0750  German template macro's
+/opt/mbse/share/int/macro/en    0750  English template macro's
+/opt/mbse/share/int/macro/es    0750  Spanish template macro's
+/opt/mbse/share/int/macro/fr    0750  French template macro's
+/opt/mbse/share/int/macro/gl    0750  Galego template macro's
+/opt/mbse/share/int/macro/nl    0750  Dutch template macro's
+/opt/mbse/share/int/macro/zh    0750  Chinese template macro's
+/opt/mbse/share/int/menus/de    0750  German menu files
+/opt/mbse/share/int/menus/en    0750  English menu files
+/opt/mbse/share/int/menus/es    0750  Spanish menu files
+/opt/mbse/share/int/menus/fr    0750  French menu files
+/opt/mbse/share/int/menus/gl    0750  Galego menu files
+/opt/mbse/share/int/menus/nl    0750  Dutch menu files
+/opt/mbse/share/int/menus/zh    0750  Chinese menu files
+/opt/mbse/share/int/txtfiles/de 0750  German ansi screens
+/opt/mbse/share/int/txtfiles/en 0750  English ansi screens
+/opt/mbse/share/int/txtfiles/es 0750  Spanish ansi screens
+/opt/mbse/share/int/txtfiles/fr 0750  French ansi screens
+/opt/mbse/share/int/txtfiles/gl 0750  Galego ansi screens
+/opt/mbse/share/int/txtfiles/nl 0750  Dutch ansi screens
+/opt/mbse/share/int/txtfiles/zh 0750  Chinese ansi screens
+/opt/mbse/tmp                   0770  Temp directory
+/opt/mbse/tmp/arc               0770  Temp archiver directory
+/opt/mbse/var                   0770  Var root
+/opt/mbse/var/arealists         0750  Areamgr arealist files
+/opt/mbse/var/badtic            0750  Bad TIC files
+/opt/mbse/var/boxes             0770  Base for nodes fileboxes
+/opt/mbse/var/bso               0770  Binkley Style Outbound directory
+/opt/mbse/var/bso/outbound      0770  Default outbound for main aka
+/opt/mbse/var/dosemu            0770  Base for DOS drives (doors)
+/opt/mbse/var/dosemu/c          0770  DOS drive C:
+/opt/mbse/var/fdb               0770  Files database
+/opt/mbse/var/inbound           0750  Protected inbound directory
+/opt/mbse/var/magic             0750  Magic filerequest names
+/opt/mbse/var/mail              0770  JAM messagebase root
+/opt/mbse/var/msgs              0770  *.msgs netmail directory
+/opt/mbse/var/nodelist          0750  Nodelists
+/opt/mbse/var/queue             0750  Queue for before outbound
+/opt/mbse/var/rules             0770  Echomail area rules files
+/opt/mbse/var/run               0770  Pid files of running programs
+/opt/mbse/var/sema              0777  Semafore files
+/opt/mbse/var/ticqueue          0750  Queue for TIC files
+/opt/mbse/var/unknown           0750  Unprotected inbound directory
+</pre>
+<p>
+Don't use UMSDOS or SAMBA filesystems for the bbs, stick by the standard
+GNU/Linux
+filesystems (ext2, ext3 or reiserfs) or ufs if you use FreeBSD.
+If you intent to make your bbs also accessible
+by FTP and WWW you must create the directory structure under the ftp user
+behind the pub directory. Read <a href="misc/ftpserver.html">the
+ftp server</a> doc for details. If you don't follow these guidlines, you
+will run into trouble later and have to spend a lot of time in correcting
+this error.
+<P>&nbsp;<p>
+
+<h3>Step 2: Running the installation script.</h3>
+<p>
+First, if you use FreeBSD, install the psmisc package. This will make sure
+that MBSE BBS is stopped properly if you shutdown your computer. Also if you 
+use FreeBSD 5.0 or later make sure that you mount procfs, see <b>man procfs</b>
+for details. If you don't mount procfs, you cannot add new users to the bbs and
+existing bbs users cannot change their passwords. As sysop, you can't change
+passwords too.<br>
+If you are upgrading, proceed with step 4. If not, follow the next steps
+very carefully!<br>
+The installation script must be run by root. It checks if there is a
+previous or failed installation on your system. If that's so the script will
+not run. In other words, you can only run this script once. The script makes
+backup copies of the system files it changes, these files will get the
+extension <strong>.mbse</strong> To run the installation script you need
+the archive <strong>mbbsebbs-@VERSION@.tar.bz2</strong>.
+Unpack this archive on your system, in /tmp:
+<pre>
+cd /tmp
+tar xfvj /path/to/the/mbsebbs-@VERSION@.tar.bz2
+</pre>
+To start the script type:
+<pre>
+cd mbsebbs-@VERSION@
+bash ./SETUP.sh
+</pre>
+Ubuntu users should do:
+<pre>
+cd mbsebbs-@VERSION@
+sudo bash ./SETUP.sh
+</pre>
+Yes, use <b>bash</b> as shell here. On some systems root doesn't use  bash
+as login shell, calling the script with bash forces the use of bash.
+The script does the following:
+<ol>
+ <li>Create the group <strong>bbs</strong>
+ <li>Create the user <strong>mbse</strong> On Ubuntu this user is added to the admin group.
+ <li>Create a <strong>.profile</strong> for user <strong>mbse</strong>
+ <li>Create and set owner of directory tree under /opt/mbse
+</ol>
+Then the script will ask you to give a password for user <strong>mbse</strong>
+This password is for system maintenance and for you to make changes to the
+bbs. You will need that frequently but you should not make that password
+easy to guess of course. The script will then continue again:
+<ol start="5">
+ <li>The user <strong>bbs</strong> is added.
+ <li>The password will be removed from user <strong>bbs</strong> This action
+will make changes in /etc/shadow (if you have that) otherwise in /etc/passwd.
+On FreeBSD it uses other tools to modify the master database.
+On NetBSD you have to do that manually, there are no tools to do that.
+ <li>If they don't exist in the file /etc/services the services fido, tfido
+and binkp will be added. 
+ <li>If they don't exist in the file /etc/inetd.conf the internet protocols
+for the mailer will be added. The <strong>inetd</strong> is restarted to
+activate the changes. If your distribution uses xinetd instead of inetd, an
+include file for xinetd is added instead.
+</ol>
+<p>&nbsp;<p>
+
+<h3>Step 3: Check the basic installation</h3>
+<p>
+The last screen of the script is about sanity checks. Perform those checks!
+If something is wrong, now is the time to fix it. Don't panic and remember
+the backups of the system files that are changed are in /etc with the 
+extension <strong>.mbse</strong> i.e: those were the original files.
+The installation logfile is copied to /opt/mbse.
+If everythings is allright, then remove the directory /tmp/mbsebbs-@VERSION@:
+<pre>
+cd /tmp
+rm -Rf mbsebbs-@VERSION@
+</pre>
+<p>&nbsp;<p>
+
+<h3>Step 4: Install the basic packages.</h3>
+<p>
+Login as user <b>mbse</b>. Yes, very important, <b>login as user mbse</b>.
+While in mbse's home directory (/opt/mbse) unpack the distribution archives:
+<pre>
+tar xfvj /path/to/mbsebbs-@VERSION@.tar.bz2
+</pre>
+You now have the subdirectory with sources in the right place. 
+Next build the binaries and install them using the following commands:
+<pre>
+cd ~/mbsebbs-@VERSION@
+./configure [--enable-optimize] [--enable-newsgate] [--enable-gdkdel]
+make
+su        <b>important, do not use "su -"</b>
+password: <em>enter root password here</em>
+make install
+exit
+</pre>
+Ubuntu users should do:
+<pre>
+cd ~/mbsebbs-@VERSION@
+./configure [--enable-optimize] [--enable-newsgate] [--enable-gdkdel]
+make
+sudo make install
+</pre>
+<b>Important:</b> it seems logical to use the <code>--enable-newsgate</code> option
+but it isn't. When you do, the mbnntp program is disabled and you cannot serve
+echomail as news to your users via internet. But you can gate echomail to the
+internet. Independant of your choice, you can allways make internet news available 
+for your bbs users. Only use --enable-newsgate if you really need to gate echomail
+to the internet.
+<p>
+To support Chinese the DELete key needs to be changed because it conflicts with one
+of the characters. If you want to use Chinese, use <code>--enable-gbkdel</code>
+to configure.
+<p>
+The last part of the installation procedure shows you the location of the bbs
+startup script that is added to your system. Remember this one for a moment.
+Because this is your first
+time installation, example menus and example textfiles are installed. 
+If they already exist on your systems (when you do an upgrade) they
+will not be installed again.
+<p>
+Now start the bbs for the first time (still as root) by executing the startup
+script you just saw on the screen followed by a space and the word <b>start</b>.
+For example:
+<pre>
+/etc/rc.d/init.d/mbsed start
+</pre>
+Ubuntu users do:
+<pre>
+sudo /etc/init.d/mbsebbs start
+</pre>
+This will start the <b>mbtask</b> daemon.
+After that the bbs will be opened for use.
+Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems.
+The first time <b>mbtask</b> is started on your system it will create a 
+lot of new configuration files with default settings.
+<p>&nbsp;<p>
+
+<h3>Step 5: Ready.</h3>
+<p>
+Now you have shell scripts in ~/etc, most of them are called by cron, some
+are called during system startup and shutdown. You also have some default
+configuration files, these are ttyinfo, modems, fidonet networks. In the
+default (english) directory you now have default menu datafiles and ansi
+screens. These are copies of my test system so you have to edit them to
+build your own bbs.<br>
+Editing ansi screens can be done on a GNU/Linux system with one of the
+following packages:
+<ol>
+ <li><strong>duhdraw</strong>, this is available from 2:280/2802 as 
+     <strong>duhdraw.tgz</strong> (68 Kbytes). 
+     The binaries are included in this archive, if you compile it yourself 
+     it may give trouble so if the binaries work, use these.</li>
+ <li><strong>bmdraw</strong> This editor is available from 
+     <A HREF="http://www.drastic.net/bmdraw/">http://www.drastic.net/bmdraw/</A>,
+     you can find the tar.gz file in 
+     <A HREF="http://www.drastic.net/bmdraw/files/bmd022.tgz">http://www.drastic.net/bmdraw/files/bmd022.tgz</A>, 
+     it's about 36 Kbytes. This is also a thedraw clone for Linux. 
+     Note, at my system I needed to run it as root.</li>
+ <li><strong>TetraDraw</strong> This is a very nice Ansi editor, you can
+     get this file as TETR~VC#.TGZ from 2:280/2802. The file is 157 Kbytes.
+</ol>
+You may also want to edit ~/etc/header.txt and ~/etc/footer.txt, these
+files are the top and bottom of the newfiles/allfiles listings.
+<P>
+Now the basic environment is finished, the next thing to do is
+<a href="setup/index.htm">configure the bbs</a>.
+<P>&nbsp;<P>
+
+<a href="index.htm"><img SRC="images/b_arrow.png" ALT="Back to Index" BORDER=0>Back to Index</a>
+
+</blockquote>
+</body>
+</html>

html/dist.html

@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: dist.html,v 1.13 2007/09/12 18:25:31 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Unix distributions.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align="right"><h5>Last update 12-Sep-2007</h5></div>
+<div align="center"><H1>Unix Distributions.</H1></div>
+
+<H3>Which distribution</H3>
+<P>
+GNU/Linux is available in several distributions, they all have advantages and 
+disadvantages for bbs use. Which distribution to pick is very personal.
+Since late 2001 a port to FreeBSD is available, from version 0.33.19 this
+port is ready to use.
+Since januari 2002 a port to NetBSD is available, later other *BSD versions
+were added.
+<P>&nbsp;<P>
+
+<H3>Slackware</H3>
+<P>
+I am using MBSE BBS on several Slackware distributions. You can make a very small
+setup for MBSE BBS like Zipslack. Not included is the mgetty package.
+<P>&nbsp;<P>
+
+<H3>Redhat and Mandrake</H3>
+<P>
+I write this as if these are the same which isn't true of course. From MBSE
+BBS's point of view they are almost the same, so that's why I treat them as
+the same distributions. The E-Smith server and gateway based on RedHat is also
+supported.
+For people with little GNU/Linux experience these 
+distributions are a good choice if you can spare the diskspace. I haven't
+found a simple dedicated setup for the bbs, so the safest way is to install
+allmost everything, which is quite simple. This will cost you about 1200 Megs.
+Maybe that someone more experienced with these distro's can give more details
+on how to build a small server.
+<P>&nbsp;<P>
+
+<H3>SuSE</H3>
+<P>
+Since SuSE 7.1 the setup scripts are working and tested. Older distro's
+might work.
+<P>&nbsp;<P>
+
+<H3>Debian</H3>
+<P>
+The installation works on a Debian 2.1, 2.2 and 3.0 distribution without any problems.
+How to build an optimized Debian system is not tested by me.
+<P>&nbsp;<P>
+
+<H3>Ubuntu</H3>
+<P>
+Since 0.91.10 the installation on Ubuntu 7.04 works fine. Read the file README.Ubuntu in
+the source for more information.
+<P>&nbsp;<P>
+
+<H3>GenToo</H3>
+<P>
+Installation and startup scripts are tested on GenToo. Read the file README.Gentoo for
+more information.
+<P>&nbsp;<P>
+
+<H3>FreeBSD</H3>
+<P>
+I tested on FreeBSD 6.2 stable release. Older releases have been used and work.
+The setup is quite simple, do a small setup (average user), and add some needed packages
+from the ports collection such as gcc, mgetty, infozip etc.
+You may need to build mgetty yourself if you have an older FreeBSD distribution.
+<P>&nbsp;<P>
+
+<H3>NetBSD</H3>
+<P>
+Currently NetBSD 3.1 is used for the latest tests. NetBSD before 3.0 doesn't
+work anymore.
+<P>&nbsp;<P>
+
+<H3>OpenBSD</H3>
+<P>
+Currently OpenBSD 3.7 is used for testing.
+<P>&nbsp;<P>
+
+<H3>Famous last words...</H3>
+<P>
+I don't have the diskspace and time for all kinds of GNU/Linux distributions
+to install for testing. Most distributions work without major changes. For
+questions about "unsupported" distributions, the best place to be is in the
+MBSE support echo.
+<P>&nbsp;<P>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/doors.html

@@ -0,0 +1,229 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: doors.html,v 1.10 2004/11/05 11:53:47 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Running DOS doors on MBSE BBS.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 05-Nov-2004</h5></div>
+<div align='center'><H1>MBSE BBS - Running DOS doors.</H1></div>
+
+<h3>Introduction</h3>
+<p>
+Running DOS doors is possible on systems that can run 
+<a href="http://www.dosemu.org">dosemu</a>. The latest versions of dosemu don't
+need to be started suid root or started using sudo, it can run as the user that
+is logged in the bbs. Since that is possible, a new location for the virtual C:
+drive is now being used withing the $MBSE_ROOT file structure. This virtual C:
+drive is owned by the group bbs. The basic ideas how doors should be run written
+by Redy Rodriguez are still valid, but some scripts are changed and some dosemu
+files must be copied into the mbse directory tree.<p>
+<em>One very important note: the virtual dos drive is now $MBSE_ROOT/var/dosemu/c
+Don't use another location or change the access rights, there will be several 
+references from mbse to that and only that location for dos support. 
+Choose another one and you are on your own!</em>
+<p>&nbsp;<p>
+
+<h3>Installing dosemu</h3>
+<p>
+Some distributions have good dosemu packages, others don't. You need a dosemu
+that can be used in a systemwide multiuser setup. The bad packages want to have
+the dos drive in each users home directory, this is not what we want for doors.
+If you don't have a good dosemu you have to compile your own. This is not too
+complicated. First download the source from <a
+href="http://www.dosemu.org">dosemu</a>. You don't need the freedos-bin source
+if you are going to use ms-dos or pc-dos. 
+Unpack the source in some directory of your choice and compile the sources:<br>
+<pre>
+mbse@seaport$ tar xfvz dosemu-1.2.2.tgz
+mbse@seaport$ cd dosemu-1.2.2
+mbse@seaport:~/dosemu-1.2.2$ ./configure --prefix=/usr --sysconfdir=/etc/dosemu --with-x
+mbse@seaport:~/dosemu-1.2.2$ make
+</pre>
+Note that the <code>--with-x</code> is not needed for running doors, but it
+might be handy that you can use dosemu as user mbse in X to do maintenance on
+your doors.<br>
+Then as root do:<br>
+<pre>
+root@seaport:~/dosemu-1.2.2# make install
+</pre>
+<p>&nbsp;<p>
+
+<h3>Setup dosemu in mbse</h3>
+<p>
+First copy <code>/etc/dosemu/dosemu.conf</code> into <code>~/etc/dosmeu</code>.
+Then edit <code>~/etc/dosemu/dosemu.conf</code> so that we have a version for
+mbse users. Set the following settings in that file:<br>
+<pre>
+$_hdimage = "/opt/mbse/var/dosemu/c"
+$_floppy_a = ""
+$_xms = (1024)
+$_ems = (2048)
+$_dpmi = (0x1000)
+$_layout = "us"
+</pre>
+Next copy this new file as <code>virtual.conf</code> in
+<code>~/etc/dosemu/</code>. Then add the following line:
+<pre>
+$_com1 = "virtual"
+</pre>
+Note that in older dosemu versions you could use a commandline option to do
+this, but this isn't supported anymore since dosemu-1.2.x. The
+<code>rundoor.sh</code> now also uses two configuration files.<br>
+Next we need to setup the C: drive. Do this as user mbse. First type <code>umask
+007</code>, this sets the create mode for directories to 0770 and files to 0660
+so that we create all files and directories read/write for all bbs users. This
+is very important! Type the following commands:
+<pre>
+mbse@seaport:~$ umask 007
+mbse@seaport:~$ cd var/dosemu/c
+mbse@seaport:~/var/dosemu/c$ mkdir dos dosemu temp util doors
+</pre>
+Now we must install dos. If you use ms-dos then in <code>~/var/dosemu/c</code>
+copy the ms-dos files <code>command.com</code>, <code>io.sys</code> and
+<code>msdos.sys</code>. In <code>~/var/dosemu/c/dos</code> copy all ms-dos
+commands. Next install the dosemu utilities, copy these from
+<code>/usr/share/dosemu/freedos/dosemu</code> to
+<code>~/var/dosemu/c/dosemu</code>. Now there is a empty
+<code>~/var/dosemu/c/util</code>, copy some utilities here such as your
+favourite dos editor, zip and unzip etc.<br>
+Next we must create <code>config.sys</code> and <code>autoexec.bat</code>. These
+files must be dos crlf formatted. You can do that with the joe editor, for
+example <code>joe -crlf config.sys</code>. Examples:<br>
+<pre>
+config.sys:
+
+BUFFERS = 20
+DEVICE=C:\DOS\SETVER.EXE
+SET TEMP=C:\TEMP
+DOS=HIGH,UMB
+FILES=50
+
+autoexec.bat:
+
+@ECHO OFF
+PROMPT $P$G
+PATH C:\DOSEMU;C:\DOS;C:\UTIL;
+SET TEMP=C:\TEMP
+Lh C:\DOS\DOSKEY /INSERT
+Lh C:\DOS\SHARE
+</pre>
+Now we are ready to try it, type <code>mbsedos</code> and the dos emulator
+should start. You can leave dosemu with the command <code>exitemu</code>.
+<p>&nbsp;</P>
+
+<h3>Installing a door</h3>
+<p>
+All doors are started using the script <code>~/bin/rundoor.sh</code>. This script
+is never started directly, you should make a copy of that with the name of the
+door, but the best solution is to make a symlink with the name of the door. For
+example:<br>
+<pre>
+mbse@seaport$ cd ~/bin
+mbse@seaport:~bin$ ln -s rundoor.sh 8ball
+</pre>
+See also inside <code>rundoor.sh</code> for the instructions. This file does
+several things, first it prepares the users home directory with the dosemu
+environment so that dosemu will run for the user. Then it creates a node
+directory in the dos C: drive and copies the door dropfiles into that node
+directory. Finally it starts dosemu in virtual comport mode and inserts the
+commands in dos to start the door.<br>
+But before we can run the door, the door itself must be installed in the dos
+partition. In this example I will explain how to install the door 8ball.
+Start <code>mbsedos</code> and create a directory <code>c:\doors\8ball</code>.
+Unpack 8ball in that directory and run <code>setup</code>. Test the door with
+the command <code>local</code>. Now goto the directory <code>c:\doors</code> and
+create the file <code>8ball.bat</code>. That file will be used to start the
+door. It will be called by <code>c:\doors.bat</code> with two parameters, the
+name of the door and the nodenumber.
+<pre>
+@ECHO OFF
+C:
+C:\UTIL\X00 E B,0,57600
+CD \DOORS\8BALL
+ASKME.EXE /E /C1 /PC:\DOORS\NODE%1
+C:\UTIL\X00
+CD \DOORS\NODE%1
+DEL DOOR.SYS
+DEL DOOR32.SYS
+</pre>
+Finally we have to make a menu entry to start the door. The Opt. Data line is
+the command to start the door, the optional <code>/N</code> is replaced by the
+current nodenumber of the user. A second option may be used,
+<code>novirtual</code>, if that is present the <code>rundoor.sh</code> will
+start dosemu without setting the comport in virtual mode. Use this if your door
+isn't a real door but a normal dos program.
+<p>
+<img src="images/doors.png" alt="door setup" border="0"><p>
+Note that I use the
+Display lines to make the menu, there are only ansi screens for the top and
+common lines on the screen, see the second image how to build the whole doors
+menu.
+<p>
+<img src="images/doors2.png" alt="doors menu" border="0">
+<p>
+<p>&nbsp;<p>
+
+<h3>Netmail support</h3>
+<p>
+In the virtual c: drive you need some directories that point to several other
+mbse subdirectories. You may need at least three of them, one to put netmail in,
+one to put files in to send and one semafore directory to tell mbse there is
+something to send. For example like this:
+<pre>
+ln -s /opt/mbse/var/msgs /opt/mbse/var/dosemu/c/msgs
+ln -s /opt/mbse/var/boxes/node92_100_60 /opt/mbse/var/dosemu/c/outbox
+ln -s /opt/mbse/var/sema /opt/mbse/var/dosemu/c/sema
+</pre>
+In dos you now have:
+<pre>
+C:\MSGS
+C:\OUTBOX
+C:\SEMA
+</pre>
+In <code>C:\MSGS</code> doors may put *.msg netmails. 
+File attaches won't work from these netmails because the netmails
+point to files with dosnames. (May be solved later). The script that calls the
+door, for example <code>c:\doors\bre.bat</code> must copy the file to send to
+the node outbound box. In the above example that would be copy to 
+<code>C:\OUTBOX</code>.
+To create the semafore to tell mbse to scan add to the batfile (for example
+<code>C:\DOORS\BRE.BAT</code> the following two lines:
+<pre>
+CD C:\SEMA
+ECHO ""&gt;MAILOUT
+</pre>
+See also the <a href="faq.html#_Doors">F.A.Q.</a> for some very usefull tips and
+tricks.
+Using the same method with symlinks, you can make all paths you need from the
+rest of mbse visible in dos. Use with care.
+<p>&nbsp;<p>
+
+<h3>What if I don't upgrade</h3>
+<p>
+That's your choice, but for a while the old method starting dosemu via sudo is
+still supported. The file <code>~/bin/bbsdoor.sh</code> is still there, but the
+file <code>~/bin/rundoor.sh</code> is renamed to
+<code>~/bin/runvirtual.sh</code>. So you should change all symlinks of your door
+names in <code>~/bin</code> (or copies) to <code>~/bin/runvirtual.sh</code>. You
+should not need to change anything else.
+<p>
+
+<h3>Problems</h3>
+<p>
+Currently there are some troubles with modem calls.
+<p>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/errcodes.html

@@ -0,0 +1,83 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: errcodes.html,v 1.3 2005/06/30 18:33:01 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Error return codes.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 30-Jun-2005</h5></div>
+<div align='center'><H1>MBSE BBS - Error return codes.</H1></div>
+
+
+<P>
+Following is a list of return codes from all official mbse programs and
+utilities. These codes can be used in scripts. If a program exits normally, the
+return code is 0. If a program exits by a signal, the return code is the signal
+number. This means if you kill a running program with a SIGTERM, the programs
+exits with the SIGTERM error number. On most platforms this is 15. These
+errorcodes are for the most part the same on all *nix platforms but because of
+some small differences I cannot list these here. Just do a <b>kill -l</b> to see
+a list of errors for your own platform.<br>
+Here is the list of other return codes:
+<OL start="100">
+ <LI>Commandline error
+ <LI>Configuration error
+ <LI>Initialisation error
+ <LI>A full disk partition
+ <LI>UPS alarm detected
+ <LI>No valid recipients
+ <LI>Execute external program failed
+ <LI>Set tty failed
+ <LI>File transfer error
+ <LI>File attach failed
+ <LI>Can't lock program, retry later
+ <LI>Node not in nodelist
+ <LI>Node may not be called
+ <LI>Can't make connection
+ <LI>Can't open tty port
+ <LI>Node is locked
+ <LI>Node IP address not found
+ <LI>Unknow session type
+ <LI>Not Zone Mail Hour
+ <LI>Modem error
+ <LI>No modemport available
+ <LI>Session error (password)
+ <LI>EMSI session error
+ <LI>FTSC session error
+ <LI>WaZoo session error
+ <LI>YooHoo session error
+ <LI>Outbound scan error
+ <LI>Can't make poll
+ <LI>File request error
+ <LI>Error processing nodediff
+ <LI>Virus found
+ <LI>General error
+ <LI>Timeout error
+</OL>
+<P>
+The mailer can also return the following error codes:
+<OL start="201">
+ <LI>TTY general error
+ <LI>TTY timeout
+ <LI>TTY EndOfFile
+ <LI>TTY Hangup
+ <LI>TTY Empty
+</OL>
+<P>
+When an external program is run, a mbse program can exit with return code 256 +
+the return code of the external program. So if the external program exits with
+error code 7, the code returned by the mbse program is 263.
+<P>
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/flow.html

@@ -0,0 +1,180 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: flow.html,v 1.11 2007/03/01 19:12:54 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Running a BBS under Unix.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 01-Mar-2007</h5></div>
+<div align='center'><H1>Running a BBS under Unix.</H1></div>
+
+<h3>Introduction</H3>
+<P>
+Everyone who has been running a (single line) BBS under DOS until now will
+need to understand that running a BBS under Unix (or any other multitasking
+os) is completly different of what you are used to. Under DOS things were
+quite simple, from AUTOEXEC.BAT you started a new .BAT file that would run
+forever and started all needed programs after each other. 
+The programs that where started 
+depended on the errorlevel of the previous program. Only one program could
+run at the same time.
+<P>
+People who had previous run a BBS on another multitasking os, or were running
+a BBS on a small lan with a fileserver and workstations for each line, are
+already more used to the idea of running more programs at the same time,
+and to "signal" what to do next with semafore files.
+<P>
+The Unix aproach is more or less the same, but there are more differences.
+The main difference is that there is no mailer connected with the modem waiting
+for a call, instead there is a getty process watching your modem(s). And for
+internet calls, these are started via (x)inetd using standard *nix methods.
+Another
+big difference is that you don't see what's happening, there is no screen
+with the mailer or bbs picture on it. All programs run in the background. If
+you don't like that, stop now and go back to your old DOS bbs. It's just the
+way everything is done.
+<P>
+Programs that must start at specific times (events in DOS), are started from
+cron, this is the event scheduler for Unix. With this
+program maintenance can be started, polls created etc. For starting programs
+when they are needed there is a taskmanager loaded at system bootup. This
+taskmanager "watches" the semafore directory of the bbs and will start what
+is needed. It will also watch the mailer outbound to see if there are nodes
+to call.
+<P>&nbsp;<P>
+
+<H3>Waiting for a call .....</H3>
+<P>
+Under Unix this is done with the mgetty program, this is the 
+process that is connected with each modem (or ISDN adapter) and waits for a
+call. The mgetty program (written by Gert Doering, gert@greenie.muc.de) will
+detect the call, and find out what or who did make the call. It can detect
+incoming humans who want a login prompt, PPP calls from users who want to
+make a PPP connection (browsing your BBS whith netscape for example), A fax
+machine trying to deliver a fax and finally a mailer trying to establish
+an EMSI, FSC-0006 or FSC-0001 session. The mgetty program is responsible for
+starting the right client programs. How to do this is explained in the 
+installation manuals, but be sure to compile it with Fido and PPP support.
+<P>
+For internet calls, via (x)inetd mbsebbs can accept calls from connections on
+ports. For example if a connection comes in on port 24554 the mailer is started
+in binkp mode.
+<P>&nbsp;<P>
+
+<H3>A Human is calling.</H3>
+<P>
+This could be a bbs user. For each user to login to your bbs there is a
+unix account. They automatic create such an account the first time they login
+with the <b>bbs</b> account. During the creation of their account the shell that is
+installed for there account is the mbsebbs binary, so that's the only thing
+that they get if they call in. When they logout the bbs, or drop carrier etc,
+the session is ended and mgetty takes over the line again.
+Note that they never can get a Unix shell unless you install a <b>door</b> 
+in the bbs that calls a shell for them.
+<P>
+Because for dialin with mgetty the mblogin program is used and not the normal
+login program, only bbs users can login. All other users including <b>root</b> are
+denied access.
+You might consider installing SSH on your system for remote maintenance.
+<p>
+It is also possible to install the mblogin program as the login program for
+telnet users if you are directly connected to the internet.
+<P>&nbsp;<P>
+
+<H3>A PPP call is detected.</H3>
+<P>
+Installing a PPP server on your system is beyound the scope of this project.
+However if you did install it, users can login your bbs with their favourite
+browser and use your bbs. Note that the necessary tools to automatic create
+newsgroups don't exist at this time. With the proper setup you can automatic
+create and maintain html pages for the file areas.
+<P>&nbsp;<P>
+
+<H3>A mailer call is detected.</h3>
+<P>
+If a mailer is detected by mgetty, the <b>mbcico</b> program is started and will
+take over from mgetty. It will establish a mail session with the caller and
+the mail and or files will be exchanged just like any DOS mailer would do.
+After the call, mbcico will hangup and mgetty will take control of your modem
+again. If there is any mail received, mbcico will place the semafore <b>mailin</b>
+so that another process can take care of the received mail.
+<P>&nbsp;<P>
+
+<h3>There is mail in the inbound</h3>
+<P>
+As I said before, if the <b>mailin</b> semafore is present, the task manager will
+then start the <b>mbfido</b> program that will toss the mail, process any files 
+received and if necessary it will create other semafore's for example to link 
+the message bases, start the nodelist compiler etc. Note that this can be done 
+while there may be a new mailsession going on, a bbs user is online, it doesn't 
+matter. Processing mail and files can be done real multitasking without any 
+damage to other processes.
+<P>&nbsp;<P>
+
+<H3>It's time to poll a node</h3>
+<P>
+At the time that you whish to poll a node, let cron create "poll" requests.
+When a poll is created, the semafore <b>scanout</b> is also created.
+The taskmanager will then start mbcico at regular intervals so that mail will
+get out. If there is no more mail to send, the <b>scanout</b> semafore is removed.
+If a timeslot ends, you can just remove the "poll" requests that didn't succeed.
+<P>&nbsp;<P>
+
+<H3>It's Zone Mail Hour, so now what</h3>
+<P>
+Relax, if you have netmail ready for nodes the
+mailer script will try to send these mails to those nodes. If it was crash
+mail, and the destination was a non CM node, the mailer will try to send those
+mails too. Note that other crashmails are send anytime. Also note that packed
+mail and files are not send during ZMH. If a node calls you during ZMH he will
+get everything that's waiting, including packed mail and files. The task manager
+(more on that later) calculates the Zone Mail Hour from UTC time, you don't
+have to change anything for summer- and wintertime. The taskmanager knows about
+all zone mail hours of all Fidonet zones (1..6). For othernets, zone mail hour
+is taken from the setup as default value. The taskmanager will also handle the
+mail for nodes with the Txx flag (FSC-0062) on the right times.
+<P>&nbsp;<P>
+
+<H3>Daily maintenane</h3>
+<P>
+This is started by cron jobs. There is no need to take
+your bbs lines down during maintenance, you can do it any time of the day.
+I have made several scripts for this, daily, weekly and monthly.
+<P>&nbsp;<P>
+
+<h3>How about system load</h3>
+<P>
+Because GNU/Linux is a 32 bit os, not bothered with a graphical user interface
+(unless you install it), it has all the time in the world to serve your
+bbs programs. Background programs are build to release time to the Unix os,
+they don't need to run fast because it's background processing. The bbs and
+the mailer, have a low server load although there is no timerelease build
+in. Only the bbs has some short moments when it needs a lot of your system,
+for example when a user logs in and scans for new mail. The bbs I run is a
+486-DX4 100 MHz, 20 MB ram, with 2 analogue lines, this seems to work fine.
+When this system's MOBO died, I used a 386DX33 for several months with
+20 MB ram, and the only thing users ever noticed was that scanning for new
+mail was slower. I think this is the slowest harware that will work.
+However, you must always use 16550A uarts for the COM ports. For best 
+performance use SCSI disks. I noticed that old 5"FH SCSI disks perform better
+for bbs usage then modern EIDE disks. This is probably caused by the fact that
+the kernel needs more time for the cheap IDE bus.
+If you want to use X11 on your bbs, you need more ram and a faster CPU or a 
+separate machine via a lan and export the display to that machine. Currently the
+smallest amount of memory you need is 36 MB, and that amount is only needed if
+you use a virus scanner which needs more memory then mbse.
+<P>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/ftsc/index.htm

@@ -0,0 +1,97 @@
+<HTML>
+	<!-- $Id: index.htm,v 1.14 2007/03/01 19:23:41 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Fidonet Standard Commitee documents.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align=right><h5>Last update 01-Mar-2007</h5></div>
+<div align=center><h1>Fidonet Technical Standards</h1></div>
+
+<h3>Introduction</h3>
+<P>
+This is an overview of used documents for the development of the MBSE BBS 
+package. Note that there are more documents, but only the relevant and valid
+documents are shown present here. The documents are not available in this
+distribution anymore, you can get these from the <a href="http://www.ftsc.org">FTSC</a>
+website.
+<P>
+Michiel Broek.
+<P>
+
+<hr>
+<h3>FSC Documents</h3>
+<ul>
+ <li>FSC-0035 Transparant Gateways to and from FidoNet, Michael Shiels
+ <li>FSC-0039 A type-2 packet extension proposal M.Howard
+ <li>FSC-0046 A Product Identifier for FidoNet Message Handlers, J.Homrighausen
+ <li>FSC-0048 A Proposed type-2 packet extension, J.Vroonhof
+ <li>FSC-0049 A proposal for passing domain information during FTS-0006 sessions, B.Hartman
+ <li>FSC-0050 A character set identifier for FidoNet message editors, T.Sundblom
+ <li>FSC-0053 Specifications for the ^aFLAGS field, J.Homrighausen
+ <li>FSC-0056 EMSI/IEMSI Protocol Definition, J.Homrighausen
+ <li>FSC-0057 Conference Managers - Specifications For Requests, F.Fabris, J.Homrighausen
+ <li>FSC-0059 Newsgroup Interchange within FidoNet, J.Decker
+ <li>FSC-0062 Nodelist Flag indicating Online Times, D.Thomas
+ <li>FSC-0070 Improving FidoNet/UseNet Gating and Dupe checking, F.Arnoud
+ <li>FSC-0072 The HYDRA file transfer protocol, J.Homrighausen, A.Lenz
+ <li>FSC-0087 File forwarding in FidoNet technology networks, R.Williamson
+ <li>FSC-0088 Compatibility and Link Qualifier Extensions for EMSI Sessions, R.Williamson
+ <li>FSC-0091 ISDN nodelist flags (rev.002), A.Lenz
+ <li>FSC-0093 Reduced seen-by lines, F.Ellermann
+</ul>
+
+<P>
+
+<h3>FSP Documents</h3>
+<ul>
+ <li>FSP-1011 BinkP - a protocol for transferring Fidonet mail over reliable connections, Dima Maloff
+ <li>FSP-1013 Character set definition in Fidonet messages
+ <li>FSP-1018 Binkp/1.0 Protocol specification
+ <li>FSP-1019 Binkp 1.0 optional protocol extension CRAM
+ <li>FSP-1026 Translation of a Fidonet Address into an Internet Domain Name
+ <li>FSP-1030 Unicode character set in FidoNet messages
+ <li>FSP-1032 Binkp optional protocol extension Dataframe Compression
+ <li>FSP-1033 The ICM Flag
+</ul>
+
+
+<P>
+<h3>FTA Documents</h3>
+<ul>
+ <li>FTA-1005 FTSC Product ID
+ <li>FTSC Product codes list
+</ul>
+
+
+<P>
+<h3>FTS Documents</h3>
+<ul>
+ <li>FTS-0001 A basic FidoNet(r) technical standard, R.Bush
+ <li>FTS-0004 Echomail specification, B.Hartman
+ <li>FTS-0006 YOOHOO and YOOHOO/2U2, V.Perriello
+ <li>FTS-0007 SEAlink protocol extension, P.Becker
+ <li>FTS-0008 Bark file-request protocol extension, P.Becker
+ <li>FTS-0009 Message identification and reply linkage, J.Nutt
+ <li>FTS-1024 Raw ifcico mail transfer protocol
+ <li>FTS-4001 Addressing Control Paragraphs, Goran Eriksson
+ <li>FTS-4008 Time zone information (TZUTC)
+ <li>FTS-4009 Netmail tracking (Via)
+ <li>FTS-5000 The distribution nodelist, David Hallford
+ <li>FTS-5001 Nodelist flags and user flags, David Hallford
+</ul>
+
+<HR>
+
+<A HREF="../index.htm"><IMG SRC="../images/b_arrow.png" ALT="Index" Border="0">Back to Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/index.htm.in

@@ -0,0 +1,140 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: index.htm.in,v 1.13 2007/03/01 19:12:54 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Running a BBS under Linux.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<center><img SRC="images/mbse.png" BORDER=0 alt="MBSE"></center>
+<div align=center><h1>MBSE BBS System Guide @VERSION@</h1></div>
+<div align=right><h5>Last update 01-Mar-2007</h5></div>
+
+
+<h3><a NAME="top"></a>Introduction</h3>
+
+<A HREF=images/mbsebbs.png><IMG SRC="images/mbsebbs-s.png" align=right alt='Screenshot'></A>
+
+<ul>
+  <li><a href="intro.html">Introduction to MBSE BBS</a></li>
+</ul>
+<P>&nbsp;<P>
+
+<h3>Release Notes</h3>
+
+<ul>
+  <li><a href="known_bugs.html">Known Bugs</a></li>
+  <li><a href="license/index.htm">Licenses</a></li>
+</ul>
+<P>&nbsp;<P>
+
+<h3>MBSE BBS Reference Manual</h3>
+
+<ol>
+  <li><a href="flow.html">Running a BBS under Linux</a></li>
+  <li><a href="dist.html">Which distribution to use</a></li>
+  <li><a href="basic.html">Basic installation MBSE BBS</a></li>
+  <li><a href="upgrade.html">Upgrade MBSE BBS</a></li>
+  <li><a href="setup/index.htm">Configuring the bbs with mbsetup</a>
+  <ol>
+  <li><A HREF="setup/global.html">Edit Global configuration</a>
+  <li><A HREF="setup/fidonet.html">Edit Fido networks</a>
+  <li><A HREF="setup/archiver.html">Edit Archiver programs</a>
+  <li><A HREF="setup/virscan.html">Edit Virus scanners</a>
+  <li><A HREF="setup/modems.html">Edit Modem types</a>
+  <li><A HREF="setup/ttyinfo.html">Edit TTY lines info</a>
+  <li><A HREF="setup/nodes.html">Edit Fidonet nodes</a>
+  <li><A HREF="setup/bbs.html">Edit BBS setup</a>
+   <ol>
+    <li><A HREF="setup/security.html">Edit Security limits</a>
+    <li><A HREF="setup/language.html">Edit Language setup</A>
+    <li><A HREF="menus/index.htm">Edit BBS menus</a>
+    <li><A HREF="setup/files.html">Edit File areas</a>
+    <li><A HREF="setup/protocol.html">Edit Transfer protocols</a>
+    <li><A HREF="setup/oneliner.html">Edit Oneliners</a>
+   </ol>
+   <li><A HREF="setup/mail.html">Edit Mail setup</A>
+   <ol>
+    <li><A HREF="setup/emgroup.html">Echo mail groups</a>
+    <li><A HREF="setup/emareas.html">Echo mail areas</a>
+   </ol>
+   <li><A HREF="setup/tic.html">Edit File echo's setup</a>
+   <ol>
+    <li><A HREF="setup/fegroup.html">Edit Fileecho groups</a>
+    <li><A HREF="setup/fileecho.html">Edit Fileecho areas</a>
+    <li><A HREF="setup/hatch.html">Edit Hatch manager</a>
+    <li><A HREF="setup/magic.html">Edit Magic files</a>
+   </ol>
+   <li><A HREF="setup/newgroups.html">Edit Newfiles groups</a>
+   <li><A HREF="setup/newfiles.html">Edit Newfiles reports</a>
+   <li><A HREF="setup/filefind.html">Edit Filefind setup</a>
+   <li><A HREF="setup/fdb.html">Edit Files database</a>
+   <li><A HREF="setup/users.html">Edit BBS users</a>
+   <li><A HREF="setup/services.html">Edit Services</a>
+   <li><A HREF="setup/domains.html">Edit Domains</A>
+   <li><A HREF="setup/taskmgr.html">Edit task manager</A>
+   <li><A HREF="setup/route.html">Edit Routing Table</a>
+   <li><A HREF="setup/chat.html">Edit Internet BBS Chat</A>
+   <li><A HREF="setup/softinfo.html">Show software information</a>
+   <li><A HREF="setup/sitedoc.html">Create site documents</a>
+  </ol></li>
+  <li><a href="invoking.html">Starting and Stopping the BBS</a></li>
+  <li><a href="mgetty.html">Setup mgetty for the BBS</a></li>
+  <li><a href="programs/index.htm">Programs and utilities</a>
+  <ol>
+    <li><a href="programs/mbaff.html">mbaff, Announce newfiles and filefind</a></li>
+    <li><a href="programs/mball.html">mball, Allfiles and newfiles list creator</a></li>
+    <li><a href="programs/mbcico.html">mbcico, The Fidonet mailer ala ifcico</a></li>
+    <li><a href="programs/mbdiff.html">mbdiff, Nodelist difference processor</a></li>
+    <li><a href="programs/mbfido.html">mbfido, Fidonet mail and files procesor</a></li>
+    <li><a href="programs/mbfile.html">mbfile, Files database maintenance program</a></li>
+    <li><a href="programs/mbindex.html">mbindex, Nodelist index compiler</a></li>
+    <li><a href="programs/mblang.html">mblang, Language datafile compiler</a></li>
+    <li><a href="programs/mblogin.html">mblogin, Unix login replacement</a></li>
+    <li><a href="programs/mbmon.html">mbmon, The monitor program</a></li>
+    <li><a href="programs/mbmsg.html">mbmsg, The messagebase utility program</a></li>
+    <li><a href="programs/mbnntp.html">mbnntp, The news server</a></li>
+    <li><a href="programs/mbout.html">mbout, The mailer outbound program</a></li>
+    <li><a href="programs/mbpasswd.html">mbpasswd, The passwd wrapper</a></li>
+    <li><a href="programs/mbsebbs.html">mbsebbs, The bbs program</a></li>
+    <li><a href="programs/mbseq.html">mbseq, Sequence number creator</a></li>
+    <li><a href="programs/mbsetup.html">mbsetup, The setup program</a></li>
+    <li><a href="programs/mbstat.html">mbstat, The bbs status change program</a></li>
+    <li><a href="programs/mbtask.html">mbtask, The taskmanager for the bbs system</a></li>
+    <li><a href="programs/mbtoberep.html">mbtoberep, The toberep.data lister</a></li>
+    <li><a href="programs/mbuser.html">mbuser, The userbase maintenance program</a></li>
+    <li><a href="programs/mbuseradd.html">mbuseradd, The useradd wrapper</a></li>
+  </ol></li>
+  <li><a href="routing.html">Netmail routing behaviour</a></li>
+  <li><a href="intergate.html">Fido to Internet Gateway</a></li>
+  <li><a href="postfix.html">Email Gateway - Postfix setup.</a></li>
+  <li><a href="nodelist.html">Nodediff and Nodelist processing</a></li>
+  <li><a href="ups.html">Using UPS semafore's</a></li>
+  <li><a href="doors.html">Running DOS doors on MBSE BBS</a></li>
+  <li><a href="errcodes.html">Error return codes</a></li>
+</ol>
+<P>&nbsp;<P>
+
+<h3>Other Notes</h3>
+
+<ul>
+  <li><a href="faq.html">Frequently Asked Questions</a></li>
+  <li><a href="ftsc/index.htm">Fidonet Standard Commitee documents</a></li>
+  <li><a href="misc/index.htm">Miscellaneous documents</a></li>
+</ul>
+
+<hr>
+<a href=".."><img SRC="images/b_arrow.png" ALT="Back" BORDER=0>Back</a>&nbsp;
+<a href="#top"><img SRC="images/uarrow.png" ALT="Top" BORDER=0>Top</a>
+</blockquote>
+
+</body>
+</html>

html/intergate.html

@@ -0,0 +1,106 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: intergate.html,v 1.8 2003/11/09 14:46:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS - Internet gateway.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 10-May-2002</h5></div>
+<div align='center'><H1>MBSE BBS - Internet Gateway.</H1></div>
+
+<H3>Introduction.</H3>
+<P>
+Since version 0.33.14 the email gateway is build into MBSE BBS and since
+version 0.33.15 the newsgateway is build into MBSE BBS. Since version 0.33.16 the
+newsgateway to UUCP nodes is added. To route
+email trafic to and from the internet you need a internet MTA. I stopped using 
+<strong>sendmail</strong> for this because it gave too much trouble setting it
+up together with MBSE BBS. 
+Today I use <A HREF="http://www.postfix.org">Postfix</A>,
+a well documented, secure and easy to setup MTA. For the actual gate from
+Postfix to the BBS you I use <b>mbmail</b> which you need to add to the 
+Postfix configuration.<P>
+<P>
+There may be two reasons to create a gateway, one is to gate internet news and
+email to the Fidonet bbs users, another reason may be that you want to make
+echomail as news available on your system so that users can connect to your 
+bbs with their favourite browser an get the mail and news using pop3 and
+nntp protocols. The setup is the same for both reasons so I will make one
+description for the whole setup.
+<P>&nbsp;<P>
+
+<H3>Setup a newsgate node with inn.</H3>
+<P>
+If you only want to gate internet news to your bbs users and not want to
+make echomail available as news, and you have a permament internet connection
+then you don't need your own news server. This will also work on dialup links,
+once the internet connection is up, make sure that <b>mbfido news -quiet</b> is
+started as user mbse.
+To do this configure MBSE BBS to use the newsserver of your ISP in screen 1.15 
+with mbsetup. 
+If you don't want to use the newsserver of your ISP or want to make echomail
+available as news for your local users you must install your own newsserver.
+You could use <A HREF="http://www.isc.org">inn news</A> for a newsserver.
+To connect a small feed with your ISP you could use <strong>suck</strong>.
+<P>
+In each echomail area you want to gate you need to fill in the newsgroup
+name of that area and echomail received in that area will automatic be 
+posted to that newsgroup. The command <b>mbfido news</b> will check all
+configured newsgroups for new newsarticles. If you set it up for the first
+time you need to run <strong>mbfido news -learn</strong> to fill the dupes
+database for news with all the already existing news articles. If you skip
+that, you may get a lot of old articles that will be gated. Just run that
+command once after you have set this up. Later when you receive fresh articles
+the command <strong>mbfido news</strong> will only gate new arrived articles.
+In each mail area you can set the number of articles to get in one run. If you
+set this too high, mbfido will scan all headers on the newsserver for new
+articles. This can cost a lot of time. The best thing to do is to set this value
+about four times higher then the average number of messages per day in that
+group. If you set it too low, warning messages will appear in the logfile.
+<P>&nbsp;<P>
+
+<H3>Setup a newsgate with rnews.</H3>
+<P>
+This is the setup if you don't want an NNTP newsserver like inn, but a simple
+cnews setup for UUCP links only. In <strong>mbsetup</strong> menu 1.15 you need
+to set this up. You need to fill in the path to the rnews program so that
+<strong>mbfido</strong> can post articles to cnews.  MORE INFO NEEDED.
+<P>
+In each echomail area you want to gate you need to fill in the newsgroup
+name of that area and echomail received in that area will automatic be
+posted to that newsgroup.
+<P>&nbsp;<P>
+
+<H3>Setup a newsgate via UUCP.</H3>
+<P>
+With this setup you don't run a local newsserver, only your bbs users and 
+Fidonet links can then use news. You need to install <strong>uucp</strong>
+on your system. With <strong>mbsetup</strong> menu 1.15 you need to set this
+up. Suppose your ISP's nodename is xs4all the you probably need to set the
+UUCP path to <code>/var/spool/uucp/xs4all</code> and the UUCP node to
+<code>xs4all</code>. Your own nodename will be your system's hostname without
+the domain part.
+<P>
+In each echomail area you want to gate you need to fill in the newsgroup
+name of that area and echomail received in that area will automatic be
+posted to that newsgroup.
+<P>&nbsp;<P>
+
+<H3>Setup a email gate.</H3>
+<P>
+See <A HREF="postfix.html">Postfix (email) configuration</A>
+<P>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/intro.html

@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: intro.html,v 1.11 2007/03/01 19:12:54 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Running a BBS under Unix.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align="right"><h5>Last update 01-Mar-2007</h5></div>
+<div align="center"><H1>Introduction to MBSE BBS.</H1></div>
+
+<H3>Distribution.</H3>
+<P>
+These are the only official distribution sites for the mbse bbs package. They are:
+<OL>
+ <LI><A HREF="http://www.mbse.eu">http://www.mbse.eu</A>
+ <LI>fidonet node 2:280/2802 binkp fido.mbse.eu
+</OL>
+If you find mbse bbs on another site it may be out of date. I have no control over these sites.
+New versions of mbse bbs are announced in the fidonet area LINUX_BBS and MBSE
+support echo. On the official fidonet
+nodes you can request the latest version with the magic MBSEBBS. You will then get a zip file,
+in this zip file is the original tar.gz file. This is to let systems who only support 8.3
+filenames to pickup the distribution package.
+<P>&nbsp;<P>
+
+<H3>History.</H3>
+<P>
+At the end of 1997 I was looking for several BBS systems that could run on
+GNU/Linux and it must be capable to run Fidonet mail. After reviewing almost
+all packages that were available at that time I found that there were no
+packages that suited my needs. Some had the plain user interfaces that
+my bbs users were used to but no Fidonet capabilities, others looked
+awfull or were difficult to use by normal bbs users without Unix experience.
+I also didn't want to run shareware anymore, one day you pay for some program,
+and the next day support is over because the writer of that program decided
+to stop development or simply dissapears from the Fidonet stage. With all
+Y2K problems ahead the solution should be Open Software so that you have
+the sources in case something goes wrong.
+One package was very interesting and had the look and feel of RemoteAcces,
+that package was RapidBBS. There was only one problem, it had no Fidonet
+capabilities. I rewrote the data structures and created a deamon that should
+control all bbs acivities. In march 1998 I started writing the mbfido program
+that should handle all Fidonet mail and .tic files. In june 1998 the final
+message base format became JAM using the LoraBBS sources as a guide to create
+the JAM libraries. The original JAMapi was not stable enough to do all the work
+that needed to be done.
+<P>
+In Juli 1998 the first version of MBSE BBS was installed on the bbs I have, 
+on the second line. The first line was running McMail, GEcho and RA on a
+Novell client while on the GNU/Linux box the mars_nwe emulator from Martin Stower 
+was running. In november 1998 mbcico was created from ifcico from Eugene M.
+Crosser. In Januari 1999 it did also compile and run on a Sun Sparcstation 2
+system.
+<P>
+In April 1999 the motherboard of the GNU/Linux server died, I replaced it with
+the MOBO of one of the client machines. From that day on, MBSE BBS became the
+only bbs running on my system, because I was short on serial port boards at
+that time. McMail and RA became history and MBSE BBS was on its own. From that
+day on, updates were almost daily, all users and up and downlinks showed that
+there were plenty of bugs to solve. One month later most problems were solved.
+<P>
+In juli 1999 Jan van de Werken started beta testing MBSE BBS on his system.
+In September 1999 MBSE BBS was public released for the first time.
+<P>&nbsp;<P>
+
+<H3>Is it Y2K ready?</H3>
+<P>
+There have been no problems since 1 januari 2000 with MBSE BBS. I do run
+pktdate by Tobias Ernst in the tosser, this solves problems with incoming
+mail. Due to the internal date format, this program should run until 2038, 
+just as long as Unix/Linux and the internet will function without changing 
+the date format.
+<P>&nbsp;<P>
+
+<H3>Future plans.</H3>
+<P>
+Plans are to completly integrate www and chat into MBSE BBS. It
+should work for browsers about the same as with ANSI character terminals.
+<P>&nbsp;<P>
+
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/invoking.html

@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: invoking.html,v 1.6 2003/11/09 14:46:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Starting and stopping the BBS.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 06-Jun-2001</h5></div>
+<div align='center'><H1>Starting and Stopping the BBS.</H1></div>
+
+Now it is time to check the starting and stopping of the BBS. As you have
+installed everything, setup the BBS etc, you must check if the shutdown and
+reboot work properly. As root type <strong>shutdown -r now</strong> and
+watch the console. You should see messages that the BBS is closing while
+the systems shuts down. This should be one of the first things to happen.
+Because Slackware up to version 7.0.0 is tricky to automatic install the shutdown scripts,
+you won't see this happen on older Slackware versions. If you want, you can edit
+/etc/rc.d/rc.6 and /etc/rc.d/rc.K and insert the line /opt/mbse/etc/rc.shutdown
+at the proper places.<p>
+
+When your system comes up again, one of the last messages before the login
+prompt appears or just before X-windows starts, you should see messages that
+the BBS is started.<P>
+
+Login as user <strong>mbse</strong> and check the logfiles if everything looks
+good. If something is wrong, reread the previous documentation and check if
+you did everything right.<p>
+
+Next logon to your BBS locally using the account "bbs". 
+You can do that by typing <b>su - bbs</b> or if you already have installed
+<b>mblogin</b> as login replacement for telnet, then type <b>telnet
+localhost</b>.
+You will then create the first user of your BBS, this will be you, the sysop of course. 
+After you logout the BBS start as user <strong>
+mbse</strong> the program <strong>mbsetup</strong> and edit your user record
+to set your level to that of the sysop. One more thing, the unix account you
+must create when you logon as new BBS user may not be <strong>mbse</strong>
+as this is the normal Admin account the BBS and its utilities use.<p>
+
+Now login with your unix account and see if everything still works. 
+If you have setup <strong>mgetty</strong> you may want to test if
+users really can login with a modem. Also check a mailer session, can you
+dialout, ie. poll other nodes and can they call you. There is a lot that can
+go wrong with unix permissions if you are not precise in wat you are doing.<P>
+
+If everything is working it is time to create poll events, and adjust other 
+scripts to your local needs to get your BBS full up and running.<P>
+
+To do this you must install a crontab for user <strong>mbse</strong>.
+As user <strong>mbse</strong> go to the directory <strong>~/mbsebbs-0.33.xx</strong>.
+In that directory type <strong>sh ./CRON.sh</strong> and a default crontab will be installed.<p>
+
+To add poll events, edit the crontab with the command <strong>crontab -e
+</strong> At the bottom of that file there is an example of how to do that.
+Now that the crontab is installed, all maintenance will now work, automatic
+dialout, scanning and tossing mail etc. In other words, the bbs is up and
+running.
+<p>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/known_bugs.html

@@ -0,0 +1,45 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: known_bugs.html,v 1.12 2007/03/01 19:12:55 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Running a BBS under Unix.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 01-Mar-2007</h5></div>
+<div align='center'><H1>MBSE BBS - Known bugs.</H1></div>
+
+There are always more bugs, but these are known....
+
+<UL>
+<LI>Reading of function keys in mbsebbs doesn't work always good, especially on
+slow links and over PPP. This is not a MBSE BBS problem.
+
+<LI>Problems with D'Bridge [1a] mailers.
+
+<LI>If you have regular sessions with a node wich only supports FTS-0001
+sessions and you use a session password you <b>must</b> also set a mail password
+and these passwords must be the same. This is a side effect of the way FTS-0001
+handshake works, by sending a small mail packet wich contains the password.
+
+<LI>Some Linux distributions have their glibc libraries compiled wrong, that
+will cause the <b>mbtask</b> program to do nothing usefull. This problem seems
+to have gone away.
+
+<LI>You cannot share the JAM message bases between little-endian and big-endian
+machines using networked filesystems because the storage format doesn't specify 
+the internal byte order for different CPU's. This is an error in the JAM spec.
+</UL>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/license/copying.html

@@ -0,0 +1,358 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: copying.html,v 1.4 2003/11/08 20:30:09 mbroek Exp $ -->
+<HEAD>
+<TITLE>GNU General Public License.</TITLE>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<PRE>
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                      59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    &lt;one line to give the program's name and a brief idea of what it does.&gt;
+    Copyright (C) 19yy  &lt;name of author&gt;
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19yy name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  &lt;signature of Ty Coon&gt;, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
+</PRE>
+
+<A HREF="./"><IMG SRC="../images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+
+</BODY>
+</HTML>
+

html/license/hydracom.html

@@ -0,0 +1,118 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: hydracom.html,v 1.4 2003/11/08 20:30:09 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<TITLE>Hydracom License.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<PRE>
+                              HydraCom Version 1.00
+
+                         A sample implementation of the
+                   HYDRA Bi-Directional File Transfer Protocol
+
+                             HydraCom was written by
+                   Arjen G. Lentz, LENTZ SOFTWARE-DEVELOPMENT
+                  COPYRIGHT (C) 1991-1993; ALL RIGHTS RESERVED
+
+                       The HYDRA protocol was designed by
+                 Arjen G. Lentz, LENTZ SOFTWARE-DEVELOPMENT and
+                             Joaquim H. Homrighausen
+                  COPYRIGHT (C) 1991-1993; ALL RIGHTS RESERVED
+
+
+  DISCLAIMER
+
+  This program is provided "as is" and comes with no warranties of any
+  kind, either expressed or implied. In no event shall the authors be
+  liable to you or anyone else for any damages, including any lost
+  profits, lost savings or other incidental or consequential damages
+  arising out of the use or inability to use this software.
+
+
+  HYDRACOM / SOURCE LICENSE
+
+  HydraCom, its associated utilities (HydraCfg) and the HydraCom
+  sourcecode may be freely distributed, copied and used, no fee charged.
+  All files, executables and sourcecode remain the copyrighted property
+  of Arjen G. Lentz and LENTZ SOFTWARE-DEVELOPMENT.
+  The distribution archives should remain intact with no files removed
+  or modified. For special purposes, it is allowed to repack the
+  archives using a different compression system.
+
+  HydraCom may be bundled up with for instance terminal or BBS packages,
+  even commercial ones, provided the buyer/user is clearly informed
+  about the fact that Hydra and HydraCom are free, not owned by the
+  distributor/retailer in question, and is not included in any possible
+  charge regarding the rest of the package. This documentation must also
+  be present so the user can inform himself about Hydra and HydraCom.
+  The same rules apply to inclusion in shareware and CD-ROM libraries.
+  In all cases, the author of HydraCom must be given credit in any
+  informational screens and literature that contain such information.
+
+  The Hydra/HydraCom sourcecode may also be freely used and integrated
+  into other software or library, provided this is clearly stated in any
+  informational screens and literature pertaining to this program, and
+  credit is given to the original author. If the sourcecode of that
+  program or library is released or otherwise published, the notices
+  present at the top of every Hydra/HydraCom source file must be
+  retained in their original unmodified form.
+
+  In addition to the above license, everyone using any part of the
+  sourcecode, programs or files is fully bound by the general license of
+  the Hydra protocol as present in the Hydra protocol description
+  document. For easy reference, the paragraph in question is reprinted
+  below.
+
+  Any use of, or operation on (including copying/distributing) any of
+  the above mentioned files implies full and unconditional acceptance of
+  this license and disclaimer.
+
+
+  HYDRA PROTOCOL LICENSE 
+
+  You are granted a license to implement the HYDRA file transfer
+  protocol, HYDRA hereafter, in your own programs and/or use the sample
+  source code and adapt these to your particular situation and needs;
+  subject to the following conditions:
+
+   -  You must refer to it as the HYDRA file transfer protocol, and you
+      must give credit to the authors of HYDRA in any information
+      screens or literature pertaining to your programs that contains
+      other such information (credits, your own copyrights, etc.).
+
+   -  HYDRA will always remain backwards compatible with previous
+      revisions. HYDRA allows for expansion of its features without
+      interfering with previous revisions. It is, however, important
+      that different people do not expand the protocol in different
+      directions. We therefore ask you to contact us if you have any
+      needs/ideas regarding HYDRA, so development can be synchronized
+      and beneficial to all.
+
+   -  If your implementation cannot converse with past or future
+      revisions as supplied by us, then you must refer to it as "HYDRA
+      derived", or as "a variation of HYDRA", or words to that effect.
+
+
+  Hydra protocol design and HydraCom driver:         Hydra protocol design:
+  Arjen G. Lentz                                     Joaquim H. Homrighausen
+  LENTZ SOFTWARE-DEVELOPMENT                         389, route d'Arlon
+  Langegracht 7B                                     L-8011 Strassen
+  3811 BT  Amersfoort                                Luxembourg
+  The Netherlands
+  FidoNet 2:283/512, AINEX-BBS +31-33-633916         FidoNet 2:270/17
+  arjen_lentz@f512.n283.z2.fidonet.org               joho@ae.lu
+
+  Please feel free to contact us at any time to share your comments about our
+  software and/or licensing policies.
+</PRE>
+
+<A HREF="./"><IMG SRC="../images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+
+</BODY>
+</HTML>
+

html/license/index.htm

@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: index.htm,v 1.5 2003/11/08 20:30:09 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Licenses.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 29-Jan-2001</h5></div>
+<div align='center'><h1>Licenses.</h1></div>
+
+<h3>Introduction</h3>
+<P>
+This is an overview of the licenses that are valid for the use of MBSE BBS or
+parts of it. 
+<BR>
+Michiel Broek.
+<P>
+
+<h3>License Documents.</h3>
+<ul>
+ <li><a href="copying.html">GNU General Public License</a>
+ <li><a href="hydracom.html">Hydracom License</a>
+ <li><a href="jam.html">JAM License</a>
+</ul>
+
+
+<A HREF="../index.htm"><IMG SRC="../images/b_arrow.png" ALT="Index" Border="0">Back to Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/license/jam.html

@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: jam.html,v 1.4 2003/11/08 20:30:09 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<TITLE>JAM License.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<PRE>
+    ---------------------------------------------------------------------
+                                  JAM(mbp)
+                The Joaquim-Andrew-Mats Message Base Proposal
+    ---------------------------------------------------------------------
+            Copyright 1993 Joaquim Homrighausen, Andrew Milner,
+                           Mats Birch, Mats Wallin.
+                             ALL RIGHTS RESERVED.
+    ---------------------------------------------------------------------
+
+
+    =====================================================================
+    LEGAL NOTICE
+    ---------------------------------------------------------------------
+
+    The JAM(mbp) documentation and JAM API and information attached
+    hereto, hereafter referred to as JAM, is protected by applicable
+    copyright laws and international treaty provisions. JAM is provided
+    "as is", without warranty of any kind or fitness for a particular
+    purpose, either expressed or implied, all of are hereby explicitly
+    disclaimed. The authors only guarantees that JAM will occupy disk
+    space.
+
+    The entire risk as to the quality and performance of JAM is with you.
+    Should JAM prove defective or incorrect, you assume the entire cost
+    of all necessary servicing, repair, and/or correction. In no event
+    shall the authors be liable to the you or anyone else for any damages
+    or costs, including, but not limited to, any lost profits, lost
+    savings, lost income, lost information, loss of the right to use JAM,
+    or other incidental or consequential damages arising out of the use
+    or inability to use JAM.
+
+    All information provided in JAM is subject to change without further
+    notice.
+
+    JAM may be published and distributed to other people as long as no
+    part of it is modified by any means, this includes translation to
+    any other language (technical or social), and as long as no charges
+    are applied (including but not limited to trading). This information
+    may not be used to reverse engineer any application developed by the
+    authors.
+
+    All applications that support JAM must include one of the following
+    notices in their documentation and somewhere in the product's credit
+    section:
+
+    "JAM(mbp) - Copyright 1993 Joaquim Homrighausen, Andrew Milner,
+                               Mats Birch, Mats Wallin.
+                               ALL RIGHTS RESERVED."
+
+    or
+
+    "This product uses the JAM(mbp) API -
+     Copyright 1993 Joaquim Homrighausen, Andrew Milner, Mats Birch,
+                    Mats Wallin. ALL RIGHTS RESERVED."
+
+    All trademarks are trademarks or registered trademarks of their
+    respective holders.
+</PRE>
+
+<A HREF="./"><IMG SRC="../images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+
+</BODY>
+</HTML>
+

html/manual.css

@@ -0,0 +1,30 @@
+/*
+ * $Id: manual.css,v 1.5 2003/11/08 16:48:03 mbroek Exp $
+ *
+ * stylesheet for the MBSE BBS manual.
+ */
+
+
+BODY      { background-color: white; font: 12pt sans-serif,helvetica,arial; }
+
+/*
+ * H1 is the page header, H3 the paragraph header, H5 is topright update date.
+ */
+H1        { color: red; font: 16pt sans-serif,helvetica,arial;  font-weight: bold }
+H2	  { color: red; font: 14pt sans-serif,helvetica,arial;  font-weight: bold }
+H3        { position: relative; left: 60px; color: black; font: 14pt sans-serif,helvetica,arial; font-weight: bold }
+H5        { color: black; font: 10pt sans-serif,helvetica,arial; }
+
+A:link	  { color: blue }
+A:visited { color: blue }
+A:active  { color: red  }
+
+TABLE     { color: black; }
+TH	  { font-family: Arial, Helvetica; font-size: 12pt; font-weight: bold; }
+TD        { font-family: Arial, Helvetica; font-size: 12pt; }
+
+PRE       { color: green; font-family: fixed; }
+CODE      { color: green; font-family: fixed; }
+HR        { border-top: solid medium navy }
+
+

html/menus/control.html

@@ -0,0 +1,134 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: control.html,v 1.12 2007/02/25 20:28:04 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - Control Codes in ANSI and ASCII files.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<DIV align=right><h5>Last update 25-Feb-2007</h5></div>
+<DIV align=center><h1>MBSE BBS Control Codes in ANSI and ASCII files</h1></DIV>
+<hr>
+
+
+<H3>Single Control characters</H3>
+<PRE>
+ Code      Description
+ ----      ---------------------------------------
+  A        Wait for a key
+  B        Print text above sec. level
+  F        Control-code F
+  K        Control-code K
+  P        Wait one second
+  U        Control-code U
+
+
+</PRE>
+The control-B syntax is: ^B&lt;seclevel&gt;^B&lt;The text to show&gt;^B<br>
+For example: ^B32000^BThis is the text^B<br>
+<P>
+
+<H3>Control-F followed by:</H3>
+<PRE>
+ Code      Description
+ ----      ---------------------------------------
+  !        Display transfer protocol
+  A        Number of uploads
+  B        Number of downloads
+  C        Downloads in Kilobytes
+  D        Uploads in Kilobytes
+  E        Download plus upload Kilobytes
+  F        Download Kilobyte limit
+  H        Current file area number
+  I        Current file area description
+  J        Download files limit
+  K        Description of user limit
+
+
+</PRE>
+<P>
+
+<H3>Control-K followed by:</H3>
+<PRE>
+ Code      Description
+ ----      ---------------------------------------
+  A        Print date in format DD-MM-YYYY
+  B        Print time in HH:MM:SS
+  C        Print date in DD-Mmm
+  D        Print date in DD-Mmm-YYYY
+  E        Print locked port baudrate
+  F        Print the name of the Last caller
+  G        Total users in userlist
+  H        Number of system calls
+  I        Current message area number
+  J        Current message area description
+  K        Print random oneliner
+  L        Print number of messages in current area.
+  M        Print users LastRead pointer of current message area.
+  N        Print users current e-mail mailbox name.
+  O        Print number of messages in current e-mail box.
+  P        Print users LastRead pointer of current e-mail box.
+  Q        Print the date and time of the last caller.
+
+
+</PRE>
+<P>
+
+<H3>Control-U followed by:</H3>
+<PRE>
+ Code      Description
+ ----      ---------------------------------------
+  A        User's full name
+  B        User's location
+  C        User's voice phone
+  D        User's data phone
+  E        User's last login date
+  F        User's first login date
+  G        User's last login time
+  H        User's security level
+  I        User's total calls
+  J        User's time used today
+  K        User's connect time this session
+  L        User's time left today
+  M        User's screen length
+  N        User's first name
+  O        User's last name
+  P        User's graphics mode allways (On).
+  Q        User's news bulletins (On/Off)
+  R        User's hot-keys (On/Off)
+  S        User's daily time limit
+  T        User's date of birth
+  U        User's messages posted
+  X        User's language
+  Y        User's handle
+  Z        User's do not disturb flag (On/Off)
+  1        User's check for new mail (On/Off)
+  2        User's check for new files (On/Off)
+  3        User's fullscreen editor (On/Off)
+  4        User's FS editor Emacs shortcuts (On/Off)
+  5        User's first address line.
+  6        User's Second address line.
+  7        User's Third address line.
+  8        User's OLR Extended Onfo (On/Off).
+  9        User's charactewr set.
+  0        User's current archiver.
+
+</PRE>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+<A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+<A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/menus/index.htm

@@ -0,0 +1,181 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: index.htm,v 1.12 2003/11/08 20:48:19 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META name="author" lang="en" content="Michiel Broek">
+<META NAME="Language" content='en'>
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menu System.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align=right><h5>Last update 11-Oct-2003</h5></div>
+<div align=center><H1>MBSE BBS Menu System</H1></div>
+
+<P>Menus sections:
+<A HREF="menu0.html">Global menus</A>&nbsp;
+<A HREF="menu100.html">File areas</A>&nbsp;
+<A HREF="menu200.html">Message areas</A>&nbsp;
+<A HREF="menu300.html">User settings</A>&nbsp;
+<A HREF="menu400.html">Onliners</A>&nbsp;
+<A HREF="menu500.html">BBS lists</A>&nbsp;
+<A HREF="control.html">ANSI Control Codes</A>
+</P>
+<P>
+<HR>
+
+<H3>Introduction.</H3>
+<P>
+One of the most powerfull features of the BBS is it's menu system. You
+have complete control over each individual menu item which can be restricted
+according to criteria such as security levels.
+<P>&nbsp;<P>
+
+<H3>ANSI Screens.</H3>
+<P>
+For the menus to work properly you can draw ANSI screens, this
+is what the users will see. For GNU/Linux there is "Duh DRAW" written by Ben
+Fowler, see sunsite.unc.edu /pub/Lunux/docs.
+If you can't find it or have no internet access, you can also use 
+THEDRAW. This utility can be found on many BBS'es around the world. Unfortunatly
+it is a DOS program so you will need dosemu on your GNU/Linux box or a seperate
+DOS computer. You can define main screens and include screens for each
+menu, the include screen may for example show the keys that you have available
+in every menu. See the list of <A HREF="control.html">control codes</A>.
+<P>&nbsp;<P>
+
+<H3>Display lines.</H3>
+<P>
+It is also possible to display menu lines with the buildin display option.
+The used colors are selectable, a normal color and a bright color.
+The normal color is the default, you can toggle bright on and of using
+the ^ in the display line. If you end a menu display line with a ; then
+no newline is send after that line. If you want to output teh ^ or ; characters
+you need to escape them with a backslash like this: \; or \^. The order of menu
+entries is important.
+<P>&nbsp;<P>
+
+<H3>Automatic commands.</H3>
+<P>
+A menu function is usually executed when a user presses the hot-key
+assigned to that particular menu item. But menu functions can also be executed
+automatically. Each menu item contains an AutoExec field. By default this
+field is set to No, but by toggling it to Yes, the menu item can be made
+to execute when it is played back (displayed) by the BBS. </P>
+<P>
+As you read through the menu function types outlined in this chapter,
+you may come to realize that this is a very powerfull feature. For example,
+when used with the menu function that displays a text file, you can design
+very elaborate, graphical text file menus that you wouldn't normally be
+able to display in a line-by-line menu. </P>
+<P>
+Automatic menu execution can be used in many other instances as well.
+Just to give you some ideas, it might be used to display a text file to
+users who have a security level equal to or greater than a certain level.
+Yet another use is to execute multiple function menus which are used to
+execute several functions when a single command is entered. 
+<P>&nbsp;<P>
+
+<H3>Multiple languages.</H3>
+<P>
+For each language you can define a set of menus. Only for the default
+language all menus must exist. It makes sense to make the filenames of
+your menus for each language the same and not to translate them. If a menu
+is missing for a non default language, the menu from the default language
+path is used instead. 
+<P>&nbsp;<P>
+
+<H3>Editing a menu.</H3>
+<P>
+The order of the menu lines in the setup is not important except for
+the autoexec menus, they must be placed in the right order from start,
+ie. begin with the menu specific screen display, then the global include
+display and finally show the prompt.
+<P>
+
+<IMG SRC="../images/e_menu.png" ALT='Menu editer' Border="0">
+<OL>
+<LI><B>Selection key.</B> This is the key a user must press to activate
+this menu. This field is ignored when AutoExec is set to Yes. </LI>
+
+<LI><B>Type nr.</B> this is the menu type to execute. For a description
+of all available types see the links at the top of this page.</LI>
+
+<LI><B>Optional data.</B> Some menus need optional data, for example the
+function goto another menu needs the name of that menu file here. </LI>
+
+<LI><B>Display.</B> What is to be displayed to the user. You can use this instead
+of ANSI screens.
+</LI>
+
+<LI><B>Security.</B> This is the minimum security level to execute this
+selection. The security is a level number combined with 32 bitmapped flags.
+NOTE: level 0 and no flags means
+everyone can select this menu. Good for logout options and all other options
+everyone must be able to execute. </LI>
+
+<LI><B>Min. age.</B> The minumum age the user must be to execute this selection.
+You may want to restrict access to certain areas to users older than 18
+years. If you leave this to 0, every one can execute this menu. </LI>
+
+<LI><B>Lo-colors.</B> The normal display color for the display line.
+</LI>
+
+<LI><B>Hi-colors.</B> The bright display color for the display line.</LI>
+
+<LI><B>AutoExec.</B> If this is an automatic executed selection. </LI>
+
+<LI><B>Door Name</B> The name of the door that will be displayed to other users.
+This name is also used to count the same doors running if the door only allows a
+single user. It is important that you use the same name in every language menu
+file for the same door. This item is only visible with menu type 7.</LI>
+
+<LI><B>Y2K style</B> Writes the dates in the door.sys file in the new style,
+with 4 digit year numbers, else the old 2 digit style is used. This item
+is only visible with menu type 7.</LI>
+
+<LI><B>No door.sys</B> Suppress writing of a door.sys file in the users
+home directory. This item is only visible with menu type 7.</LI>
+
+<LI><B>Use Comport</B> Writes COM1: with 19200 as baudrate to the door.sys file, 
+this is for dosemu with the vmodem patch. This item is only visible with menu
+type 7.</LI>
+
+<LI><B>Run nosuid</B> If set to Yes the door will run in non-suid mode.
+Most doors need this. This item is only visible
+with menu type 7.</LI>
+
+<LI><B>No Prompt</B> If set to Yes then when the door is finished there will be
+no prompt to press Enter, instead the bbs menu will show up immediatly. This
+item is only visible with menu type 7.</LI>
+
+<LI><B>Single User</B> Set to yes of the door only allows one user at the same
+time. Make sure you have set a unique name that must be the same for the door in
+every language file so that the bbs is able to count the instances of the door
+running. This item is only visible with menu type 7.</LI>
+
+<LI><B>Hidden door</B> Set to yes to hide the door from being visible for other
+users. If someone is using that door the whoson list displays "External Door"
+instead of the door name. This may be good to hide some special sysop only
+doors. This item is only visible with menu type 7.</LI>
+
+</OL>
+<P>&nbsp;<P>
+
+<H3>Final warning.</H3>
+<P>
+If a submenu is missing, the BBS falls back to the main menu. This menu
+must be called &quot;main&quot; (or else set another name in the global
+setup) or your BBS won't start and complain. Submenus may be nested 50
+levels deep. 
+<P>
+
+<A HREF="../index.htm"><IMG SRC="../images/b_arrow.png" ALT="Back" BORDER=0>Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/menus/menu0.html

@@ -0,0 +1,181 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: menu0.html,v 1.12 2003/11/08 20:48:19 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - Global Menus.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<DIV align=right><h5>Last update 01-Apr-2003</h5></DIV>
+<DIV align=center><h1>MBSE BBS Global Menus</h1></DIV>
+<hr>
+
+<OL>
+
+ <LI value="1"><strong>Goto another menu:</strong> This will start the execution
+ of another menu. The current menu level is not stored on the stack.<br>
+ <strong>Optional data:</strong> The name of the new menu.<Br>
+ <P>
+
+ <LI value="2"><strong>Gosub another menu:</strong> This will start the execution
+ of another menu. The current menu level is stored on the stack. Gosub's may
+ be nested 50 levels deep.<br>
+ <strong>Optional data:</strong> The name of the new menu.<br>
+ <P>
+
+ <LI value="3"><strong>Return from Gosub:</strong> This will go back one
+        gosub level. If you are already at the top level nothing happens.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="4"><strong>Return to top menu:</strong> Return to the top (main)
+     menu. The name of this menu is set in the global setup. 
+     Default is main.mnu<br>
+    <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="5"><strong>Display .a?? file with controlcodes:</strong> This will
+   display an ANSI file to the user. If the user has <em>Graphics No</em> set
+   then the ASCII version is shown. Search is done first in the users language
+   path and if that fails the default language path is used. 
+   <A HREF="control.html">Control codes</A> in the
+   file are substituted with the current values the represent.<BR>
+   <strong>Optional data:</strong> The name of the file to display. Do not
+   give the filename extension!<BR>
+   <P>
+
+ <LI value="6"><strong>Show menu prompt:</strong> Display the menu prompt.<br>
+   <strong>Optional data:</strong> The prompt to display. This string may
+   contain some control characters that are replaced with information. The
+   prompt is displayed in White on Black and is hardcoded at the moment.
+   <ul>
+     <li><strong>~</strong> This will insert the number of minutes the user
+        has left.
+     <li><strong>@</strong> This will insert the name of the current file area.
+     <li><strong>^</strong> This will insert the name of the current message area.
+     <li><strong>#</strong> This will insert the current local time.
+   </ul>
+   <P>
+
+ <LI value="7"><strong>Run external program:</strong> This will execute 
+    external programs.<br>
+   <strong>Optional data:</strong> The full path and filename of the external
+   program to run. There are a few switches you can give on the commandline:
+   <UL>
+    <LI><b>/N</B> will be replaced by the current nodenumber. The nodenumber is
+    faked by using the record number of the tty lines setup.
+    <LI><b>/A</b> will prompt for a filename to enter. The filename the user
+    enters is then replaced on the commandline. This is a dangerous option!
+    <LI><b>/T=your prompt</b> is an alternate prompt for entering a filename
+    if used together with the <b>/A</b> option.
+   </UL>
+   <br>
+   <P>
+
+ <LI value="8"><strong>Show product information:</strong> This will show
+   copyright information about MBSE BBS.<br>
+   <strong>Optional data:</strong> None.<br>
+   <P>
+
+ <LI value="9"><strong>Display todays callers:</strong> This will display a
+   list of todays callers to the BBS.<br>
+   <strong>Optional data:</strong> "/H" Show handles instead of real names, "/U"
+   show Unix names instead of real names.<br>
+   <P>
+
+ <LI value="10"><strong>Display userlist:</strong> Display all users in the
+   users database except those that are hidden.<br>
+   <strong>Optional data:</strong> "/H" Show handles instead of real names, "/U"
+   show Unix names instead of real names.<br>
+   <P>
+
+ <LI value="11"><strong>Time statistics:</strong> Display the users time
+   statistics.<br>
+   <strong>Optional data:</strong> None.<br>
+   <P>
+
+ <LI value="12"><strong>Page Sysop:</strong> Page sysop for a chat.<br>
+   <strong>Optional data:</strong> A message to the user<br>
+   The message to the user could be something like "Calling sysop, please
+   wait ..." or "I will see if Michiel wants to chat with you, please wait!"
+   As sysop you will know best what to put in that line.
+   <P>
+
+ <LI value="13"><strong>Terminate call:</strong> Terminale this call and 
+   hangup.<br>
+   <strong>Optional data:</strong> None.
+   <P>
+
+ <LI value="14"><strong>Make a log entry:</strong> This will write a line in
+   the logfile.<br>
+   <strong>Optional data:</strong> The information you want in the logfile.<br>
+   <P>
+
+ <LI value="15"><strong>Print text to screen:</strong> Write text to the users
+   screen.<br>
+   <strong>Optional data:</strong> The text that must appear on the users
+   screen. The <em>@</em> character is replaced with a newline.<br>
+   <P>
+
+ <LI value="16"><strong>Who is online:</strong> Displays the who is online
+   list and what they are doing. Users that are hidden are not displayed.<br>
+   <strong>Optional data:</strong> "/H" Show handles instead of real names, "/U"
+   show Unix names instead of real names.<br>
+   <P>
+
+ <LI value="17"><strong>Comment to sysop:</strong> Enter the texteditor and
+   let the user write a message to the sysop. The area is predefined in the
+   global setup.<br>
+   <strong>Optional data:</strong> None.<br>
+   <P>
+
+ <LI value="18"><strong>Send online message:</strong> Send an online message
+   to a user on another line.<br>
+   <strong>Optional data:</strong> "/H" Use handles instead of real names, "/U"
+   use Unix names instead of real names.<br>
+   <P>
+
+ <LI value="19"><strong>Display textfile with more:</strong> This will display
+   a textfile to the user. After each full screen the user is prompted with
+   <em>More Y/n/=</em>.<br>
+   <strong>Optional data:</strong> The full path and filename to the file.<br>
+   <P>
+
+ <LI value="20"><strong>Display .a?? file with control codes and wait:</strong> 
+   This will display a ANSI or ASCII file to the user with <A HREF="control.html">
+   control codes</A> and wait for <em>Enter</em> when it is finished.<br>
+   <strong>Optional data:</strong> The filename without extension of the
+   file to display.<br>
+   <P>
+
+ <LI value="21"><strong>Display line</strong> This entry does nothing except
+   that it displays the text on the display line. This is always displayed,
+   even if the display line is empty. In that case an empty line is displayed.<br>
+   <strong>Optional data:</strong> None.<br>
+   <P>
+
+ <LI value="22"><strong>Chat session</strong> This connects the user to the
+   chatserver. The user is connected with his unix name as default name. The chat
+   server is a very simple IRC look alike server.<br>
+   <strong>Optional data:</strong> None yet, maybe the channel later.<br>
+   <P>
+ 
+</OL>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+   <A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+   <A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/menus/menu100.html

@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: menu100.html,v 1.5 2003/11/08 20:40:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - File Area Menus.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 02-Feb-2001</h5></div>
+<div align='center'><h1>MBSE BBS File Area Menus</h1></div>
+<hr>
+
+<OL>
+
+ <LI value="101"><strong>Select another area:</strong> This option will show
+ a list of available areas and let the user select a new area. If there is
+ optional data the new area will be selected without user intervention.<br>
+ <strong>Optional data:</strong> If there is an option the area is direct
+ selected. Current options are: <strong>F+</strong> goto next available area.
+ <strong>F-</strong> goto previous available area.<Br>
+ <P>
+
+ <LI value="102"><strong>File List:</strong> This option will display a list
+ of files with their dates, sizes and description. During the display of the
+ list the user can select (Tag) files for later download.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="103"><strong>View File:</strong> Not yet implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="104"><strong>Download File(s):</strong> This option will start to
+ transmit files to the user if he has tagged files for download. Tagging files
+ for download can be done during File List, Keyword Scan, Filename Scan or
+ Newfile Scan. If a user didn't select a transfer protocol before now he will be
+ forced to select a file transfer protocol.<br>
+ <strong>Optional Data:</strong> None.<br>
+ <P>
+
+ <LI value="105"><strong>Raw Directory:</strong> This option will display the
+ contents of a directory in raw format.<br>
+ <strong>Optional data:</strong> If the option is <strong>/F</strong> the
+ contents of the current directory is shown. If the option is the full path
+ to a directory, the contents of that directory is shown. <br>
+ <P>
+
+ <LI value="106"><strong>Keyword Scan:</strong> This option will search for
+ files in the files database for a matching keyword. The search is not case
+ sensitive. If there are files found the user is able to select (Tag) these
+ files for later download.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="107"><strong>Filename Scan:</strong> This option will search for
+ a filename match in the files database. The search is not case sensitive.
+ If there are files found the user is able to select (Tag) these files for
+ later download.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="108"><strong>Newfiles Scan:</strong> This option will scan for new
+ files available for download since the last time the user was online. As
+ option the user can change that date from which to start the search. Any files
+ found the user may select (Tag) for later download.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="109"><strong>Upload:</strong> This option will let the user upload
+ files to the bbs. If the current area has an alternate upload area, the upload
+ will end up in that area. If the user uses X-modem or another ancient protocol
+ he will first be asked for a filename. Normal modern protocols don't need this.
+ The filename is checked before the transfer is done to protect the bbs. Further
+ the files the user will upload will at first be placed under the users home
+ directory <strong>~/upl</strong>. After the upload(s) the files are checked
+ for virusses. If all is well, the file is imported in the bbs. If the file
+ contains a valid FILE_ID.DIZ file inside the archive, that file will be used
+ for the description of the upload, if not, the uploader will have to describe
+ the file.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="110"><strong>Edit Taglist:</strong> This option is for the user to
+ edit the list of files he has tagged for later download.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="111"><strong>View file in homedir:</strong> Not yet implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="112"><strong>Download Direct:</strong> Download a file direct.<br>
+ <strong>Optional data:</strong> The full path and filename to the file to
+ download.<br>
+ <P>
+
+ <LI value="113"><strong>Copy file to Homedir:</strong> This option will copy 
+ a file from a download directory to the users home directory. It will be 
+ checked if the user has enough room in his directory, the default Quota for
+ users is 10 MBytes.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="114"><strong>List Homedir:</strong> This option will list the files
+ in the users home directory.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="115"><strong>Delete in Homedir:</strong> This option will let the 
+ user delete one or more files from his home directory.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="116"><strong>Unpack file in Homedir:</strong> Not yet implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="117"><strong>Pack files in Homedir:</strong> Not yet implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="118"><strong>Download Homedir:</strong> This option will let the 
+ user download from his home directory.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="119"><strong>Upload Homedir:</strong> This option will let the user
+ upload files to his home directory.<br>
+ <strong>Optional data:</strong> None.<br>
+</OL>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+<A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+<A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/menus/menu200.html

@@ -0,0 +1,153 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: menu200.html,v 1.9 2003/11/08 20:40:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - Message Area Menus.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<DIV align=right><h5>Last update 20-Feb-2003</h5></DIV>
+<DIV align=center><h1>MBSE BBS Message Area Menus</h1></DIV>
+<hr>
+
+<OL>
+
+ <LI value="201"><strong>Select another area:</strong> This option will show
+ a list of all available areas and let the user select a new area. If there
+ is optional data the area will be selected without user intervention.<br>
+ <strong>Optional data:</strong> If there is an option the area is direct
+ selected. Current options are <strong>M+</strong> goto the next available
+ area. <strong>M-</strong> goto the previous available area. If you use the
+ <strong>U+</strong> and <strong>U-</strong> instead, the area is changed to the
+ previous or next area with unread messages, areas without unread messages are
+ skipped.<br>
+ Another option is the <strong>N</strong>, if this is used for area select the
+ areas with new unread mail are marked with a yellow star.
+ <P>
+
+ <LI value="202"><strong>Post a Message:</strong> This option lets the user
+ post a new message.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="203"><strong>Read Messages:</strong> This option lets the user
+ read messages. If he has done that before in that area he will be suggested
+ to start after the message he has last read. During reading of messages
+ the user can reply to other messages.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="204"><strong>Check for Mail:</strong> Check for new arrived mail.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="205"><strong>Quickscan Messages:</strong> Make a quick overview
+ list of all messages in that area.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="206"><strong>Delete a Message:</strong> This option will let the
+ user delete a specific message. He must the the owner of that
+ message or have sysop rights in that area to be able to delete a message.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="207"><strong>Mail Status:</strong> This gives a complete overview
+ of all available mail at the bbs.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="208"><strong>OLR: Tag Area:</strong> This option lets
+ the user tag one or more areas to be included in his offline mail packet.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="209"><strong>OLR: Untag Area:</strong> This option lets
+ the user untag one or more areas not to be included in his offline mail
+ packet.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="210"><strong>OLR: View Tags:</strong> This option lets
+ the user view which areas will be included in his offline mail packet.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="211"><strong>OLR: Restrict Date:</strong> Not yet
+ implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="212"><strong>OLR: Upload Mail:</strong> Let the user upload
+ mail or a new offline reader setup. The packet format is automatic detected.
+ Currently BlueWave is supported. QWK support will be added later.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="213"><strong>OLR: Download BlueWave:</strong> Download mail in
+ BlueWave version 2 format.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="214"><strong>OLR: Download QWK:</strong> Download mail in QWK
+  format.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="215"><strong>OLR: Download ASCII:</strong> Download mail in flat
+ ASCII format. Not yet implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="216"><strong>Read Email</strong> Read users private email.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="217"><strong>Write Email</strong> Post an email message.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="218"><strong>Trash Email</strong> Put email in the trashcan.
+ Not Yet implemented.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="219"><strong>Choose Mailbox</strong> Choose another private
+ mailbox. Valid boxes are: mailbox (normal in/out), archive and trash.<br>
+ <strong>Optional data:</strong> If there is an option the area is direct
+ selected. Current options are <strong>M+</strong> goto the next mailbox.
+ <strong>M-</strong> goto the previous mailbox.<br>
+ <P>
+
+ <LI value="220"><strong>Quickscan Email</strong> Make a quick overview
+ list of all messages in the selected e-mail area.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+ <LI value="221"><strong>Show area rules</strong> Show the rules of a 
+ echomail area if such rulefile is present in the rules directory. The file
+ seached for needs to have a name that is the same as the area tag, or the area
+ tag plus .rul, or the first eight characters of the area tag plus .rul like
+ the rulefiles in the elist package.<br>
+ <strong>Optional data:</strong> None.<br>
+ <P>
+
+</OL>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+<A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+<A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/menus/menu300.html

@@ -0,0 +1,139 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: menu300.html,v 1.10 2007/03/01 19:12:55 mbse Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - User Settings Menus.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<DIV align=right><h5>Last update 01-Mar-2007</h5></DIV>
+<DIV align=center><h1>MBSE BBS User Settings Menus</h1></DIV>
+<hr>
+
+<OL>
+
+ <LI value="301"><strong>Change Transfer Protocol:</strong> Let the user 
+ select a new file transfer protocol.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="302"><strong>Change Password:</strong> Let the user change
+ his FidoNet password.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="303"><strong>Change Location:</strong> Let the user change 
+ his location.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="304"><strong>Obsolete:</strong> This command does not exist.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="305"><strong>Change Voicephone:</strong> Let the user change
+ his voice phonenumber.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="306"><strong>Change Dataphone:</strong> Let the user change
+ his data phonenumber.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="307"><strong>Change Expertmode:</strong> This command will be
+ removed.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="308"><strong>Obsolete:</strong> This command does not exist.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="309"><strong>Change Date of Birth:</strong> Let the user set a
+ new date of birth. Check's are done if the date is more or less realistic.
+ This command should not be made available users if you use the regular
+ date of birth validation check.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="310"><strong>Change Language:</strong> Let the user select a new
+ default language.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="311"><strong>Change Hotkeys:</strong> Let the user toggle the
+ use of Hotkeys on or off..<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="312"><strong>Change Handle:</strong> Let the user select a new
+ handle (nickname).<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="314"><strong>Change Don't Disturb:</strong> Let the user toggle
+ the "do not disturb" flag.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="315"><strong>Change check for new files:</strong> Let the user
+ toggle the "check for new files at logon" flag.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+ 
+ <LI value="316"><strong>Change fullscreen editor:</strong> Let the user
+ toggle the "use fullscreen editor" flag.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+ 
+ <LI value="317"><strong>Change FS edit shortcut keys:</strong> Let the user
+ toggle the "FS edit shortcut keys between Emacs/Wordstar" flag.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="318"><strong>Change Address:</strong> Let the user change his
+ three lines home address.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="319"><strong>Change signature:</strong> Let the user change
+ his mail signature file (.signature in his home directory). He is allowed
+ to edit at most 4 lines of 74 characters.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="320"><strong>Change OLR Extended Info:</strong> Let the user toggle
+ the setting of the Offline Reader download of extended info (kludges).<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="321"><strong>Change character set:</strong> Let the user change
+ the default character set for messages.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+ 
+ <LI value="322"><strong>Change archiver:</strong> Let the user change the
+ archhiver to use to build offline reader packages.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+ 
+</OL>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+<A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+<A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/menus/menu400.html

@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: menu400.html,v 1.5 2003/11/08 20:40:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - Oneliner Menus.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 02-Feb-2001</h5></div>
+<div align='center'><h1>MBSE BBS Oneliner Menus</h1></div>
+<hr>
+
+<OL>
+
+ <LI value="401"><strong>Oneliner Add:</strong> Let the user add a new
+ oneliner.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="402"><strong>Oneliner List:</strong> Let the user list all the
+ available oneliners.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="403"><strong>Oneliner Show:</strong> Let the user show a
+ specific oneliner.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="404"><strong>Oneliner Delete:</strong> Let the user delete a
+ oneliner. In order to do so he must be the owner of that oneliner or
+ he must have sysop access level. The oneliner is not really removed, only
+ marked for deletion.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="405"><strong>Oneliner Print:</strong> Show a random chosen
+ oneliner on the screen. If you make this command automatic, each time that
+ this menu is executed a new oneliner will popup.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+</OL>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+<A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+<A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/menus/menu500.html

@@ -0,0 +1,57 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: menu500.html,v 1.5 2003/11/08 20:40:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>MBSE BBS Menus - BBS List Menus.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 02-Feb-2001</h5></div>
+<div align='center'><h1>MBSE BBS BBS List Menus</h1></div>
+<hr>
+
+<OL>
+
+ <LI value="501"><strong>Add a BBS:</strong> Let the user add a BBS to the
+ BBS advertising database.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="502"><strong>List BBS'es:</strong> Show a list of BBS'es in the
+ BBS database.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="503"><strong>Show BBS:</strong> Show a specific BBS.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="504"><strong>Delete BBS:</strong> Delete a specific BBS. The BBS
+ must have been entered by the user or the user must have sysop rights to
+ be able to delete a BBS.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+ <LI value="506"><strong>Search BBS:</strong> Search for a specific BBS.<br>
+ <strong>Optional data:</strong> None.<Br>
+ <P>
+
+</OL>
+
+<HR>
+<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Index" BORDER=0></A>
+<A HREF="../">Main Index</A>&nbsp;
+<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" BORDER=0></A>
+<A HREF="./">Menus Index</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/mgetty.html

@@ -0,0 +1,188 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: mgetty.html,v 1.9 2003/11/09 14:46:32 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Setup mgetty for MBSE BBS.</TITLE>
+<LINK rel=stylesheet HREF="manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align='right'><h5>Last update 07-Jan-2002</h5></div>
+<div align='center'><H1>Setup mgetty for MBSE BBS</H1></div>
+
+To handle incoming calls you can use <strong>mgetty</strong> written by
+Gert Doering, (gert@greenie.muc.de). Others may work. You have to compile
+<strong>mgetty</strong> with the -DFIDO flag to accept Fidonet mailer calls.
+If you want incoming PPP calls as well, add the -DAUTO_PPP as well. If you want
+to use ISDN, make sure you have ISDN support compiled in the kernel.
+Below you can see the mgetty.config and login.config for mgetty that you may
+need. 
+I have also included a part of my /etc/inittab to show how <strong>mgetty
+</strong> will spawn from <strong>init</strong>.
+<P>
+
+<HR>
+<PRE>
+# inittab       This is only a part of /etc/inittab!
+#               In this example it runs in runlevel 3 and 4.
+#
+# Serial lines
+s1:34:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyS0
+#
+# ISDN lines, two channels
+I1:34:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyI0
+I2:23:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyI1
+#
+# End of /etc/inittab
+</PRE>
+<HR>
+<PRE>
+# mgetty configuration file: mgetty.config
+#
+# ----- global section -----
+#
+# In this section, you put the global defaults, per-port stuff is below
+#
+# set the global debug level to "4" (default from policy.h)
+debug 4
+#
+# set the local fax station id
+fax-id ++31-255-515973
+#
+# access the modem(s) with 38400 bps
+speed 38400
+#
+#  use these options to make the /dev/tty-device owned by "uucp.uucp" 
+#  and mode "rw-rw-r--" (0664). *LEADING ZERO NEEDED!*
+port-owner uucp
+port-group uucp
+port-mode 0664
+#
+#  use these options to make incoming faxes owned by "root.uucp" 
+#  and mode "rw-r-----" (0640). *LEADING ZERO NEEDED!*
+fax-owner root
+fax-group uucp
+fax-mode 0640
+#
+#
+# ----- port specific section -----
+# 
+# Here you can put things that are valid only for one line, not the others
+#
+# Dynalink 1428EXTRA faxmodem at port 0 (COM1).
+#
+port ttyS0
+speed 57600
+switchbd 19200
+modem-type cls2
+init-chat "" \d\dAT&amp;F&amp;C1&amp;D3X4W2B0M0Q0V1H0&amp;K3S0=0 OK
+#
+#
+# ISDN ports.
+# With AT&amp;E you set the MSN/EAZ the device should listen to.
+# This should for an MSN be your telephone number _with_ the area
+# code but _without_ the leading 0.  
+# For an EAZ the last digit of your EAZ.
+#
+port ttyI0
+modem-type data
+init-chat "" ATZ OK AT&amp;E714015437&amp;W0 OK AT&amp;B512 OK
+#
+port ttyI1
+modem-type data
+init-chat "" ATZ OK AT&amp;E714017198&amp;W0 OK AT&amp;B512 OK
+#
+# end of mgetty.config
+</PRE>
+<HR>
+<PRE>
+# login.config
+#
+# This is a sample "login dispatcher" configuration file for mgetty
+#
+# Format:
+#	username userid utmp_entry login_program [arguments]
+#
+# Meaning:
+#       for a "username" entered at mgettys login: prompt, call
+#	"login_program" with [arguments], with the uid set to "userid",
+#	and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
+#
+#
+# Use this one for fido calls (login name /FIDO/ is handled specially)
+#
+#  mgetty has to be compiled with "-DFIDO", otherwise a fido call won't
+#  be detected.
+#
+/FIDO/	mbse	fido	/opt/mbse/bin/mbcico @
+#
+#
+# Automatic PPP startup on receipt of LCP configure request (AutoPPP).
+#  mgetty has to be compiled with "-DAUTO_PPP" for this to work.
+#  Warning: Case is significant, AUTOPPP or autoppp won't work!
+#  Consult the "pppd" man page to find pppd options that work for you.
+#  See also PPP-HOWTO on how to set this up.
+#
+/AutoPPP/ -	a_ppp	/etc/ppp/paplogin
+#
+# This is the "standard" behaviour - *dont* set a userid or utmp
+#  entry here, otherwise /bin/login will fail!
+#  This entry isn't really necessary: if it's missing, the built-in
+#  default will do exactly this.
+#  Here we replace the standard login with MBSE BBS login:
+#
+*	-	-	/opt/mbse/bin/mblogin @
+#
+#
+# end of login.config
+</PRE>
+<HR>
+
+<P>
+I have added the <strong>-i /opt/mbse/etc/issue</strong> options to the 
+<strong>mgetty</strong> line in /etc/inittab. 
+The file /opt/mbse/etc/issue is a plain textfile to give a small banner just
+before the login prompt. 
+It could look like this:<br>
+<pre>
+
+        .--.     Welcome at MBSE BBS Development.
+       |o_o |    --------------------------------
+       |:_/ |
+      //   \ \   This may or may not work today...
+     (|     | )
+    /'\_   _/`\
+    \___)=(___/  
+Powered by GNU/Linux.
+
+</pre>
+There is a default /opt/mbse/etc/issue installed by the installation script.
+You need to edit this to insert your bbs name in it or even completely replace
+this file for a nicer one. Don't make it too big, don't put control characters
+or ANSI sequences in it as this may prevent some mailers to connect to your system.
+<p>
+I discovered that some systems don't have the right permissions on the serial
+port for MBSE BBS. To fix this type the following commands:
+<pre>
+su
+password: <em>enter root password here</em>
+chmod 666 /dev/ttyS0
+chown uucp.uucp /dev/ttyS0
+exit
+</pre>
+Note that /dev/ttyS0 is for COM1, /dev/ttyS1 for COM2 etc. This is not a nice
+solution. If youre system allows it, try to add the the user <b>mbse</b> as
+a legal user of your serial ports. Most distributions have some tool for this.
+<p>
+
+<A HREF="index.htm"><IMG SRC="images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>

html/misc/dropfile.html

@@ -0,0 +1,114 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: dropfile.html,v 1.6 2003/11/08 21:02:35 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>BBS doors dropfiles.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<BLOCKQUOTE>
+<div align=right><h5>Last update 23-May-2003</h5></div>
+<div align=center><H1>BBS doors dropfiles.</H1></div>
+
+<h3>Dropfiles for Unix BBS systems.</h3>
+<p>
+Not all options that are available under DOS or OS/2 can be used with Unix
+BBS systems and must be faked. The doorfiles are written in the users
+homedirectory when the user starts a door.
+<p>&nbsp;<P>
+
+<h3>DOOR.SYS format.</h3>
+<P>
+The door.sys format is a 52 lines ascii textfile, each line is terminated with 
+a cr/lf pair. In the setup it is possible to force the creation of MM-DD-YYYY
+dates instead of the MM-DD-YY style. Newer doors sometimes need that.
+<pre>
+Line	Description
+-----	-----------------------------------------------------------------
+1	Port, 5 characters in DOS format, COM1: or COM0:
+2	Effective Baudrate, 19200 or 0 for COM0:
+3	Databits, always 8
+4	Nodenumber, 1..9999
+5	Locked baudrate, 19200 or tty portspeed for COM0:
+6	Screen display, Y=snoop on, N=snoop off, on Unix allways Y.
+7	Printer Y=on N=off, on Unix always N
+8	Page Bell Y=on N=off, on Unix allways Y
+9	Caller alarm Y=on N=off, on Unix allways Y
+10	Users first name and lastname
+11	Users location
+12	Voice/Home phone
+13	Work/Dataphone
+14	Users password.
+15	Security level, 0..32768
+16	Users number of calls
+17	Users last call date MM-DD-YY or MM-DD-YYYY
+18	Seconds remaining this call
+19	Time left in minutes
+20	ANSI, "GR" is yes, otherwise "NG"
+21	Screen length
+22	User mode, always N
+23	Always blank
+24	Always blank
+25	Subscription expire date MM-DD-YY or MM-DD-YYYY
+26	Users record number
+27	Default protocol
+28	Users total number of uploads
+29	Users total number of downloads
+30	Users daily download kilobytes total
+31	Daily download kilobyte limit
+32	Users date of birth MM-DD-YY or MM-DD-YYYY
+33	Path to users database files, cannot be used on Unix
+34	Path to message database files, cannot be used on Unix
+35	Sysop first and last name
+36	Users handle
+37	Next event starting time, "none" on Unix
+38	Error-free connection Y=Yes or N=No, always Y
+39	Always set to N
+40	Always set to Y
+41	Text color as defined in setup 7 = gray.
+42	Always 0
+43	Last new files scan date MM-DD-YY or MM-DD-YYYY
+44	Time of this call HH:MM
+45	Time of last call HH:MM
+46	Always set to 32768
+47	Number of files downloaded today
+48	Total kilobytes uploaded
+49	Total kilobytes downloaded
+50	Comment stored in users record
+51	Always set to 0
+52	Total number of messages posted
+</pre>
+<p>&nbsp;<p>
+
+<h3>DOOR.SYS format.</h3>
+<p>
+The door32.sys format is a 11 lines ascii textfile, each line is terminated with
+a cr/lf pair.
+<pre>   
+Line	Description
+-----	-----------------------------------------------------------------
+1	Com type: 1=serial, 2=telnet, with mbse always 1
+2	Com port: 1 or 0 for local mode
+3	Effective baudrate: 19200 or 0
+4	BBS name
+5	User record number
+6	User's real name
+7	User's handle
+8	User's security level
+9	Time left in minutes
+10	Graphicsmode: 1 or 0
+11	Node (line) number
+</pre>
+
+<A HREF="index.htm"><IMG SRC="../images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+</BLOCKQUOTE>
+</BODY>
+</HTML>
+

html/misc/filefind.html

@@ -0,0 +1,332 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: filefind.html,v 1.5 2003/11/08 21:18:53 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>Implementation and Usage of FileFind Utilities.</TITLE>
+</HEAD>
+<BODY>
+<PRE>
+ Document:   fsc-00xx
+ Version:    0.6
+ Date        Aug 30, 1995
+ Title:      Implementation and Usage of FileFind Utilities
+ Authors:    Robert Williamson FidoNet#1:167/104.0  robert@ecs.mtlnet.org
+
+  Intro
+
+    A portion of the document is derived from information in
+      AllFix.DOC by Harald Harms @ 2:281/910
+    with  additional  sections  from
+      FQuery.DOC by Robert Williamson @ 1:167/104
+
+        The  MSdos program ALLFIX by Harald Harms first introduced the idea
+    of searching for files via echomail.  The term applied to this function
+    is  'FileFind'.   A FileFind system allows sysops, points and BBS users
+    to  search  for  files  by  placing  a  message  to 'ALLFIX' in an echo
+    designated  for  the purpose of finding files.  All FTN sites running a
+    FileFind  processor which is configured to scan that echo will reply to
+    that  user if there any files matching his query.  This system provides
+    a  method  for  searching  many  FTN sites throughout the world, with a
+    single message.
+
+        FileFind  programs  work by either scanning through defined message
+    bases or scanning packets for defined AREA tagnames for messages to the
+    default  name  ALLFIX.   All FileFind programs MUST respond to the name
+    ALLFIX,  but  may also respond to the name FILEFIND and the name of the
+    particular  FileFind  program  in  use  or  defined  for the echo.  The
+    FileFind  program  will  process  these messages, examining the Subject
+    field  for  search  queries.  If any valid query is found, the FileFind
+    program  will  search  the  sites files database for files matching the
+    users's query.
+
+        If the FileFind program finds any matches, it will generate a reply
+    containing  a list of the files found, and some basic information ABOUT
+    the  system  posting  the reply.  When the user who initially wrote the
+    request  reads  the reply, he will then be able to decide if any of the
+    reported  files  meet  his  needs,  and  from the ABOUT included in the
+    reply, learn where and how he may get those files.
+
+
+  FileFind Query Message Structure
+
+    To: name_of_FileFind program
+
+    The  message  must be addressed to ALLFIX so that all FileFind programs
+    can  respond.   To  use  features  specific  to  a  particular FileFind
+    program,  or  to  limit  the  responses  to  a particular platform, the
+    message  should  be  addressed  to  that program's name.  Some FileFind
+    programs  will  respond  to more than two names.
+
+    Subject:
+    A  space-separated  list  of  file  specifications,  keywords or quoted
+    strings.
+
+    keyword     - single word preceeded by a '/' with no intervening spaces,
+                  must be at least 3 characters, not including the '/'.
+                  a keyword search is in actually a substring search of the
+                  site's filelist.
+
+    description - string enclosed in double-quotes,
+                  if a single word, must be more than 3 characters.
+
+    filespec    - single word, no spaces, no double-quotes or preceding /,
+                  must be at least 3 characters, not including any wildcard
+                  or pattern matching charcaters, such as '*'.
+                  Messages addressed to ALLFIX must not have any embedded
+                  pattern matching characters.
+
+
+        The  minimum  number  of  characters  for  description, keyword and
+    filespec  queries  is an implementation detail of the FileFind program.
+    These  values  should  be configurable, but should never be settable to
+    values of less than 3.
+
+        Each  implementation  should  allow  the  operator  the  ability to
+    configure a list of disallowed keywords.
+
+  NetMail Queries
+
+        Some  FileFind  programs  may also have the ability to process file
+    search  queries  received  as  netmail and addressed to the name of the
+    particular  FileFInd  program  with this capability.  In this case, all
+    replies are via netmail also.
+
+  NetMail Commands
+        FileFind   Netmail   commands  are  identifed  by  a  leading  '%'.
+    Implementation  of  netmail  commands  is  optional.   If  implemented,
+    compliant  FileFind  utilities  should be able to process the following
+    minimum NetMail command set.
+
+
+    %HELP       - netmail only, returns an extended help text for the
+                  FileFind program, the ABOUT of the the site and a list
+                  of MAGIC freqable names.
+    %ABOUT      - netmail only, returns the ABOUT of the site and a full
+ or %MAGIC        list of MAGIC names.
+
+    %NEWFILES   - netmail only, returns the NEWFILES list of the site
+ or %NEW          via netmail.
+
+    Extended NetMail Commands:
+        Implementation  of  the  following netmail commands is optional and
+    not required for compliance with the FileFind NetMail Command set.
+
+    %REPORT &lt;tagname&gt;
+                - sends a configuration report for echo &lt;tagname&gt;
+                  this allows an echo moderator to check if a site running
+                  a  FileFind  utility  is  compliant with the rules of the
+                  filefind echo.
+
+    %REQUEST &lt;filename&gt;
+                - if found, will place requested file on hold for remote
+                  site
+
+    %UUREQUEST &lt;filename&gt;
+                - if  found,  and  the filesize after uuencoding is less
+                  than 60K, it will be sent as multiple netmail messages
+
+
+  The Site ABOUT
+
+        Obviously,  a  system that neither accepts file requests nor allows
+    users  to  download  on  their  first  call should not be responding to
+    FileFind  messages.   If  there  are  any limitations for the caller to
+    acquire  any  of  the  files  that  the  site  has  advertised as being
+    available  in  it's FileFind response, these limitations MUST be listed
+    in  the  reply.   This information should be included in the ABOUT file
+    that the FileFind program user creates.
+
+        The  site  ABOUT  should  contain  the  following information.  The
+    FileFind  program  implementor  should  instruct  his  users  on  these
+    requirements.
+
+      - sitename
+      - site operator's name
+      - complete phonenumber
+      - baud rate
+      - hours during which filerequests are accepted, if at all
+      - hours during which users can download
+      - conditions for file requests and user downloads
+      NOTE: the above information should be within the first 14 lines.
+      optional:
+      - a list a MAGIC names
+      - an indication if magic names are also available to terminal users.
+
+  Searching for Files and Creating Replies
+
+        The  method  used by the FileFind program to search for requests is
+    up  to  the  implementor.   However,  if searching a list, the FileFind
+    program should confirm the actual existance of all files that match the
+    query specification.
+
+        The  FileFind  program  should  only  process  description strings,
+    filespecs  or  keywords  that  contain more than 3 valid characters and
+    should  have configuration options to define greater minimum lengths on
+    a per-echo basis.
+
+        For  filespecs,  the  wildcard  character '*' IS considered a valid
+    specification  as  well  as the '?' wildcard, but only the '?' is to be
+    counted  as  a  character  when  determining the length of query.  File
+    extensions  are  not necessary and any characters AFTER a '*' are to be
+    ignored.   The  FileFind  program should be configurable so as to allow
+    replacement  all  of the file extensions with '.*' or '#?' dependant on
+    platform.   This  results  in  queries being independant of the various
+    archivers in use.
+
+    Replies
+
+        Replies  created  by  FileFind  utilities  are  expected  to  be in
+    compliance with the following FTN specifications:
+        FTS-0001    -  packed message format
+        FTS-0009    -  MSGID/REPLY
+        FSC-0046    -  PID and tear line
+
+        In  addition, a FileFind utility may use the FID:  control line for
+    any  information needed that cannot be put in a PID:  without violating
+    that specification.
+
+        ^AFID: ascii text CR
+
+    Must be less than 80 characters including ^A and terminating CR.
+
+    There  are three ways in which the FileFind program can create replies:
+        - write the replies in the echo in which the query appeared.
+        - write the replies in an echo that has been specifically
+          designated for that purpose in the particular FTN or for
+          a gorup of echos in that FTN.
+        - reply via routed netmail.
+
+        Since each FTN site connected to a particular FileFind program area
+    is  capable  of creating an information reply, there is much concern as
+    to  the  amount  of  traffic  that  can  be generated, FileFind program
+    developers  must  be sensitive to these concerns by providing the means
+    to  their users to limit the traffic on a per-echo basis.  For example,
+    various  FileFind  echos  have  rules  limiting  the  size or number of
+    replies,  or  the length of the system information that may be included
+    in a reply.
+
+  Limiting replies
+
+    It is strongly suggested that some default limitations be built-in.
+
+    Limiting Site Header (ABOUT):
+
+        If the site's ABOUT, (the text that has been configured in order to
+    add  the  system's  information  and Magic names list to the reply), is
+    greater  than  14  lines,  the  remainder should NOT be posted.  A line
+    should  be  added  to  the response indicated this, and the user may be
+    invited to either Freq or download the MAGIC name's ABOUT or MAGIC, for
+    a  full  list of magic names.  The FileFind program may optionally send
+    the full system information and magic name list via routed netmail.
+
+    Limiting Match List due to ambiguity of query:
+
+        If  the list of matches (note:  not the size of the message itself)
+    is  greater than 32K, the FileFind program should post a message to the
+    user to indicate that his query may have been too ambiguous and perhaps
+    invite him to freq or download the MAGIC name FILES for a full list.
+
+    Splitting Match List into Multiple Messages:
+
+        If the list of matches is greater than 10K, it should be split into
+    multiple  messages  of  no more than 8K.  Although the backbone permits
+    messages  up  to  16K  in length, 8K is a more readable size.  Only the
+    first  split  message  may  contain  the ABOUT information of the site.
+    Each  message must be given both a unique Subject field (eg:  prepended
+    by  "Part n/n") and a unique MSGID:.  This because some tossers may use
+    either or both for dupe detection.
+
+    Limiting Number of Split Messages:
+
+        If  the  number of messages is greater than the preset limit of the
+    echo,  and  the FileFind Program does not have an option to forward the
+    replies  via  netmail,  the  replies  should  be discarded and the user
+    informed that his request may have been too amibiguous.
+
+
+    NetMail Reply:
+
+        The  FileFind program may have an option to forward all replies via
+    routed netmail, or to do so under certain conditions as outlined above.
+    Obviously, if the FileFind program can process netmail queries, it MUST
+    respond via netmail.
+
+    User NetMail Reply Request:
+
+        Alternativly the user can request a netmail reply for his echomail
+    query by preceeding the query with either "%" or "!".
+      eg;
+        Subject:  % /fsc /fts
+
+        If  the  FileFind  program  does  not support this feature, it must
+    ignore  any  echomail  query message that has a "%" or "!" as the first
+    WORD of the Subject field.
+
+    Second Reply or Extended Response Request:
+
+        The  FileFind  site  indicates  availablility  of  Second  Reply by
+    placing the string 'program_name 4d_address' in the From:  field of the
+    message.
+        eg: FROM: FQUERY 1:167/104.0
+
+        When a user replies to a FileFind reply, the message will be to the
+    FileFind  program  @  {network  address}.  When processing the FileFind
+    conferences, the FileFind program will treat any message to itself that
+    includes the site address as a Second Reply Request.
+
+        If  this feature is available, the FileFind program will include up
+    to  a maximum of 15 files (maximum 12K match list) in it's replies.  If
+    the  user  wants  a  more  detailed  listing,  he simply replies to the
+    FileFind  program's  reply.   Only  the system that posted the original
+    reply  will  respond to that new request.  This second, specific reply,
+    will  contain  up  to  50  files (32K of matchlist) either including or
+    SKIPPING the first 15.  These numbers may be replaced by byte limits in
+    some implementations.
+
+    No Second Reply in Designated Reply Echo:
+
+        The Designated Reply Echo method does not allow replies to be made,
+    because  the FileFind program may not be permitted to scan a Designated
+    Reply  Echo.  The FileFind program should automatically report up to 50
+    files  for any requests.  Therefore, the traffic limitaion features may
+    be  disabled for networks that require the FileFind program to reply in
+    a Designated Reply Echo, and disallow Second Reply in that echo.
+
+    Disable Local Messages:
+
+        The  FileFind  program must be able to to disable the processing of
+    local  messages.  What this means is that the FileFind program will not
+    process  any messages generated on that FTN site, including messages by
+    the  sysop  using  an  offline  reader,  or by a site's BBS or off-line
+    reader users.  This should NOT exclude messages from a site's points.
+
+
+    Limit by Age:
+
+        The  FileFind program must be configurable so that the operator can
+    limit  the  age  of an query message that is acceptable for processing.
+    This  should  be  in  number  of  days.   The  FileFind  program may be
+    configured  to  process all the FileFind requests regardless of how old
+    they are.  Age should never be greater than 365 days.
+
+    LinkMGR Support:
+        Implmentors  may choose to support the LinkMGR proposal for netmail
+    queries  and  commands.   In this proposal, the queries and commands do
+    not  appear  in  the  subject  field but rather, in the the BODY of the
+    message.  The subject field wil contain the LinkMGR password.
+        Use of the LinkMGR method allows the user to send multiple commands
+    to the fIleFind program.
+</PRE>
+
+<A HREF="index.htm"><IMG SRC="../images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+
+</BODY>
+</HTML>
+

html/misc/fileid.html

@@ -0,0 +1,388 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<HTML>
+<!-- $Id: fileid.html,v 1.5 2003/11/08 21:18:53 mbroek Exp $ -->
+<HEAD>
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META http-equiv="Content-Style-Type" content="text/css">
+<META NAME="Language" content='en'>
+<META name="author" lang="en" content="Michiel Broek">
+<META name="copyright" lang="en" content="Copyright Michiel Broek">
+<META name="description" lang="en" content="MBSE BBS Manual">
+<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
+<TITLE>FILE_ID.DIZ Information.</TITLE>
+<LINK rel=stylesheet HREF="../manual.css">
+</HEAD>
+<BODY>
+<PRE>
+FILEID.TXT v1.8 by Richard Holler [CIS 73567,1547]
+Last Revision 05/05/94
+
+This text file was prepared at the request of the ASP (Association of 
+Shareware Professionals), but the information contained in it may be of 
+value to any shareware author.
+
+
+FILE_ID.DIZ INFORMATION
+-----------------------
+Basically, the FILE_ID.DIZ file is a straight ASCII text file, distributed 
+inside your distribution archive file along with your program files, which 
+contains a description of your program. This file will be used by most BBS 
+(Bulletin Board System) softwares for the online file description of your 
+file. We recommend that the FILE_ID.DIZ file be used in all of your 
+distribution archives. 
+
+This text file contains a description of the FILE_ID.DIZ file, as well as a 
+description of the recommended distribution archive format.
+
+
+WHY SHOULD YOU USE FILE_ID.DIZ?
+-------------------------------
+The use of this file will insure that the online description of your 
+program will be in your own words (and who better to describe your program 
+than yourself?), and that it will remain the same no matter how many 
+different people upload your file to various BBS systems. 
+
+As more and more BBS software makes use of this file, you can be assured 
+that your own description will replace such online descriptions as "Cool 
+Program" or "OK utility, but needs better ..."
+
+Please note that the ASP Hub Network, the Author Direct FDN (File 
+Distribution Network), and the majority of other electronic distribution 
+services *REQUIRE* that a valid FILE_ID.DIZ file be contained in your 
+submitted distribution archive. If your file doesn't contain a valid 
+FILE_ID.DIZ file, then it simply won't be distributed by these services. 
+Furthermore, most BBS sysops will not accept uploads of files which do not 
+contain a valid FILE_ID.DIZ file, so you automatically lose out on that 
+distribution as well.
+
+
+DESCRIPTION:
+------------
+FILE_ID.DIZ was created by Clark Development for use with their PCBDescribe 
+utility, as a means for BBS callers to upload a file without having to 
+manually type in a file description. It also ensures that the online 
+description is always the same regardless of the number of different BBS 
+systems the file is posted on. It has since been accepted by the BBS 
+industry more-or-less as the "standard" file description source. (The 
+extension of "DIZ" actually stands for "Description In Zip").
+
+NOTE: The FILE_ID.DIZ file *MUST* be named exactly that, and *NOT* 
+something like &lt;filename&gt;.DIZ. It will *ONLY* be used if it is named 
+FILE_ID.DIZ!
+
+The FILE_ID.DIZ file is nothing more than a straight ASCII text file which 
+contains the full description of the archived file containing it. It is 
+used by most popular BBS software to describe your program, rather than 
+using the description supplied by the person that uploaded your file. It 
+should be placed *INSIDE* your distribution archive file.
+
+The BBS software will "look" inside the archive file. If a FILE_ID.DIZ file 
+is found, it will replace any existing online file description with the 
+text contained in FILE_ID.DIZ. It is an excellent method for making sure 
+that your program files are described the way that "you" want them 
+described. Even sysops who's software can't automatically make use of the 
+FILE_ID.DIZ file have found it to be an excellent source for their manually 
+added file descriptions.
+
+
+STRUCTURE:
+----------
+The file consists of straight ASCII text, up to 10 lines of text, each line 
+being no more than 45 characters long. It should *NOT* contain any blank 
+lines, any form of centering or formatting, or any Hi-ASCII or ANSI 
+characters. (i.e. it should ONLY contain alpha &amp; numeric characters).
+
+We recommended that it consist of 5 basic parts:
+
+   1. the proper name of your program
+   2. the version number
+   3. the "ASP" identifier (optional, for ASP members)
+   4. the description separator
+   4. the description
+
+All of the above parts should be separated by a single "space".
+
+PROGRAM NAME: To set it apart from the rest, it is recommended that you use 
+ALL CAPS for the program name.
+
+VERSION NUMBER: The version number should be in the form of "v12.34". 
+
+ASP IDENTIFIER: If you are an ASP author, we recommend that an "&lt;ASP&gt;" 
+identifying mark be added after the version number, to identify your 
+product as an ASP-authored product.
+
+DESCRIPTION SEPARATOR: To separate the actual description text, insert a 
+simple "-" (dash/minus) character after the ASP identifier (or version 
+number, if not using the ASP identifier), and in front of the description 
+text.
+
+DESCRIPTION: You should attempt to FULLY describe your product, including 
+its most important functions and features. Be sure to include anything 
+which will separate your program from it's competition, and make the BBS 
+user want to download your file. Also try to include any hardware or 
+software requirements that your product may have.
+
+You should try to use the first 2 lines of the text to give a basic 
+description of your program. This is helpful for sysops who's BBS software 
+limits them to less than 10 lines, 45 characters. Sysops who are limited to 
+using shorter descriptions can simply use the 1st two lines and truncate 
+the rest. Thus, you can basically still supply your own description for BBS 
+software which does not actually utilize the FILE_ID.DIZ feature.
+
+The remaining lines of text can be used to elaborate on the programs 
+features, enhancements from the prior version, information concerning 
+multi-file sets. Please note that older versions of some BBS software can 
+only use 8 lines of text. It is advisable that you create your FILE_ID.DIZ 
+file so that the file can be truncated to various line lengths without 
+destroying it's usefulness.
+
+
+EXAMPLE
+-------
+MY PROGRAM v1.23 &lt;ASP&gt; - A program which will
+do anything for anybody. Will run in only 2k
+of memory. Can be run from the command line,
+or installed as a TSR. Completely menu-
+driven. Version 1.23 reduces the previous 4k
+memory requirements, and adds an enhanced
+graphical user interface. Also, MY PROGRAM 
+now contains Windows and DESQview support. 
+Coming soon - an OS/2 version.
+From Do-It-All Software, Inc. $15.00
+
+
+MULTIPLE DISK INFO
+------------------
+Please note that if your distribution archive requires multiple archive 
+files, you should create a separate, specific FILE_ID.DIZ file for each 
+archive. This can be utilized to describe the various contents of each 
+archive, and to identify each disk in the set. For example, the FILE_ID.DIZ 
+file for disk #1 could contain:
+
+   "MY PROGRAM v1.23 &lt;ASP&gt; Program Executable 
+    Files - Disk 1 of 2"
+    [followed by detailed description text]
+
+while the FILE_ID.DIZ file for disk #2 could contain:
+
+   "MY PROGRAM v1.23 &lt;ASP&gt; Documentation Files - 
+    Disk 2 of 2"
+    [followed by more detailed description text]
+
+Optionally, you could also create a "complete" FILE_ID.DIZ file for the 
+first disk, which would fully describe the program in detail, and identify 
+it as Disk 1 of x. Then, for each remaining file in the set, simply include 
+the Program Name, version number, ASP identifier, and the disk number (i.e. 
+"MY PROGRAM v1.23 &lt;ASP&gt; Disk 2 of x").
+
+
+ADDITIONAL INFO
+---------------
+Please don't be tempted to use fancy graphic or ANSI sequences in the 
+FILE_ID.DIZ file, as most BBS software will not allow this, and will render 
+your FILE_ID.DIZ file useless. Also, don't be tempted to simply copy your 
+program description file to FILE_ID.DIZ. Attempting to "format" your 
+FILE_ID.DIZ file (i.e line centering, right &amp; left justification, etc) will 
+also cause unexpected results, especially for BBS software which re-formats 
+descriptions to other than 10line/45char.
+
+Fred Hill &lt;ASP&gt; has written a freeware utility which interactively creates 
+a valid FILE_ID.DIZ file. The file is called DIZGEN.ZIP and can be found on 
+CompuServe (GO IBMBBS, Library 2) as well as on many fine BBS systems. I 
+highly recommend that you download a copy of this wonderful utility for 
+creating your FILE_ID.DIZ files.
+
+==========================================================================
+
+The following is a recommendation for the structure and contents of 
+distribution archives prepared for use on BBS systems.
+
+
+DISTRIBUTION DISK RECOMMENDATIONS
+---------------------------------
+The following are recommendations for preparing your program files for 
+distribution to Bulletin Board Systems (BBSs) via the ASP's distribution 
+services, as well as other methods.
+
+Two varieties of program files are defined here:
+
+1) Program files which utilize an "install" utility and self-extracting 
+program archives (later referred to as "Author-Installed Programs").
+
+2) Programs files which do not use install utilities or self-extracting 
+archives (later referred to as "User-Installed Programs").
+
+
+AUTHOR-INSTALLED PROGRAMS:
+--------------------------
+These programs require a bit more work from the author, but will eliminate 
+many user mistakes, especially in programs which require complicated 
+setups.
+
+Most "installation" utility programs will make use of program files which 
+have been "archived" into Self-Extracting (SFX) archives. We will attempt 
+to define which files should be contained in the Self-Extracting archives, 
+and which files should not.
+
+1. Files which should be contained in the self-extracting program file
+archive:
+
+        a. All program-specific executable files.
+        b. Any required configuration and/or data files required by the
+           program.
+        c. Program documentation files. Optionally, these may be left
+           outside of the self-extracting archive, in order to allow
+           them to be viewed/read by the various archive viewing utlities.
+        d. Any other program-specific files that are required for the
+           operation of the program.
+
+2. The files described above should be compiled into a self-extracting 
+archive file, which will then be extracted by the install utility.
+
+NOTE: the author is required to abide by any distribution requirements 
+specified by the archive utility author, and to obtain any required 
+distribution rights necessary. Please check to see if distribution rights 
+are required for your archive utility choice.
+
+3. Files which should NOT be contained in the self-extracting program file 
+archive:
+
+        a. The install utility itself (obviously).
+        b. The FILE_ID.DIZ file. (described in detail in the section
+           preceding this one)
+        c. Any distribution/information files, such as VENDOR.TXT,
+           SYSOP.TXT, etc.
+        d. Any description or information file, such as DESCRIBE.TXT.
+        e. A user file (such as README.1ST), which should explain how
+           to use the install utility, what the user should expect
+           during the installation, and any preparation that the user
+           should make prior to the installation. This file might also
+           contain a brief description of your program, in case the user
+           is able to read the documentation files in the distribution
+           archive prior to downloading (many BBS systems offer this
+           ability to the user).
+
+4. The actual distribution archive file (described below) should then 
+contain the install utility, the self-extracting program archive, and the 
+files described in #3 above.
+
+
+USER-INSTALLED PROGRAMS:
+------------------------
+This type of distribution archive is much simpler than the Author-Installed 
+variety. It should simply be an archive file, containing all of the files 
+for the program described above.
+
+Since this type of program requires the user to do all of the installation 
+manually, it should contain very specific and detailed information 
+regarding the installation requirements (such as INSTALL.TXT).
+
+
+THE DISTRIBUTION ARCHIVE FILE:
+------------------------------
+The actual distribution archive file should merely be an archive file 
+containing the files described above. For BBS distribution, this archive 
+should be of the standard archive format, and -NOT- a self-extracting 
+archive.  Many sysops will not allow self-extracting archives, and most BBS 
+software will not allow self-extracting archives to be uploaded.
+
+There are many popular archive utilities available, such as PKZIP, LHA, 
+LHARC, ARJ, etc. Most BBS systems are capable of handling archives in 
+virtually any format. However, you should be aware that most BBS systems 
+will convert your archive format to the format of choice by the sysop. By 
+following the methods described above, this conversion process should not 
+affect your program, or any self-extracting files which are contained 
+within your distribution archive file.
+
+You should also retain the default archive file extension defined by the 
+archive utility. For example, PKZIP uses a ".ZIP", LHARC uses "LZH", etc. 
+Changing the file extension may cause the BBS software to delete your file 
+because it doesn't recognize the format.
+
+For the actual filename for your distribution archive, it is recommended 
+that the program filename be limited to 6 characters to represent the 
+program's name (i.e. MYPROG could represent "My Program"). This should be 
+followed by 2 numeric digits which will represent the version number of 
+your release. Even if this is your initial release it should include the 
+version number in the filename (i.e. MYPROG10.ZIP would indicate the 
+program called "My Program" version 1.0).
+
+Please note that CompuServe limits filenames to only 6 characters. By 
+limiting the file "name" to 6 characters, you will easily be able to rename 
+the archive for CompuServe uploading by simply removing the 2-digit version 
+identifier, to make the file compatible with CompuServe libraries.
+
+By including the 2-digit version number in the archive filename, it will be 
+very easy for both the user and the sysop (and yourself) to identify older 
+versions of your program.
+
+
+MULTIPLE DISTRIBUTION ARCHIVES
+------------------------------
+At one time, it was recommended that your final distribution archive not be 
+larger than 350k, so that it would fit on a single 360k floppy disk and 
+still leave room for any distribution files necessary for Disk Vendors. 
+(i.e. Disk Vendors will often include their own GO.BAT file, or other 
+various small files to help their customers install the software). This 
+limitation is slowly falling by the wayside as more and more computer 
+systems have 3.5" floppy disk drives as standard.
+
+If your program is large enough to require more than one distribution 
+archive, it is recommended that your filename be limited to 5 characters 
+rather than 6 as described above. Following the 5-character name should be 
+the same 2-digit version number. Then, append a single "letter" to identify 
+the disk (i.e. MYPGM10A.ZIP, MYPGM10B.ZIP, etc.). For uploading to 
+CompuServe, these filenames may then be shortened to 6 characters by 
+removing the version identifiers (i.e. MYPGMA.ZIP, MYPGMB.ZIP). However, 
+for CompuServe it is recommended that you simply create a single 
+distibution file, and eliminate the multi-part file set.
+
+If your program requires multiple distribution archives, -BE SURE- to 
+create separate FILE_ID.DIZ files for each distribution archive. Also, each 
+FILE_ID.DIZ file should contain disk number information pertaining to each 
+individual archive (i.e. Disk 1 of 3, Disk 2 of 3, etc.).
+
+
+THE DISTRIBUTION DISK
+---------------------
+It is recommended that your distribution disk simply contain a ZIPd version 
+of your product. However, If you choose to supply "unarchived" files on a 
+distribution disk for Disk Vendor use, it is _VERY_ important that you 
+specify in your documentation a suggested archive filename, so that BBS 
+sysops can create archived files with the proper author-specified 
+filenames. This information should be contained in your SYSOP.TXT (or 
+VENDOR.TXT) file. If you don't supply a suggested archive file name, the 
+sysops will be forced to create the name themselves, thus you may end up 
+with thousands of versions of your products on BBS systems all over the 
+world, but all with different filenames.
+
+Please note that the ASP Hub Network, and nearly every other electronic 
+distribution service *REQUIRE* that your files be submitted as an archived 
+file, using the ZIP format. Also note that many BBS sysops will not go to 
+the trouble of ZIPing your unarchived files for you. If you don't supply 
+them with an archived distribution version of your product, it might not 
+get distributed by BBSs.
+
+If you supply your own disk labels, it is recommended that the ASP logo, or 
+at least the initials "ASP" be included on the label, so that anyone can 
+immediately identify your disk as an ASP member's software.
+
+
+SUMMARY
+-------
+Your distribution disk should now be ready to submit to the various BBSs, 
+distribution services, and Disk Vendors.
+
+You may choose to create a separate distribution disk for use by BBSs and 
+Disk Vendors. However, if you follow the above steps in preparing your 
+distribution archive file, a separate "Disk Vendor" disk is probably not 
+necessary. The majority of disk vendors will be able to accept your 
+distribution file/disk if it is prepared in the above described format.
+
+</PRE>
+
+<A HREF="index.htm"><IMG SRC="../images/b_arrow.png" ALT="Back" Border="0">Go Back</A>
+
+</BODY>
+</HTML>
+