=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The Rose
Council of Guardians
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Presented by

Runtime Computing
A division of Metropolis, Inc.

8650 College Blvd
Overland Park, KS 66210
(913) 663 - 9545 Voice
(913) 451 - 3690 Fax
mailto://info@rcomputing.com
http://www.rcomputing.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Warren D. Johnson
Sr. Programmer
warrenj@rcomputing.com
-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Last updated August 25, 1998


	
	Welcome to the realms of Corinthia!  After many years of strife the six races have 
settled their differences and now enjoy a time of great prosperity and happiness.  To insure 
the continued peace and stability of the realms, it has come to pass that a Council of 
Guardians shall watch over the land, protecting it and ensuring it's continued prosperity 
and growth.  Your goal as a young adventurer is to prove yourself worthy of membership 
in The Council of Guardians.  
	The game you are about to play is medieval fantasy role playing in the tradition of  
paper and dice oriented role playing games such as Advanced Dungeons and 
Dragons(TM) and White Wolf(TM).  In these games, the output of events and actions 
which you perform is governed through the roll of the dice.  The Rose works much in the 
same manner except the calculations are computer based.  You create a character based 
on what you feel will help you survive and prosper in this magical and dangerous realm.  
Each character has varying levels of proficiency in different areas of life.  Some players are 
stronger fighters, while others are more intelligent.  While your character develops 
experience you are given the chance to increase your level of proficiency in many different 
arts, thus shaping your alter-ego to your will.

	 In Corinthia there exist six races: the elves, the humans, the dwarves, the fairfolk 
(much akin to Leprechauns), the giants and the gnomes.  Each race has varying levels of 
physical and mental quality.  For example while the giants are stronger than the gnomes, 
the gnomes are much more dexterous than the giants.  There are six walks of life or 
professions that your character may hail from: warrior, scholar, gypsy, priest, mage and 
archtypical.  Each of these walks of life has it's strengths and weaknesses.  For example, 
the mage may cast spells from the sphere of force more aptly than they will wield a 
longsword in combat.  Unlike many role playing systems, where your character class or 
walk of life forces you to use only certain abilities (for example, warriors may only engage 
in combat and may not cast spells), The Rose allows you to train any proficiency you wish 
to train.  There is of course a catch.  Certain walks of life will learn certain proficiencies 
faster and more economically than others.  For example, the warrior will learn the "melee 
combat" proficiency faster and cheaper than he will learn the "Sphere of Life" proficiency.  
Improving your proficiencies is essential to survival and gameplay.  To train a proficiency 
you will spend some "development" points but first must find the proper place to learn.


	





Contents


Beginnings - 1	4
Welcome - 1a	4
Installation - 1b	  5
Your activation code file - 1c	5
Offline configuration - 1d	5
General Compatibility issues - 1e	5
Memory, speed and stability considerations - 1f	6
Sysop menu - 2	7
Configuring game settings - 2a	7
Setting midnight clean-up routines - 2b	9
Event logging - 2c	9
Configuring access keys and locks - 2d	10
Runtime Sysop commands - 3	12
Level one Sysop commands - 3a	12
Level two Sysop commands - 3b	12
Level three Sysop commands - 3c	13
Troubleshooting and commonly asked questions - 4	15
Obtaining technical support and reporting buglets - 5	16
RoseNet Considerations - 6	17
Purchase Information - 7	18
License and usage agreement - 8	20



Section 1 - Welcome

1a. Welcome

Salutations and welcome to the Realms of Corinthia!

We will begin the documentation with a short explanation of the installation procedure and 
the initial offline configuration options.  From there we will move on to an extensive 
explanation of the Sysop menu (including game settings, event logging, and access keys 
and locks) and in game Sysop commands and afterwards discuss memory, speed and 
stability considerations.  The section following will be troubleshooting and RoseNet 
information and we will conclude the documentation with a brief discussion on obtaining 
technical support and reporting bugs.

If you're not interested in doing much reading you may burn this set of docs (or just close 
the file) after reading the installation, offline configuration and compatability consideration 
sections (which contain information pertinent to getting the game to run) and just boot the 
game up as the default configuration is sufficient for most systems. 

