From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0033_01C5710F.8CA3A470
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   The ! prefix is only needed if you do not use the query specific =
syntax.  It's the override mechanism that forces the query service even =
if not requested.

   Now you may ask, why isn't the service the default?  I can only =
speculate that because of how it works people may believe it didn't work =
because it will only find content in indexable files and only what the =
filter reports.  For example, adam whined that the HTML filter returns =
the HTML text and not comments within the HTML.  He is an example of =
someone that might be unhappy (in fact I'm sure he would say so whether =
true or not).  Of course he would likely also complain if it found the =
deceptive terms that folks trying to fool search engines or spammers =
trying to trick filters include in comments.

   You could also ask why isn't this better documented (or documented at =
all?).  I never knew of this.

Rich

  "John Beckett"  wrote in message =
news:68vua159alkl6uar4otkulv1cv4spp79tq{at}4ax.com...
  On Tue, 14 Jun 2005 17:32:40 -0400, "Gregg N"
   wrote:
  > You can reliably use the indexing service by bypassing "search =
companion"=20
  > altogether, directly accessing the indexing service.

  Thanks, but I found ciadv.msc some time ago (should have mentioned
  that). There was a brief discussion here a week or so ago when I said
  I would like something with less mouse clicks, and I started
  investigating the IIS4 RK srch.exe that Rich mentioned.

  It was part of my general investigation of searching that I wanted to
  see why the damn Windows Search didn't use the index. You can actually
  use all those {at} keywords if you start the search with an exclamation
  mark (which also causes it to use the index).

  John

------=_NextPart_000_0033_01C5710F.8CA3A470
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   The !
prefix is only =
needed if you do=20
not use the query specific syntax.  It's the override mechanism =
that forces=20
the query service even if not requested.
 
   Now you
may ask, why isn't =
the service=20
the default?  I can only speculate that because of how it works =
people may=20
believe it didn't work because it will only find content in indexable = files and=20
only what the filter reports.  For example, adam whined that the = HTML=20
filter returns the HTML text and not comments within the HTML.  He
= is an=20
example of someone that might be unhappy (in fact I'm sure he would say = so=20
whether true or not).  Of course he would likely also complain if
= it found=20
the deceptive terms that folks trying to fool search engines or spammers = trying=20
to trick filters include in comments.
 
   You could
also ask why =
isn't this=20
better documented (or documented at all?).  I never knew of=20
this.
 
Rich
 

  "John Beckett" <FirstLast{at}compuserve.com.om=">mailto:FirstLast{at}compuserve.com.omit">FirstLast{at}compuserve.com.om=
it>=20
  wrote in message news:68vua159alk=
l6uar4otkulv1cv4spp79tq{at}4ax.com...On=20
  Tue, 14 Jun 2005 17:32:40 -0400, "Gregg N"<invalid{at}invalid.invalid>=20">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>=20
  wrote:> You can reliably use the indexing service by bypassing =
"search=20
  companion" > altogether, directly accessing the indexing=20
  service.Thanks, but I found ciadv.msc some time ago (should =
have=20
  mentionedthat). There was a brief discussion here a week or so ago =
when I=20
  saidI would like something with less mouse clicks, and I=20
  startedinvestigating the IIS4 RK srch.exe that Rich =
mentioned.It=20
  was part of my general investigation of searching that I wanted =
tosee why=20
  the damn Windows Search didn't use the index. You can actuallyuse =
all=20
  those {at} keywords if you start the search with an exclamationmark =
(which=20
  also causes it to use the =
index).John

------=_NextPart_000_0033_01C5710F.8CA3A470--

--- BBBS/NT v4.01 Flag-5