










      
      
      
      +---------------------------------------------------+
                                                         
                               
                             
                                 
                                 
                           
                               
                                                         
      +---------------------------------------------------+
      
      
      



                      OPERATION: OVERKILL ][
                        ~~~~~~~~~~~~~~~~~~~
                      System Operator Manual

                    Public Release Version 1.20

                Copyright (c) 1995-2001 Dustin Nulf
                  Michael Montique / Bryan Turner
                        All Rights Reserved








[   Documentation to Operation: Overkill - Version 1.20    Page 1   ]







                               Table of Contents
                               =-=-=-=-=-=-=-=-=



  Terms and Conditions .................................. Page 2
  Registration .......................................... Page 2
  Contents of OOII120.ZIP ............................... Page 3
  Setting Up Overkill ................................... Page 4
  Running OOII Locally .................................. Page 4
  Online Keys ........................................... Page 5
  Additional Text Files ................................. Page 6
  External Programs for Overkill ........................ Page 7
    OOSETUP.EXE ......................................... Page 7
    MAINTOO.EXE ......................................... Page 7
    OOINFO.EXE .......................................... Page 7
    BBSVSBBS.ZIP ........................................ Page 7
  Multi-Nodes ........................................... Page 8
  Baud Rates ............................................ Page 8
  EMS/XMS Memory ........................................ Page 8
  Multi-Game Setup ...................................... Page 10
  Optional Configuration Files .......................... Page 11
  Trouble Shooting ...................................... Page 12
  That's All Folks!...................................... Page 12
  Special Thanks ........................................ Page 13
  The Next Project ...................................... Page 14



[   Documentation to Operation: Overkill - Version 1.20    Page 2   ]


   [  TERMS AND CONDITIONS  ]
      ~~~~~~~~~~~~~~~~~~~~
This product is completely copyrighted by Dustin Nulf.  Ideas and actual
mechanics based on the concept of Operation: Overkill II (which include
the main scenario, the Complex layout, the Infrared Scanner, Action Combat,
combat descriptions, all text files, and self-evident ideas) are also fully
copyrighted with text applicable from the Library of Congress.

In no way should the object code be modified and redistributed. This could
result in an abnormal function with the program, in which the authors bear
no responsibility.

No exterior programs should interfere with the normal registration process.

This program is presented on an "as is" basis with no guarantee to the system
operator or liability against the author.



   [  REGISTRATION  ]
      ~~~~~~~~~~~~
Registration for Operation: Overkill II (OOII) is completely
optional.  With Registration, you are capable of having up to 100 active 
players as well as removing the delay screen at initialization.

You can Register FOR FREE at http://vagabond.virtualave.net/register.html
Just fill out the form and your registration code will be emailed
to you as soon as it is processed.


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

Without registering OOII, the program is FULLY functional.  The only drawback
is that a maximum of 10 users can access the game, active or not.

You can always find the latest updates and new utilities for OOII
on the support bulletin boards and the main website.

















[   Documentation to Operation: Overkill - Version 1.20        Page 3   ]

   [  CONTENTS OF OOII120.ZIP   ]
Programs:
 OOII.EXE        | Main Program
 OOSETUP.EXE     | Configuration Setup
 OOINFO.EXE      | BBS-to-OOII Conversion Program
 MAINTOO.EXE     | Maintenance Program

Documents/Manuals:
 README.1ST      | An Introduction Text File
 OOII.DOC        | Overkill Sysops Manual
 OOSETUP.DOC     | OOSETUP Configuration Manual
 OOINFO.DOC      | OOINFO Manual
 OOIITS.DOC      | Trouble-Shooting Guide for Overkill
 REGISTER.DOC    | Overkill Registration Form
 WHATS.NEW       | New Features for the 1.20 version

Data Files:
 DESC.DAT        | Combat Descriptions
 BADNAME.DAT     | Invalid Handles/Aliases
 BANNED.DAT      | Invalid/Banned Real Names
 MONSTERS.DAT    | Monster File
 QUOTES.DAT      | External Quotes File
 BMENUS.PIX      | Special Picture Data
 CMENUS.PIX      | Special Picture Data
 LOGONS.PIX      | Special Picture Data

Map Files:
 VIDLAND.MAP     | Vidland Terrain Maps (beginner maps)
 VIDLAND.TXT     | Text File for Vidland Maps
 PRISONS.MAP     | Hydrite Prison Maps
 AFBS.MAP        | Airforce Base Maps

Text Files:
 ASSIST.ASC       | On-Line Tutorial help
 BASE.ASC/ANS     | Base Information
 BMENUS.ASC/ANS   | Base Menus
 CHARINFO.ASC/ANS | Character Information
 CMENUS.ASC/ANS   | Complex/Wasteland Menus
 COMBAT.ASC       | Combat Help Files
 COMPLEX.ASC/ANS  | Complex Information
 DEATH.ASC        | Death Descriptions
 DISEASES.ASC     | Disease Descriptions
 INVNTORY.ASC     | Inventory descriptions
 LOGON.ASC/ANS    | Logon Title Screens
 NEWS.ASC         | Overkill News File
 SCENARIO.ASC/ANS | Background Scenario Information
 TWONODES.ASC     | Multinode Detection Warning
 USERDOCS.ASC     | Players' Documents/Manual
 WASTELND.ASC/ANS | Wastelands Information

Included Packages:
 MAPFILES.ZIP     | 50+ map files
 MAPTEXT.ZIP      | ASCII printout of the map files
 INTERBBS.ZIP     | BBS vs. BBS competitions (interBBS play)

[   Documentation to Operation: Overkill - Version 1.20  Page 4   ]


   [  SETTING UP OVERKILL  ]
      ~~~~~~~~~~~~~~~~~~~
To set up and initialize a new game for Overkill, follow these
basic steps:

1) Make a directory on your hard drive called OOII or OVERKILL.

