From 86c57ee73435628e731ab0717ba32a7392c03998 Mon Sep 17 00:00:00 2001 From: Michiel Broek Date: Sat, 11 May 2002 19:52:56 +0000 Subject: [PATCH] Updated docs --- ChangeLog | 8 +- MBSE.FAQ | 182 --------------- Makefile | 2 +- examples/Makefile | 13 +- html/faq.html | 581 ++++++++++++++++++++++++++++++++++++++++++++-- html/index.htm | 6 +- html/manual.css | 4 +- 7 files changed, 576 insertions(+), 220 deletions(-) delete mode 100644 MBSE.FAQ diff --git a/ChangeLog b/ChangeLog index 9689ff16..66ca5f41 100644 --- a/ChangeLog +++ b/ChangeLog @@ -4893,9 +4893,9 @@ v0.33.20 10-Feb-2002 The Makefile now selects the right little or big endian menu files to install. Rebuild the menus and txtfiles for the new external editor. - Added templates.tar. For the time of development they will be - installed destructive, ie. all private changes will be lost - with every install. Later this will be a normal install. + Removed the mbsetup door from the sample sysop menus. + Added templates.tar, these are the default english macro files + for the diesel library. rundoor.sh Called door.bat instead of doors.bat @@ -4903,5 +4903,5 @@ v0.33.20 10-Feb-2002 installinit.sh Modified for SuSE 7.1 and later, the location of the startup script moved from /sbin to /etc. Patch by Joachim Kuwan. - Also modified init.SuSE for Yast on SuSE 8.0 + Also modified init.SuSE for Yast2 on SuSE 8.0 diff --git a/MBSE.FAQ b/MBSE.FAQ deleted file mode 100644 index 40cadf1b..00000000 --- a/MBSE.FAQ +++ /dev/null @@ -1,182 +0,0 @@ -Frequently asked questions for MBSE BBS - - -Author: P.E. Kimble aka King Kimerud - kimerud@bayhaus.org - - - -Introduction - -This FAQ is a work in progress. It is not complete, nor does its author claim -that it is complete. This FAQ only answers questions pertaining to using MBSE -BBS on your Linux box. It is a compilation of previous questions that Michiel -Broek has recieved and answered from us newbies in getting MBSE up & running. - - - -TABLE OF CONTENTS - -MBSE Installation - 1.1 Why do I have to install mbse in the /opt directory? - 1.2 Will MBSE ever be ported to other Operating Systems? - 1.3 Will MBSE BBS ever be ported to DOS/Windows or OS/2? - 1.4 What does the guest switch in BBS user setup mean? - 1.5 How do I monitor as the things happen? - 1.6 How to start mbsebbs from inetd? - -FidoNet Setup -2.1 The nodelist compiler crashes -2.2 What is the purpose of the "Comment" line in the tic area setup? -2.3 How do I poll a node? -2.4 I created a filerequest but mbcico doesn't call out. -2.5 Does MBSE support fidonet via ftp feeds? - -Internet Setup -3.1 Posting newsmessages to the newsserver fails. -3.2 Ftp fidonet feeds how-to - - - -INSTALLATION - -1.1 Why is MBSE installed in /opt/mbse, I want to install in /usr/local. - -A: The /opt is for extra applications, when mbse is installed there it - is easier to upgrade the OS. If insist on installing in /usr/local - the do it in /usr/local/mbse. - - -1.2 What other operating systems will MBSE run on? - -A. Currently only linux, most distributions. The author, Michiel Broek, -has made a valiant effort ensuring that MBSE-0.33.17 will recognize and -install on the major distributions of linux. Additionally, MBSE will compile -on FreeBSD, but is still in testing. - - -1.3 Will MBSE BBS ever be ported to DOS/Windows or OS/2. - -A: No. - - -1.4 What does the guest switch in BBS user setup mean. - -A: Nothing yet. - - -1.5 How do I monitor as the things happen? - -A: tail -f /opt/mbse/log/system.log or start mbmon. - - -1.6 How to start mbsebbs from inetd? - -A: This is described in the documentation of the mblogin program. - - - -FIDONET SETUP -2.1 The nodelist compiler crashes - -Note: From previous experience, it is vital that you follow the docs -closely. Also, ensure that you have a copy of a valid nodelist and -nodediff file. I have ran into problems where either the noddiffs -don't match the nodelist, the crc checks fail, or I have files from -two different zones. I have even had to back up several months before -finding a valid noddiff that would match the nodelist. - -A: Make sure the domain translations do exist, with mbsetup enter -menu 17 and save it even if you didn't change anything. - - -2.2 In Menu 10.2 (Tic Area Setup) line 1: comment, Is this an internal - comment or will this be extracted somehow and sent to downlinks? - -A: The downlinks will see this when receiving FileMgr replies. It is - meant only as a description for the filearea. - -2.3 How do I poll a node? - -A: mbout poll f2802.n280.z2 - - -2.4 I created a filerequest but mbcico doesn't call out. - -A: You need to add a poll for that node to do the call. - - -2.5 Does MBSE support fidonet via ftp transfers? - -A. No, not directly. It is a matter of using scripts to translate the .*lo -(*.flo, *.clo, *.dlo, *.ilo) files for each node, and copying the node's -outbound files to their respective directory. Refer to 3.2. - - - -INTERNET SETUP - -3.1 Posting newsmessages to the newsserver fails. - -A: Check if you need the "mode reader" command for the newsserver. - Set this flag in mbsetup 1.14.5 - - -3.2 How do I configure MBSE for my ftp filenet feeds? - - 1. In mbsetup menu 1.3.11, remove any reference to a DOS translation path. - 2. In mbsetup menu 1.3.12, remove any reference to a DOS translation path. - -This will give you a "True' path to your files directory where mbcico tosses -the inbound files. - - 3. Ftp Script for running a ftp feed with MBSE -NOTE: Gracefully contributed by Janis Kacht - -a. This script does not delete or change the .flo file. It reads it in and -creates a new script that will be used to move and copy the files to the user's -outbound directory you specify on the command line. Just call this script, -then call the finalflo.sh script with the directory name where the files -should be PUT, like: - - parseflo - finalflo.sh /home/fido/jdoe/out - -b. You will need a full path to the flo file in the "test" line below and change -the name of the flo file (it's not going to be 00000063.flo) -Uncomment the "if test" line, and also uncomment the last line (fi) - -#!/bin/sh -if test -e /opt/mbse/mail/outbound/00000063.flo ; then -cat 00000063.flo | sed 's/\/home/cp \/home/' > newflo.txt -cat newflo.txt | sed 's/\^\cp \/home/mv \/home/'> newflo2.txt -cat newflo2.txt | sed 's/$/ \$1/' > finalflo.sh -fi - -c. here's what finalflo.sh looks like, -$1 is a variable for the directory name you specify on the command line, -or in a cron script: - -cp /home/ftp/pub/filegate/fg_worf/filegate.zxx $1 -mv /opt/mbse/mail/outbound/00000063/dooqi39k.tic $1 -cp /home/ftp/pub/filegate/ss_areas/ss_areas.zip $1 -mv /opt/mbse/mail/outbound/00000063/dooqi39l.tic $1 -cp /home/ftp/pub/filebone/admin/backbone/backbone.z1b $1 -mv /opt/mbse/mail/outbound/00000063/dooqi39m.tic $1 - -## Janis Kracht can not and will not be held liable if harm is done to your -computer system due to any use of this script, either directly or indirectly. -This script works perfectly when instructions are followed, and the correct -directories are substitiuted. How it will affect your system, is the -responsiblity of the system administrator! - -### In the future this segment will be moved to the MBSEBBS-HOWTO! - -4. Do not forget to test this setup. It has work fine on my system, but -nothing works the way it should the first time out of the box! Pay close -attention to the ftp script and directories you enter. It seems as if 75% -of the problems experinced with this sed script is due to improper -outbound directories. - -"And that is all I am going to say about that"! - ~Forrest Gump diff --git a/Makefile b/Makefile index 2b3ba4be..001bc25c 100644 --- a/Makefile +++ b/Makefile @@ -4,7 +4,7 @@ include Makefile.global OTHER = AUTHORS ChangeLog COPYING DEBUG CRON.sh FILE_ID.DIZ.in \ - INSTALL.in MBSE.FAQ Makefile Makefile.global.in NEWS \ + INSTALL.in Makefile Makefile.global.in NEWS \ README README.GoldED README.isdn SETUP.sh TODO UPGRADE \ aclocal.m4 \ checkbasic config.h.in configure configure.in diff --git a/examples/Makefile b/examples/Makefile index 05a5c897..e2b52be1 100644 --- a/examples/Makefile +++ b/examples/Makefile @@ -29,15 +29,10 @@ install: tar xfC txtfiles.tar ${PREFIX}/english/txtfiles ; \ echo "Installing default english txtfiles" ; \ fi - @echo -e "\a" - @echo "WARNING: overwriting all your templates! Do not customize them yet," - @echo "there will be a lot of changes coming. If you still do so, it is not our fault" - @echo "Also do not make any translations yet! Wait until we are ready with this" - @echo "End of WARNING WARNING WARNING." - @echo -e "\a" - @echo -n "Press ENTER to continue: " - @read junk - tar xfC templates.tar ${PREFIX}/english/macro + @if [ ! -f ${PREFIX}/english/macro/html.tic ]; then \ + tar xfC templates.tar ${PREFIX}/english/macro ; \ + echo "Installing default english macro files" ; \ + fi clean: rm -f filelist Makefile.bak diff --git a/html/faq.html b/html/faq.html index ecf50edd..a5f4f753 100644 --- a/html/faq.html +++ b/html/faq.html @@ -13,52 +13,591 @@
-

