
		              
		         ߱      ߱
		                       
		                
		            ߱      ߱
		                      
		         
		                

		  InterStellar Annihilation Version 0.993a
		  Copyright (c) 1996-2001 Andy Stewart
	Portions Copyright (c) 1991-1995 Minds Edge Productions Inc.
			     All Rights Reserved.

			     SysOp  Documentation
			   Written by Myles Bunbury

       (This .DOC file is gradually being rewritten (in plain english)
        over the v0.992 version. Please be patient with us, as some parts
        may still be a little confusing.)

         
       Note: 4.11.01 - Contact information still includes Myles' information.
                       As far as I know, he has no idea I am working on ISA again,
                       as I have lost contact with him.  If you know of his new email
                       address, please let me know!



              	ͻ
               	۲ Licensing Agreement ۺ
            	ͼ

   "ISA" refers to the software and documentation contained in
   InterStellar Annihilation distribution archive released by
   Andy Stewart

   InterStellar Annihilation is Copyright (c) 1996-2001 by Andy 
   Stewart.  All Rights Reserved.

   Distribution and use is subject to the following conditions:

1. Only the original, authenticated ZIP format file is authorized
   to be distributed.

2. You are encouraged to distribute ISA provided that no fee is
   charged for its distribution. Written permission must be
   obtained before including ISA with any "bundled" software
   package that is marketed and distributed for profit, such as
   those for sale by vendors, individuals or companies. Pay
   Bulletin Board Systems may however charge their regular fee
   provided that no additional charge for ISA is levied. A
   copying fee of $3.00 or less per diskette may be charged by
   a non-profit user-group.

3. No part of ISA may be modified, altered or reverse engineered.

4. ISA may not be used in any unlawful or illegal manner.

5. Andy Stewart is not obligated to provide future versions of, or
   support for, ISA.

   This software and accompanying materials are distributed "as is"
   without warranty, expressed or implied; including, but not limited
   to, any implied warranties of merchantability or fitness for a
   particular purpose. In no event shall Andy Stewart or anyone involved
   with the creation and production of this product be held liable for
   any damages, including, but not limited to, any lost profits, savings,
   data or other incidental, indirect, special, or consequential damages
   arising out of the use or inability to use this software, or for any
   claim by any other party, even if Andy Stewart, any of the ISA Beta
   Testers, or other personnel have been advised of the possibility of
   such damages. The person using the software bears all risk as to the
   quality and performance of the software.


   	        ͻ
                ۲ Copyright Acknowledgements ۺ
                ͼ

   This document mentions several other products.  All copyrights,
   trademarks and reserved rights held by these products are
   acknowledged. All trademarks and registered trademarks belong to
   their respective owners.


        ͻ
        ۲ Upgrading from 0.992 or earlier to 0.993 ۺ
        ͼ

   Due to the long delay since ISA's last release, new ownership,
   and a complete overhaul (the first of many) of the code, we're
   advising people to do a fresh install of ISA, in order to prevent
   possible conflict, and to keep your directory from getting cluttered
   up! Nuke your current ISA directory, and reinstall from scratch.
   Trust us, you thank us in the long run!

*NOTE!* - ISA v0.993a's InterBBS files are still compatible with
	  v0.992.  However, this will soon change as the IBBS
	  routines will be undergoing a major overhaul for v0.994
          in order to eventually make way for 'Myles Routing'.
          (Hey, we had to call it something!) :)

          Andy's Note:  Can you see the size of Myle's head increasing?


	ͻ
	۲ Installing From Scratch ۺ
	ͼ

1) If you haven't done so already, unzip the contents of the ISA ZIP
   file into its own directory (i.e. C:\BBS\DOORS\ISA)

2) Run ISASETUP.EXE.

3) Create the NODEx.CFG file.

   NODEx.CFG format:

   GAP          (Dropfile type - See below)
   C:\TP\BIN\   (Path to dropfile)
   DreamNET     (BBS Name)
   Andy Stewart (Sysop Name)
   57600        (Locked baud rate - 0 if not locked)

   * Dropfiles:
     As illustrated above, the door's data file type is specified
     in line 1 and can be PCB for PCBoard, GAP for GAP (DOOR.SYS,
     WildCat! v3.x-5.x), SF for Spitfire, RBBS for RBBS, WC for
     WildCat! v2.x, TRIBBS for TriBBS, or WWIV for WWIV/VBBS.  If
     your BBS is able to produce DOOR.SYS, I suggest using GAP for
     line 1.

