MESSDOS(tm)/Door Version Log


------------------------------------------------------------------------------


                           VERSION 3.40 (28-May-1992)

Version 3.40 is the final version of MESSDOS(tm)/Door.  All registration code
has been removed, and all "registered version only" features have been added
to this release.


------------------------------------------------------------------------------


                           VERSION 3.30 (1-Feb-1992)

Version 3.30 features a new configuration variable, EXITPATH.  Specifying
an EXITPATH in the configuration file (.CNF) will cause MESSDOS(tm)/Door
to search for DORINFO1.DEF and (if it exists) EXITINFO.BBS in the specified
directory, instead of the current directory.

In addition, I have added word-wrap to the internal chat mode.

------------------------------------------------------------------------------


                           VERSION 3.22 (27-Aug-1991)

MESSDOS(tm)/Door will now correctly handle situations where the EXITINFO.BBS
file does not exit (for example when using a door converter with non-Quick/RA
compatible software).


------------------------------------------------------------------------------


                           VERSION 3.21 (14-Jun-1991)

Version 3.21 fixes a few minor bugs.

I also added the @CHATFLAG action statement to the AutoChat commands (contained
in the .AUT file).  This will allow AutoChat to force on the "want-to-chat"
flag on the status line, so that the Sysop will know that the user wanted to
chat.


------------------------------------------------------------------------------


                           VERSION 3.20 (8-Feb-1991)

I converted MESSDOS(tm)/Door over to use the RkPlus registration key unit,
instead of rKey.

The AutoChat feature is now available, only when MESSDOS(tm)/Door has been
registered.  However, all MESSDOS(tm) commands and functions are still
fully functional.

I added the @REG action statement.  This statement will only execute the
statements following it, if the MESSDOS(tm)/Door has been registered.  The
main reason for this is to allow the distribution files to contain
@AUTOCHAT statements, even though AutoChat doesn't work until MESSDOS(tm)/Door
has been registered.


------------------------------------------------------------------------------


                           VERSION 3.12 (5-Feb-1991)


The CHATMSG configuration variable may now take one of two forms :

CHATMSG=Text

or

CHATMSG=/Keyword

If the first form is used, AutoChat will display they text as the introductory
message.  For example :

CHATMSG=Hello.  Can I help you?

AutoChat would display "Hello.  Can I help you?" as the introductory message.

If the second form is used, AutoChat will look up the keyword and display
the message text as the introductory message.  For example :

CHATMSG=/HELLO

AutoChat would look up "HELLO" in the AutoChat control file (.AUT) and display
the resulting text as the introductory message.

All of MESSDOS(tm)/Door's %PARAMETERS% may now be used in the AuotChat control
file (.AUT).  For example :

BBS, %BBSNAME%, SYSTEM
[
How do you like %BBSNAME%?
]

If the user typed "BBS" or the name of the BBS or "SYSTEM", AutoChat would
display the message text, replacing %BBSNAME% with the name of the BBS.

I also fixed a bug where lines that displayed past column 79 (using |) would
sometimes write over the status line.


------------------------------------------------------------------------------


                           VERSION 3.11 (25-Jan-1991)


I added CHATERR and CHATMSG configuration variables (defined in the
.CNF configuration file).  The text in CHATERR will be displayed if AutoChat
is unable to find any keywords (in the .AUT file) that match what the user
has typed.  A typical definition might be :

CHATERR=I don't understand.

The text in CHATMSG will be displayed when the user first enters AutoChat.
This will allow you to "name" your AutoChat and allow him/her to introduce
himself/herself.  A typical definition might be :

CHATMSG=I am the PIRKLE 1000 computer.  May I help you?

I have also added AutoChat commands to the sample KLONEDOS files that are
included with MESSDOS(tm)/Door.

------------------------------------------------------------------------------


                           VERSION 3.10 (24-Jan-1991)


