       YOUR EXCLUSIVE PARA-Site codes are as follows:

    		DISK ID		- DEMO6
   		SERIAL #	- Y2PSTS5IP005
		PASSWORD	- CANDY
		KKEY$		- PSTEST

OVERVIEW:

PARA-Site is a PARADOX add-in utility that acts as a security "gateway" to a PARADOX application. Testing is done on three levels for authorized access:

     1) Licensed start date/end date window

     2) Host P.C. Rom Bios identification number

     3) Host P.C. Key file(s) sector number


     If any one of the three tests fail, PARA-Site halts the execution of the application and, if applicable, allows for correction of the problem or intervention of the system administrator or application author. PARA-Site will halt application execution in the following cases:

     1) The application has been moved from it's original P.C. to  another  P.C.

     2) The application has been relocated to another directory on the same  P.C.

     3) An attempt is made to run the application outside of the pre-set  start date/end date window.
-------------------------------------------------------------------------

PROCEEDURAL STEPS:

1)  Install the following files from your KEY disk, to the application directory

	INITIAL.SC  LICENSER.SC  PARASITE.SC  FIRST.SC  PS.LIB
	ATTR.COM  SECURITY.DB   SECURITY.F1  PARASITE.LTT
                PARASITE.LOT  YOURSCP.SC 

(NOTE: Install PARA-Site in the same directory as your application and associated files)

2)   Begin PARADOX and follow next set of instructions.

3)   From within PARADOX, run the file LICENSER.SC.
     Fill out the appropriate information on the SET-UP / CHANGE  screen.
     (NOTE: the LAUNCH SCRIPT name must be a valid script in current directory)
   (YOURSCP.SC is supplied as a means of testing your installation only)

4)   Edit your LAUNCH SCRIPT to include your KKEY$ variable.(see ABOUT YOUR  LAUNCH SCRIPT)

5)   Begin your application by running INITIAL.SC from PARADOX.
--------------------------------------------------------------------
















































              --- Elements of the Security Setup/Change Screen ---

Auto Install : (OPTIONAL)
     In some cases, PARA-Site will have to be sent (with the application) to a third party as part of a package. It may be desireable to afford the user the privledge of installing the software (and PARA-Site) on a first-time basis, without the usual telephone  coordination  involved in a standard license update session.
    If this is your desire, check this option. (any character here will be considered a check)
    With this option checked, PARA-Site will automatically license the application for a temporary one-time term of "n" days. "n" is determined by the number placed in the field TERM/DAYS. If the AUTO INSTALL field is left blank the TERM/DAYS field will be made blank by default.

NOTE: If AUTO INSTALL is used, there is no need to place dates in the START/END date fields as they are automatically filled in upon the initial running of the program. START date becomes the present "system" date and END date becomes a date "n" days after START date.   

Term/Days: (OPTIONAL)
      This field is used only if the field AUTO INSTALL is checked. Place the number of days desired for the initial auto-installation license term. 

Client Name: (OPTIONAL)  
     This entry will usually contain the client's company name. The contents of this entry will appear on the PARA-Site greeting screen upon running INITIAL.SC.

Address: (OPTIONAL)        City:    (OPTIONAL)        State:   (OPTIONAL)  
     These entries will usually contain the client's business address. The contents of these entries will appear on the PARA-Site greeting screen upon running INITIAL.SC.

License#: (NOT ADJUSTABLE)  
     This entry contains your unique PARA-Site License/Disk I.D. number. It will appear on the PARA-Site greeting screen on start-up.

Start Date: (NOT ADJUSTABLE) 
     This entry will contains today's system date. It is automatically set to the current system date during a routine license update session weather done locally or remotely. This date will be the beginning date for the license term.

End Date: (MANDATORY)  
     This entry represents the end of the license term. It can be set by the Administrator "on site" or automatically by phone during the license update session. If the date you select for End Date happens to be a Saturday or Sunday, PARA-Site will automatically advance the date to the following Monday to allow the user time to contact you on a business day. (see Remote License Updating)