I'd like to take this time to thank you for your purchase and to wish your users good luck 
in their adventures.

Sincerely,

Warren D. Johnsson 
Sr. Programmer
Runtime Computing
warrenj@rcomputing.com

1b. Installation

Note: One version of The Rose exists which supports MajorBBS v6.25, Worldgroup 
v1.01 and Worldgroup v2.0.  As of the writing of this documentation, The Rose is not 
compatible with Worldgroup v3.0 for DOS or Worldgroup v3.0 for NT.

By this point, you should already have an uninstalled, compressed (zipped) copy of The 
rcomputingRose.  The file name is likely rciros20.zip or something similar.  Unzip the file 
to an empty temp directory on your hard disk and execute the "install.exe" program.  The 
install program will prompt you for the source directory (this is the temp directory) and 
the destination directory.  The destination directory is the directory which houses your 
Galacticomm software (for example, c:\bbsv6 or c:\wgserv).  Once you've specified the 
directories press the enter key and the install program will unzip and copy files into the 
destination directory.  After copying is complete, the install program will invoke some 
miscellaneous Galacticomm programs and will compile some .msg files (message files).  
The install program will then terminate.

1c. Your activation code

In order for your module to run unrestricted (assuming you have purchased the product) 
you must enter your activation code in CNF Level 4 option ACTCODE.  Without this 
code your users will only be allowed to play their characters until level 5.  Operating The 
Rose in demo mode does not require an activation code.

1d. Offline configuration

In an attempt to follow the *NO MSG* standard, there is only ONE offline configuration 
option for you to configure: CNF Level 4 option ACTCODE as discussed above.

1e. General compatibility issues

To the best of our knowledge The Rose will co-exist harmoniously with all other modules 
in existence.  However, we know of two modules for which you must make considerations 
when running them with The Rose:

System Sentinel from Annex.com: If you are running System Sentinel you must configure 
it to ignore The Rose.  This is accomplished by entering level 99 of the offline 
configuration (type CNF -L99 at the DOS prompt) and setting RCIROSE as a .DLL to be 
excluded from memory tracking.  For more information please contact Greg Gooden at 
Annex.com (818) 779 - 5646.

FU Globals from Dialsoft:  If you are running FU Globals you must configure your 
module to prevent users from entering into the telegram system's full screen editor while 
they are in The Rose.  For more information please contact Marc Frega at Dialsoft (201) 
586 - 1550.

1f - Memory, disk space, speed and stability 
considerations

Memory: The Rose was designed from the ground up to be memory efficient.  The driving 
force behind the module, rcirose.dll, is approximately 970k. The internal caches in the 
game requires approximately 1.2 megabytes of space to load in it's entirety (and load it in 
it's entirety you must, there is no configuration for the cache at the moment).  In addition, 
there are other incidental memory requirements such as players coming into the game.  If 
you resign yourself to setting aside 3 megabytes of memory for The Rose you will do well.  
We store all room, item, monster and spell  descriptions on hard disk.

Hard disk space: The Rose requires approximately twenty five megs of free hard disk 
space to operate safely.

Speed: The Rose was alpha tested on an AMD 5x86 with 16 megs of RAM, a 1 gigabyte 
Seagate Hard drive and 4 megs of read-only cache.  With 5 players in the game, and 700 
monsters in the realm we managed to keep our response time down to approximately <1 
ms.  The response time will fluctuate during periods when The Rose is performing it's 
incremental back-ups (that is explained later on in detail).

Stability issues: We have done everything in our power to insure that The Rose is stable 
and market worthy.  However, nothing ever works perfectly.  To insure the stability of 
your game data files, The Rose will backup it's data files at certain intervals.  These 
concepts are explained at length in the sections to follow.  See the section entitled 
"Obtaining technical support and reporting buglets" towards the end of the 
documentation.

Section 2 - The Online Sysop menu

