Dec 122017
 
DoorMaster is a BBS utility that will allow a QuickBBS 2.00, RBBS-PC 16.0, Professional OLEcom 3.0, TP-Board 5.0, or any other BBS package that uses the DORINFOx.DEF to run almost any BBS Door.
File DM56.ZIP from The Programmer’s Corner in
Category BBS Files
DoorMaster is a BBS utility that will allow a QuickBBS 2.00, RBBS-PC 16.0, Professional OLEcom 3.0, TP-Board 5.0, or any other BBS package that uses the DORINFOx.DEF to run almost any BBS Door.
File Name File Size Zip Size Zip Type
BUG.FRM 4092 546 deflated
DM.CFG 64 64 stored
DM.DOC 52957 13154 deflated
DM.EXE 226178 81755 deflated
DM.TBL 557 207 deflated
ORDER.FRM 4125 613 deflated
PCB14.DAT 12400 1976 deflated
SUG.FRM 4152 537 deflated
WHATS.NEW 1318 652 deflated

Download File DM56.ZIP Here

Contents of the DM.DOC file






















DoorMaster v5.6 - The ultimate door convertor!

Copyright (C) 1988,89,90,91,92 by Michael P. Otto, All Rights Reserved


Michael P. Otto
213 Casalon Drive, Suite 6
O'Fallon, MO 63366
United States of America


BBS: 314.281.4707
CompuServe: 70524,2621
PRODIGY: gwkh37a
BIX: m.otto
Exec-PC: Michael Otto
Internet: [email protected]
Inter-Comm Network (ICN) 91:314/1
FidoNet 1:100/625
ToadNet 86:8012/30
EchoNet 50:5314/625





NOTE: Text updated from the previous release of this manual has been
marked with a "|" at the beginning of each line.














Table of Contents

1 Overview

1.1 Introduction To DoorMaster
1.2 Files Contained In This Archive
1.3 Hardware/Software Requirements
1.4 Knowledge Requirements
1.5 Distribution And Registration Policy
1.6 Disclaimer
1.7 Technical Support
1.8 Bugs And Suggestions
1.9 Version Numbering Scheme


2 Software Supported

2.1 List of Supported Software and Their Modes
2.2 If Your Software Isn't Supported


3 Usage

3.1 Configuration
3.2 Conversion Command Line Format
3.3 Using the Lookup Table
3.4 PCBoard Advanced Mode Setup
3.5 Locking the BPS on a DORINFO1.DEF File
3.6 Registering Your Copy
3.7 Using the Help Facility


4 Notes on Supported Software

4.1 2AM-BBS (2AM)
4.2 Auntie BBS (AUNTIE)
4.3 Batch File Mode (BATCH:)
4.4 B.H. Forbes (FORBES)
4.5 BBSX (BBSX:)
4.6 DoorWay (DW143, DW, DW200)
4.7 EIS-PC (EIS)
4.8 Emulex and FCP/Emulex (EMULEX)
4.9 Fido BBS (FIDO)
4.10 Feathernet (FNET)
4.11 Force! (tm) (FORCE)
4.12 FoReM (FOREM)
4.13 Forum-PC 2.5+ (FORUM)
4.14 GAP Communications (GAP)
4.15 GT Power Host (GT)
4.16 Genesis Deluxe (GENESIS)
4.17 Magpie (MAGPIE)
4.18 Maximus 2.0 (MAX)
4.19 Milton GameWorks (MGW)



Table of Contents Page i



4.20 ModuleX (MODULEX)
4.21 NoChange BBS (NOCHANGE)
4.22 Odessey BBS (ODESSEY)
4.23 Omegacom BBS (OMEGACOM)
4.24 Opus-CBCS (OPUS)
4.25 Parameter Mode (PARMS:)
4.26 PCBoard 12.x (PCB12)
4.27 PCBoard 14.x (PCB14)
4.28 PCBoard 14.x Custom Mode (PCB14C)
4.29 PCBoard 14.x Advanced Mode (PCB14ADV)
4.30 Phoenix RCS (PHOENIX)
4.31 PILOT BBS (PILOT)
4.32 Professional OLEcom (OLECOM)
4.33 QuickBBS (QBBS)
4.34 RBBS-PC 15.x (RBBS15)
4.35 RBBS-PC 16.x/17.x (RBBS)
4.36 RemoteAccess (RA)
4.37 RyBBS (RYBBS)
4.38 Sapphire BBS (SAPPHIRE)
4.39 Searchlight BBS (SLBBS)
4.40 Spitfire BBS (SPITFIRE)
4.41 SuperBBS (SBBS)
4.42 TAG BBS (TAG)
4.43 Telegard BBS (TELEGARD)
4.44 TP-Board (TPBOARD)
4.45 WildCat! (WC1, WC2, WC3)
4.46 WWIV (WWIV, WWIV-ALIAS)
4.47 XBBS (XBBS)
4.48 DCI (DCI)
4.49 MaxiHost (MAXIHOST)
4.50 Osiris (OSIRIS)
4.51 Executive Host (EXECHOST)
4.52 TriTel (TRITEL)