Chase Date: (OPTIONAL)  
     PARA-Site is sent with this option "checked" as it is anticipated that under most circumstances this option will be exercised. With Chase Date checked, PARA-Site automatically sets the Start Date field to Today's Date each time it is run. Since PARA-Site will only run if the system date falls between the Start Date and End Date keeping the Start Date current will prevent the user from "rolling back" the system date in an attempt to avoid license lapsing. If the option is left un-checked the Start Date will remain as was originally set by the Administrator or Remote License Update. Incidently, this field need not actually contain an "X". It can contain ANY character in order to be considered "checked".

Check Bios: (OPTIONAL)
    PARA-Site is sent with this option "checked" as it is anticipated that under most circumstances this option will be exercised. With Check Bios checked, PARA-Site will verify the system bios identification number. NOTE: any character can be inserted here to consider the field "checked". Remember: leaving this field "UnChecked" reduces the effectiveness of the security of PARA-Site considerably. It should remain "Checked" in most cases.

Check Sector: (OPTIONAL) 
     PARA-Site is sent with this option "checked" as it is anticipated that under most circumstances this option will be exercised. With Check Sector checked, PARA-Site will perform one of its most beneficial features, checking against movement of files from their original setup location on the client's computer. NOTE: any character can be inserted here to consider the field "checked". Remember: leaving this field "UnChecked" reduces the effectiveness of the security of PARA-Site considerably. It should remain "Checked" in most cases.

Check Date: (OPTIONAL) 
     PARA-Site is sent with this option "checked" as it is anticipated that under most circumstances this option will be exercised. With Check Date checked, PARA-Site will check the system date against the Start Date and End Date fields. NOTE: any character can be inserted here to consider the field  "checked".  If you leave this field "UnChecked" there will not be any date checks made by PARA-Site, essentially leaving the user with "Unconditional" licensing privileges. This however, DOES NOT turn off the copy protection feature of PARA-Site. He may use your application indefinitely, but he may not transfer the program from his P.C.

See Screen: (OPTIONAL)  
     With this option "checked" the built in PARA-Site greeting screen will be presented upon startup or running of "INITIAL.SC". If this option is left "UnChecked" the PARA-Site greeting screen is not shown, and whatever was on the screen prior to running  INITIAL.SC" remains on the screen until either your LAUNCH script begins to run, or PARA-Site issues a SYSTEM INFORMATION NOTICE to the user. This feature allows you to put up a custom greeting screen if you choose. Simply run your script (with your startup screen) as the first script and have it run INITIAL.SC. Remember: INITIAL.SC acts as the "gateway" through which the user must pass to get to your application.

# Of Days: (MANDATORY)
      This option allows you to adjust the "alarm" interval  within which the client will be prompted about his license expiration. You may place any number in here between 3 and 15. Numbers less than 3 and greater than 15 will default to 3. 
 
Set1:, Set2:, Set3: (OPTIONAL)
      These options are actually switches you can turn on or off  to allow portions of  your application to be on or off remotely. This feature is especially useful for DEMOS and limited use applications. By placing any character in the field, you set variables KKEYVAR1$, KKEYVAR2$, and KKEYVAR3$ to "ON". By default these variables are set to "OFF" (notice UPPERCASE).  Write your script code to check for the value of these variables and then take appropriate action.  An example might be:

	If KKEYVAR2$="OFF" then
		PLAY "LEDGER"
	else ?"This feature not included with DEMO copy"
	     sleep 2000
	endif

	A scenerio might be: After having given a prospective client your DEMO copy, you simply need only "release" the features you have limited, to give him a full-fledged copy, by phone, after receiving payment.	

Sector Code: (NOT ADJUSTABLE)       Bios Code: (NOT ADJUSTABLE)
    These entries are numeric values used by PARA-Site to "lock" itself onto the client's P.C. THE SETTING  OF THESE VALUES IS TOTALLY AUTOMATIC AND CANNOT BE CHANGED.

Title Line 1: (OPTIONAL)       Title Line 2: (OPTIONAL) 
     Both of these entries will appear at the top of PARA-Site's greeting screen. We believe they are best suited for displaying information about your company or service, however you may enter any 30 character line of text in each.