The Rose follows the *NO MSG* standard and allows you to configure the entire game 
while online.  All users with the Sysop or Master key will be allowed access to the "s" 
selection on The Rose's main menu.  The Sysop menu is divided into four sections: 
Configure game settings, set auto-cleanup actions, event logging, and configure access 
keys and locks.  Each of these options is explained in full.

2a - Configure game settings

Player vs. player level setting: This configures the maximum level difference between two 
combatants before The Rose will inform them that they are not compatible for player vs 
player combat.  Setting this option to 0 will disable player vs player melee and player vs. 
player ranged combat. 

Gossip channel enabled: The Rose maintains a global gossip channel within the game 
which all players are attuned to unless they specify otherwise.  Here you may toggle the 
actual availability of the gossip channel.

Time between backups: The Rose will periodically backup it's data files to insure that it 
has a secure set of files to work from in the event of a system crash.  This setting dictates 
the minimum amount of time that must elapse before The Rose will attempt to backup its 
files.  Note that we specify minimum because The Rose must make sure that all its buffers 
and internal caches are empty before proceeding with a backup.  If your system crashes 
your players will lose an amount of game time equivalent to approximately (backup 
time)/2 + (backup time).  We recommend a setting of 15 minutes.  

Astral channels enabled: The Rose maintains a range of chatter channels within the game 
(frequencies range from 0 to 30000) known as Astral Channels.  Here you may toggle the 
actual availability of these channels.

Starting stats adjustment: All players begin with a statistic of 20 in each of their bodily and 
mental attributes after which these numbers are randomized slightly based on walk of life 
and character race.  Here you may configure whether your users start with slightly higher 
or slightly lower stats.  We recommend a setting of 20.

Compile highs at backup: The Rose maintains information known as "The Halls of 
Achievement and Disgrace" which chronicle the realms mightiest adventurers.  These high 
scores are normally compiled at system boot.  If you'd like to compile them after each 
incremental backup (see Time between backups) please toggle this to YES.  It is possible 
that this may lag your system for upwards of two or three seconds once you've acquired a 
large base of players.  

Starting hit points adjustment: Increasing this setting will allow your users' characters to 
begin with more hitpoints thus making them slightly more durable at lower levels.  This 
adjustment only applies to starting hitpoints.  We recommend setting this to 0.

Idle base setting:  This option is not currently used.

Starting gold adjustment: Here we define the amount of gold that a player begins with in 
the game. Giving players too much gold is liable to unbalance the game but giving the 
players too little gold will make gameplay overly difficult. We suggest setting this to a 
number in the range of 75-150.

Show log on message: Here you may ENABLE or DISABLE the printing of the log-on 
message at log-on.

Starting silver adjustment: Here we define the amount of silver that a player begins with in 
the game.  Since 1 singular gold piece is equal to 100 silver pieces, this setting is used 
mostly for cosmetics.  We recommend setting this to a number in the 250 - 500 range.

Astral character: You may configure the character required to initiate a message on the 
astral channels.  *Use one character only*

Monster hit dice adjustment:  Here you may increase or decrease the starting hitpoints of 
the monsters in the realms.  We recommend setting this to 0.

Gossip character:  You may configure the character required to initiate a message on the 
gossip channel.  *Use one character only*

Monster attack dice adjustment: Here you may increase or decrease the relative accuracy 
of monster attacks.  We recommend setting this to 0.

Whisper character: You may configure the character required to send a global whisper to 
someone in the game.  *Use one character only*

Player attack strength:  By increasing this setting you will make your players more 
effective combatants.  We recommend setting this to 0.

Directed character: You may configure the character required to send a directed message 
(such as >Sysop hi!) to someone in your room. *Use one character only*

Monster attack strength: Here you may increase the relative strength of successful 
monster attacks.  We recommend setting this to 0.

Surcharge: If you wish to charge your credit based classes additional credits to play The 
Rose you may define the amount here.  This number is the amount of credits deducted per 
minute in addition to their normal consumption. 

