        README.TXT for FWH use of Protection PLUS   - R.W. Seiler  3/22/2008

Protection PLUS, from SoftwareKey.com, is a 3rd party tool providing a robust
system for managing software copy protection, demo expiration, unlocking codes,
the licensing of networks for a given number of concurrent workstations, etc.

Before you purchase P. PLUS from Softwarekey.com, you will only be able to run
the PlusTst2.exe demo program provided here. You will not be able to compile
PlusTest.prg until you get Keylib32.lib which comes with the P. PLUS purchase.
However, what you'll see with PlusTst2.exe is virtually the same as what you'd
see if you compiled PlusTest.prg .  The only difference is that PlusTst2.exe
uses some special codes assigned to us by Softwarekey.com, whereas with your
purchase of P. PLUS, you will be assigned your own special codes - which you
will insert into ProtPlus.prg so that it will work properly.

To use this kit with Protection PLUS v.4, create a "Test" folder within
your main Protection PLUS folder (SWKEY?), and also create a parallel folder
in the main folder and name it "TempTT" (where the temp network semaphore files
will go).  Then wihtin the Test folder, create two subfolders: "Wrk" and
"Reset". All of the files below should be in the Test folder, and then the
InitFile and Journal filesets

(Be sure to see the important note about using the PLUS LFEdit program below.)

In order to use Protection PLUS 4.4.1 with FiveWin for Harbour (FWH),
the following files are supplied here:

ProtPlus.prg - A sample program utilizing PLUS V4 to manage both single user
              and network applications, including execution-count limit,
              demo-date limit, and concurrent network user rights. Also 
              includes special tactics to defeat attempts to circumvent or 
              "crack" the Protection PLUS rules. You can adapt this to your
              own purposes. This is the main PLUS implementation program,
              to manage demos, unlocks and network rights. It contains many
              optional non-PLUS reduncancies to further confound would-be
              cheaters. You can use these optional features or dump them -
              your choice. I find them useful, so I thought you might too.

Plus.rc     - The screen resources for dialog boxes used by ProtPlus.prg. Just
              copy these resources and paste them into your app's own .rc file.

Plus.dll    - The .rc compiled into a screens DLL for runtime use by PlusTest.

BWCC32.dll  - The Borland resources file that contains some resource elements
              used in Plus.rc & Plus.dll . (Recessed panels and lines, mainly.)

PlusTest.prg - A simple application program that uses ProtPlus.prg, demon-
              strating how to use PLUS V4.

PlusTest.exe.xbp - xBuilder project file

PlusTst2.exe - A demo program based on a prg that is identical to PlusTest.prg
              except that it works with LF files that have our license codes
              instead of yours - just for demo purposes.

Netopen.prg - Network function used by ProtPlus.prg
Netlock.prg - Network file/record locking, plus record recycling function to
              avoid having to actually delete records on a network.
Mylib.ch    - need to include this in order to use Netopen.prg

Keylib.ch   - Must #include this file, as shown in prg's here
KeylibB.ch  - a dummy file for test compiling with Clipper to check warnings
Keylib32.dll - The PLUS distributable DLL, needed to run the Plustst2.exe demo.

PPP4FWH.prg - Contains "DLL32" FWH command calls to over 80 functions
              contained in the "PLUS 4.4.1" DLL, KeyLib32.dll . Refer to the
              PLUS documentation that comes with the product for explanations
              of these functions and how to use them.

              Assuming that you have PLUS 4.4.1, just include Keylib.ch and 
              compile and link this .prg into your project and you will be
              able to use the PLUS functions in your app.

              Of course, in building your app, you will also need to link
              in the KeyLib32.lib.  KeyLib32.DLL is required for runtime.

PPP4xHb.prg - If you aren't using FWH, but are using xHarbour, link this prg
              into your app instead of PPP4FWH.prg, to do the same job.
DLLxHb.ch   - If using PPP4xHb.prg, then you will need to #include "DLLxHb.ch"
              in your program.
DLLCALL.c   - An temp interim fix needed for a piece of xHarbour - just link in.

DumProcs.prg- Dummy procs/funcs to enable PlusTest to link okay.

xHbTest.prg - A non-FWH, Winapi only, app framework for testing.
xHbTest.exe.xbp - xBuilder project file.

InitFile.dbf- Used for optional features in ProtPlus.prg
InitFile.cdx- Index file for the above.
              (For the demo to work, you must create a "Wrk" subfolder within
              the app folder and copy these 2 files there, as well as the
              Journal fileset below.)

Journal.dbf - These are stand-in files representing whatever is the most used
Journal.fpt   fileset in your app.  Its disk date likely represents the most
Journal.cdx   recent use of the app (in addition to the same date stored in
              other files, which should match, unless the user is trying to
              circumvent your demo control system).

Semaphor.ini - Used for placing momentary blocks to prevent others from signing
              on to an app until the current user is "through the front gate."

Changes.txt - A list of obsolete PLUS V3 functions and their corresponding
              PLUS V4 replacements.

Readme.txt - You're looking at it.

If you previously used PLUS version 3, then be sure to take a look at 
Changes.txt for a description of functional differences between 
Protection PLUS version 3 and version 4.

Protection PLUS 4.4.1 can be ordered online from:

SoftwareKey.com ( Concept Software, Inc. )

An important note about using the LFEdit program that comes with PLUS:

In this program you will be working with TWO SEPARATE files describing EACH of
your products - 1) the Product Description File, and 2) the product's License 
File. It's important to understand this subtle fact, because it's easy to 
overlook this and think that both the product description and license file
are one and the same thing, which THEY ARE NOT! For each product, you must 
first create the necessary data in the Product Description File, and then
only after that is accomplished do you then create the product's License File,
which will automatically import key info from the Product Description File.
If you later change anything in the Product Description File, you must then
re-create the products's License File in order for the changes to take effect.

- Roger Seiler
  Leadership Software Corp.
  Nyack, New York, USA
  (reachable on the FWH forum)