5 Credits




















Table of Contents Page ii



Chapter 1: Overview

1.1 Introduction To DoorMaster

DoorMaster (hereafter referred to as DM) is a software utility that
allows sysops to run doors that are designed for literally any BBS
package on the market. It does this by converting door exit files
from one format to another. Support for more and more BBS packages is
being added constantly. It also contains other features, including a
Time-Lock system that lets you limit the time of day that certain
doors may be used. It is the ultimate door convertor!


1.2 Files Contained In This Archive

This archive should contain the following files:

File Name Description
---------------------------------------------------------------------
DM.CFG Sample Configuration File
DM.TBL Sample Lookup Table
DM.DOC Documentation
DM.EXE Executable File
PCB14.DAT Commented PCBoard 14.x PCBOARD.DAT File
ORDER.FRM Registration Mailer
BUG.FRM Bug Report Mailer
SUG.FRM Suggestion Mailer


1.3 Hardware/Software Requirements

The only hardware/software requirements are that you have the BBS
package of your choice previously installed, along with your favorite
text editor. Make sure your BBS package is on the list of supported
software. DM has been tested under MS, PC, and DR DOS, as well as the
DESQview multitasking/multiwindowing environment.


1.4 Knowledge Requirements

In order to use DM to it's fullest extent, you should be familiar with
the following:

How to use, create, and maintain MS/PC/DR DOS subdirectories.

How to use, create, and maintain MS/PC/DR DOS batch files.

How to use a text editor to create and update ASCII files.








DoorMaster v5.6 Page 1



1.5 Distribution And Registration Policy

DM is distributed under the "User-Supported" concept. You are
encouraged to distribute this software to others as long as you do not
charge, in any way, for it.

Since DM, like a variety of other software products, is distributed
via the "User-Supported" concept, it is not sold anywhere for a
commercial value. Rather, profits rely solely on you, the consumer,
to support our hard work. For the literally hundreds of hours spent
in developing DM, I ask only that you send a small contribution of
$25. To register, complete the enclosed ORDER.FRM mailer. Send this
form, along with a check or money order (sorry, no credit cards) for
$25, to the address on the cover page of this document. Once I have
received your check, you will be given a unique Serial Number Password
(SNP). When you have received your SNP, you will invoke DM with the
/REGISTER parameter and answer all questions it asks you. Your SNP
will work on all future versions of DM, unless otherwise noted. This
SNP may enable certain features not available in an UNREGISTERED
version.

The latest version of DM can always be downloaded from DataPoint!, in
addition to many of the commercial online services.


1.6 Disclaimer

The authors of DM make no warranty as to the contents of this manual
or the accompanying software. Although every effort has been made to
insure that the manual is accurate and the software is reliable, the
authors of DM cannot be held responsible for any damages incurred from
the use of this product.


1.7 Technical Support

Technical support for DoorMaster can be obtained by sending a letter
via U.S. Mail to the address listed on the cover page of this
document, or by e-mailing me on any of the e-mail addresses listed on
the cover pages of this document.

VOICE CALLS ARE NOT RECOMMENDED AND MAY NOT BE ACCEPTED.


1.8 Bugs And Suggestions

If you find any bugs or things that just don't look quite right in DM,
PLEASE report them so that they can be fixed! Enclosed in this
archive you will find a file named BUG.FRM. When you find a bug, fill
out this form and return it to me. Include as much detail as
possible.

If the bug appears to be serious, include the contents of your DMx.CFG



DoorMaster v5.6 Page 2



file, along with your command line. Also, there is a special command
line parameter, /DEBUG, that allows DM to help me when trying to track
down bugs. Run DM in the same manner that you did when you got the
bug, but add "/DEBUG" to the end of your command line. This will
cause DM to write helpful debugging information to a file called
DEBUG.RPT in the current directory. Please print this file and mail
it to me, along with BUG.FRM. A sample command line is:


C>dm /f=xbbs /t=pcb14 /debug


If you ever have any suggestions as to features you would like added
to DM, fill out the enclosed form, SUG.FRM, and return it to me.



1.9 Version Numbering Scheme

Version numbers are determined using the following scheme:

| n.n
|
|
|
|
| incremented on feature updates and bug fixes
incremented on major revisions





























DoorMaster v5.6 Page 3



Chapter 2: Software Supported

2.1 List of Supported Software and Their Modes