MBSE BBS FAQ and Howto.

+

MBSE BBS FAQ and Howto.

-
Last updated 03-Apr-2002
+
Last updated 11-May-2002
+ 
+  Author: P.E. Kimble aka King Kimerud
+          kimerud@bayhaus.org
+
+ Introduction +

+ This FAQ is a work in progress. It is not complete, nor does its author claim + that it is complete. This FAQ only answers questions pertaining to using MBSE + BBS on your Linux box. It is a compilation of previous questions that Michiel + Broek has recieved and answered from us newbies in getting MBSE up & running.

  1. Installation
    1. Why do I have to install MBSE in the /opt directory?
      2. -
    2. Will MBSE ever be ported to other Operating Systems?
      3. -
    3. Will MBSE ever be ported to DOS/Windows or OS/2?
      4. -
    4. What does the quest switch in the bbs user setup mean?
      5. -
    5. How do I monitor as the things happen?
      6. -
    6. How do I start mbsebbs from inetd?
      7. +
    7. What other operating systems will MBSE run on?
      8. +
    8. Will MBSE ever be ported to DOS/Windows or OS/2?
      9. +
    9. What does the quest switch in the bbs user setup mean?
      10. +
    10. How do I monitor as the things happen?
      11. +
    11. How do I start mbsebbs from inetd?

     

    -
  2. Fidonet Setup
    3. +
  3. Fidonet Setup
      4. -
    1. The nodelist compiler crashes.
      2. -
    2. What is the purpose of the "Comment" line in the tic area setup?
      3. -
    3. How do I poll a node?
      4. -
    4. I created a filerequest but mbcico doesn't call out.
      5. -
    5. Does MBSE support fidonet via ftp feeds?
      6. +
    6. The nodelist compiler crashes, why?
      7. +
    7. What is the purpose of the "Comment" line in the tic area setup?
      8. +
    8. How do I poll a node?
      9. +
    9. I created a filerequest but mbcico doesn't call out.
      10. +
    10. Does MBSE support fidonet via ftp feeds?

     

    -
  4. Internet Setup
    5. +
  5. Internet Setup
      6. -
    1. Posting newsmessages to the newsserver fails.
      2. -
    2. FTP fidonet feeds how-to.
      3. +
    3. Posting newsmessages to the newsserver fails.
      4. +
    4. FTP fidonet feeds how-to.

     

    -
  6. BBS Setup
    7. +
  7. BBS Setup
      8. -
    1. How do I run DOS doors under MBSE BBS?
      2. +
    2. How do I run DOS doors under MBSE BBS?
