LOOKUP(TM) and RCROSREF(TM) are part of
FWKCS(TM) Contents_Signature System, Ver. 2.03, 1995 Apr 19.
(C)Copyright Frederick W. Kantor 1989, 1995. All rights reserved.

Kit for remote Lookup and Rcrosref.   Current release: 1995 Apr 19.

For resource material re protecting against software piracy, download
FWKCS203.ZIP and the current release of FWKCXnnn.ZIP.

New in FWKLU203.ZIP:

This provides current code for the "remote lookup" functions supporting also
Rcrosref, in a relatively small kit, for use by those who have not yet
downloaded the larger FWKCS(TM) system package (current FWKCS release:
FWKCS203.ZIP).  The version of FWKCS.EXE contained in this kit has been
revised since the last major prior release. All FWKCS.EXE functions are
enabled in the unregistered copy.

To run an unregistered copy, keep a copy of REGISTER.FRM in the same
directory with FWKCS.EXE. You can put the whole set of files on your PATH,
and call LOOKUP from anywhere on your system. Suggested test time is up to 30
days, before registering.

If this software is used in a public, commercial, school, institutional, or
governmental environment, then the test period is restricted to no more
than 45 days.

Until FWKCS has been registered, when it is run, a notice appears on the
screen above the program identification:

  "This is an unregistered copy. After evaluation day 45, if you do not
   register, a delay of about 1 second will be added for each additional
   day. The suggested test time is up to 30 days, to allow time for your
   registration to normally reach you by mail before those delays start.

   You are now at Evaluation Day    0.

   To register, see instructions in D:\PATH\REGISTER.FRM."

The Evaluation Day is updated, counting the first day of use as day 0, and
D:\PATH gives the drive and path for the registration form.  Registration
suppresses that message and those potential delays.

The registration form, REGISTER.FRM, is a plain ASCII text file which can
be copied to a standard printer.

You can use the remote Lookup to help find the missing files that go with a
single file you have, by doing a remote Lookup and calling the giant
electronic bulletin board systems that run FWKCS(TM). For example, if you
want to find the .DOCs that go with a program, there's a good chance that
Lookup and a call to one of those giant boards will find for you the name of
the zipfile which contains that whole set of files.  Even if the name of the
file you have was changed, Lookup can still be used.  Then, just download
that whole zipfile...

If you are a bulletin board system operator, Lookup helps you use tens of
Gigabytes of collected files on giant boards to support your users's special
requests.  Your board's users can call you locally at low speed -- you use
your high_speed modem to get what they needed -- letting you devote more of
your resources to the kinds of files you're specially interested in.  Then,
if you run FWKCS(TM), you could become a preferred resource for that special
area of work that you like. As a specialist in your own area, you can
prepare automatic FWKCS cross references to help guide users in finding
conceptually related files.

-------------------------

To keep FWKCS.EXE relatively small, some help is provided via a text file,
FWKCS203.H00.  FWKCS.EXE can search for it in the current directory and on
your path. So, if you put FWKCS.EXE on your path, preferably keep this
text file in the same directory with it.  FWKCS <enter> brings up a list
of commands for further help.

The extended help (option /** ) uses FWKCS203.REF, which, for reasons of
size, is not included in this kit.

Note:  FWKCS(TM) has many features not supported in this kit -- this kit is
intentionally kept small to serve your special needs in using remote Lookup.