Software DoorType Mode
-----------------------------------------------------------
2AM-BBS 2AM BOTH
Auntie BBS AUNTIE BOTH
Batch File Mode (DOOR.BAT) BATCH: TO
B.H. Forbes FORBES TO
DoorWay 1.43 (Short DOOR.SYS) DW143 TO
DoorWay 2.00 (Long DOOR.SYS) DW or DW200 TO
BBSX BBSX: FROM
EIS-PC EIS BOTH
Emulex and FCP/Emulex EMULEX BOTH
Feathernet FNET BOTH
Fido BBS FIDO BOTH
Force! (tm) FORCE BOTH
FoReM FOREM BOTH
Forum-PC 2.5+ FORUM BOTH
GAP Communications GAP BOTH
GT Power Host GT BOTH
Genesis Deluxe GENESIS BOTH
Magpie MAGPIE BOTH
Maximus 2.0 MAX BOTH
Milton GameWorks MGW TO
ModuleX MODULEX BOTH
NoChange BBS NOCHANGE: FROM
Odessey BBS ODESSEY BOTH
Omegacom BBS OMEGA BOTH
Opus-CBCS OPUS BOTH
Parameter Mode PARMS: FROM
PCBoard 12.x PCB12 BOTH
PCBoard 14.x PCB14 BOTH
PCBoard 14.x Custom Mode PCB14C TO
PCBoard 14.x Advanced Mode PCB14ADV TO
Phoenix RCS PHOENIX BOTH
PILOT BBS PILOT BOTH
Professional OLEcom OLECOM BOTH
QuickBBS QBBS BOTH
RBBS-PC 15.x RBBS15 TO
RBBS-PC 16.x/17.x RBBS BOTH
RemoteAccess RA BOTH
RyBBS RYBBS BOTH
Sapphire BBS SAPPHIRE BOTH
Searchlight BBS SLBBS BOTH
Spitfire BBS SPITFIRE BOTH
SuperBBS SBBS BOTH
TAG BBS TAG BOTH
Telegard BBS TELEGARD BOTH
TP-Board TPBOARD BOTH
WildCat! 1.xx WC1 BOTH
WildCat! 2.xx WC2 BOTH



DoorMaster v5.6 Page 4



WildCat! 3.xx WC3 BOTH
WWIV WWIV BOTH
WWIV with aliases WWIV-ALIAS FROM
XBBS XBBS BOTH
DCI DCI BOTH
MaxiHost MAXIHOST BOTH
Osiris OSIRIS BOTH
Executive Host EXECHOST BOTH
TriTel TRITEL BOTH

Mode Legend: 'TO' means that DM only converts to this software; 'FROM'
means that DM only converts from this software; 'BOTH' means that DM
converts both to and from this software.


2.2 If Your BBS Package Isn't Supported

PLEASE fill out the SUG.FRM and let me know! If possible, also please
include the name and formats of the door data file.

Note that if your BBS makes use of a DORINFOx.DEF, but does not have
it's own doortype built into DM, you can use the doortype of
"DEFAULT". Please let me know about this so that I can give it it's

own doortype.
































DoorMaster v5.6 Page 5



Chapter 3: Usage

3.1 Configuration

Before running DM, you may want to setup a configuration file for each
node of your system, although it is not required. The data in this
file is ONLY used if the door exit file you are converting from cannot
supply your BBS name, your communications port, and your name.

If you do not create this file, and your BBS cannot supply the above
data, DM will default to 'BBS' as the BBS name, 'COM1' as the
communications port, and 'SYSOP' as the sysop name.

Invoke DM with the following command line to setup the configuration
for each node:


C>DM /CONFIG [/N=]


/N is an optional parameter. If you have a single node system, omit
this parameter.

Technical data concering the actual DMx.CFG files follows:

If you only have a single node, the filename will be DM.CFG. If you
have multiple nodes, the filenames will be DMx.CFG, where "x" is equal
to the node number. These files must be kept in the
directory.

The file is in the following format:


*** DoorMaster vn.n.n Config ***
DataPoint!
COM1
MICHAEL
OTTO


Line 1 is used internally by DM and SHOULD NOT be modified.

Line 2 contains your BBS name.

Line 3 contains the COM port for the node this file is created for.
If this is a local node, this parameter can be COM0.

Line 4 contains the first name of the sysop, in all capital letters.

Line 5 contains the last name of the sysop, in all capital letters.






DoorMaster v5.6 Page 6



3.2 Conversion Command Line Format

The command line format for using DM normally is described below.


C>DM /F= /T=
[/BP=] [/DP=] [/N=] [/LB=]
[/TL=] [/FOSSIL]


/F= is the type of BBS you are converting from.
Refer to page 4, the doortype column, for a list of valid doortypes.
Note that if you want to convert from a BBS that uses a DORINFOx.DEF
"standard" file and there is no DM doortype for your BBS package, you
may supply the word DEFAULT for this parameter, and let me know more
information about your BBS package so I can support it in future
versions.