4) Create ISA.CFG, simply answer the configuration questions.


5) Reset ISA.

6) Create a batch file to call ISA.EXE from your BBS.
   Example:
   @Echo off
   C:
   CD \BBS\DOORS\ISA
   ISA.EXE NODEx.CFG (where x is the node you are running under).
   CD \BBS

7) Setup your BBS to execute the batch file in step 3.

8) Logon to your BBS and test the setup

9) Create an empire and kick some butt! :)

	ͻ
	۲ Files Included In the Original Archive ۺ
	ͼ

	SYSOP.TXT       - This file - ISA Sysop Documentation
	ISA.TXT         - Player Documentation - Used inside ISA!
	WHATS.NEW       - History of changes to the game
	SAMPLE.ZIP      - Sample Configuration files
	ISA.EXE         - ISA's main Executable
	ISACLEAN.EXE    - Utility to delete sent files
	ISASCORE.EXE    - Utility to create score board
	ISASETUP.EXE    - Setup Utility
	ISAPACK.EXE     - ISA File Packer/Unpacker
        LEAGUES.LST     - The *Official* ISA League Listing
        L116INFO.ZIP    - League 116 InfoPack (Official ISA InterBBS League)
	ISAROUTE.ZIP    - Additional Documentation about ISA's Routing
		          (By Jeff Bolton) (Unchanged by DreamWare)
        SURVEY.TXT      - Short survey form
        FILE_ID.DIZ     - Description File
        DESC.SDI        - Short Description File
        ISAREG.EXE	- ISA RegNum Generator (nothing fancy).


	ͻ
	۲ ISASETUP.EXE ۺ
	ͼ

   A utility called ISASETUP.EXE is provided to make installation
   easier.  If you have any problems with this program you can
   setup ISA manually (Read the sections: ISA.CFG and Multi-BBS for
   help with manual installation).  To auto-setup ISA run ISASETUP
   then select Install/Edit ISA.CFG, the program will then prompt
   you to answer several simple questions.  If ISA.CFG already
   exists the information will be loaded as the default.  When you
   tell the program to save, it will write the file ISA.CFG to the
   current directory.  If you did not run ISASETUP.EXE in the ISA
   directory then you will have to move ISA.CFG to the ISA
   directory.

   InterBBS Setup: If you select "Add a BBS to your NODES.CTL" you
   will be prompted to answer several questions and the answers
   will be recorded in your ISANODES.DAT (if it does not exist it will
   be created).  As well, if a <user code>.REP file is found in
   your ISA directory it will ask you if you wish to attach it to
   the system you have just configured.  If you select "Yes" the
   program will attach the file along with a message telling the
   sysop that you have configured their BBS to be hooked up to your
   ISA game and will tell them to do the same.  If you are not
   prompted, or answer "No" to the prompting of sending a .REP file
   you MUST manually send a copy of this file to the BBS you are
   configuring.  The BBS that you have configured must also
   configure your system, so be sure to tell them what your three
   character code is to allow them to add your system to their
   NODES.CTL file.  If you do not have a <user code>.REP file in
   your ISA directory run ISA and it will create one for you.

   Routing: ISA Setup will also help you to establish the routing
   of files.  It is recommended you get the game set up and working
   without routing at first and implement it later. However if you
   do wish to set up routing it can easily be done from within
   ISASetup. For help manually setting up routing please read the
   files included in the sub-archive ISAROUTE.ZIP and the routing
   section lower down in the documentation.


	ͻ
	۲ ISA.CFG ۺ
	ͼ

	You must have a file called ISA.CFG in the ISA directory.  The
	file is plain ASCII and can be edited with any text editor or
	ISASetup.  The structure of the file is:

   1)       0000000
       - Registration code

   2)       1:231/146
      - Your Net/Node address (blank line if none)

   3)       C:\BBS\DOORS\ISA\
      - Path to Game Directory

   4)       C:\MAILER\NETMAIL\
      - Path to your netmail directory *.MSG files

   5)       C:\MAILER\FILES\
      - Path to Inbound files directory

   6)       DRM
      - Your three letter code (see multi BBS section in the docs)

   7)       No
      - No or Yes, check for dupe users (see multi BBS)

   8)       5
      - Number of turns each users has per day

   9)       10
      - Optional: number of Spy Operations, default:10

   10)      10
      - Optional: number of turns of protection, default:10

