home *** CD-ROM | disk | FTP | other *** search
- The Funky Jewel Master Version 1.00 -- Program & Design by Joe Clarke
- Copyright (C) 1996
-
-
- 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 FunkySoft. FunkySoft 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 FunkySoft.
-
- 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 FunkySoft beyond the cost of distributing
- unregistered copies without prior expressly written permission from
- FunkySoft.
-
- A major portion of this software comes from the DDPlus Door Driver
- Package and was written by the authors of that package. The DDPlus
- Doordriver kit has been used for the communications, interrupt
- handling and some utility functions and that part of the software
- remains copyrighted by the authors of the DDplus Package.
-
- 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:
- ------------
-
- This is a cool game kinda of like columns for sega.
- you match up the jewels to break lines to get points:)
-
-
-
- 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.
-
-
- --> NOTE: The word "JEWEL" is used in place of the program name
- for both the executable file (example JEWEL.EXE), and the CTL
- file (Example JEWEL.CTL) in the documentation from this
- point on. JEWELDIR is used in place of the program directory
- in the documentation from this point on.
-
- 1. Create a directory for the JEWEL:
- example: "WC30\DOORS\JEWELDIR"
-
- 2. Make sure that ALL files listed above from the JEWEL package
- are moved into that directory.
-
- 3. Type "DDSETUP.EXE" and hit the enter key. The first thing it
- will ask you is what the name of the CTL file is. Type in
- "JEWEL.CTL" and then proceed to the other settings. After
- you are done the JEWEL.CTL file should be correctly configured.
- Two versions of a fully commented CTL file are provided for
- manual configuration. One is identified by the JEWEL title
- (example: JEWEL.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. A CTL file generated by DDSETUP.EXE will have NO comments
- and look quite different from my samples, but they WILL work
- just as well, never fear.
-
- Where to put this file?
- Put this file wherever you are running the JEWEL 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 JEWEL directory put the file here. See the example
- SAMPLE#.bat files.
-
-
- 4. To insure proper multi-node use DOS SHARE must be loaded
- prior to the JEWEL and prior to DESQview.
-
- 5. In order to run the JEWEL program online the following
- parameters may be used.
-
- "/Bxxxxx" This tells JEWEL.EXE to lock its baud rate at
- xxxxx. In order to get the most efficiency out of a high speed
- error correcting modem (9600 baud or above), you may lock the baud
- rate to a speed higher than what the caller is actually using.
- By locking the baud to say 38,400, the modem can compress text data
- that is being sent and achieve a baud rate much higher than the
- actual transmission rate.
- 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 JEWEL.CTL file.
-
- "/Cx" (where x is 1..4) This specifies a comport number.
- Some bbs software does not create door information files (dropfiles)
- that contain the comport number. If your bbs does have a comport
- listed in the dropfile then there is no need for this parameter.
- The default is comport 0, local mode.
-
- "/E" - Expanded Memory Specification If your machine has over one
- megabyte of memory, then you may have some available. JEWEL.EXE can
- utilize EMS to improve JEWEL performance and reduce conventional
- memory requirements.
- This command will tell JEWEL.EXE to use EMS memory to hold its
- overlay buffer. Otherwise disc area may be used to hold this buffer.
- This needs a memory manager and when enabled and is compatible with
- DESQview. Default is NOT to use available EMS.
-
- "/F" This is a generic maintenance mode. It logs
- into the JEWEL with the name "SYSTEM MAINTENANCE" in local mode.
-
- "/H" This is a generic maintenance mode. It logs
- into the JEWEL with the name "SYSTEM MAINTENANCE" in local mode.
-
- "/L" This tells JEWEL.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.
-
- "/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 JEWEL.EXE would use
- DORINFO2.DEF.
-
- "/Mx" (where x is up to 2 filename acceptable characters)
- Used to specify one of Multiple control files. If you have created
- more than one JEWEL.CTL file (JEWEL1.CTL, JEWEL2.CTL, etc.) for each
- node or network PC then you can select the one you want by using
- the /M parm.
- Example: "/M2" will force JEWEL.EXE to use JEWEL2.ctl.
-
- "/Pyyy" This specifies the path to the drop files.
- For example, "/PC:\WILDCAT\WCWORK\NODE1" would tell JEWEL.EXE to
- look for the drop file in C:\WILDCAT\WCWORK\NODE1. If this is left
- out the program assumes the drop file is local.
-
- "/R" To force local RIP for the sysop. Used only if the program
- has RipLink built in and the door supports RIP. Use AFTER the
- /L parameter if you are using the door in local mode.
-
- "/V" This command will tell JEWEL.EXE not to show any display
- on the local screen. Only a colored screen and a message will be
- displayed. The cursor will not move as it will be turned off.
- Saves a little processing on multi-tasking systems.
-
- "/W" This flags the program that a network is present even
- though no multitaskers are detected. This is useful if the door is
- run on a network such as Novell that doesn't use multitaskers.
-
-
- COMMON ERRORS
- 003 File path not found. Check to make sure the JEWEL
- directory is correctly named as JEWELDIR.
- 201 Files not found. Check to make sure that all required
- JEWELs files are in the JEWELDIR directory.
-
- 6. 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 JEWELDIR directory and run JEWEL.EXE -
- Thats all there is to it! Three different batch files sample
- are included to help you run the JEWEL. These are included with
- the JEWEL for editing and your use. Remember when writing the
- batch routines for my JEWELs you must ensure that the JEWEL is
- run from it's home directory AND that the JEWEL knows where to
- find the drop file. Satisfy these two requirements and you
- should have no problems running the JEWEL as long as the other
- setup criteria has been met. For dorinfo systems try using the
- following:
-
- Sample Batch File
- -----------------
-
- COPY DORINFOx.DEF \RBBS\DOORS\JEWELDIR\*.*
- CD \RBBS\DOORS\JEWELDIR
- JEWEL 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...
-
-
-
-
- RESTRICTIONS ON THE UNREGISTERED JEWEL
- -------------------------------------
- Until the JEWEL is registered the following restrictions are
- in effect:
-
- a. You Only Get 1 Turn...in the registered you get 10
-
- b. you only ger 1 live.. in the registered you get 3 per turn.
-
- 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 gamess - 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.
-
-
- 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 a game with a locked
- baud rate:
-
- a. When using a locked baud rate, I highly recommend
- using a FOSSIL driver. This JEWEL 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 JEWEL.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 JEWEL.exe to use that.
-
- Several converter programs are readily available
- on most BBS systems. CallDoor is a good one if you
- can find it. I have it on my BBS for download if
- you need 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 JEWEL.ctl file. To correct this make
- sure the right port is shown in the dropfile OR
- JEWEL.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
- JEWEL.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.
-
-
- CREDITS:
-
- 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.
- I also habitually monitor ALL door related echos in the FIDO
- Net System.
-
-
- Registration
- ------------
- If you or your users enjoy this game, then please register it.
- Information on price and how to register is shown on the
- enclosed REGISTER.FRM. Registration will disable the delay,
- allow additional options 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 to:
-
- Joe Clarke
- 6738 Evergreen Rd
- Hudson, OH 44236
-
-
- HOW TO REACH ME BY MODEM
- ---------------------------
-
- The Game World BBS (USA)
- (216) 342-0216 (at&t - 2400 to 28800 baud)
- Fidonet 1:2215/283
- Internet jclar59@mail.idt.net
-