2) Unzip all the files of OOII1120.ZIP into this newly created directory.

3) View the text file "README.1ST" if you haven't already.

4) Run the configuration/setup program, OOSETUP.EXE.  If you need help
   at any time in OOSETUP, press F1 at any menu or command, or for full
   documentation on OOSETUP, view the text file OOSETUP.DOC.

5) If this is your first install, check the file OOIIDOOR.BAT which OOSETUP
   creates upon its exit.  This is the batch file that you can use to
   invoke Overkill from your BBS.

6) Run the maintenance program, MAINTOO.EXE in your Overkill directory.


After that final step, your Overkill game is now ready to be played!  It's
as easy as that!  All you have to do now is test it out locally and modify
your BBS settings to have Overkill as a loadable door.


   [  RUNNING OVERKILL LOCALLY  ]
      ~~~~~~~~~~~~~~~~~~~~~~~~
To run Overkill locally, type in "OOII L" or "OOII LOCAL" at the
DOS prompt in Overkill's directory, or Run LOCAL.BAT from the same
directory.



[   Documentation to Operation: Overkill - Version 1.20   Page 5  ]


   [  ONLINE FUNCTION KEYS  ]
      ~~~~~~~~~~~~~~~~~~~~
The Sysop has access to function keys that can be applied when a
user is
online.

     F1 : Toggle Status line
     F3 : Time - 1
     F4 : Time + 1
     F5 : Enter chat mode  /  ESC = exit chat
     F7 : Drop to DOS
ALT- F1 : Toggle Sound (if initialized upon startup)
ALT- F6 : Logoff Player
ALT- F8 : Ban, Kill, Clear player*
ALT-F10 : Sysop Override*


 *ALT-F8: Ban, Kill, Clear Player

    When the SysOp presses this key, he/she is asked whether or not if the
    current online player should be BANNED from the game.  If the Sysop
    agrees to this, the player is killed instantly, wiped from the userfile,
    and added to the text file BANNED.DAT.  When the person tries to access
    the game again, they will find that they can not play because of Sysop
    banishment.  The player may never enter the game again until the Sysop
    has manually erased the player's name from BANNED.DAT using a standard
    text editor.


 *ALT-F10: Sysop Override

    This function can be used to override the "Minutes Between Plays" for
    players, or to bypass the 24 hour "death" wait period.  This function
    key must be pressed before a user enters their alias (or real name in
    local mode).  Use this special function for emergency situations only!


