From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_00CD_01C62123.D9051A00
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   If the index is corrupted it gets rebuilt.  Did you install any third =
party IFilter implementations?  Buggy ones may crash causing problems.  = I
know some would crash though its been a while since one triggered a =
rebuild of my index.

   I'd also look in the event log.  I think an event gets logged when =
corruption is detected.  My memory is fuzzy on this.

Rich

  "Gregg N"  wrote in message =
news:43d683ad{at}w3.nls.net...
  Every so often (maybe a couple of times a day) Windows Desktop Search=20
  decides that it needs to do a massive reindexing of 20,000 or so =
files. The=20
  status dialog shows that it is scanning seemingly unrelated =
directories that=20
  I have not touched in ages (e.g., "c:\Program Files\Microsoft Platform =

  SDK\", "c:\cygwin", etc.).

  Once it is finished, it stays at "items left to scan: 0" for a few =
hours=20
  until it decides to do it again.

  Anyone know what triggers this? It does this on two different =
computers,=20
  both XP Pro.

  While it is at 0, it behaves normally. If I create a new file, it =
briefly=20
  jumps up to 1 and then after 15 seconds of computer idle, it goes back =
to 0=20
  again, as I expect.

  WDS version: 02.06.0000.2083

  Gregg

------=_NextPart_000_00CD_01C62123.D9051A00
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   If the
index is corrupted =
it gets=20
rebuilt.  Did you install any third party IFilter =
implementations? =20
Buggy ones may crash causing problems.  I know some would crash =
though its=20
been a while since one triggered a rebuild of my index.
 
   I'd also
look in the event =
log. =20
I think an event gets logged when corruption is detected.  My = memory is=20
fuzzy on this.
 
Rich
 

  "Gregg N" <invalid{at}invalid.invalid>">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>
= wrote in=20
  message news:43d683ad{at}w3.nls.net...Ev=
ery so=20
  often (maybe a couple of times a day) Windows Desktop Search =
decides that=20
  it needs to do a massive reindexing of 20,000 or so files. The =
status=20
  dialog shows that it is scanning seemingly unrelated directories that =
I=20
  have not touched in ages (e.g., "c:\Program Files\Microsoft Platform=20
  SDK\", "c:\cygwin",
etc.).Once it is finished, it stays at =
"items=20
  left to scan: 0" for a few hours until it decides to do it=20
  again.Anyone know what triggers this? It does this on two =
different=20
  computers, both XP Pro.While it is at 0, it behaves =
normally. If I=20
  create a new file, it briefly jumps up to 1 and then after 15 =
seconds of=20
  computer idle, it goes back to 0 again, as I
expect.WDS =
version:=20
 
02.06.0000.2083Gregg

------=_NextPart_000_00CD_01C62123.D9051A00--

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