/T= is the type of BBS you want to convert to.
Refer to page 4, the doortype column, for a list of the valid
doortypes. Note that if you are converting to a DORINFOx.DEF
"standard" file and there is no DM doortype for the BBS package you
want to convert to, you may supply the word DEFAULT for this
parameter, and let me know more about the BBS package you are
coverting to so I can support it in future versions.

/BP= is the path where your BBS system files and the DMx.CFG
file are stored. If you are running DM from your BBS directory, you
can leave this parameter off.

/DP= is the path where the particular door that you want to
run is stored. This is the path where DM will write the files it
produces. If you are running DM from your door directory, you can
leave this parameter off.

/N= is the node number that DM will use when reading the BBS
data files, and it's own DMx.CFG file. This is an optional parameter;
if you are running a single-node system, leave this off.

/LB= is the BPS rate that you have your communications port
locked to. This is an optional parameter; if you don't have your BPS
rate locked, leave this off. Use caution when locking the BPS rate to
38400, as many BBS packages do not yet support it and DM may not
operate properly if you are trying to convert to one of these
packages.

/TL= activates DM's Time-Lock feature. Time-Lock allows
you to lock a door for certain time range. If someone tries to use
the door during the time range that it is locked, they will receive a
message telling them that the door is locked and informing them of
when it will be unlocked. DM writes a zero-length file called DM.LOK
if the door is locked. You can check for the existance of the file in
your door batch file to determine whether to load the door or not. An



DoorMaster v5.6 Page 7



example follows:


@echo off
dm /f=qbbs /t=pcb14 /dp=\doors\ /tl=15:00-20:00
if exist dm.lok goto end

:loaddoor
cd \doors
door.exe door.cfg
goto end

:end
cd \qbbs
if exist dm.lok del dm.lok


/FOSSIL is used to tell DM that the FOSSIL is hot. This is an
optional parameter that currently only applies if you are writing to
one of the doortypes that uses a DORINFOx.DEF file. The last line of
this normally contains a -1 if the FOSSIL is hot, a 0 otherwise. If
you include this command line parameter, a -1 will be written to the
DORINFOx.DEF file.


3.3 Using the Lookup Table


C>DM @


DM now has a feature that allows you to store your command lines in a
lookup table. The name of the file is DM.TBL. DM expects this file
to exist in the directory you are in when you invoke DM. This feature
comes in handy if you use the same command line for several doors,
such as writing the data files for all PCBoard doors to C:\PCB instead
of to the actual door path, etc.

NOTE: Make sure you do NOT put a space between @ and !

The format of this file is as follows:


;Name Command Line
;-----------------------------------------------------------------



begins in column 1, begins in column 20.
Lines beginning with a semi-colon (;) are treated as comments. A
sample DM.TBL is include in this archive.

NOTE: This feature only works in REGISTERED versions.



DoorMaster v5.6 Page 8





3.4 PCBoard Advanced Mode Setup


C>DM /PCBSETUP=


NOTE: THIS FEATURE MAY BE REMOVED FROM FUTURE VERSIONS DUE TO LIMITED
USE IN TODAY'S BBS WORLD. COMMENTS ARE APPRECIATED.

This will cause DM to invoke the setup mode for PCBoard 14.x Advanced
Mode use. You will be display a menu that allows you to create
various
PCBoard 14.x files. You must first create the [pcbpath] directory,
and the subdirectories MAIN and GEN under that directory. Refer to
the section "Notes on PCBoard 14.x Advanced Mode" for more
information.

NOTE: This feature is generally not required for most PCBoard doors to
run, and may be dropped in future versions of DM!


3.5 Locking the BPS on a DORINFO1.DEF File


C>DM /LOCK= [/N=]


NOTE: THIS FEATURE MAY BE DROPPED FROM FUTURE VERSIONS DUE TO LIMITED
USE IN TODAY'S BBS WORLD, AS MOST PACKAGES SUPPORT BPS LOCKING
INTERNALLY. COMMENTS ARE APPRECIATED.

This mode only works for BBS packages that make use of a DORINFOx.DEF
file. This will read the DORINFOx.DEF file and insert the value
contained in the parameter as the baud rate in the file.
Note that in local mode, a baud rate of 0 is always used.



















DoorMaster v5.6 Page 9



3.6 Registering Your Copy


C>DM /REGISTER


This puts DM into registration mode. You will be prompted for your
REGISTRATION NAME and SNP. These are obtained from me upon
registration of the program. Refer to section 1.5, "Distribution and
Registration Policy" for information on registering. The registration
data is written to the DM.EXE file in an encrypted format. Any
attempts to modify the registration data in DM.EXE using a hex editor
will cause DM to display an "Illegal copy, terminating program..."
message when it is run.