Contact Name / Phone Number: (OPTIONAL)  
     This field contains the name and phone numbe of the support person or group that the client can call when there is need to update or if there is a problem. This information appears on the "System Information" screens which appear during problem alerts.

Launch Script Name: (MANDATORY) 
     This entry represents the name of the script which is "launched" by PARA-Site. It is important to remember that any script MUST BE PASSWORD PROTECTED from within PARADOX to make PARA-Site a viable tool for security. Enter the name of your first script here WITHOUT THE EXTENSION .SC. 
       (see ABOUT YOUR LAUNCH SCRIPT for important information.)
             - F2 -: Exits Security Setup / Change Screen.





CREATING A DEMO:

     PARA-Site make issuing a demo to a prospective client easy. Simply install your application with only a 7 or 30 day licensing period. (this can be done on-site or by phone) Your demo can be an actual "full featured" copy. If the client wants to purchase the program, you need only update him to a more "liberal" licensing period. If he chooses not to purchase your program, his license will just expire on the "end date" and the program will cease to run. Demo applications can also be restricted by use of the Set1, Set2 and Set3 switches found on your Security Set-Up  / Change Screen.  (See Security Set-Up / Change)

SENDING PARA-Site TO A CUSTOMER:

     It may be necessary to send your application as a "package" to a client or customer. In this case follow these steps to include PARA-Site in the package.

     1) Copy all of the files specified in the install proceedure (pg 2) to the disk containing the application.
     2) License your client's P.C. by following the instructions in "REMOTE LICENSING" found in this manual, or by using the convenient AUTO-INSTALL feature discussed on page 2.

REMOTE LICENSE UPDATING:

     One of the nicest features about PARA-Site is it's ability to change license and status updates remotely.  This means that as an Administrator, you can maintain control over the site license by simply working through a few minutes worth of screen prompts with the client over the phone. The client a may receive a "SYSTEM INFORMATION" messages when one of several conditions exist.

     1) His license term is near the End Date.
     2) His license has expired.
     3) Some condition has caused the "movement" of PARA-Site files.
     4) His system date has been "rolled back". (prior to the last date PARA-Site remembers having been run) 

(NOTE: this message will only pop-up if the "Chase Date" entry has been checked on the Security Setup / Change Screen.)
 
    In any case, the same procedure is followed to reset his system. Have him type the word UPDATE (not case sensitive) at the prompt "Type UPDATE to update or ENTER to Quit". This option will automatically present itself what a problem has occurred. At this point you, the Administrator, should be on the phone with him ready to cooperatively perform the update. Install your Key Disk and from the PARADOX main menu, switch your working directory to the drive in which your Key Disk resides and run UPDATE2.SC. You will be asked for your unique disk password. You and the client will then follow a series of prompts and numeric checks, offering and receiving information from each other. You should insure that his numeric responses match yours in cases where a match is expected. If they do not, you should both check your system dates to be sure they are accurate and identicle.   (see attached sheet for REMOTE UPDATE PROCEEDURE)        
       Caution: Giving the Client the number associated with UNRESTRICTED LICENSE will give all privileges to the client forever without recourse. Although dates will no longer be of any  onsequence, the COPY PROTECTION offered by PARA-Site will still be in place. Copy Protection will only be lifted if you DO NOT
CHECK "CHECK SECTOR" and "CHECK BIOS" in the Set Up screen. This has to be done on-site by the Administrator. Lastly, you will give the client the "code" representing the license term you wish him to have. If all has gone well, his system will be updated with the last key stroke. 
(NOTE: this procedure is the same for correcting any of the problems listed above.)

REMOTE UPDATE PROCEEDURE:

	Remote updateing will be necessary if one or more of the following is true:

1) The client has moved his files from one P.C. to another or from one directory to another.
 
2) The client has set his system date back, and attempted to run INITIAL.SC.

3) The client has used a defragmentor or optimizer which has relocated his files.

4) The END DATE set previously has expired.




         ------------ REMOTE UPDATE COARSE OF EVENTS -------------

                        PROCEEDURE "CLIENT SIDE":       

