README.TXT
SUMMARY 
======= 
 
The CATQ sample shows how to run a query against a catalog generated by 
the Microsoft Index Server.  By default, in this example, the catalog is 
for files on the local machine and the query is restricted to the scope 
of the SDK.  As such, this sample provides fast full text search over all 
text-based files in the SDK. 
 
 
MORE INFORMATION 
================ 
 
Content indexing (CISVC) is a service included in all versions of Windows NT 5, 
but it is not running by default.  When the CATQ sample is started, it checks 
the status of CISVC, and starts it up if it is not running. 
 
In the status window at the bottom of the CATQ sample, the progress of the 
indexing effort is displayed as a fraction and as a blue "progress bar."  The 
numerator and denominator of this fraction are read as performance registry 
counters, which are written out by CISVC. 
 
The denominator in the progress display is the total number of files that 
CISVC must index in order for the catalog to be up-to-date.  Unfortunately, 
this value is not known instantly at the time of CISVC startup, and in fact, 
it typically grows over time as the numerator grows.  For this reason, the 
progress percentage can decrease even as the content indexer is making 
progress.  I.e. it is finding new files to index as fast as it is indexing 
files in its existing list. 
 
As a result of running the CATQ sample, the CISVC service is started.  This 
will place a small load on your CPU and on your disk controler.  The resulting 
catalog will also take up some amount of disk space. 
 
If you would like to stop the CISVC service, use the service control manager 
built into the system, or the SC.EXE utility distributed with the SDK.  In the 
case of the later tool, the appropriate command line is: 
 
    SC stop CISVC 
 
If you wish to reclaim disk space occupied by the catalog, after the service 
has been stopped, delete all of the files in %SystemRoot%\system32\catalog.wci. 
 
By default, most of the text file formats present in the SDK are indexed. 
Additional file formats can also be indexed and searched by providing custom 
filters.  See IFilter in the documentation for more information.