Definition of time unit part 1,2,3,4:  Each attack or spell casting in the game is followed 
by a slight action or attack delay.  These delays are measured in time units.  One real 
second is equal to approximately 65,535 cycles.   The sum total of all four of these 
settings is the actual definition of a time unit.  If you wish to speed the time units up you 
may alter these to equal any number but we recommend leaving it set at 16,300 for each.

Max Monsters:  This setting dictates the maximum number of monsters that may exist in 
the realms at any given time (except for those summoned to arena's of combat).  We 
recommend setting this to 2000.  The more monsters you have, the more memory that will 
be used. 

2b - Setting midnight clean-up routines

There is two configurable options that pertain to events which transpire during the 
automated cleanup. 

User's deleted from BBS, delete their Rose character too?  You may wish to have users's 
Rose characters remain in the Rose database even if their User-Id is deleted from the 
system.  Select YES here if you wish them to remain and not be deleted.

Extended cleanup logging:  If you are experiencing lockups during cleanup (you shouldn't 
be, but if you do) enable extended logging to track the events during The Rose's midnight 
cleanup.  A series of "checkpoints" are recorded to the file "rcirose.log" during cleanup if 
this option is set to YES.  In every SysOps life the inevitable "lock-up during cleanup" 
turns up.  You would use this setting to prove that it's not The Rose doing it.

Purge limited items: If set to YES, The Rose will recycle the limited items from all dead or 
inactive players who have not played within the last 45 days.  It will then toggle the data 
file recovery flag to on for the bootup subsequent to cleanup and set this option to NO.  
This purge will take a few minutes during your cleanup hour.

2c - Event logging

The Rose maintains a permanent log file in your BBS directory named rcirose.log.  There 
are several events which you may monitor during game play by logging their occurrence to 
this file.  None of these are mandatory and each of them that is set to YES will incur a 
very slight performance hit due to disk access.

Log user deaths: Make an entry in the rcirose.log file each time a person dies. 

Log player vs. player combat: Each time a player strikes another player in the game with a 
player vs. player spell or a melee or ranged attack it will be logged to the rcirose.log file.

Log each random stocking: Make an entry in the rcirose.log file each time we randomly 
populate the world with monsters.

Log each incremental backup: Make an entry each time the system successfully completes 
an incremental backup.

Log all user input: Set to YES, the system will log every single thing a user types while in 
The Rose.  Due to the disk activity this generates, we suggest setting this to NO.
 
Log each entry to Sysop menu: A safety precaution you may wish to use.  This will log the 
handle of a user each time she enters the Sysop menu.

Participate in RoseNet: RoseNet is an advanced feature of The Rose and requires internet 
e-mail facilities on your BBS.  Please see section 6 concerning the RoseNet features.

2d - Configuring access keys and locks

There are eleven locks in The Rose which you may define keys for.

First player character key: The Rose has the capability to allow multiple characters per 
user-id.  The module comes stock with the ability for each of your users to have two 
characters in the game. An add-on is available to extend this limit to five characters.  This 
is the key required to use the first character.  The default setting is "normal".

Second player character key: This is the key required to use the second character.
The default setting is "normal".

Third player character key: This is the key required to use the third character. The default 
setting is "normal".

Fourth player character key: This is the key required to use the fourth character. The 
default setting is "normal".

Fifth player character key: This is the key required to use the fifth character. The default 
setting is "normal".

Feedback mailer key: Not currently implemented.

Rose moderator key 1: The Rose has several Sysop/Moderator commands within the 
game.  These commands are divided into three levels.  Each of these levels is explained in 
detail in Section 3 - Sysop commands.  This key is required to access the first level of 
Sysop commands (which are the most powerful ones).  The default setting is "rosemod".

Rose moderator key 2: This key is required to access the second level of Sysop 
commands. The default setting is "rosemod".

Rose moderator key 3:  This key is required to access the third level of Sysop commands.  
The default setting is "rosemod".

Global gossip key: This key is required to access the global gossip channel within The 
Rose.  The default setting is "normal".

Astral channel key: This key is required to access the astral chatter channels within The 
Rose.  The default setting is "normal".

Annoying user key: Any user who is annoying you in any way shape or form can be 
tormented right back by being given this key.  Users with this key will experience an 
occasional cloud of black karma (giving them an additional 60 seconds to their action 
timer) settling upon them and will also notice that all monsters strike with double the 
ferocity of normal (but only on them).

Exclusion key: If you wish to revoke access to The Rose from a user simply add this key 
to their personal key ring and they will no longer be able to get into the game.  The 
"Sysop" account and MASTER key holders are exempt from this setting.




Section 3 - Runtime Sysop commands

The Rose maintains approximately 24 Sysop commands within the runtime environment.  
These Sysop commands are divided into three levels and each level is accessible only to 
those holding the key designated for that level as defined in "Configure access keys and 
locks" in the Sysop menu. 

3a - Level one Sysop commands

lastpid - This will give you the ID number of the last item in the game's internal caches.
Syntax - lastpid

addlives - This command adds one life to a selected user.
Syntax - addlives [user]

systalk - This command will allow you to speak to the entire realm, regardless of gossip or 
whisper settings.
Syntax - systalk [message]

tourney - This will turn on tourney mode.  During tournament mode, players who die will 
not lose items, stats, experience or lives. 
Syntax - tourney

version - Issuing this command will reveal the version number embedded into the data 
files.
Syntax - version

monstercount - This command will reveal the number of monsters living in the realm.
Syntax - monstercount


3b - Level two Sysop commands

teleport - This command may be used to transport yourself to any room in the game.  You 
must specify a room number for example, "teleport 324" will take you to room 324.  
Syntax - teleport [room number]  NOTE: This command is not yet active.

summon - This command may be used to summon a player currently in the game to your 
room; for example, "summon warren".
Syntax - summon [player]

sysmove - This command may be used to remotely move a player currently in the game to 
a new room; for example, "sysmove warren 20" will teleport Warren to room 20.
Syntax - sysmove [player] [destination room]  NOTE: This command is not yet active.

locate - This command will reveal a player's room location within the game provided they 
are currently in the realms.
Syntax - locate [player]

sysarmor - This command will reveal the target's inventory and armor configuration.
Syntax - sysarmor [player name]

hismods - This command will list all of the "data objects" that are connected to the target 
you specify (for example, hismods warren).  We do not explain this command any further 
as it has no real effect on game play and is used purely on a technical support basis should 
the need arise.
Syntax - hismods [player]

sysbook - This command will reveal the spellbook of its target.
Syntax - sysbook [player]

sysskills - This command will reveal the skill levels of its target.
Syntax - sysskills [player]

hisquests - This command will reveal which quests a player has completed.
Syntax - hisquests [player]

godslap - This command may be issued to any player in the game and will cause them 
bodily harm and timer additions.  This command is anonymous and the player will only see 
that an evil spirit appears and slaps them.
Syntax - godslap [player]

smite - This command may be issued to any player in the game and will cause them bodily 
harm.  This is the non-anonymous version of godslap.
Syntax - smite [player]

3c - Level three Sysop commands

healme - This command will restore the issuer's hitpoints to maximum.
Syntax - healme

maname - This command will restore the issuer's manapoints to maximum.
Syntax - maname

feedme - This command will refill your food/water timers to maximum.
Syntax - feedme

scanastral - This command will indicate which astral channel each player is on.
Syntax - scanastral

syspardon - Issuing this command upon another will pardon them of all criminal activities. 
Syntax - syspardon [player]

hideme - Issuing this command will hide the player so well that he is not perceivable by 
anyone.
Syntax - hideme

syscure - This command will purge all poison and disease from the body of the recipient.
Syntax - syscure [player]


Section 4 - Troubleshooting and commonly 
asked questions

Q1: I received an error message "The Rose - Council of Guardians - Error message 101" 
followed by a board catastro.  What is the deal with this?
A1: This error message occurs when The Rose is unable to open a file (not including 
btrieve files because they have their own internal error handlers) which it needs to read for 
the purpose of copying or backing up.  This error might also occur in the event that your 
system runs out of available file handles or you are running a btrieve network and the 
permission for the files is set incorrectly.
Possible solution 1: Edit the line "Files=xxx" in your config.sys adding a higher number to 
your files count.
Possible solution 2: For btrieve network users make sure that the files for The Rose were 
created under the BBS user's login name.
If you encounter this problem, please contact Runtime Computing.

Q2: The response time on my system periodically jumps to well over a few hundred 
milliseconds.  What causes this?
A2: Every so often (depending on your Sysop configuration) The Rose will backup it's 
data files.  This backup routine is regulated by the loading of the system but will still lag 
the system slightly for the duration of the backup.
Possible solution: There is currently no way to avoid this slight response time hit except to 
spread your backups out further.  We do not recommend having your backups spread any 
farther than 30 minutes apart.

Q3: It seems that the gameplay response time in The Rose is lagging.  How may I fix this?
A3: See QA 2.

Q4: My users have been playing for years fanatically and I want to reset the game.  How 
can I do so?
A4: Resetting Rose is a bit involved.  We recommend you contact us before trying it.

Q5: I'm having trouble getting my system hooked up to RoseNet through my DMA 
server.  Any suggestions?
A5: Typically, inability to send email through a DMA server can be fixed through 
configuration.  You must enable SMTP email on your DMA server and if you are using 
the TCPSITES.BAN file you must include your DNS server IP the TCPSITES.BAN file. 

Q6: How do I reroll an annoying user in my game?
A6: Catch the user in the game and smite him to death.  SMITE is a sysop command=).