I removed the "Sysop increased time" and "Sysop decreased time" messages
from the [Ins] and [Del] keys, since the time is displayed on the status
line.

I also added a very simplistic version of AutoChat.  The AutoChat function
is initiated by pressing [Alt-A] from the console or issuing an @AUTOCHAT
command in the Command Data File (.DAT).  AutoChat is controlled by the
AutoChat Control File (.AUT).  An entry in the file has the following
format :

KEYWORD1,KEYWORD2,KEYWORD3
[
Text to be displayed.
]

Lines starting with # will be ignored (comment lines). Each line may be up to
80 characters wide.  Text ending with | will be displyed without a trailing
carriage return & linefeed.  There may be any number of keywords divided by
commas.  There may also be more than one line of keywords for an entry.  All
text must be contained between lines starting with [ and ]. Any text surrounded
by ^ will be displayed in bold.  The _ character may be used to force a pause
and ~ will backspace.  Using these you can give the AutoChat a more "human"
appearance, by allowing the display and correction of "errors".  For example :

HELP,CONFUSED,?
[
I am not~~~unable to helo~p you __at~~right now. |
Please try again later.
]

AutoChat will type "I am not" and then backspace 3 spaces, type "unable to
helo", backspace and type "p you ", pause, type "at", backspace and type
"right now. Please try again later."

If "@ENDCHAT" appears between [ and ], AutoChat will terminate, returning the
user to MESSDOS(tm)/Door.

The best way to understand AutoChat is to edit that MDD.AUT file (or create
your own) and watch how it acts.  Unlike normal Chat mode, AutoChat WILL work
in local mode.

Future versions of MESSDOS(tm)/Door will feature a more configurable and more
powerful version of AutoChat (including @ACTION statements and %VARIABLES%).


------------------------------------------------------------------------------


                           VERSION 3.02 (1-Dec-1990)


Version 3.02 will display the blinking "[Chat]" message, if the user paged
the Sysop in the BBS, before running MESSDOS(tm)/Door.


------------------------------------------------------------------------------


                           VERSION 3.01 (10-Nov-1990)


Version 3.01 fixes a few minor bugs that slipped past the 3.00 beta tests.

The @IFUSER action statement was comparing incorrectly.  This has been fixed
in 3.01.

The blinking "[Chat]" message was the wrong colour (and not blinking), if the
user's ANSI was turned off.  This has been corrected in 3.01.

If MESSDOS(tm)/Door was run with the -N (No BBS) parameter and the user
pressed ALT-C, the BBS local status line was appearing.  This no longer occurs
in version 3.01.


------------------------------------------------------------------------------


                           VERSION 3.00 (8-Nov-1990)


Version 3.00 features several changes to the format of the command data file.
Because of this, version 2.x files will need to be converted to version 3.xx
format.  The MDD/Convert utility has been re-written to correctly handle
file conversions for all future versions of MESSDOS(tm)/Door, through the use
of version ID stamping.  MESSDOS(tm)/Door can now detect the major version ID
of the data file and MDD/Convert can detect and update it.  Since there is no
version ID stamp on 1.x and 2.x files, the old conversion program (renamed as
MDD/1to2) is still required to convert from 1.x to 2.x.  See MDD1TO2.DOC,
MDDCONV.DOC and MDD.DOC for conversion information.

The version ID stamp (;X where "X" is the major version ID) has been added to
the command data file in version 3.00.  This will be placed in 2.x files by
MDD/Convert.

The file list ($) option characters < and > have been changed to { and } in
version 3.00.  MDD/Convert will convert all occurances of <option> to {option}.

@IFSEC and @IFTIME handling has been changed to allow for the new greater-than
and less-than processing of numeric comparisons in version 3.00.  In version
2.x, @IFSEC would do a greater-than-or-equal test and @IFTIME would do a
less-than-or-equal test.  Now that all numerics can be tested with greater-than
and less-than logic, @IFSEC and @IFTIME now work the same as other numeric
comparisons.  MDD/Convert will convert all occurances of @IFSEC and @IFTIME
to use greater-than and less-than tests, so that they will retain their
original meaning.