3.7 Using the Help Facility


C>DM /?

- or -

C>DM /HELP


This causes DM to display brief instructions for usage. Use the
cursor keys (Up, Down, PgUp, PgDn, Home, End) to page back and forth
in the text. Press Esc to exit.

There are also some hidden, novelty, commands in the help facility.
Feel free to experiment by pressing other keys.
























DoorMaster v5.6 Page 10



Chapter 4: Notes on Supported Software

This section contains brief notes on each software package supported
by DM.


4.1 2AM-BBS (2AM)

The file read/created when translating to or from 2AM-BBS is:
JUMPER.DAT


4.2 Auntie BBS (AUNTIE)

The file read/created when translating to or from Auntie BBS is:
AUNTIE.SYS. This file is the same format as a PCBoard 12.x
PCBOARD.SYS.


4.3 Batch File Mode (DOOR.BAT) (BATCH:)

This option allows you to have DM write a batch file called DOOR.BAT
that will pass a program various parameters. This allows you to use
program that require baud rate, user name, etc., as command line
parameters and your BBS program cannot pass these parameters.

DOOR.BAT contains one line. It simply writes out the batch file name
that you gave DM on the command line, along with node number, baud
rate, communications port, time left, graphics mode, first name, and
last name. The format of DOOR.BAT is:


FILENAME.BAT



An example of how to use it follows. Lets assume that TW.BAT needs
the bps rate and node number, respectively, given as command line
parameters. The following would be your initial batch file; we'll
call it TWLOAD.BAT.


@echo off
dm /f=qbbs /t=batch:tw /dp=\tw\
door.bat


DOOR.BAT would then load TW.BAT, passing it all the parmeters
described above as %1 %2 %3 %4 %5 %6 %7. TW.BAT would look like this:







DoorMaster v5.6 Page 11




@echo off
cd \tw
tw.exe %2 %1
cd \qbbs
if exist door.bat del door.bat



4.4 B.H. Forbes (FORBES)

The file created when translating to B.H. Forbes is: USERFILE.


4.5 BBSX (BBSX:)

The conversion process from BBSX is a little different than the
others. This is because BBSX passes DOS "replacable parameters" to
the door
batch file. Your command line will look like the following. Note
that all data beginning with "%" are DOS "replacable parameters".


C>DM /F=BBSX:%2,%3,%5,%6,%8,%9 /T= [/BP=]
[/DP=] [/N=] [/LB=] [/TL=]
[/FOSSIL]


The BBSX "replacable parameters" used by DM are:


Parameter BBSX Data

%2 COM port (1 or 2)
%3 baud rate (300,1200,2400,9600)
%5 first name
%6 last name
%8 security level (1-999)
%9 time left in minutes (1-1440)



4.6 DoorWay (DW143, DW, DW200)

The files created when translating to DoorWay are: DOOR.SYS,
GRAPHICS.SYS (explained below). With the DW143 module,
the DOOR.SYS is the short style. With the DW or DW200 module, the
DOOR.SYS is the long style, like GAP's.

Note: DW and DW200 are identical in this version.

When you translate to either of the DoorWay modes, DM will write a
file called GRAPHICS.SYS, in addition to the DOOR.SYS, if the user has



DoorMaster v5.6 Page 12



ANSI graphics on. This is useful because it will allow you to have
ANSI menus if you use the menu mode of DoorWay. An example follows:


@echo off
dm /f=qbbs /t=dw /dp=\doors\
if exist graphics.sys goto ansi

:noansi
doorway sys /r:^k /g:off /i:menu.asc
goto end

:ansi
doorway sys /r:^k /g:on /i:menu.ans

:end
cd \qbbs
if exist graphics.sys del graphics.sys



4.7 EIS-PC (EIS)

The file read/created when converting to or from EIS-PC is:
DORINFO1.DEF.


4.8 Emulex and FCP/Emulex (EMULEX)

The file read/created when converting to or from Emulex or FCP/Emulex
is: PCBOARD.SYS. This is a PCBoard 12.x compatible file.


4.9 Fido BBS (FIDO)

The file read/created when converting to or from Fido BBS is:
LASTUSER.BBS.


4.10 Feathernet (FNET)

The file read when converting from Feathernet is: PCBOARD.SYS. The
files created when converting to Feathernet are: PCBOARD.SYS, USERS.
These files are the same format as PCBoard 14.x files.


4.11 Force! (tm) (FORCE)

The file read/created when converting to or from Force! (tm) is:
DOOR.SYS. This file is the same format as GAP's file.






DoorMaster v5.6 Page 13



4.12 FoReM (FOREM)

The file read/created when converting to or from FoReM is:
DORINFO1.DEF.


