| RE: Windows Indexing Service and Desktop Search 3.0 "GobinderConvert?" wrote:
> I had a real problem after installing WDS 2.x, the CPU would peg at 99% for
> long periods of time. Indows Indexing Service was presumably the culprit. I
> finally disabled it.
Yep. I seem to be having the same problem. I have a fresh install of XP
(tablet pc edition), fesh install of Onenote 2007 w/beta refresh, and fresh
install of WDS 3.0.
It seems like I am hitting a race condition. The last time it happened, I
was making simple boxes for network diagrams and dragging-and-dropping them
around in Onenote, then the indexing thread kicks off and I seem to be
deadlocked in Onenote.
I had a couple of these CPU pegs in a row for 20 minutes at a time. Finally
Onenote gave up, and crashed. I believe the developers should have received
my crash output automatically.
-Steve |