Starting with version 3.00, lines in the command data file no longer have to
start in column one.  The control character still must be the first non-blank
character on each line, but it can be preceeded by any number of blanks.

Starting with version 3.00, MESSDOS(tm)/Door features a registration key.
The unregistered version is NOT crippled, it will merely display the message
"unregistered".  The new MDD/Brand program is used to "brand" MESSDOS(tm)/Door
after registration.  See REGISTER.FRM for information on obtaining a
registration key.

New in 3.00 are comparisons of numeric variables (@IFNx).

Version 3.00 also features less-than and greater-than testing.  Any numeric
comparison (@IFNx, @IFSEC and @IFTIME) may be used in several ways :

  @IFN.COUNT 4     (if N.COUNT equals 4)
  @IFN1 <9         (if N.1 is less than 9)
  @IFN.TRY ~10     (if N.TRY is NOT equal to 10)
  @IFN17 >8        (if N17 is greater than 8)
  @IFSEC ~<10      (if ?SECURITY is NOT less than 10)
  @IFTIME ~>20     (if ?TIME is NOT greater than 20)

Version 3.00 also features contains and is-contained testing for strings.
Any string comparison (@IFVx, @IFUSER, @IFPARAM, etc.) may be used one of
several ways :

  @IFV.TEST THIS   (if V.TEST equal "THIS")
  @IFUSER >SMITH   (if ?USERNAME contains "SMITH")
  @IFV4 ~READY     (if V4 is NOT equal to "READY")
  @IFKEY <AEIOUY   (if ?KEY is contained in "AEIOUY")
  @IFKEY ~<YN      (if ?KEY is NOT contained in "YN")
  @IFUSER ~>JONES  (if ?USER does NOT contain "JONES")

Version 3.00 features the @BREAK action statement.  This will cause the
current command to stop executing, as if the end of the command had been
reached.

Version 3.00 features chat requests.  This is handled through the @CHAT action
statement and the CHATON, CHATOFF and CHATGO configuration variables.  Whenever
a @CHAT action statement is executed, it will compare the current time
against the values of CHATON and CHATOFF.  If it falls between those times,
the program will attempt to page the sysop.  If not (or if the sysop doesn't
respond), the program will go to (@GOTO) the label specified by the CHATGO
configuration variable.  If CHATON and CHATOFF both equal 0, paging will be
allowed at all times.  If CHATON = CHATOFF (but not 0), paging will NEVER be
allowed.  If the sysop fails to respond to a chat request, or the request is
made outside of allowable hours, a blinking "[Chat]" message will be displayed
on the local status line.  This message will disappear if the sysop goes into
chat mode with the user (ALT-C).

User command parameter checking has been added in version 3.00.  This is
handled through the @IFPARAM action statement and the ?PARAM variable.
?PARAM will contain everything typed by the user EXCEPT the command itself.
The value of ?PARAM may be tested with @IFPARAM, which may use contains and
is-contained testing.

Also new to version 3.00 is user flag testing.  User flags are tested with
the @IFAx, @IFBx, @IFCx and @IFDx action statements.  User flags may be
displayed in the format "--------" (with "X" appearing for flags that are
ON and "-" appearing for flags that are OFF), using the ?AFLAG, ?BFLAG, ?CFLAG
and ?DFLAG variables.

Boolean comparisons (@IFANSI, @IFAx, @IFBx, @IFCx and @IFDx) may now use
not (~) logic in version 3.00.  Like all @IF statements, a space is required
between the statement and the ~ (if used).

The following utilities were also updated :

  MDD/Random  (current version is 1.4)
  MDD/Convert (current version is 2.0)
  MDD/Brand   (current version is 1.0)
  MDD/1to2    (renamed version of original conversion utility)