+ + +BackGo Back +
-

1. Installation

+

1. Installation.

-1.1 Why do I have to install MBSE in the /opt directory?

+ + +
Q 1.1Why do I have to install MBSE in +the /opt directory?
A 1.1 The /opt is for extra applications, when mbse is installed there it is easier to upgrade the OS. If you insist on installing in /usr/local the choose /usr/local/mbse. -

+

Up

+ + +
Q 1.2 +What other operating systems will MBSE run on? +
A 1.2 +Currently only on most Linux distributions, FreeBSD and NetBSD. +The author, Michiel Broek, +has made a valiant effort ensuring that MBSE will recognize and +install on the major distributions of Linux. +
+Up +

+ + + +
Q 1.3 +Will MBSE BBS ever be ported to DOS/Windows or OS/2? +
A 1.3 +No. +
+Up +

+ + + +
Q 1.4 +What does the guest switch in BBS user setup mean? +
A 1.4 +Nothing yet. +
+Up +

+ + + +
Q 1.5 +How do I monitor as the things happen? +
A 1.5 +tail -f /opt/mbse/log/system.log or start mbmon. +
+Up +

+ + + +
Q 1.6 +How to start mbsebbs from inetd? +
A 1.6 +This is described in the documentation of the mblogin program. +
+Up +

