home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 17
/
CD_ASCQ_17_101194.iso
/
vrac
/
tfb110.zip
/
SYSOP.DOC
< prev
next >
Wrap
Text File
|
1994-09-08
|
23KB
|
452 lines
TASK FORCE BROADSIDE Version 1.10 -- Program & Design by Robert A. Dalton
Copyright (C) 1994
DISCLAIMER
The author has taken every precaution to insure that no harm
or damage will occur on computer systems operating this package.
Nevertheless, the author shall NOT be held liable for whatever
may happen on your computer system or to any computer systems
which connects to your own as a result of operating this package.
The user assumes full responsibility for the correct operation of
this software package, whether harm or damage results from software
error, hardware malfunction, or operator error. NO warranties are
offered, expressly stated or implied, including without limitation
or restriction any warranties of operation for a particular purpose
and/or merchantability. If you do not agree with this then do NOT
use this program.
LICENSE AGREEMENT
The game program, support files, and documentation are
copyrighted products of Bob Dalton. Bob Dalton reserves all rights
to these products. This is protected by the United States of America
(USA) and International Copyright Laws. In no way shall the
components of the game software package be reproduced
or modified in any form or method without prior expressly written
permission from Bob Dalton.
Tampering with or altering the contents or integrity of the game
software package is prohibited. No fee may be charged by any
agency other than Bob Dalton beyond the cost of distributing
unregistered copies without prior expressly written permission from
Bob Dalton.
A major portion of this software was written by Scott Baker and
Steven Lorenz. Mr. Baker's Doordriver kit and the changes made
by Mr Lorenz have been used for the communications and interrupt
handling and this part of the software remains copyrighted by them.
This game is distributed under the Shareware concept. You are
allowed to operate this game for a trial period of thirty (30)
days. After this trial period, you must register the game
or discontinue its usage. Again if you do not agree with this
then do NOT use this game.
INTRODUCTION:
------------
Task Force Broadside (TFB) is half wargame and half card game and can be
played in a single user log on session on most BBS's. It takes place in
the Pacific Ocean of the 1940s. The goal is simple: Utilizing cards drawn
from a play deck attempt to sink the COMPUTER opponents fleet while
attempting to keep that fate from happening to yours. Easy? Think again!
REQUIREMENTS:
------------
At this point in time the only requirements are FILES=10 (or more) in your
config.sys file and ANSI.SYS. SHARE must also be loaded IF you intend to
use the game in a multi-node environment OR under DesqView. The game is
RIP aware but NOT a RIP Game at this time. A FOSSIL is NOT required to run
the game, although one will be supported if it exists. Automatic time
slicing support is provided to most common multi-taskers as well.
Files Included
--------------
Below is a listing of all files for the this Game. If you are
missing ANY of these files (except for the DOC and FRM files), the game
will NOT function. Feel free to give out copies of the ENTIRE archive
package of this game but please make sure all the files below are in that
package:
WARSHIP.ANS - ANSI Opening Screen for Task Force Broadside
SAMPLE1.BAT - A sample BAT file which runs the game program from the
game directory.
SAMPLE2.BAT - A sample BAT file which runs the game program from any
node directory.
SAMPLE3.BAT - A sample BAT file identical to the one I use on my Single
node WildCat Support BBS.
TFB.CTL - Un-edited Control file for setting up Task Force Broadside
and hereafter referred to in the game documentation as
GAME.CTL.
SAMPLE.CTL - A copy of the TFB.CTL file which I use on my BBS to
run the game (WildCat 3.91S System, 386 33Mhz Computer,
Single Node, 8Mb RAM, DesqView 2.41/QEMM 7.03, BNU Fossil
locking port #1 at 19200 and using FrontDoor 2.02 and a
US Robotics DS Modem, ANSI.sys loaded and SHARE loaded).
KEY.DAT - Dummy Key for Task Force Broadside (Good forever!)
FILE_ID.DIZ - Ascii Description File for BBS Sysops on Task Force Broadside
B4UASK.DOC - Checklist for resolving setup/game play problems
HISTORY.DOC - Task Force Broadside Version History information file
SYSOP.DOC - This text file you are reading
*UPGRADE.DOC - If you are upgrading - read this first!
TFB.EXE - Task Force Broadside Main Program and hereafter referred to
in the game documentaion as GAME.EXE.
REGISTER.FRM - Preprinted registration form and mailer
BUGRPT.FRM - Preprinted bug report/suggestion/comment form and mailer
CATALOG.TXT - A catalog with descriptions of all door games available
from me.
INSTRUCT.TXT - Game Player Instructions for Task Force Broadside
SOTL.ZIP - Compressed copy of the above instructions to make
available on your BBS for download by players of the game.
Files created by the game when first played:
TFBSCORE.DAT - Ascii Deep Six List Scoreboard and hereafter referred to
in the game documentaion as *SCORE.DAT.
SCORE.DAT - Data file to store player scores between plays
Files created by the game when errors are encountered:
ERROR.LOG - Log of system errors which happen during game play.
Installation
------------
--> NOTE: The word "game" is used in place of the program name for
both the executable file (example GAME.EXE), and the CTL
file (Example GAME.CTL) in the documentation from this
point on. GAMEDIR is used in place of the program directory
in the documentation from this point on.
1. Create a directory for the game (example: "WC30\DOORS\GAMEDIR")
2. Make sure that ALL files listed above from the game package
are moved into that directory.
3. Edit the control file (GAME.CTL) for your type of BBS software, user
name, etc. The control file should be self-explanatory. Two versions
are provided. One is identified by the game title (example: GAME.CTL)
and this is the UN-EDITED version and the other is identified as
SAMPLE.CTL is what a CTL file should look like AFTER it is edited. If
all else fails - try the one I use on MY support BBS (Sample.CTL). If
you have fossil drivers be sure to uncomment the 'fossil' option. If
you have a modem set to a non-std IRQ be sure to use the PORT# option
for that com port.
Where to put this file?
Put this file wherever you are running the game executable file from.
If you are running multi-node you could put a copy in each node
directory and run from there. If you change directory to the GAME
directory put the file here. See the example SAMPLE#.bat files.
If you only need one copy of this file but you want to run from a
directory other than where the game files are you can use the /C parm.
This tells the program to use the ".ctl" file in the game directory.
4. Edit the Key.DAT file. Line #1 should be the sysops name, Line
#2 should be the name of the using BBS, do NOT change or edit
line #3.
5. To insure proper multi-node use DOS SHARE must be loaded prior to
the game and prior to DESQview.
6. In order to run the game program online the following parameters may
be used.
"/Bxxxxx" This tells the game.exe to lock its baud rate
at xxxxx. This will lock the baud rate at the same value for
all nodes that use this command line. If you perfer a more
selective way to lock baud use 'LOCKBAUD' command in the
game.ctl file.
"/C" This tells game.exe to look for the game.CTL
file in the GAMEDIR directory and not the local directory. Normally
game.exe will look for the game.ctl file locally, thus if
it is run with the /Z parm in say C:\BBS\Node2 directory it will
look in the Node2 dir for the game.ctl file. When this is used
game.exe will look for the game.ctl file in the GAMEDIR directory
while running from the node2 dir.
"/L" This tells game.exe to load up in LOCAL
mode. This is good for testing or when a sysop just wants
to "try out" the door without messing with his BBS setup.
The "/L" mode will ask the user for his name and run the
door in local mode. Example: GAME.EXE /L
"/Nx" (where x is 1..9) This specifies a "node
number". Some bbs software support multinode environments
in which you must know the node number of the drop file to
use. For example, RBBS-PC uses DORINFOx.DEF. If you
specified "/N2" then RBBJACK.exe would use DORINFO2.DEF.
"/Pyyy" This specifies the PATH to the drop files.
For example, "/PC:\WC30\WCWORK\NODE1" would tell game.exe
to look for the drop files in C:\WC30\WCWORK\NODE1.
"/Z" This command you can run game.exe from anywhere in your
system as long as you include the correct file path. game.exe
will derive the file path to the files area from this file path.
Example: G:\BBS\Doors\gamedir\game /Z
'G:\BBS\Doors\gamedir\' now will be used as the part of the path
to the Data and Help directories.
COMMON ERRORS
003 File path not found. Check to make sure the game directory is
correctly named as GAMEDIR.
201 Files not found. Check to make sure that all required games
files are in the GAMEDIR directory.
7. Install the door into your BBS software (see your BBS software
documentation for more information). A batch file is normally
used to do this. To run the program just have your batch file
change to the GAMEDIR directory and run GAME.EXE - Thats all there
is to it! Three different batch files sample are included to help
you run the game. These are included with the game for editing
and your use. For dorinfo systems use the following:
Sample Batch File
-----------------
COPY DORINFOx.DEF \RBBS\DOORS\GAMEDIR\*.*
CD \RBBS\DOORS\GAMEDIR
GAME x <-=- NODE number !!DO NOT USE "x"!!
del dorinfox.def
CD \WC30
-=*=- Please note that you replace the "x" with the appropriate node
number. Ex: Dorinfo1.def ; Dorinfo2.def ; etc...
8. If you would like a score bulletin just have the game batch file
copy the *SCORE.DAT file to wherever you have your bulletins.
Example:
Copy C:\WC30\DOORS\GAMEDIR\*SCORE.DAT C:\WC30\BULL\BULL11.BBS
Please note that NO *SCORE.DAT or SCORE.DAT files will be generated
UNTIL a player completes a game and has better then a zero (0) score.
If the first player quits BEFORE finishing the game neither of the
files will be created.
9. Surprise! There is NO daily maintenance to be performed.
RESTRICTIONS ON THE UNREGISTERED GAME
-------------------------------------
Until the game is registered the following restrictions are in effect:
a. Players can only have one game choice option at the beginning (usually
means they can choose only one side or one map depending on the game).
b. There will be a slight delay experienced by players at the beginning of
the game.
c. Registering the game disables the above.
d. Once you are registered any future updates can be obtained free
through my BBS and my upgrades are ALWAYS easy to implement!
e. I am always improving my games - so check my BBS for a more current
version.
WHAT TO DO IF THERE ARE PROBLEMS
--------------------------------
Every effort is made to ensure that the game runs correctly before it leaves
my BBS as Shareware. If you are experiencing problems please do the
following BEFORE calling me:
1. Read ALL the SYSOP.DOC to ensure you have setup the program
and have met all the program requirements.
2. Use the B4UASK.DOC as a checklist to ensure that you have
not done anything wrong.
Multinode use
-------------
This game supports multinode use and provides automatic multi-tasker
support (time slice releasing) for a wide variety of multi-taskers.
Common Problems (Locked Bauds, High Speed modems, etc)
------------------------------------------------------
1. The game does NOT require a fossil driver to run.
2. If you are running a high speed modem (9600 baud or above), then I
suggest you run your bbs/mailer/doors at a locked baud rate. On high
speed error correcting modems, locking the baud rate will have a
noticeable increase on the speed of text that is sent. It's beyond
the scope of this document to discuss configuring your BBS and
mailer for a locked baud rate; you may wish to consult those docs
for information on that. Here are a few things to keep in mind when
setting up GAME with a locked baud rate:
a. When using a locked baud rate, I highly recommend using a FOSSIL
driver. This game will work at high speeds without one though.
BNU is a good fossil driver which can even be loaded and unloaded
before and after you run this game.
b. If you are using a fossil, then make sure to tell the fossil
that the port is locked. For BNU, to lock com1: at 38,400, you
would use something like "L0=38400" on BNU's command line.
c. If you lock the baud for one program, it must be locked
for everything. You can't lock the baud for just this game, but
not your BBS/mailer.
d. You may need to use the /B switch on the game.exe Command line
to specify the locked baud rate. For 19,200 this would be "/B19200"
and for 38,400 this would be "/B38400". Please note there is no
space between the "/B" and the baud rate.
3. What follows is some information on possible strange situations
that may occur:
a. Low speed users can play the game, but high speed users get
garbage.
- If you are not using the DORINFOx.DEF or DOOR.SYS drop file
then you may wish to find a converter program to convert
whatever drop file your BBS produces to the DORINFOx.DEF
or DOOR.SYS format and tell game.exe to use that.
Several converter programs are readily available on most
BBS systems. CallDoor is a good one if you can find it.
b. The game hangs up when a user enters the game.
- Sounds like the game is getting the wrong baud rate somehow.
Try switching over to the DOOR.SYS drop file method
if possible.
c. Text and screens are getting cut off.
- If you are running with a locked baud, then this could
be caused by some sort of FLOW CONTROL problem. Try using
a fossil if you aren't already.
d. If you're using something other than the DOOR.SYS drop file,
then I always suggest trying to use DOOR.SYS if possible. It is
the most reliable method and has had the most testing. If that
is not possible try DORINFOx.DEF as an alternative.
e. A door locks up node 1. This can happen with fossils or the
internal communications routines because it uses the default
comport of 1 when NONE is found in the dropfile or game.ctl
file. To correct this make sure the right port is shown in
the dropfile OR game.ctl file.
f. ANSI is reflected correctly on the local screen but the user
is getting garbage. Assuming the user has ANSI installed then
most likely the problem is at your end. First make sure you
have configured the game.ctl file to show the correct locked
port rate. Second make sure the dropfile is passing the locked
port rate INSTEAD of the actual conncet rate. If it is not
passing the locked port rate then you may need to use a
different dropfile format OR use a dropfile converter program
to change the line to show the locked port rate INSTEAD of
the actual connect rate.
"Corrupted" data files
----------------------
It is possible that something could happen to your game data file.
A power outage, game crash, or other event could damage the data
files. If you get one of these messages, then the best thing to do is
eliminate the SCORE.DAT and *SCORE.DAT files and start the game again to
create a new one.
CREDITS:
--------
This relatively small section is just to recognize the GOOD people
who have made this door a possibility.
Scott Baker -=*=- The author of the door driver package which
made this game possible. Great job Scott!!
Steven Lorenz -=*=- The author of the enhanced add on package
to Scott Bakers DoorDriver. Thanks to his
allowing me to use his modifications I
was able to delete the fossil requirement
and add many new communication and other
enhancements to my games. Thanks Steve!
DESQview is a registered trademark of Quarterdeck Office Systems.
Doordriver kit is proprietary software by Scott Baker.
Ripscript & Ripterm are registered trademarks of TeleGrafix Communications.
Where to reach me
-----------------
I can usually be reached at my BBS system, which should be listed in the
section entitled "registration" which is below.
Registration
------------
If you or your users enjoy this game, then please register it.
Registration is $20.00 and you get a key code by mail or posted on my
BBS which will disable the delay, allow players to have more choices,
and entitle you to life time support through my BBS. BBS Support
includes unlimited free updates and upgrades (not like some door game
authors who charge for major upgrades/updates!) through my BBS and access
to the game support conference on my BBS. To register this game
just print out the registration form (REGISTER.FRM) file included with
the game and send it with your check or money order for $20.00 to:
Robert A. Dalton
203 Old Farm Road
Harrison, AR 72601
HOW TO REACH ME BY MODEM
---------------------------
The TANSTAFL BBS (USA)
(501) 741-5699 (USR Dual- 2400 to 14400 baud)
Fidonet 1:391/3010
Reminder: You will be mailed a LETTER with your registration code.
Just allow an appropriate amount of time (a week or two) after dropping your
check in the mail for it to arrive to me and the code to be sent by mail
back to you. If you need it sooner log onto my BBS, leave me a message
telling me you mailed the registration and when I receive your check or
money order I will post a private message on the BBS giving you the key
code. If you do it this way please allow at least a week from the time
you mail it to the time you call and get your code. If you go the BBS
route you will ALSO receive a key code by mail. If you live in NORTH
AMERICA I can also send your key via Netmail, if you would like,
through the FIDO system (only). REMINDER: No disks are sent, if you
need the most current version you must call OR freq my BBS for it.
Bug Reports/Comments/Suggestions
--------------------------------
I have made every attempt to make sure the game is free of bugs, BUT the
possibility always exists that one may have been missed by me or the
playtesters. If you find a bug, or have a suggestion or comment to make
which would make future versions better please print out the BUGRPT.FRM and
mailer, fill it out, and send it to me. I read ALL of them and those people
that lead me to find a bug or generate a better game will receive credit in
the game documentation. PLEASE DO NOT NOTIFY ME OF PROBLEMS AND EXPECT ME
TO FIX THEM IF YOU HAVE FAILED TO PROVIDE ME WITH THE BUGRPT.FRM AND ANY
ERROR.LOG WHICH MIGHT HAVE BEEN GENERATED BY THE GAME DURING PLAY.
FIDO INFORMATION
----------------
My BBS supports file "freq"ing at 9600 baud or above. Just call 1:391/3010.
I also carry a door library of over 350 of the all time best door games
which I try to keep current. For a list of these doors just freq "DOORS".
I am always adding new things to my games so most likely there will be a
later version of the program available on my BBS then the one you have.
For a current version of the game just freq the magic name shown in the
catalog document which is in the game package. For a list of ALL my
files just freq "TANSTAFL.ZIP". If you are a door game/program writer
why not send me a copy of your game/program? If you have a more current
version of a door then I have, please consider sending me a copy as a token
of your appreciation for the service I offer at NO cost to you. Thanks!