------------------------------------------------------------------------------


                                 VERSION 2.71


Version 2.71 upgraded the program to use JP Door 2.71 SE.


------------------------------------------------------------------------------


                                 VERSION 2.70


Version 2.70 now features variable definitions.  This will allow the sysop to
use more meaningful variable names in the command definition file (instead of
V45, N17, etc).  Definition names may be any length (but only the first 12
will be used), must begin with a letter and may contain letters, numbers and
underscores.  Definition names are defined in the configuration file (.CNF),
using the DEFVx= and DEFNx= configuration variables.  They may also be defined
in the command data file, using the @DEFVx and @DEFNx action statements.

After a definition name has been defined for a variable, it may be used to
refer to that variable, by using the "." special symbol.

For example, after defining a definition name of "TEST" for "V1" :

@DEFV1 TEST

you may now refer to V1 as V.TEST :

"The results of the test was|
!V.TEST

This will display the value of V.TEST (which is actually V1).  Definition
names may be used anywhere that a variable name (Vx or Nx) is used.  If more
than one definition is defined for the same variable, the last one defined will
be used.

Also in 2.70 a minor local display bug was corrected in the <ins> and <del>
(increase time and decrease time) functions.


------------------------------------------------------------------------------


                                 VERSION 2.62


Version 2.62 features improved critical error handling.  If a hardware error
or unexpected program error occurs, the program will display a message to
the user requesting that he/she notify the sysop that an error has occured.
On the local console, an error message will be displayed in the following
format :

Error nnn (error message) at ssss:oooo

nnn        will be the error number.
ssss:oooo  will be the address of the error (segment:offset)

The error message will also be posted to the error log file.  When reporting
an error, please be sure to include the error number (nnn) and the error
address (ssss:oooo) to assist us in locating and correcting the problem.

Also in version 2.62, @SHOWFILE will no longer attempt to decode the
QuickBBS (tm) control codes, if MESSDOS(tm)/Door was executed with the
-N (no BBS) command line parameter.  This is to prevent the program from
attempting to read a non-existant EXITINFO.BBS file.  The QuickBBS (tm)
control codes will still be decoded correctly, when running from a BBS,
either remote or local.


------------------------------------------------------------------------------


                                 VERSION 2.61


Version 2.61 now decodes QuickBBS (tm) control codes contained in ASCII and
ANSI files.  This is due to enhancements in JP Door (tm).

Version 2.61 also corrected a minor bug where a user could turn on and off the
sysop's bold-text mode, in chat.


------------------------------------------------------------------------------


				 VERSION 2.60


Version 2.60 features a 2 line status area at the bottom of the screen
(instead of the 1 line status area at the top of the screen in previous
versions).  This is due to enhancements in JP Door (tm).

Version 2.60 will display a leading $FE character on all messages to the
local console.

The list option delimiters were changed from to '<' and '>' to '{' and '}'
in version 2.60.  MESSDOS(tm)/Door will still recognize '<option>', but
'{option}' is preferable.  '<' and '>' will be reserved for other uses in
a major future release (most likely, 3.0).

The <ALT-H> sysop control key was added in version 2.60.  This will
immediately hang-up the user, by forcing DTR off for 700 milliseconds.
If the modem has carrier detect forced on, or MESSDOS(tm)/Door is running
in LOCAL mode, ALT-H will function the same as ALT-Q (force the user to
quit the program).

Version 2.60 also corrected a minor problem where sysop control keys were being
logged, even if logcmd was set to OFF in the configuration file.


------------------------------------------------------------------------------


				 VERSION 2.52


Version 2.52 corrected a minor problem with the local display, when a sysop
control key was pressed. Also, due to key assignment conflicts, the sysop
control keys for increasing and decreasing time were changed to <ins> and
<del> (instead of <up> and <down>).

Also, in version 2.52, hot key checking was added when viewing a file
(@SHOWFILE). While viewing a file, the user may now press 'S' to stop.