+ +

+

2. Fidonet setup.

+ + + +
Q 2.1 +The nodelist compiler crashes, why? +
A 2.1 +Note: From previous experience, it is vital that you follow the docs +closely. Also, ensure that you have a copy of a valid nodelist and +nodediff file. I have ran into problems where either the noddiffs +don't match the nodelist, the crc checks fail, or I have files from +two different zones. I have even had to back up several months before +finding a valid noddiff that would match the nodelist. +
+Make sure the domain translations do exist, with mbsetup enter +menu 17 and save it even if you didn't change anything. +
+Up +

+ + + +
Q 2.2 +What is the purpose of the "Comment" line in the tic area setup? +
A 2.2 +The downlinks will see this when receiving FileMgr replies. It is +meant only as a description for the filearea. +
+Up +

+ + + +
Q 2.3 +How do I poll a node? +
A 2.3 +mbout poll f2802.n280.z2 +
+Up +

+ + + +
Q 2.4 +I created a filerequest but mbcico doesn't call out. +
A 2.4 +You need to add a poll for that node to do the call. +
+Up +

+ + + +
Q 2.5 +Does MBSE support fidonet via ftp transfers? +
A 2.5 +No, not directly. It is a matter of using scripts to translate the .*lo +(*.flo, *.clo, *.dlo, *.ilo) files for each node, and copying the node's +outbound files to their respective directory. +Refer to 3.2. +
+Up +

+ +

+

3. Internet setup.

+ + + +
Q 3.1 +Posting newsmessages to the newsserver fails. +
A 3.1 +Check if you need the "mode reader" command for the newsserver. +Set this flag in mbsetup 1.15.5 +
+Up +

+ + + +
Q 3.2 +How do I configure MBSE for my ftp filenet feeds? +
A 3.2 +
    +
  1. In mbsetup menu 1.4.12:2, remove any reference to a DOS translation +path. +
  2. +In mbsetup menu 1.4.12:3, remove any reference to a DOS translation +path. +
+ +This will give you a "True" path to your files directory where mbcico tosses +the inbound files. +
    +
  1. +Ftp Script for running a ftp feed with MBSE.
    +NOTE: Gracefully contributed by Janis Kacht <janis@filegate.net> +

    +This script does not delete or change the .flo file. It reads it in and +creates a new script that will be used to move and copy the files to the +user's +outbound directory you specify on the command line. Just call this script, +then call the finalflo.sh script with the directory name where the files +should be PUT, like: +

    +

    +parseflo <enter>