4.13 Forum-PC 2.5+ (FORUM)

The file read/created when converting to or from Forum-PC 2.5+ is:
USERINFO.TXT. This is the same format as the Milton GameWorks file.


4.14 GAP Communications (GAP)

The file read when converting from GAP Communications is: DOOR.SYS.
The files created when converting to GAP Communications are: DOOR.SYS,
GAPBBS.CNF.


4.15 GT Power Host (GT)

The file read/created when converting to or from GT Power Host is:
GTUSER.BBS.


4.16 Genesis Deluxe (GENESIS)

The file read/created when converting to or from Genesis Deluxe is:
CALLINFO.BBS.


4.17 Magpie (MAGPIE)

The file read/created when converting to or from Magpie is: DOOR.SYS.
The format of the file is the same as the GAP file.


4.18 Maximus 2.0 (MAX)

The file read/created when converting to or from Maximus 2.0 is:
DORINFO1.DEF. Maximus 2.0 must be set to write out a DORINFO1.DEF
file when converting from it.


4.19 Milton GameWorks (MGW)

The file created when converting to Milton GameWorks is: USERINFO.TXT









DoorMaster v5.6 Page 14



4.20 ModuleX (MODULEX)

The file read/created when converting to or from ModuleX is:
NUMBER.TXT. This is the same format as the Odessey file. Note that
ModuleX and
Odessey are created by the same author, ModuleX being the newer of the
two.


4.21 NoChange BBS (NOCHANGE:)

The conversion process from NoChange BBS is a little different than
the others. Since NoChange BBS data is stored in "memory variables",
you must pass certain information on the command line. Your command
line will be in the following format. Note that the data beginning
with "&&" are the NoChange BBS "memory variables"


C>DM /F=NOCHANGE:&&FIRST,&&LAST,&&BAUD,&&LEFTTIME,&&PORT,&&ANSI
/T= [/BP=] [/DP=] [/N=]
[/LB=] [/TL=] [/FOSSIL]



4.22 Odessey BBS (ODESSEY)

The file read/created when converting to or from Odessey BBS is:
NUMBER.TXT. Read the comments in the ModuleX notes above.


4.23 Omegacom BBS (OMEGA)

The file read/created when converting to or from Omegacom BBS is:
DORINFO.DEF.


4.24 Opus-CBCS (OPUS)

The file read/created when converting to or from Opus-CBCS is:
LASTUSER.BBS.


4.25 Parameter Mode (PARMS:)

Parameter Mode is a unique feature of DM. It allows you to pass door
data on the command line rather than reading it from a door data
file. This comes in handy if your BBS program is able to pass command
line parameters, but does not create a door data file. Your command
line will look like the following.







DoorMaster v5.6 Page 15




C>DM /F=PARMS:,,,,,
, /T= [/BP=]
[/DP=] [/N=] [/LB=] [/TL=]
[/FOSSIL]


is the user's first name.

is the user's last name.

is the communications port being used. Note that it is just
a number, such as 0, 1, or 2 and does not have COM preceding it.

is the baud rate.

is the user's time left in minutes.

is the user's security level.

is the graphics mode of the user. It can be 0 for no
graphics, or 1 for graphics.

You will need to use DOS "replacable parameters" on the actual DM
command line.


4.26 PCBoard 12.x (PCB12)

The file read when converting from PCBoard 12.x is: PCBOARD.SYS. The
files created when converting to PCBoard 12.x are: PCBOARD.SYS, USERS,
PCBOARD.DAT.


4.27 PCBoard 14.x (PCB14)

The file read when converting from PCBoard 14.x is: PCBOARD.SYS. The
files created when converting to PCBoard 14.x are: PCBOARD.SYS,
USERS, PCBOARD.DAT. Read the below notes concerning the Custom and
Advanced modes for special applications, such as ProKit doors, etc.


4.28 PCBoard 14.x Custom Mode (PCB14C)

The PCBoard 14.x Custom Mode is identical to the regular PCBoard 14.x
mode, but it will not create a PCBOARD.DAT file. Instead, use the
supplied PCB14.DAT, copy it to PCBOARD.DAT, and customize it to your
tastes. I have fully commented the PCB14.DAT file included in this
archive. Make sure you remove the comments from the copy you will be
using with DM! The PCBSETUP.EXE utility included in the PCBoard 14.x
*DEMO* package also comes in handy. If you need a copy of this
utility, feel free to contact me. I can't include it in this
DoorMaster package because it is a copyrighted work of Clark



DoorMaster v5.6 Page 16



Development Company.


4.29 PCBoard 14.x Advanced Mode (PCB14ADV)

NOTE: THIS FEATURE MAY BE REMOVED FROM FUTURE VERSIONS DUE TO LIMITED
USE IN TODAY'S BBS WORLD. COMMENTS ARE APPRECIATED.