------------------------------------------------------------------------------


				 VERSION 2.51


Version 2.51 fixed a bug in the display colours, which was causing RCOLOUR
and MCOLOUR definitions to be reversed.

Also, in version 2.51, the remote line entry routines were improved (including
the addition of CTRL-R command recall).


------------------------------------------------------------------------------


				 VERSION 2.5


Version 2.5 features %PARAMETERS to action statements. Any ?VARIABLE may be
specified as the parameter of an @ACTION statement, by enclosing it between
% special characters. When a %PARAMETER is encountered as the parameter of an
@ACTION statement, it is replaced by the value of the corresponding ?VARIABLE.
If a %PARAMETER is the last (or only) item on a line, the final % is not
required.

Also new in version 2.5 is the TAB control key in Chat Mode. This key allows
the sysop to toggle bold-text, during chat.


------------------------------------------------------------------------------


				 VERSION 2.4


Version 2.4 features Sysop Control Keys, which allow sysops to perform
certain local functions, while a user is in MESSDOS(tm)/Door. The following
Control Keys may be pressed (at the local console ONLY) :

F1	 Pressing F1, will display a list of Sysop Control Keys to the local
	 console. Nothing will be displayed at the user's terminal.

<up>	 Pressing the <up arrow> key will increase the user's time limit
	 and display a message to the local console stating that the user's
	 time had been increased. Nothing will be displayed at the user's
	 terminal.

<down>	 Pressing the <down arrow> key will decrease the user's time limit
	 and display a message to the local console stating that the user's
	 time had been decreased. Nothing will be displayed at the user's
	 terminal.

ALT-C	 Pressing ALT-C will enter CHAT mode. You may press ESC to cancel CHAT
	 mode.

ALT-Q	 Pressing ALT-Q will force the user to Quit MESSDOS(tm)/Door. No
	 message will be displayed at the user's terminal.

Note : Changes to user's time limit are ONLY in effect while the user is in
       MESSDOS(tm)/Door.


------------------------------------------------------------------------------


				 VERSION 2.3


Starting with version 2.3, there are now 255 variables and numeric variables
available for use (instead of 3). @SETVx, @SETNx, @IFVx, @ADDNx, ?Vx and ?Nx
now allow a value of "x" between 1 and 255.

New in version 2.3 are the @READ and @WRITE action statements. They will allow
the current variable values to be read from and written to a file.

Also new to version 2.3 are the @GOTO action statement and the : control
character. They will allow you to define labels, in the command data file, and
branch to them. The STARTUP statement, in the configuration file, may be
specified, causing MESSDOS(tm)/Door to branch to a specific label, when
starting the program.

MDD/Random has been update to allow a -N parameter to be specified. If this
parameter is specified, it will passed on to MESSDOS(tm)/Door (allowing it
to run in NO BBS mode).


------------------------------------------------------------------------------


				 VERSION 2.21


Version 2.21 fixed a minor bug in the Runtime Error Handling routines and
added the posting of a System Error message to MDD.ERR, if a Runtime Error
occurs.

Also, some minor changes were made to the MDD.DAT and KLONE.DAT files.


------------------------------------------------------------------------------


				 VERSION 2.2


Version 2.2 now features the -N command line parameter, which specifies NO BBS
mode. This allows MESSDOS(tm)/Door to be run, with no DORINFO1.DEF file. All
of the values, which are normally defined in DORINFO1.DEF, may be changed in
the configuration (.CNF) file. These values will be ignored (and DORINFO1.DEF
will be used), if the -N parameter is not specified.

Starting with version 2.2, MESSDOS(tm)/Door can be configured to log all of
the commands, typed by a user. This will allow the sysop to see which commands
are being used and to determine if there are any commands that should be
added.


------------------------------------------------------------------------------


				 VERSION 2.1


Version 2.1 is now distributed with a specially-written DORINFO1.DEF file, that
will allow MESSDOS(tm)/Door to be run without a BBS.