[   Documentation to Operation: Overkill - Version 1.20           Page 6   ]


   [  ADDITIONAL TEXT FILES  ]
      ~~~~~~~~~~~~~~~~~~~~~

 BULLETIN.ASC:

  In the Information Cabinets in HQ, pressing 7 will display this text file
  if it exists.  If this file does not exist, the "WHATS.NEW" file will be
  displayed so players may see the new features of each version.

 NEWS.ASC:

  This file will be displayed directly after a user signs on.  You can edit
  this also to your likings on any information that may be necessary to the
  players.  The NEWS can also be accessed through the Information Cabinet.


 USERDOCS.ASC:

  The players who need assistance with the play of OOII can refer to
  this file within the game.  For those Sysops who like to keep their
  users up to date at all times may want to make this file available to
  his/her users for downloading and reading offline.

 FRONTIER.ANS/ASC:

  All activities that occur during Overkill maintenance and player logins
  are written to a data file called FRONTIER.OO.  When Overkill exits from
  play, two text files are created, FRONTIER.ANS (an ansi color file), and
  FRONTIER.ASC (an ascii file).  These files can be displayed from your
  BBS.

 TOP10.ANS/ASC:

  When Overkill exits from play, a listing of the Top 10 Player is created
  in the files of TOP10.ANS (an ansi color file), and TOP10.ASC (an ascii
  file).  These files can be displayed from your BBS as well. 

 WHATS.NEW:

  This file stores all the information concerning the new features from
  the Overkill 1.10 version to the 1.20 version.


[   Documentation to Operation: Overkill - Version 1.20          Page 7   ]


   [  EXTERNAL PROGRAMS  ]
      ~~~~~~~~~~~~~~~~~

 OOSETUP.EXE --

To setup and configure your Overkill game, use the OOSETUP program.  If
you should need help at any time, press the F1 key.  A small window of
text will pop up with an explanation or advisement on your current subject.
The text file that OOSETUP reads from is OOCONFIG.DAT, which can be edited
with a standard text editor.  For full documentation on OOSETUP, read the
manual file OOSETUP.DOC. 

 MAINTOO.EXE --