*  11)      3
       - Optional: The level of "special effects"
		   Where:   1 = All special effects
			    2 = One of the special effects
			    3 = No special effects

*  12)      YES
       - Optional: YES or NO, if the casino can be used or not

*  13)      0
       - Optional: Prompt user for graphics type.
		   0 = No prompting all info is read from DORINFOx.DEF
			or DOOR.SYS
			Where: 0 = ASCII
			       1 = ANSI
			       2 = Avatar
			       3 = ANSI and Avatar
		   1 = Ask user if they would like ANSI
		   2 = Ask user if they would like Avatar
		   3 = Ask user if they would like ANSI and Avatar

*   14)     NO
	- Optional: YES or NO, if the system requires multi-node aware
		    support (See Multi-Node Aware, later in the Docs,
		    this is different from ISA's Multi Node feature).

*   15)     YES
	- Optional: YES or NO, if you would like ISA to use the fossil
		    buffer.  If the buffer is filled the local side
		    display will be faster then the remote side, so if
		    you would like to see exactly what the user sees set
		    this to NO, however it may slow the game down,
		    especially on multitasking systems. (Previous
		    versions of ISA automatically set this to NO, this
		    option has been added to increase display speed).

    16)     1
	- Optional: This is the interest rate calculated on the users
		    money in their bank account.  Interest is calculated
		    every turn.

    17)  10000
	- Optional: This is the maximum time the user can spend in ISA.
		    If it is not specified the users maximum time is
		    used.  If the user has less time than specified,
		    their time gets lowered. The amount of time the user
		    has played per day is not remembered by ISA, so a
		    user can reenter the game after they run out of time
		    and still have some time left.

    18)  Path to routed Files Directory
	- Optional: This is the directory that ISA will use to store
		    it's files when routing is implemented. *.(I) files
		    are stored here and Pass Through files.  If this
		    directory is not configured The ISA Game Path is
		    used instead.  That would be the same as line 3 of
		    the configuration file.  (Routing is explained later
		    in the documentation).

    19)  Yes  
	- Optional: INTL Kludge Toggle.  If this option is Yes the INTL
		    kludge will be inserted in all netmail messages.  If
		    it is set to No, then the INTL Kludge will only be
		    used when the destination and origin addresses are
		    in different zones.

   20)  Yes
       - Optional:  Direct Flag Toggle.  This option should be set to
		    YES unless you are familiar with file routing.
		    * NOTE: If the Direct flag is turned off, you can
		    route files via your mailer, instead of using ISA's
		    built in file routing.  However, this method is not
		    recommended for one simple reason: you do NOT have
		    control over the files that get routed through your
		    system.  This means that somebody could take
		    advantage of a file routing setup by sending a large
		    file through your system to a long distance
		    location leaving you with the phone bill.  If you
		    use the built in routing to ISA, ISA will make sure
		    to only forward files that belong to the game to
		    avoid such a situation.

   21)  Other
       - Optional:  Mailer Type.  This line should read one of the
		    following: Binkley, FrontDoor, D'Bridge or Other.

   22)  Yes
       - Optional:  Local Attacks.  Set this to No if you want to
		    disable local attacks.  Yes allows local attacks.
		    You may want to set this to encourage users to
		    attack remote systems.
   23)  200
       - Optional:  Maximum amount of planets a user can buy in one
		    turn.

*  24)  I forget what it was, but it's gone.

*  25)  I forget what it was, but it's gone.