Section 5 - Obtaining technical support and 
reporting buglets

Technical support or bug reports may be requested or sent via:

Telephone: +1 (913) 663 - 9545   
Fax:    	      +1 (913) 451 - 3690
Internet email: info@rcomputing.com

Section 6 - RoseNet Considerations

One of the most exciting features of The Rose is RoseNet.  RoseNet tracks the high score 
list and important gameplay information from each Online System which wishes to 
participate.  These high scores and important gameplay information are sorted against 
other systems and placed on display for all to see at http://www.rosecog.com in the 
RoseNet section of the page.  The only requirement for particpation is that you have 
internet email enabled on the machine which The Rose operates on.  Participation is 
optional and may be disabled in the Event Logging section of the SysOp menu.

Global high score list - Each system up, The Rose compiles the high score list from the 
assumed and non-assumed characters and dispatches it to our central RoseNet server.  
Each high score list is then compiled and sorted with the other high score lists from 
around the world.  In this fashion, players may see how they compare when ranked against 
the other players of the world.

Global event tracking - Each time something exciting happens in your copy of The Rose, 
such as a player assuming a class or defeating a boss monster, the event is dispatched to 
our central RoseNet server.  Once accepted by the RoseNet server, it is added to the list 
of exciting events.

Section 7 - Purchasing information