This is the maintenance that needs to be executed before EACH run of OOII.
The maintenance program takes care of bank interest, Hydrite Transmissions,
and various other necessary details.  Make sure you add this option into
your door batch file (if it hasn't already implemented) BEFORE you call OOII.
MAINTOO echoes its information over the modem so the players know the status
of Overkill's maintenance.

Also, if you plan to install MAINTOO.EXE in your BBS's nightly event, your
batch file will need to delete a file called BBSINFO.OO before running
MAINTOO.EXE.  BBSINFO.OO is created in Overkill's data directory every
time a user plays the game, so when MAINTOO.EXE is ran at your nightly
event, no user is present, so BBSINFO.OO must be deleted.

 OOINFO.EXE --

The OOINFO program processes the "dropfile" data that is created by your
main BBS software.  This dropfile data consists of the user's full name,
communications port, baud rate, time remaining, and an Ansi graphics switch.
Consult OOINFO.DOC for more information on setting up your batch file for
Overkill.

 INTERBBS.ZIP --

This zip package contains information for setting up BBS vs. BBS
competition ("InterBBS").  Bringing Overkill to a new level of play,
Donna Murrell and Paul Fusco have created a setup that allows two
bulletin board systems to play Overkill against one another! Check
into this INTERBBS.ZIP package if you are interested in setting up an
Overkill game to compete against another BBS.

  MAPTEXT.ZIP & MAPFILES.TXT

This zip package contains more map files and there TEXT version
that you can allow your players to have.  Just unzip into the Main
overkill Directory and then run oosetup.



[   Documentation to Operation: Overkill - Version 1.20            Page 8 ]


   [  MULTI-NODES  ]
      ~~~~~~~~~~~
Although Overkill does not run in a live multi-node system, Overkill does
have the ability to prevent multiple nodes from accessing Overkill data
files simultaneously.  Having two nodes loading the game at the same time
could result in a system lockup.  In order to prevent this, a text
file named OONODE.DAT keeps track if someone is logged onto the game.
When another user tries to access Overkill and finds that OONODE.DAT
exists, the program will inform the user and abort the loading, returning
that user back to the BBS.  If the file OONODE.DAT does not exist, the game is
not in use and may be accessed.  This is all done automatically and provides
for a security system for Sysops running multi-node systems.

This process only functions when the "Running more than 1 node" in OOSETUP
is set to 'Y'es.  If you should find a problem with OOII claiming that
another player is in fact "already playing" and is not correct, simply
delete the OONODE.DAT file and try again.


   [  BAUD RATES  ]
      ~~~~~~~~~~
Overkill has been tested at 28.8k baud successfully.  If you plan on
running the game with baud rates of 9600 or above, it is suggested that
you install a fossil driver.  The two main fossil drivers on the market
today (and public domain), are X00 and BNU drivers.  These fossil drivers 
can be found on most any public domain BBS.

Make sure you have the "Fossil" setting correct in the configuration of
OOSETUP.  If you have problems with high speed connections, try locking your
baud rate to 38400 baud on the BBS.  The BNU 1.70 fossil driver works
the best in conjunction with Overkill (from personal experience),and
BNU 1.88beta for some VFAST modems.

If your modem setup has different IRQs from the standard (com 1: irq 4,
com 2: irq 3, com 3: irq 4, com 4: irq 3), a fossil driver will be required
to change the IRQ setting.  Please consult your fossil driver's documents
about using a command line to alter the IRQ setting.

As a side note, if your players should be experiencing "delays" in action
combat (and if you are not running a multi-tasking program), the problem
lies in the modem buffers.  Your users can turn the "error- correcting"
option off with their modems.  This does not permanently write that command
to the modem's configuration.  Users can also disable another feature (if
their modems have it) called data-compression.


   [  EMS/XMS MEMORY  ]
      ~~~~~~~~~~~~~~
To utilize your computer's upper memory with Overkill for increasing
processing speed, you can use one of two parameters in the command line.
In your batch file, you may specify which of the two memory handlers you
wish to use.  The options are '/XMS' and '/EMS'.  XMS (Extended Memory) is
the quickest while EMS (Expanded Memory) is quicker than regular

[   Documentation to Operation: Overkill - Version 1.20              Page 9 ]


conventional memory.  Here are two examples of how to utilize upper memory
handling:

OOII OOCONFIG.DAT /XMS

..or for Expanded Memory..

OOII OOCONFIG.DAT /EMS

Please note that the /EMS must be stated *after* the configuration file
name, and if '/EMS' or '/XMS' is to be used, the configuration file name
must be stated first.



[   Documentation to Operation: Overkill - Version 1.20            Page 10   ]


   [  MULTI-GAME SETUP ]
      ~~~~~~~~~~~~~~~~
  Overkill allows for the "sharing" of the main files.  To do