Client receives a SYSTEM INFORMATION notice, and dials Support. He then types UPDATE to begin proceedure.

Client types in today's date with no separators or slashes

Client reads DATE CHECK number to Support.

Client reads BOOT NUMBER to Support.

If release codes are to issured, they are typed in here.

Client receives authorization number and types it in.

Client receives EXTENTION code and types it in.

Client receives update notice and is brought to C:\ prompt.. 



                       PROCEEDURE "SUPPORT SIDE":
   
Support installs KEY DISK and types UPDATE2. 

Support types in today's date with no separators or slashes.

Support verifies DATE CHECK number.

Support types in BOOT NUMBER 

If Support is issuing release codes they are given here.

Support issues AUTHORIZATION number.

Support issues EXTENTION code.

Exit.






ON-SITE LICENSE UPDATING:

     When at the client's location, certain maintenance procedures can be carried out. From the main PARADOX menu, run LICENSER.SC. You will be asked to install your Administrator's Key Disk. Follow the prompts for password authorization. Update your Security Setup / Change Screen as necessary.
 (see Security Setup / Change Screen instructions for details)

ABOUT YOUR LAUNCH SCRIPT:

     Your Launch Script is the first script of your application. (not counting INITIAL.SC) This script may contain various variable establishments or environmental set-ups as required by your application, however the primary thing to remember is to include your KKEY$ variable AT THE BEGINNING of your Launch Script. KKEY$ is set in the INITIAL.SC to a value unique to your copy of PARA-Site. (FIND YOUR KKEY$ VALUE IN YOUR PARA-Site LITERATURE) The KKEY$ line in your first script will check this variable value to be sure that INITIAL.SC has in fact run. Let's suppose the user is knowledgeable enough to try to circumvent security by running your Launch Script directly from PARADOX or PARADOX RUNTIME. KKEY$ in your first script will not have had a value set to it and the script will not run. In fact, if he was running the script from PARADOX, he would be offered a chance to enter the DEBUG mode, and therefore be granted access to your script and of course be able to ascertain the logic of KKEY$. FOR THIS REASON, YOUR LAUNCH SCRIPT MUST BE  ASSWORD PROTECTED BEFORE YOU DISTRIBUTE YOUR APPLICATION.





     Also, to keep prying eyes from discovering the variable which allows your application to run, YOU MUST ADD THE FOLLOWING LINE DIRECTLY AFTER YOUR KKEY$ LINE:

          RELEASE VARS KKEY$

     Without this line, your variables can be easily seen by issuing the PARADOX SAVEVARS command at the end of the program.

     In summary: Your LAUNCH SCRIPT should look like this at the top:
        (assume your KKEY$ is "GOLDEN"

     Clear
     ClearAll
--> If  KKEY$ <> "GOLDEN" then  EXIT  EndIf  ; <---
--> RELEASE  VARS  KKEY$            ; <---
     SetKey 14 Beep
     Var1 = ".08"
     Var2 = ".06"
     Play "MYNEXT.SC"


 Notice lines 3 and 4.
     THESE LINES MUST BE ENTERED INTO YOUR SCRIPT AS YOU SEE THEM AT THE TOP OF YOUR SCRIPT FOR PARA-Site TO OPERATE!  All of the other lines are simply examples. When you have entered these lines, PASSWORD PROTECT your script using the PARADOX PASSWORD menu selection under any password you choose. Of course, REMEMBER IT!.  For procedures as the first event, follow the instructions for Launch Script above; put your script into a procedure and run it as a script. See your PARADOX user's manual for complete instructions on creating procedures.


NOTE: Because INITIAL.SC essetially branches to your LAUNCH script, your scripts become password protected by PARADOX under the password for INITIAL.SC.  What this means is that even though your scripts may not be password protected, if an error occurs PARADOX will not give you the option to go into the DEBUG mode. Your script will simply fail, and INITIAL.SC (password protected) will issue an "Error Occured In Protected Script" message. To eliminate the problem, be sure all of your scripts EXIT PROPERLY. Check your scripts to be sure none are ending illogically. All scipts called by another script (including INITIAL.SC) must contain either a RETURN or QUIT at their end.











QUESTIONS Answered:

Q    "IF MY CLIENT BUYS A COPY OF PARA-Site, DOES HE HAVE THE ABILITY TO UPDATE HIS OWN SYSTEM?"

A    No. Each copy of PARA-Site is individually coded to prohibit this.


Q    "WILL I NEED A SEPARATE KEY DISK FOR EACH CLIENT LOCATION?"

A    No. Each system you set up using the files sent to you under your license  number, will operate with the Key Disk associated with that license umber.

     REMEMBER: Giving a copy of your PARA-Site program to others minimizes your security. Only your KEY DISK works with your protected system. Offering your KEY DISK and PARA-Site files to anyone else only defeats your purpose. PARA- Site is priced so that most everyone should be able to afford their own copy.

Q    "CAN I PROTECT ALL OF MY SCRIPTS WITH THE KKEY$ LINE AS I DO IN MY LAUNCH SCRIPT?"

A    No. The line which follows it erases the variable KKEY$ from memory for  security reasons, therefore it cannot be used afterward.
     It makes good sense however, to password protect your scripts or put them in libraries for to make them as secure as possible.




ASSISTANCE:

     If you are having problems, you may leave your name, phone number and license number at 716-947-4409 between 9am and 5pm eastern time and we will contact you as soon as possible.

     PARA-Site is a trademark of Softouch Software Systems, a division of The CAM Group, 860 Niagara Falls Boulevard, Buffalo, New York 14207.

     Softouch Software Systems, 1195 Peppertree Drive, Derby, New York, 14047

     PARADOX is a trademark of BORLAND INTERNATIONAL.









WARRANTY:
This book explains how to use PARA-Site site protection software on ,MS-DOS micro-computers. PARA-Site and documentation is provided "as-is" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
Softouch Software Systems warrants that the PARA-Site book and diskette(s) are free from mechanical and recording defects. We will replace any defective media within ninety(90) days of original purchase.
Information in the document is subject to change without notice and does not represent a commitment on the part of Softouch Software Systems.
Softouch Software Systems and it's officers and employees shall have no responsibility or liability to you or any other person, persons, or entity with respect to loss or damage caused directly or indirectly by use of PARA-Site and/or it's documentation. The liability of Softouch Software Systems under the warranty set forth above shall  be limited to the amount paid by the customer for the product. No other warranties are expressed or implied as to  the operation, use or suitability of PARA-Site.
COPYRIGHT:
The computer files and this book are protected by United States Copyright law. That means you need our permission to make copies of them. You own this copy of the book and the diskette(s). Softouch Software Systems owns and retains title to the computer programs, files and the contents of this book. Copyright 1992/93, Softouch Software Systems.
COPY AND USE RESTRICTIONS:
Softouch Software Systems grants you the right to use one copy of the software on a single-user computer. You may not sublicense or lease the software, but you may permanently transfer your license to use the software and accompanying materials by delivering the original distribution diskette(s) and materia ls comprising the software package to another party, and by destroying all copies of the software and accompanying materials in your possession. Such transfer terminates your license to use the software. The new recipient of the software and accompanying materials is licensed under the terms of this agreement.
You are encouraged to make a backup copy of the distribution diskette(s) for your own use and back-up  protection. Copies of the distribution diskette made for any other purpose is expressly prohibited. You may not decompile, reverse engineer, disassemble, or otherwise reduce the software to humanly perceivable form.
ACKNOWLEDGMENTS:
The programs and utilities in the PARA-Site software package were created using various language editors, compiler and link programs and library toolbox routines. These include PARADOX 3.5 from Borland International of Scotts Valley, CA. IBM is a trademark of International Business Machines Corporation. PARADOX is a registered trademark of Borland International. PARA-Site is a registered trademark of Softouch Software Systems.

PUBLISHED BY:
     Softouch Software Systems
     1195 Peppertree Drive
     Derby, New York 14047

All rights reserved: No part of this book may be reproduced by any means without the express written  permission of the publisher.

 

