From: "Gary Britt" 

It was Win2K on a 256 meg machine and 1.7 ghz P4 processor.  It could have
been a paging effect possibly, I guess.

Thanks,

Gary

"Gregg N"  wrote in message
news:43ce7356$1{at}w3.nls.net...
> Rich wrote:
> >> "Gary Britt"  >> > wrote in message
> >> news:43cde00b{at}w3.nls.net...
> >> Well this was on a bit older hardware (but still should have been
plenty
> >> fast enough to avoid this) and it was in a Domain situation that
> >> maybe could
> >> have had some effect on this.  I know for sure when I stopped the
> >> indexing
> >> service and disabled it, the problem immediately went away and never
> >> returned.  It was definitely related to hard disk activity, because I
> >> could
> >> see the hard disk indicator flickering busily as the problem was
> >> happening
> >> while I was typing in word.  When I stopped the indexing service, the
> >> hard
> >> disk activity went away and so did the interference with my keyboard
> >> responsiveness.
> >>
> > Older hardware doesn't matter.  If there is any user activity it
> > stops.  It won't restart until there is a period of inactivity and
> > will stop as soon as there is any.
> >
> > Rich
>
> Even though the indexing service stops running when the user starts
> typing, its effect on the responsiveness of a memory-constrained system
> can linger. This can happen if the indexing service consumes enough
> memory while it is running that it causes the system to start paging.
> When the user returns to typing, there will be a pause while the system
> pages back in what is needed.
>
> Gregg
>
>

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