this, you can specify where you want to store the data files and where to
store the text files Overkill uses.  This can be customized with OOSETUP
by changing the desired directories for the "data" and the "text" storage
(please note that this is for multi-GAMES, not necessarily multi-NODES).

                       OVERKILLĿ
                                DATA
                                TEXT

  As an example for a one game setup, the main directory will be the basic
  "C:\OVERKILL\".  Now, say that you wanted to split up the data and the
  text files into different directories.  So, make two new directories:
  one in "C:\OVERKILL\DATA\" and one in "C:\OVERKILL\TEXT\". Next, you
  will have to copy all the ansi files (*.ANS) and ascii files (*.ASC) to
  the text directory, "C:\OVERKILL\TEXT\".  Then, when you execute OOSETUP,
  change the "data" path and "text" path to these newly created directories
  in Menu 1.  When OOSETUP exits, it will then create the data files in
  the "C:\OVERKILL\DATA\" path.  Finally, load up OOSETUP one last time,
  and it should tell you what files are missing or out of place. If any
  appear on your screen, simply exit OOSETUP and copy the files from the
  main Overkill directory to their correct directories.  Of course, with
  a one game setup, these two extra directories are optional. Everything
  could be placed in one directory, "C:\OVERKILL\".

  For a multi-game setup, the process is similar to the above. It's
  difficulty (or ease) depends on how complex you want to make your setup!
  For example, you can create two games that branch off from the main
  "C:\OVERKILL\" directory, as so:

                       OVERKILLĿ
                                GAME1
                                GAME2

  Since most Sysops do not edit the text files of the game to their own
  likings, we can leave the "text" directory in "C:\OVERKILL\", while
  selecting the "data" to the different "C:\OVERKILL\GAME1\" and
  "C:\OVERKILL\GAME2\" directories.

  Now, the question is how will Overkill know which configuration file
  to read in if OOCONFIG.DAT is stored in "C:\OVERKILL\"?  There are
  several ways one could do this, but the easy way is to add a parameter
  to your door batch file (which will be the name of the desired
  configuration file).



[   Documentation to Operation: Overkill - Version 1.20         Page 11   ]


  If you want to load up Overkill using GAME1's configuration, you can
  create a new configuration file called GAME1.DAT instead of the standard
  OOCONFIG.DAT file.  To create a configuration file of GAME1.DAT, simply
  type in: "OOSETUP GAME1.DAT".  To create a configuration file for GAME2,
  you would enter "OOSETUP GAME2.DAT".

  In your batch files to load up each game, you specify which configuration
  file you wish to use by putting its name after each program .EXE.  For
  example, GAME1's batch file could look as so:
     cd\overkill
     ooinfo GAME1.DAT 10 \bbs\ 1
     maintoo GAME1.DAT
     ooii GAME1.DAT
     cd\bbs

  ...or similarly for GAME2:

     cd\overkill
     ooinfo GAME2.DAT 10 \bbs\ 1
     maintoo GAME2.DAT
     ooii GAME2.DAT
     cd\bbs

  With this multi-game setup, Overkill only uses its programs from the
  main "C:\OVERKILL\" directory and doesn't need to be copied over into
  new directories each time you want to add a new game.  Here are the
  basic steps again to add a new game:

  1) Create a new subdirectory, like "C:\OVERKILL\GAME1".
  2) Load OOSETUP with the desired configuration file name, such
     as "OOSETUP GAME1.DAT"
  3) Change the "data" path to the new directory that you added in
     step 1.  This is done in OOSETUP from the System Information menu.
  4) When you exit and save OOSETUP, the new data files will be created in
     the "data" directory that you assigned.
  5) When creating your batch file to load up this new game, remember to
     add the name of the configuration file that you want Overkillto
     use (ie: MAINTOO GAME1.DAT, OOII GAME1.DAT, etc.)
  6) Load up OOSETUP one last time to see if any files are out of place.
     If any files are missing, copy the files from your main Overkill
     directory into the directory where the files are required.

  If you have trouble with this setup and have found an easier way to
  setup multi-games with one directory (such as tooling with the batch
  files, copying different configuration files back and forth, etc), go
  with what works!  If you read this section over again after installing
  your first game, you'll find it easier to understand.



[   Documentation to Operation: Overkill - Version 1.20         Page 12   ]


   [  TROUBLE SHOOTING  ]
      ~~~~~~~~~~~~~~~~