The PCBoard 14.x Advanced mode is unique. You must first use the
PCBSETUP mode to create all of your PCBoard 14.x data files.
This mode is only used if you need to maintain a COMPLETE PCBoard 14.x
file/directory structure. The only situation where I can see this
mode being used would be if you wanted to run ProDoor under a
non-PCBoard BBS. When run in PCBoard 14.x Advanced mode, DM will
create a PCBOARD.SYS file and maintain a USERS file, as PCBoard 14.x
would do. It will scan the existing USERS file for the user name, and
if not found, will add a record for him/her. For the PCBOARD.DAT
file, you must use the supplied PCB14.DAT file, copy it to
PCBOARD.DAT, and customize it to your tastes. You will need to put
PCBOARD.DAT in your PCBoard 14.x "artificial" directory (the directory
you use as . I have fully commented the PCB14.DAT file
included in this archive. Make sure you remove the comments from the
copy you will be using with DM!


4.30 Phoenix RCS (PHOENIX)

The file read/created when converting to or from Phoenix RCS is:
INFO.BBS.


4.31 PILOT BBS (PILOT)

The file read/created when converting to or from PILOT BBS is:
CHAIN.TXT. This file is in the same format as a standard DORINFO1.DEF
file.


4.32 Professional OLEcom (OLECOM)

The file read/created when converting to or from Professional OLEcom
is: DORINFO1.DEF.


4.33 QuickBBS (QBBS)

The file read/created when converting to or from QuickBBS is:
DORINFOx.DEF. Note that "x" is the node number, or "1" if you are a
single node system.







DoorMaster v5.6 Page 17



4.34 RBBS-PC 15.x (RBBS15)

The files created when converting to RBBS-PC 15.x are: MESSAGES,
RBBSxPC.DEF. Note that "x" is the node number, or "-" if you are a
single-node system.


4.35 RBBS-PC 16.x/17.x (RBBS)

The file read/created when converting to or from RBBS-PC 16.x/17.x is:
DORINFOx.DEF. Note that "x" is the node number, or "1" if you are a
single node system.


4.36 RemoteAccess (RA)

The file read/created when converting to or from RemoteAccess is:
DORINFO1.DEF.

When converting from RemoteAccess, users with only AVATAR enabled are
treated as ASCII users; users with both ANSI and AVATAR enabled are
treated as ANSI users. This may be changed in the future when more
BBS packages support AVATAR.

Note that you can also use DM to convert RemoteAccess's DORINFO1.DEF
to a regular DORINFO1.DEF without AVATAR codes. This is useful if you
have a door that reads a DORINFO1.DEF, but doesn't know what to do
when it finds a 2 or 3 as the graphics type in DORINFO1.DEF. If you
specify RA for BOTH the from and to DoorType's, it will strip out a 2
or 3 as graphics type, and use the standard 0=no-ansi, 1=ansi used in
a regular DORINFO1.DEF file.


4.37 RyBBS (RYBBS)

The file read/created when converting to or from RyBBS is: CURRUSER.x.
Note that "x" is the node number, or "BBS" if you are a single node
system.


4.38 Sapphire BBS (SAPPHIRE)

The file read/created when converting to or from Sapphire BBS is:
SAPPHIRE.DAT.


4.39 Searchlight BBS (SLBBS)

The file read/created when converting to or from Searchlight BBS is:
PCBOARD.SYS. The format of this file is the same as the PCBoard 12.x
file.





DoorMaster v5.6 Page 18



4.40 Spitfire BBS (SPITFIRE)

The file read/created when converting to or from Spitfire BBS is:
SFDOORS.DAT.


4.41 SuperBBS (SBBS)

The file read/created when converting to or from SuperBBS is:
DORINFOx.DEF. Note that "x" is the node number, or "1" if you are a
single node system.


4.42 TAG BBS (TAG)

The file read/created when converting to or from TAG BBS is: DOOR.SYS.
The format of the file is the same as the GAP file.


4.43 Telegard BBS (TELEGARD)

| The file read/created when converting to or from Telegard BBS is:
| DORINFO1.DEF.


4.44 TP-Board (TPBOARD)

The file read/created when converting to or from TP-Board is:
DORINFO1.DEF.


4.45 WildCat! (WC1, WC2, WC3)

The file read/created when converting to or from WildCat! 1.xx or 2.xx
is: CALLINFO.BBS.

The file read/created when converting to or from WildCat! 3.xx is:
DOOR.SYS (long style).


4.46 WWIV (WWIV, WWIV-ALIAS)

The file read when converting WWIV is: CHAIN.TXT. The files created
when converting to WWIV are: CHAIN.TXT, DOOR.SYS (see notes in next
paragraph).

NOTE: If you wish to use the user's alias instead of the user's real
name from CHAIN.TXT when converting from WWIV, use a DoorType of
"WWIV-ALIAS" instead of "WWIV".

When converting to WWIV 3.xx series doors, you will have to use
DoorWay or another I/O redirector to actually run the WWIV door. This
is because WWIV 3.xx doors normally depend on WWIV to redirect them;



DoorMaster v5.6 Page 19



they do not have their own communications routines built-in. A
DoorWay DOOR.SYS is created for your convience so that you don't have
to run DM twice. Also note that your WWIV doors will most likely
display some "garbage" to the user (ascii 3, etc.). This is because
WWIV uses a special color code system that it interprets as it's doing
the I/O redirection. You will need to patch your door to remove the
special codes and convert them to normal ANSI, or recompile the door
using a modified COMMON.PAS that uses regular ANSI instead of ANSIC.
If needed, I will create a modified COMMON.PAS that will use regular
ANSI and possibly do it's own I/O redirection.

If you are using WWIV 4.xx series doors, everything should work fine.


4.47 XBBS (XBBS)

The file read/created when converting to or from XBBS is:
USERINFO.XBS.


4.48 DCI (DCI)

The file read/created when converting to or from DCI is: DORINFO1.DEF.
If you are converting from DCI, make sure you tell it to write a
DORINFO1.DEF style door exit file. This is done using "5. Parm Type"
and a "4" for "DORINFO1.DEF".


4.49 MaxiHost (MAXIHOST)

The file read/created when converting to or from MaxiHost is:
DORINFO1.DEF. If you are converting from MaxiHost, make sure you tell
it to write a DORINFO1.DEF style door exit file.


4.50 Osiris (OSIRIS)

The file read/created when converting to or from Osiris is: OUTx.QBS,
where "x" is the node number. When you are converting from Osiris, DM
will
recognize your ORISIS=drive:\path and COMx=BAUD_RATE environment
variables and use the values in them. Note that the DM /BP switch, if
used, overrides the ORISIS=drive:\path environment variable.


4.51 Executive Host (EXECHOST)

The file read/created when converting to or from Executive Host is:
DORINFO1.DEF. If you are converting from Executive Host, make sure
you tell it to write a DORINFO1.DEF style door exit file.






DoorMaster v5.6 Page 20



4.52 TriTel (TRITEL)

The file read/created when converting to or from TriTel is:
TRITEL.SYS.




















































DoorMaster v5.6 Page 21



Chapter 5: Credits

The following is a list of the various software packages that I have
referred to throughout this documentation, along with the respective
author/company. If you know the author/company of any of the
"Unknown"'s, please let me know.

Software Author/Company
---------------------------------------------------------------------
2AM-BBS Unknown
Auntie BBS Wes Meier
B.H. Forbes B.H. (Pat) Forbes
BBSX Richard B. Levin
DoorMaster Michael P. Otto
DoorWay Marshall Dudley
EIS-PC Justin Langseth
Emulex Sam Brown, Magnus Creel
FCP/Emulex Sam Brown, Magnus Creel
Fido BBS Tom Jennings
Force! (tm) Unknown
FoReM Unknown
Forum-PC Unknown
GAP Communications GAP Development Company
GT Power Host Paul Meiners/P&M Software
Genesis Deluxe Kiriwuth Path
Magpie Steve Manes/Roxy Recorders, Inc.
Maximus 2.0 Scott J. Dudley
Milton GameWorks Larry Pieniazeck
ModuleX Joe Hilinski
NoChange BBS NoChange Software
Odessey BBS Joe Hilinski
Omegacom BBS Unknown
Opus-CBCS Wynn Wagner III
PCBoard Fred Clark/CDC
Phoenix RCS Unknown
PILOT BBS Len Ballard
Professional OLEcom Tom Oleson
QuickBBS The QuickBBS Group
RBBS-PC Tom Mack, Jon Martin, Ken Goosens
RemoteAccess Continental Software
RyBBS Greg Ryan
Sapphire BBS Pinnacle Software
Searchlight BBS Frank LaRosa
Spitfire BBS Mike Woltz/Buffalo Creek Software
SuperBBS Risto Virkkala & Aki Antman
TAG BBS Unknown
Telegard BBS Unknown
TP-Board Jon Schneider
WildCat! Jim Harrer/Mustang Software, Inc.
WWIV Wayne Bell
XBBS M. Kimes
DCI Cassi Nordevald/Nordevald Software
MaxiHost Don Mankin



DoorMaster v5.6 Page 22



Osiris Micro Tech
Executive Host John Wright
TriTel Mark D. Goodwin





















































DoorMaster v5.6 Page 23



 December 12, 2017  Add comments

Leave a Reply