+finalflo.sh /home/fido/jdoe/out <enter>
+
    +

    +You will need a full path to the flo file in the "test" line below +and change +the name of the flo file (it's not going to be 00000063.flo) +Uncomment the "if test" line, and also uncomment the last line (fi) +

    +#!/bin/sh
+if test -e /opt/mbse/mail/outbound/00000063.flo ; then
+    cat 00000063.flo | sed 's/\/home/cp \/home/' > newflo.txt
+    cat newflo.txt | sed 's/\^\cp \/home/mv \/home/'> newflo2.txt
+    cat newflo2.txt | sed 's/$/ \$1/' > finalflo.sh
+fi
+
    +

    +here's what finalflo.sh looks like, +$1 is a variable for the directory name you specify on the command line, +or in a cron script: +

    +cp /home/ftp/pub/filegate/fg_worf/filegate.zxx $1
+mv /opt/mbse/mail/outbound/00000063/dooqi39k.tic $1
+cp /home/ftp/pub/filegate/ss_areas/ss_areas.zip $1
+mv /opt/mbse/mail/outbound/00000063/dooqi39l.tic $1
+cp /home/ftp/pub/filebone/admin/backbone/backbone.z1b $1
+mv /opt/mbse/mail/outbound/00000063/dooqi39m.tic $1
+
    +

    +Janis Kracht can not and will not be held liable if harm is done to your +computer system due to any use of this script, either directly or indirectly. +This script works perfectly when instructions are followed, and the correct +directories are substitiuted. How it will affect your system, is the +responsiblity of the system administrator! +

  2. + Do not forget to test this setup. It has work fine on my system, but + nothing works the way it should the first time out of the box! Pay close + attention to the ftp script and directories you enter. It seems as if 75% + of the problems experinced with this sed script is due to improper + outbound directories +
+
+Up +

+ +

+

4. BBS setup.

+ + + +
Q 4.1 +How do I run DOS doors under MBSE BBS? +
A 4.1 +
Written by: Redy Rodriguez, sysop of Parolas BBS 2:348/609
+Fidonet:    Redy rodriguez 2:348/609
+Email:      redy@users.sourceforge.net
+            Redy_Rodriguez@f609.n348.z2.fidospain.org
+
+

+NO WARANTEE +

+The information gathered here, works for the indicated intention. +It is proven and working in PAROLAS BBS, however, I do not guarantee that it +works correctly in all the cases. +The author is not responsible for the damage this can cause. +If you follow the instructions, and you get not the expected result, or as +a result of it you get undesired results, you loose data or destroy your +system, you you will be the only person in charge. +

+INTRODUCTION +

+This document describes how I have been able to execute MS/DOS doors in +MBSEBBS. Probably it is not the best way to do it, but this is the one that +works for me. +If somebody finds one more more effective, or simpler or safer a solution, +the I like to hear this solution. +

+WHAT IS NEEDED? +

+MBSEBBS is correctly compiled and working, in my case I have the version +0.33.19, that is at the moment the most recent and stable, I suppose that +this method can be valid for newer versions. +DOSEMU 1.0.2 I have tried previous versions, but these do not work correctly +with virtual ports. You can download dosemu.1.02.tgz from +www.dosemu.org, +you may also need to download the freedos archive dosemu-freedos-bin-1.02.tgz. +A partition with MS/DOS, I have on my disc a partition with installed MS/DOS, +and that is the one that I use, but I'm sure that many doors could work +correctly with the freedos. +You also need sudo. +Sudo is a utility that let's ordinary users execute certain programs as +superuser, this is available with almost all Linux distributions. +

+COMPILING DOSEMU +

+Unpack dosemu in some directory, for example /usr/src, then changed into +that directory and execute 'make'. When this is ready we have dosemu compiled. +If we already had a previous version of dosemu it is advisable to uninstall it +before continuing. +Copy dosemu-freedos-bin-1.02.tgz to the toplevel directory of the dosemu source +and execute: +

+
+./install_systemwide -fd dosemu-freedos-bin-1.02.tgz
+
+
+In the directory etc, within the directory where we have decompressed the +source code of dosemu we have configuration examples. Create the directory +/var/lib/dosemu if it does not exist the directory, and copy global.conf to +that directory. Also copy dosemu.conf to directory /etc and copy +dosemu.users.secure as dosemu.users to /etc. +

+ +CONFIGURE THE DOS PARTITION +

+Now we must configure the dos partition, in my case this exists as a mounted +dos partition in /dos/c. If this is not the case then you could work with an +image of freedos. I have created in my dos partition a directory c:\doors +where I install all doors that I want to use, and a file called c:\doors.bat +with the following contents: +

+@echo off
+c:
+cd \doors
+if exist %1.bat call %1 %2 %3 %4 %5 %6 %7 %8 %9
+c:\dosemu\exitemu
+
+
+Change to the directory /var/lib/dosemu and create directory called for +example 'c': +
+
+mkdir c. 
+
+
+A link to the mounted partition could be made but I prefer to create a new +directory and in that directory make links to dos program which are only +of interest for us. Many programs and directories of the dos partition +are not needed in dosemu and to run doors. +Change to the created directory and make links to everything what we have +in our dos partition (we will erase soon what we do not need). +Autoexec.bat and config.sys must copied instead of making links so we can +modify them, because surely we will want that they are different in dosemu, +then in real dos. +
+
+cd c
+ln -s /dos/c/* .
+rm autoexec.bat
+rm config.sys
+cp /dos/c/autoexec.bat config.sys .
+
+
+Create a directory dosemu and copy the typical utilities of dosemu. +
+
+mkdir dosemu 
+cp /usr/src/dosemu-1.02/1.0.2.0/commands/* dosemu
+
+
+Now we modify the copy of config.sys and autoexec.bat to erase everything what +is not necessary to execute our games as doors, like drivers for cdrom, mouse +etc... We will clear the keyboard driver 'KEYB XX' and make sure that in the +path in autoexec.bat to include the directory c:\dosemu. Also load the fossil +emulator, for example add these two lines: +
+
+path %PATH%:c:\dosemu
+c:\dosemu\fossil
+
+
+If there is another fossil, such as bnu or x00 in config.sys or autoexec.bat we +clear all references to these, we will load them if that is necessary in the +file that it executes the door when needed, this can be necessary for some +doors and for other not. +Now we can erase all the links to the directories who are not necessary, and +that we do not want that they are visible. +

+Then edit the file /etc/dosemu.conf and look for the line that begins with +"$_hdimage =" and change that to: +

+$_hdimage = "c" 
+
+
+Now login as root and you should be able to execute our dos emulator by +executing '/usr/bin/dosemu.bin' +

+(to leave dosemu type in exitemu) +

+ + +CONFIGURING SUDO +

+Normally the dos partition is not accessible to the users of the BBS, except +from within dosemu, and to be able to have access without activating the +setuid bit of dosemu, we use sudo so that any user of the BBS can execute +dosemu.bin as root. As root execute visudo to edit the configuration file of +sudo add the lines: +

+%bbs    ALL=NOPASSWD:/opt/mbse/bin/bbsdoor.sh
+%bbs    ALL=NOPASSWD:/opt/dosemu/bin/dosemu.bin
+
+
+The first command is a script that takes care of copying the file door.sys to +the dos partition, the second line is to allow to execute dosemu.bin. +Any user of group BBS can execute these commandos like root without password +is asked. +

+In order to test that this works login as user mbse and execute: +

+
+ sudo dosemu.bin 
+
+ +

+INSTALLING A DOOR +

+First we need a pair of scripts. These scripts are installed when you did +install MBSE. These scripts are needed to execute the doors and are installed +in /opt/mbse/bin: +

+--- rundoor.sh ---
+
+#!/bin/bash
+#
+# rundoor.sh - Never call this script directly, create a symlink
+#              to this file with the name of the door. For example
+#              tu run the door ilord do:
+#              cd /opt/mbse/bin
+#              ln -s rundoor.sh ilord
+#
+# by Redy Rodriguez and Michiel Broek.
+#
+DOOR=`basename $0`
+COMMANDO="\"door $DOOR $*\r\""
+
+/usr/bin/sudo /opt/mbse/bin/bbsdoor.sh $DOOR $1
+/usr/bin/sudo /opt/dosemu/bin/dosemu.bin \
+        -F /var/lib/dosemu/global.conf \
+        -I "`echo -e serial { com 1 virtual }"\n" keystroke $COMMANDO`"
+reset
+tput reset
+stty sane
+
+
+
+--- bbsdoor.sh ---
+#
+#  Initialize DOS environment before starting a bbs door.
+#  Parameters: $1 = name of the door
+#              $2 = the nodenumber for this session
+#
+#  by Redy Rodriguez, 22-Oct-2001
+
+if [ "$1" != "" ]; then
+    if [ "$2" != "" ]; then
+        mkdir -p /dos/c/doors/node$2 >/dev/null 2>&1
+        # Copy door.sys to dos partition
+        cat ~/door.sys >/dos/c/doors/node$2/door.sys
+        # Create .dosemu/disclaimer in user home to avoid warning
+        if [ ! -d $HOME/.dosemu ]; then
+            mkdir $HOME/.dosemu
+        fi
+        if [ ! -f $HOME/.dosemu/disclaimer ]; then
+            touch $HOME/.dosemu/disclaimer
+        fi
+    fi
+fi
+
+
+The script rundoor.sh is never called directly, simply create a link with the +name of the door to this file, this name must be the same as the one of the +.bat file that starts the door in the doors directory of the dos partition. +Let me explain this with an example: +

+I have chosen the door Virtual Sysop, but it could be any other door. +My experience says to me that not all doors work correctly with a serial port +in virtual mode. This one is working at Parolas BBS. +

+Unpack Virtual Sysop in the dos partition, in the directory c:\doors\vsysop. +Execute as user mbse 'sudo dosemu.bin' and make sure that the door works in +local mode (these commands are for this door): +

+cd doors
+cd vsysop
+vsysop -local
+
+
+If everything is correct then create the file c:\doors\vsysop.bat with the +following contents: +
+
+--- vsysop.bat ---
+@echo off
+C:\COMUNIC\X00\X00 E B,0,57600
+cd vsysop
+vsysop -D c:\doors\node%1\door.sys -BBSNAME PAROLAS
+deltree /y c:\doors\node%1
+C:\COMUNIC\X00\X00
+cd ..
+
+
+Before passing the control to dosemu, the file door.sys will be copied to +c:\doors\node???? where the ???? is the node number from which the door is +invoked (to allow that several users can execute the door at the same time). +This nodenumber also is passed as the first parameters to the .bat file, this +is to indicate to which directory to copy the door.sys file. +

+The Virtual Sysop door supports door.sys and that is the only dropfile that +is generated by mbsebbs and that is supported by most of the doors. +If you need another format you must use a converter to change the format of +the dropfile. +

+I use the fossil X00, I have it installed in C:\COMUNIC\X00 and this door works +for me correctly with these parameters, it is alos possible that it works +without X00 or that you can load another fossil. +

+Now create a link to rundoor.sh in /opt/mbse/bin called vsysop. The name must +be the same one that the name of the .bat file created in the dos partition, +but without the extension bat. +

+ln -s /opt/mbse/bin/rundoor.sh /opt/mbse/bin/vsysop
+
+
+Now we execute mbsetup and enter the menu setup to add an entrance like this +(It puts option 16 to Yes): +
+
+ 8.3. EDIT MENU ITEM
+
+ 1.  Sel. key  V
+ 2.  Type nr.  7         Run external program in shell
+ 3.  Opt. data /opt/mbse/bin/vsysop /N
+               1234567890123456789012345678901234567890123456789012345678901234
+ 4.  Display
+ 5.  Security  0     --------------------------------
+ 6.  Min. age  0
+ 7.  Max. lvl  0
+ 8.  Password  <null>                    13. No door.sys No
+ 9.  Credit    0                         13. Y2K style   No
+ 10. Lo-colors Normal display color      14. Use Comport Yes
+ 11. Hi-colors Bright display color      15. Run nosuid  Yes
+ 12. Autoexec  No                        16. No Prompt   Yes
+
+
+And that is everything... +
+Up +

+ +

diff --git a/html/index.htm b/html/index.htm index 40729668..85593f36 100755 --- a/html/index.htm +++ b/html/index.htm @@ -13,10 +13,11 @@
-

MBSE BBS System Guide v0.33.20

+

MBSE BBS System Guide v0.33.20

-
Last update 10-May-2002

+

Last update 11-May-2002
+

Introduction

@@ -123,6 +124,7 @@

Other Notes

diff --git a/html/manual.css b/html/manual.css index d9818384..ce14f386 100644 --- a/html/manual.css +++ b/html/manual.css @@ -1,9 +1,11 @@ /* + * $Id$ + * * stylesheet for the MBSE BBS manual. */ -BODY { background-color: white; font-family: Arial, Helvetica; font-size: 12pt; } +BODY { background-color: white; font-family: Arial, Helvetica; } /* * H1 is the page header, H3 the paragraph header, H5 is topright update date.