If you continue to have problems setting up Overkill, try reading the
Overkill Trouble Shooting text file called OOIITS.DOC.  It contains many
Common questions/problems by other Overkill Sysops replied with answers.



   [  THAT'S ALL FOLKS!  ]
      ~~~~~~~~~~~~~~~~~
That's basically all the information you should need to get OOII and running!
Although this document is fairly short, Overkill's setup is self-explanatory
with help available in OOSETUP.


Any notes or comments are appreciated and my address is:

                           Bryan Turner
                            5737 Diana
                        Garland, TX  75253


If you prefer a direct connection, you can contact me on my BBS:

           Bryan Turner (aka Perseus aka Rabbit aka BAT)
                        Pegasus Flight BBS
                          (972) 226-2783

                       FidoNet - 1:124/7013
                  Internet- Vagabond@darktech.org


You can also reach me through echomail in FidoNet's DOORWARE, ON_LINE
GAMES, DOORGAMES, or On the internet at:

http://vagabond.virtualave.net



[   Documentation to Operation: Overkill - Version 1.20         Page 13  ]

   [  SPECIAL THANKS!  ]
      ~~~~~~~~~~~~~~~
A very special thanks to the following people for helping make Operation:
Overkill a success!

Donna "Suprax" Murrell, Paul "Macroman" Fusco, Mark "Hawk" Stroud, Bruce
"Eieio" Peterson, Jason "Scratchy" Varian, Jacob "Vitas" Linscott, Andy
"F*I*D*O" Mans, Alan Davenport, DDS Systems, Ken Givens, Scott James,
Kyle "Shadow Lord" Sessions, Robert "Captain Marvelous" Gray, Tim "Money"
Hodges, Jay "Julumon" Mori, Tom Cochill, Cy Curnin, Larry Nulf, OOII
Distribution Sites, Michael "Tarix" Montague, Bob McGrath, Ryan "Togzik"
Miller, Bill "Toe" Densmore, Chris "The Terminator" Green, Brian "The
Punisher" Amick, William Idol, Holland Hitch of Texas, Tom Hazel, registered
OOII Sysops, Sarah "Pasta Slayer" Snyder, Robert "Viper" Aaron, Cindy Wright,
Susan Bowman, Ed "Bladin Warrior" Phonephrachanh, Kenneth Bledsoe, James
Ray, Mayo "Minotaur" Caceres", Arnold Robinson, Lance Powell, Rick
"Warlord" Joyce, RSAL Ansi Graphics, the "OOII" and "OKILLERS" participants,
the Alpha Testers of Dallas; San Antonio; San Diego; Rochester; Richmond;
Denton, Borland Intl., PKWare, XRobot, Front Door, Remote Access, DoorNet,
Andrew Mead, Rod Hancock, Mike Phillips, George Romero, Gordon "Drake"
Brandt, Michael Willis, Tauran Knight, Andrew "Mr. Scary" Welch, Chris
"Hobbit" Strong, Joe Kemp, Marty Bogle, Byron Smith, Jeff Lancton, Cyberpunks
of America, PGNet, DeathNet, Fidonet, all the map terrain authors,
Glenn Joyner, and last but not least, Cleve "Osprey" Sanders for the
excellent Overkill Guide (if he ever puts it out!).


And the 1.20 Beta Testers:

Dennis Haddox
Robert Olsen
"ACE"
GenTalon@aol.com

And a SPECIAL thanks to:

Grant "Teucer" Rodgers EMAIL AT: uh_oh_im@hotmail.com
The Official keeper of the Operation Overkill FAQ.

THANK YOU EVERYONE!



[   Documentation to Operation: Overkill - Version 1.20        Page 14  ]



   [  THE NEXT PROJECT  ]
      ~~~~~~~~~~~~~~~~
So what's next in the works after Overkill?

There are a lot more OVERKILL files on the horizon, you will just
have to stick around and see what Michael and I have up our
sleeves.



EOF!