As of this writing, The Rose - Council of Guardians is compatible with MajorBBS 6.25, 
Worldgroup 1.x and Worldgroup 2.0.  The Rose is sold in license counts and upgrades to 
higher license counts requires you to pay the difference of the higher price and lower 
price.  The following options are available:

  04 User License - $199.00
  16 User License - $399.00
256 User License - $599.00

Currently, The Rose comes stock with the ability for each User-ID to have 2 characters in 
the game.  However, for an additional $99.00 you may extend that limit to 5 characters 
per User-Id.

All prices are in US dollars.

Ways to purchase The Rose

1. A secure online ordering service is available at http://www.gameport.com.  You will 
require a major credit card (Visa, Mastercard, American Express or Discover) to use 
this service and will receive your activation code within minutes as well as an emailed 
receipt of the transaction.  More complete information is available on the web site.  
Please utilize this method if possible as it is the simplest and fastest.

2. You may purchase The Rose by calling Metropolis Gameport at +1 (913) 663 - 9595, 
Monday through Friday 8am to 5pm Central Standard Time.  We accept Visa, 
Mastercard, American Express and Discover over the telephone and will generate you 
an activation code during the phone call.

3. You may fax your order to +1 (913) 663 - 3200.  Please include your full name, postal 
address, telephone number, BBS Name, BBS registration code (without the 
registration code, we cannot create an activation code for you) and email address.  
Also, please specify which user license you are purchasing and if you are purchasing 
the extension which allows all 5 characters in gameplay please specify such.  Specify 
Visa, Mastercard, American Express or Discover and your credit card number and 
expiration date.  