Starting with version 2.1, MESSDOS(tm)/Door will attempt to display an
ANSI/ASCII startup file, when it first runs. It will use the filename
specified on the command line (default MDD) with the extension .ANS (if the
user's ANSI flag is set ON) or .ASC. If you don't want a startup file
to display, simply make sure that no .ANS or .ASC files (with same name as
the .CNF and .DAT files) exist in the current directory.

Version 2.1 now features conditional action statements. Because they are
being read from a text file, conditionals in MESSDOS(tm)/Door work somewhat
differently than their "traditional" counterparts (ie. those found in most
languages). When MESSDOS(tm)/Door encounters any conditional action statement,
within the "text" of a command, it evaluates the condition. If it is true,
it continues with the next line. If it is false, it skips to an @ELSE or
@ENDIF statement (an @ENDIF statement will be assumed, if the next command is
reached and no @ENDIF has been found). Therefore, conditionals can not be
"nested", as such. However, any conditionals encountered before an @ENDIF,
will be evaluated *only* if the preceeding conditions were true. Thus, allowing
you to use "and" logic. If the first character of the parameter of any
conditional action statement is ~ (not), the test will evaluate opposite
of how it would've evaluated without the ~. If the first character of the
parameter of any non-conditional action statement is ~, it will be ignored.
Examples can be found with explanations of the various conditional action
statements, as well as, in the sample .DAT files distributed with
MESSDOS(tm)/Door.

Version 2.1 also features "conditional" commands (based on the current value
of ?PROMPT). This (combined with enhanced @SHOWDIR and @SHOWCMD action
statements) will allow you to setup different commands that will only work
when the user is in the correct "directory". Examples can be found with
explanations of @SHOWDIR and @SHOWCMD, as well as, in the sample .DAT files
distributed with MESSDOS(tm)/Door.

There are several new action statements and variables available in version
2.1 of MESSDOS(tm)/Door. Also, a bug was corrected in @SETV3 and the
?V3 and !V3 variables, and a bug was corrected in MDD/Random, which caused
it to use a range of 1 less than the total of the weights specified.


-------------------------------------------------------------------------------


				 VERSION 2.0


Starting with version 2.0, the configuration and command data file for
MESSDOS(tm)/Door can be randomly selected by the MDD/Random program.
MDD/Random reads the MDDRND.LST file to determine the available .CNF/.DAT
files and the "weight" of each one (how often it is to be selected). This
will allow you to set up several different files and have a random one
selected, wnen the user chooses the menu option. For example, you might
have MESS-DOS[tm] (MDD), KLONEDOS (KLONE), SO/2 (SO2) and ZENYUCKS (ZEN).
You could define them in MDDRND.LST as follows :

mdd:3
klone:3
so2:2
zen:1

MESS-DOS[tm] (MDD) would be selected 3 out of 9 time, KLONEDOS (KLONE) would
be selected 3 out of 9 times, SO/2 (SO2) would be selected 2 out of 9 times,
and ZENYUCKS (ZEN) would be selected 1 out of 9 times.

The format of each line of MDDRND.LST is filename:weight. Up to 100 filenames
may be specified, with a weight value of up to 100 per filename. (Comments
are specified by starting the line with #).

When MDD/Random is executed, the weights are totalled and each weight then
represents the number of chances (out of the total weights) that the
particular filename will be selected.

If MDD/Random is executed with a -t (testing) parameter, it will display
the total weights (from MDDRND.LST), the weight picked randomly, and the
file that would've been selected (MDD.EXE won't be run).

New to 2.0 are action statements. Action statements are specified by lines
starting with @ in the command data file. These lines are treated as text,
except that when the line is to be displayed, the specified action is
performed, instead.

Also new to 2.0 are variables. Variables are specified by lines starting with
! or ? in the command data file. These lines are treated like text, except
that when the line is to be displayed, it is replaced by the value of the
variable. If the variable begins with !, it will be displayed bold.


-------------------------------------------------------------------------------


				 VERSION 1.3


This is an in-house version of MESSDOS(tm)/Door, used for testing some of
the earlier features of 2.0. This version should not exist outside of
Serious Cybernetics. If you are running 1.3, you should replace it IMMEDIATELY,
with 2.0 (or later). It uses the old 1.x command data file format and
contains *several* bugs in the @SHOWDIR and @SHOWCMD action statements
(among others).

I can't see any way that any copies of this version could've reached the
general public, but I have included this message, just in case.


-------------------------------------------------------------------------------


				 VERSION 1.2


Several people indicated interest in having MESSDOS(tm)/Door emulate different
environments (rather than MESS-DOS [tm]. Therefore, version 1.2 includes
new configuration variables to allow you to change the headings, version
message and error messages displayed by MESSDOS(tm)/Door. You should be able
now to make it appear as if the user has shelled out of the BBS into
whatever-you-want-to-make-them-think-they-are-in.

Also, in version 1.2, I have added the bold response colour (which is set
with the "bcolour" configuration variable, in the configuration file). Any
text marked as bold (enclosed between ^ and ^) will be displayed in the
bold colour. If you don't want any text to be displayed as bold, simply
change the value of "bcolour" to the same value as "rcolour".

Since it is now possible to completely change the way that MESSDOS(tm)/Door
looks and acts, I have allowed you to specify a name for your configuration
and command data files, on the command line. This will allow you to have more
than one "shell" setup. For example, you could keep have MESS-DOS (tm)
defined in "MDD.CNF" and "MDD.DAT" (the default), KLONEDOS defined in
"KLONE.CNF" and "KLONE.DAT", SO/2 defined in "SO2.CNF" and "SO2.DAT", and
ZENYUCKS defined in "ZEN.CNF" and "ZEN.DAT" (you get the idea). I have
included a copy of KLONE.CNF and KLONE.DAT in MDD12.ZIP, to help
illustrate the point. These files provide a complete copy of KLONEDOS.

In the above examples, MDD would run MESS-DOS (tm), MDD KLONE would run
KLONEDOS, MDD SO2 would run SO/2 and MDD ZEN would run ZENYUCKS. The
extentions (.CNF and .DAT) are supplied by MESSDOS(tm)/Door. The default
filename (MDD) is determined by parsing the filename of the MESSDOS(tm)/Door
program. Therefore, if you need to be able to run it without using command
line parameters, you can rename (or copy) MDD.EXE to the same name as your
configuration and command data files. In the previous examples, you could
copy MDD.EXE to KLONE.EXE and SO2.EXE and ZEN.EXE, after which you could
simply type the program name to run MESSDOS(tm)/Door with the correct
.CNF and .DAT files.


-------------------------------------------------------------------------------


				 VERSION 1.1


Starting with version 1.1, all MESS-DOS(tm) commands are defined in an external
command data file, that may be changed by the sysop.


-------------------------------------------------------------------------------


				 VERSION 1.0


Version 1.0 was the first release of MESS-DOS(tm) as a door program for
QuickBBS(tm).  Copies of the original, non-door version of MESSDOS(tm)
may still exist as MESSDOS.EXE.


-------------------------------------------------------------------------------


MESS-DOS[tm] (c) 1987-92 C. Scott Davis and Serious Cybernetics
MESSDOS(tm)/Door (c) 1990-92 Serious Cybernetics
MDD/Random, MDD/Brand and MDD/Convert (c) 1990, 1991 Serious Cybernetics
MDD/1to2 (c) 1990 Serious Cybernetics
RkPlus (c) 1991 Serious Cybernetics
rKey (c) 1990, 1991 Serious Cybernetics
Turbo Pascal (c) 1983, 1989 Borland International
JP Door (c) 1989 John Parlin
QuickBBS (c) The QuickBBS Group