home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 - The BEST of 1994
/
monster1.zip
/
monster1
/
BBS_GAM2
/
OO110_1.ZIP
/
OOINFO.DOC
< prev
next >
Wrap
Text File
|
1994-09-27
|
4KB
|
131 lines
OOINFO - Operation: Overkill BBS Converter Program
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
OOINFO.EXE reads in the BBS information of the user (name, time left, baud
rate, etc.) from the BBS dropfile and creates a separate file called
BBSINFO.OO in Overkill's data directory. This BBSINFO.OO file contains
only the necessary information Overkill needs.
When first installing an Overkill game, the configuration program, OOSETUP,
will create a batch file automatically: OOIIDOOR.BAT. This batch file
may need editing or changing later.
[ USING OOINFO ]
~~~~~~~~~~~~
The command line for OOINFO.EXE is:
C:>OOINFO <optional config file> bbstype \directory\ node
The default configuration file is OOCONFIG.DAT and is assumed as so if the
optional config file field is left blank. This field is primarily used for
multi-game setups. Please see OOII.DOC for more information on setting up
multi-games.
In the "bbstype" field, you must enter a number for the representing BBS
systems:
1 - SpitFire (SFDOORS.DAT)
2 - Gap/Wildcat 3.0 (DOOR.SYS)
3 - GT Power 16.0 (GTUSER.BBS)
4 - PCboard 14.5 (PCBOARD.DAT)
5 - RBBS (DORINFOx.DEF) { where x represents the node }
6 - WildCat! 2.x (CALLINFO.BBS)
7 - WWIV (CHAIN.TXT)
8 - Phoenix (INFO.BBS)
9 - GT Power 15.1 (GTUSER.BBS)
10 - RemoteAccess (DORINFOx.DEF) { where x represents the node }
11 - QuickBBS (DORINFOx.DEF) { where x represents the node }
12 - SearchLight (CONFIG.SL2)
If your BBS software is not listed above, check which drop file that
your BBS creates when exiting to a door. Then, match that name with
one of the above settings. For example, VBBS software can create a
DOOR.SYS file, although VBBS is not directly listed above. You would
then set OOINFO as a type 2 setting, which tells OOINFO to use the
DOOR.SYS drop file.
For the "directory path", the path must end with a '\'. If not, the
program will be unable to find the correct dropfile created by the
BBS software. For example, "\OOII\" is valid, whereas "\OOII" is not.
"Node" numbers are only needed for bbs types of 5,10,11 (RBBS/RA/QuickBBS).
[ BATCH FILE EXAMPLES ]
~~~~~~~~~~~~~~~~~~~
Batch File Examples:
~~~~~~~~~~~~~~~~~~~
{PCBoard} {RemoteAccess} {SearchLight}
CD\OOII CD\OOII CD\OOII
OOINFO 4 \PCBOARD\ OOINFO 10 \RA\ 1 OOINFO 12 \SLIGHT\
MAINTOO MAINTOO MAINTOO
OOII OOII OOII
CD\PCBOARD CD\RA CD\SLIGHT
...more batch files can be listed if you load up OOINFO with a '?'
parameter, such as "OOINFO ?"
[ BBSINFO.OO CONTENTS ]
~~~~~~~~~~~~~~~~~~~
BBSINFO.OO (a standard text file created from OOINFO.EXE) contains the
following information:
<Full Name> FIRST LAST
<Com Port> 0=local, 1=Com1, 2=Com2
<Baud Rate> 0-38400
<Time Remaining> 0-999 (in minutes)
<Color> Y=Yes N=No
Example BBSINFO.OO created from OOINFO.EXE:
DUSTIN NULF
2
19200
60
Y
[ NOTES ]
~~~~~
*GT Powercomm systems do not provide the ComPort in the data files they
create. In effect, the node field must be replaced by the Com Port on
the command line.
For example, GT Powercomm 16.0 running on a Com Port of 2.
OOINFO 3 \GTBBS\ 2
...or just replace the "2" with "1", whichever setting is your ComPort.
Telegard BBS does not create its own drop files but can emulate other
BBS dropfiles. To emulate a DORINFOx.DEF dropfile, use the 'DD' command
for Telegard systems. This dropfile is equivalent to QBBS's drop file,
which is a type 11. See above for setting up QBBS with OOINFO.
In case OOINFO.EXE is incompatible with your BBS software, it may be
possible to create your own conversion program that works specifically
for your BBS.