4. Rather than faxing, you may mail the information specified in option number 3 to:

Runtime Computing c/o Metropolis, Inc.
8650 College Blvd
Overland Park, KS 66210

You may also e-mail this information to info@gameport.com or 
info@rcomputing.com

5 - You may purchase The Rose by check.  Please make your check payable to:

Metropolis, Inc.
8650 College Blvd
Overland Park, KS 66210

Please include your full name, postal address, telephone number, BBS Name, BBS 
registration code (without the registration code, we cannot create an activation 
code for you) and email address.  Also, please specify which user license you are 
purchasing and if you are purchasing the extension which allows all 5 characters in 
gameplay please specify such.



Section 8 - License and usage agreement

The Rose - Council of Guardians
Version 2.0
                                       
Copyright 1998
Runtime Computing
A division of Metropolis, Inc.
All Rights Reserved


1.	GRANT OF LICENSE.  This License Agreement ("License") permits you  to use  one  copy  of  the 
specified version of the  product  identified above, which may include user documentation provided in 
"on-line"  or electronic form ("SOFTWARE").  The software is licensed as  a  single product to be 
operated on a single machine.  Its component parts  may not  be  separated for use on more than one 
computer or by more  than one BBS at any time.  Once licensed, the license to use this software is  
NOT TRANSFERABLE to any other person or corporation, without  the express, written permission 
of an officer of Runtime Computing.
2.	COPYRIGHT.   The SOFTWARE (including any images and text incorporated into  the  
SOFTWARE)  is  owned  by  Runtime   Computing  and      is protected  by  United States copyright 
laws and international  treaty provisions.   Therefore, you must treat the SOFTWARE like  any  other 
copyrighted  material (e.g. a book or musical recording) except  that you may either (a) make one 
copy of the SOFTWARE solely for backup or archival purposes, or (b) transfer the SOFTWARE to a 
single hard disk provided  you  keep  the  original  solely  for  backup  or  archival purposes.   You  
may not copy the printed materials accompanying  the SOFTWARE, nor print copies of any user 
documentation provided in "on-line", electronic form or paper form.
3.	LIMITED  WARRANTY.  This documentation and any related  software  are sold  "as-is",  without  
any warranty either  expressed  or  implied, including,   but   not   limited  to,  the  implied   
warranties   of merchantability,  fitness  for  a particular  purpose,  and  loss  of profits or other 
economic damages.  Runtime Computing does not warrant that the operation of this software will be 
uninterrupted  or error-free.  In  no  event  and under no  circumstances  will Runtime Computing  be 
liable  for any damages  in  excess  of  the  sum paid  by  customer  for the product to which any  
claim  for  damages relates.
4.	SHARED-DMA ACCESS USAGE POLICY. Except as advised via written, dated confirmation the 
user may not operate this software on a  DMA server which provides access to more than one 
incoming I.P..
5.	REFUND POLICY.  For the thirty (30) day period following the date  of sale,  Runtime  Computing,  
warrants  to the  customer  that  the product  shall operate in a manner satisfactory to the customer.   
As the   customer's  sole  remedy  under  this  refund  policy,  Runtime Computing shall refund to  
the customer the  purchase price of any  product the customer returns to Runtime Computing within 
the thirty (30) day period, provided the product has not been damaged  by  the  customer, all original 
packaging and documentation, together  with  the  original  sales  receipt and a written  request  for  
said refund, is returned to Runtime Computing.

YOU  MAY NOT USE, COPY, MODIFY, MERGE, DISASSEMBLE, OR TRANSFER  THIS 
SOFTWARE,  IN WHOLE OR IN PART, EXCEPT AS EXPRESSLY PROVIDED  FOR  IN THIS 
LICENSE.  Violation of any parameter of this license will result in the immediate forfeiture of said license 
with no compensation.


2