NOTE:  Entries marked with a "*" are no longer used by ISA v0.993a, however
       make sure those lines are there or else the rest of the .CFG file
       will be hosed!  The lines can be empty, but they MUST exist!


	ͻ
	۲ InterBBS Play ۺ
	ͼ

	This is the main feature of the game.  The idea for it is not
	original there are several games that are InterBBS playable.
	Basically what the game will do is this: Using a FTN compatible
        mailer it will send various file attaches to other BBS' which
	you have configured.  These BBS' will then process the files
	and send information back to your BBS. You may see a bunch of
	files in your incoming files directory (e.g. c:\mailer\files\)
	these will be moved by ISA on it's next run (or you can run ISA
	/F as described later in the documentation).  Once you have ISA
	running, it should require no further attention. This InterBBS
	feature allows users to send attacks and messages to other users
        that are on different BBS' and will hopefully make the game a
	lot more exciting and interactive.

	NOTE: The following is a description of what you must do to
	      configure the game for InterBBS play.  If you do not want
	      the game setup for InterBBS play, then leave lines 2,4,5
	      and 6 of your ISA.CFG blank, and set line 7 to No.

        To configure ISA for multiple BBS', each system that is going
	to be connected to your system as well as your own system must
	come up with an unique three character code.  Something like
	"Dog" or "Bif" or "$#X" is perfectly fine.  You cannot use
	characters such as ".", "*", "?" in your code since your three
	letter code is used to assign a file name for InterBBS packets.
	Any valid filename character is permitted. If you cannot create
	a file with a particular character then do not use that
	character in your three letter code. You may not use the three
	letter code 'PKT' since it is used by ISAPack. Your code must go
	on line 6 of your ISA.CFG.  You must also configure all the
	directories in your ISA.CFG as explained in the above section.
	You must also create a file called ISANODES.DAT the structure is as
	follows (remember ISASetup can edit the ISANODES.DAT file for you
	if you find it easier):

		<Net/Node Address of BBS>
		<Name of BBS>
		<BBS Code>
		<Path for BBS>
		<Net mail Status>
		<Net/Node Address of the Next BBS>
		<Name of BBS>
		etc.
	 e.g.
		1:231/146
		DreamNET
                DRM    {This is NOT your code it is that BBS' code}
		c:\bbs\doors\isa\dream\
		C
                1:163/114
                Myles' Games Extravaganza
                MGE
                d:\ibbsfiles\isa\myles\
		H
		etc.


    Where:

    Line 1:  Is the Address of the BBS you wish to configure on your
	     network.  It must be in the form of ?:?/? and must be in
	     your current node list.  Points are NOT supported.

    Line 2:  The BBS Name is self explanatory.

    Line 3:  The BBS' code, this is the code that  BBS has in it's
	     ISA.CFG file it must be three characters and only three
	     characters.  Get this code from the BBS that you are
	     configuring, and you must give your code to that BBS so
	     they can configure you.  Both of you must have each others
	     systems configured or it will not work.

    Line 4:  A directory that will be used for incoming and out going
	     files for that BBS.  You must create this directory and
	     have a different one for every BBS you have configured in
	     your network.

    Line 5:  C,I,N, or H.  This stands for Crash, Immediate, Normal or
	     Hold.  Most systems will want to set this status to Crash,
	     it is the only way the game is very effectively running in
	     a multiple BBS set up.  However you can set it to hold or
             normal if you need to for some reason (e.g. one of the BBS'
	     is a private system).

    Line 6:  This would be the address of the next BBS you wish to have
	     configured in your network.

		  Etc.

    Note:  The Duplicate check option in the config does the following
	   if set to Yes.  When a user logs onto your BBS it will scan
	   all the known users of the network.  If it finds that the
	   user is already playing on another BBS, it will not allow
	   them to join the game on your BBS.  If they manage to join
	   one game on one BBS and then log onto another BBS in the
	   network and join that game before an updated file gets
	   through, their newest Empire will be deleted.

    You must then obtain a <user code>.REP file from the other BBS, and
    must file attach your <user code>.REP to the other BBS (this can be
    automatically done with ISASetup).  You will find the <user code>.REP
    file in your  ISA game directory after the first run. InterBBS
    operations will not work until both BBS' have received a copy of each
    other's <user code>.REP file. You may have to file attach this to
    the other BBS manually if ISASetup does not attach a copy for you.
    Once it is set up ISA will automatically make the file attaches to
    the other BBS with updated <user code>.REP files as needed.

    It is also a good idea to agree on your set-up with the other BBS'
    you're playing with. For instance if one BBS has 30 plays per day
    and the other(s) have 5 then the game is going to be unbalanced, so
    you might want to agree on the amount of turns per day given on all
    the BBS' involved in the game.


	ͻ
	۲ Routing ۺ
	ͼ


     ISA now supports file routing.  To implement this feature you must
     create a ROUTE.CFG file in the ISA Game Directory (ISASetup can
     create and modify this file for you).  The format is as follows:

      *<Your AKA to use when the message is written>
      %<The Destination of the mail>
      #<Mail Status, C,H,I,N for Crash, Hold, Immediate and Normal>
      ?<Destinations that get routed through the above destination>
      ?<This gets repeated as much as needed>

      The entire portion above can be repeated as many times as needed
      to configure more than one BBS to route through.

      You can use ISASetup to create the ROUTE.CFG file and setup your
      routing.  This may be the easiest way to get started.

      If you are setting up routing it is HIGHLY recommended that you
      read the files included in the sub-archive ISAROUTE.ZIP.  There
      are three text files written by Jeff Bolton that explain in detail
      the setup of routing from within ISA.

      NOTE: If a file is routed and the destination or pass through
	    destination is not configured in the ROUTE.CFG file the file
	    will NOT be forwarded and it will be used by ISA on your
	    BBS.  This can cause attacks intended for another BBS to end
	    up on your BBS attacking the wrong person.  Do not set up
	    your ROUTE.CFG to forward files until you have checked with
	    your uplink and they are ready to forward the file on to the
	    next destination.

	ͻ
	۲ ISASCORE.EXE ۺ
	ͼ

	ISASCORE is a separate program used to create ASCII,ANSI and
	AVATAR text files of the ISA score board.  These files can then
	be displayed on your BBS.  The command line to run ISASCORE is:

	ISASCORE <Name of ASCII file> <Name of ANSI file> <Name of Avatar file>

	If you run ISASCORE with no parameters you can view the score
	board on the screen.  If you  omit the name of the Avatar file
	only and ANSI and ASCII one will be created.  If you omit both
	the Avatar and ANSI file name only an ASCII file will be
	created.

	ISASCORE supports a multi-node setup, meaning it can be run while
	another user is online without worrying about crashing the game
	or causing any share violations.


	ͻ
	۲ ISACLEAN.EXE ۺ
	ͼ

	ISA Clean is a separate program that is used to clean up ISA's
	out-bound files IF your mailer does not support the Kill/Sent
	flag with file attaches.  Simply run it from the main ISA
	directory and it will clean up the files.  It is recommended that
	you run this in your nightly event if your mailer does not
	delete files with the Kill/Sent flag.  It doesn't hurt to run
	ISAClean if your mailer deletes sent files, ISAClean will simply
	have nothing to clean up! So if your not sure about your mailer
	just run it and see what happens.  ISAClean also uses standard
	I/O so if you wish to log what it is doing you can simply
	redirect the output to a textfile, i.e.:

			ISAClean > ISACLEAN.LOG


	ͻ
	۲ ISAPACK.EXE ۺ
	ͼ

	ISAPack is a utility used to pack outbound ISA files into one
	compressed file. You do not need to use this utility in order to
	play the game, however if you prefer sending one file instead of
	many files to other systems this utility will pack outbound ISA
	files into one outbound file for you. The command line is:

	   ISAPACK <options>

	Options:
	    /P - Pack outbound files
	    /U - Unpack inbound files

	When packing outbound files ISAPack scans the netmail folder for
	attached outbound files and adds them to the packed file going
	to the same destination.  It determines the priority of the mail
	by reading the ROUTE.CFG if available, if not then the NODES.CTL
	file.  If ISAPack is not run often enough and you have a system
	configured to Crash mail you may have a problem: the packets
	that ISA creates may be sent off before the ISAPack is run and
	therefore the packer is not as effective as it could be. To fix
	this problem you should select Hold priority in your ROUTE.CFG
	and NODES.CTL for all your outbound nodes that you pack files
	for and then create the file ISAPACK.CFG. If found, ISAPACK.CFG
	will be used to determine which systems to send packed files to
	(it will not send files to systems not listed) and their
	priority. In this way you can selectively pack files only for
	certain destinations. ISAPACK.CFG is an ASCII text file made up
	as follows:

	<Destination Address>,<Priority>

	Each line is another entry. You may use as many lines as needed.
	Destination address is in the form Zone:Net/Node and is followed
	by a comma and then the Priority. Priority flags are N,C,H,I for
	Normal, Crash, Hold and Immediate.

	When should you run ISAPack /P?  Well the best times are
	immediately after ISA /M (ISA's maintenance) since it always
	creates outbound files.  You will also want to make sure you run
	ISAPack before any mail events to ensure that you have your
	outgoing ISA files packed.  You probably do no want to run
	ISAPack every time someone exits the game since it will slow
	things down considerably.  If ISA is used a lot on your BBS you
        may want to run it every time a user logs off the system.  Make
	sure you run it at least once a day.

	To unpack files simply run ISAPack /U and it will all be taken
	care of for you.  You do not need to configure anything for
	this.  You may want to put this command in your nightly
	maintenance in case people start sending you packed ISA files.

	ISAPack also uses standard I/O so if you wish to log what it is
	doing you can simply redirect the output to a textfile, i.e.:

			ISAPack <options> >>ISAPACK.LOG


	ͻ
	۲ ISA v0.994 ۺ
	ͼ

   The next release of ISA will likely be the v0.994 bugfix. This will
   correct any bugs that v0.993a might have that the Beta Testers didn't
   track down, balance the game more, and improve security a little.
   Furthermore, it will probably include a couple of new features that
   were meant to get into v0.993a, but didn't make it due to time
   constraints (mainly the new InterBBS routines).  v0.994 will also
   include 32-bit EXEs.

   Of course, all, some, or none of that might be included in the next
   version.  You never know, we just might get it right on the first
   try! (Uh, yeah). If that's the case, v1.0 will be the next version,
   and you can read the next section for a list of things that might
   pop up there.

   The release date of v0.994 is not known, so don't be heckling us
   if it isn't out yet!  When we have a general release date, we'll be
   sure to post it..


	ͻ
	۲ ISA and the Future.. ۺ
	ͼ

   ISA is a continually ongoing project that is always under development.
   Here are a list of some things that you'll hopefully	see in upcoming
   releases of ISA:

	* New, better InterBBS routines.
	* RIP Graphics
	* ANSI Animated Sequences
	* Internal User Help System
	* Full Screen Message Editor
	* Dynamic Battles/Spying
	* Improved InterBBS capabilities
	* Support for Internet Email transfers
	* Improved InterBBS Security
	* "Cheat Resistant" Programming
	* More Random Events
	* Different Races
	* Technology
	* Leaders/Generals
	* NPC Empires
	* NPC Mercenaries
	* 32Bit compiled EXEs.
	* AND MORE!
	* Possibly a Web version!

   If you have any other suggestion that you'd like to bring up, feel
   free to contact the author!

 **I.S.A. v1.0 (maybe even v0.994) WILL MORE THAN LIKELY REQUIRE A RESET!!!**
                               ***BE WARNED!***

        ͻ
        ۲ ISA On The 'Net! ۺ
        ͼ

  Looking for the latest and greatest news on ISA? Trying to track down
  the latest version? What the inside scoop on ISA development? Then visit
  the official homepages:

  ISA
  http://www.taynik.com/isa/

  TayNik Online
  http://www.taynik.com

  It's your source for all your ISA & TayNik Software needs!

	ͻ
	۲ Features ۺ
	ͼ

	 ISA is multi-user and multi-node aware!

	 ISA supports InterBBS play!

	 InterBBS operations support file routing and gating.

	 ISA will monitor carrier and return to the BBS if it is lost.

	 ISA will monitor the users time left and return them to the
	  BBS when it is up.

	 ISA will monitor inactivity and return to the BBS after a user
	  has been found inactive too long. (i.e. went to have a coffee
	  <grin>)

     ͻ
     ۲ Error Messages ۺ
     ͼ

Borland Turbo Pascal Error Messages you can get with ISA:

Number Meaning                 With regards to ISA
------ ----------------------- -------------------------------------------    2  File not found          You are missing a file.
    3  Path not found          You are not using the batch files we included.
    4  Too many open files     Increase your FILES= statement in your
			       CONFIG.SYS  We recommend 25 or more.
    5  File access denied      Either a file has been set to read only, a
			       directory is full, a RENAME tried to rename to
			       an existing file name or a file is not open.
    6  Invalid File Handle     Your file handles have become corrupted, DOS err.
  100  Disk Read Error         An attempt was made to read past the end of a
			       file most often.  Something is corrupted in the
			       record pointers.
  101  Disk Write Error        Generally an indication of a full hard disk.
  103  File Not Open           File is closed when it shouldn't have been.
  104  File Not Open for Input Text file is closed when it shouldn't have been.
  105  File Not Open for Output "   "     "   "       "      "       "
  106  Invalid Numeric Format  Generally this is only caused when reading a
			       BBS interface file (that has the user's info).
			       It happens when ISA is trying to read a 
			       numeric value from an interface text file and 
			       there isn't a valid number in the file.

  Errors 150 through 162 indicate various HARDWARE failures.  If you're 
  getting these, then something is wrong with your PC and we can't be 
  of much help there.

	Some common ones are:
  152  Drive not ready         Controller problem or drive not spinning
  154  CRC error in data       Scrogged disk (real technical eh? (grin))
  156  Disk Seek error         Head problem or bad controller
  157  Unknown media type      Did you just change to DOS 4.0 or 5.0???
  158  Sector not found        Head problem or bad controller
  159  Printer out of paper    Hit Control P!  Disable printer logging.
  160  Device write fault      Disk problem
  161  Device read fault       Disk problem
  162  Hardware Failure        Reported due to Dos sharing violations,
			       mostly having to do with LAN or multi-
			       user problems.  If you encounter this
			       error, then you have a configuration 
			       problem with your multinode BBS setup.
			       Make sure Share is being run.

  Fatal errors generally indicate a problem that must be fixed before you 
  can continue to run the game.

  200  Division by zero        Now I hope you cannot make one of these happen
			       as I check before every division to make sure
			       it DOESN'T happen, but to you, it just might.
  201  Range Check Error       Array index out of range.
  202  Stack Overflow          NOT ENOUGH MEMORY for the stack!
  203  Heap overflow error     Same as 202.
  204  Invalid Pointer Op.     Can be caused the same as 202.
  205  Floating point overflow This is generally caused when a number exceeds
			       around 2.1 billion, and thus becomes to large
 			       for ISA to handle.
  207  Invalid Floating point  You have a real that's trying to be converted to a
       Operation               Long int and its greater than 2 billion.
  209  Overlay File read error ISA had a problem getting an overlay from the
			       ISA.OVR file.  If you're not using EMS, then
			       the .OVR file is missing or is setting on a bad
			       sector on your harddisk.  If you are running EMS
			       then you have a bad memory chip! (yak)


   Hopefully, if you're getting any of these errors, this chart will help.
   If you're getting any of the above errors and are unable to resolve
   them yourself, please feel free to give the author a call, and he'll
   be more then happy to help.

        ͻ
        ۲ Credits ۺ
        ͼ

	I would like to credit Minds Edge Productions for creating ISA.
	Without them, I wouldn't be releasing this. :)

	Myles Bunbury.  Mr.IdeaMan, Mr. Bug Finder, Mr. Beta Tester,
	Mr. Pain in the Butt.  Without Myles, I probably would have
	put ISA on a shelf.

        NOTE:  If anyone knows the where-abouts of Myles Bunbury, please contact me
               with his email address!  i've lost contact with him!!!

	My wife and kids.  It's hard to find time to balance family,
	work and coding.  Family comes first, thus explaining the
	time between when I obtained the rights to ISA and the release
	of 0.993, then the time between 0.993 and 0.993a.

	ͻ
	۲ Registration ۺ
	ͼ

	There is no obligation on your part to register ISA, ISA
        is in no way crippled.  In fact, ISA is now freeware!  Run the included
        ISAREG.EXE to generator your RegNum!

	ͻ
	۲ Contacting The Author ۺ
	ͼ

   If for some strange reason, you're having difficulties with ISA, or
   if you just wish to drop off some comments, feel free to contact the
   Author or another ISA Staff member. Below is a list of people and
   where they can be reached:

Author - Andy Stewart
~~~~~~~~~~~~~~~~~~~~~
	Internet - astewart@taynik.com

	Subjects: Tech. Support, Reg. Info, "Pats on the back", etc.

Lead Beta Tester/Game Designer - Myles Bunbury
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	InterNet - lbunbury@cyberplus.ca
	FidoNet Netmail - 1:163/114
	FidoNet Echomail - DOORGAMES, BBSDOOR, BBSDOORS, ON_LINE_GAMES,
			   DOORWARE
	SCIFI Netmail - 42:42/101
	InTraTec Netmail - 191:2000/100
	TATTLE Netmail - 86:100/3
	TCN Netmail - 201:935/104

        Myles can be reached in the Sysop and InterBBS Echoes of the above
        four Echomail networks as well.

	Myles' Games Extravaganza (BBS) - (613) 234-0975

	Subjects: Game design, Bugs, Suggestions, etc.

 ** Note **
   Feel free to contact any staff member about any topic. The subjects
   listed are merely their "specialty", and thus are more likely to be
   able to help you.  Also, remember, if you have a problem, TELL US!
   Giving us a pat on the back and saying "Great job!" may give us a
   warm fuzzy, but a good dose of constructive criticism will allow us
   to improve our game so that later, there could be potentially 10 warm
   fuzzies coming to us because of the improvements!

 -- End --

