From: "Rich" 

This is a multi-part message in MIME format.

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

   This applies when you switch between any applications.  Once you =
start using the machine, the service stops and remains stopped for a =
while.  This is not what gary is describing.

Rich

  "Gregg N"  wrote in message =
news:43ce7356$1{at}w3.nls.net...
  Rich wrote:=20
      "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.
       =20

    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


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






   This
applies when you =
switch between=20
any applications.  Once you start using the machine, the service =
stops and=20
remains stopped for a while.  This is not what gary is=20
describing.
 
Rich
 

  "Gregg N" <invalid{at}invalid.invalid>">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>
= wrote in=20
  message news:43ce7356$1{at}w3.nls.net...Rich=20
  wrote:=20
  
    
    

    
      "Gary Britt" <email{at}from_Gary_Britt.org&g=">mailto:email{at}from_Gary_Britt.org">email{at}from_Gary_Britt.org&g=
t;=20
      wrote in message news:43cde00b{at}w3.nls.net...We=
ll=20
      this was on a bit older hardware (but still should have been=20
      plentyfast enough to avoid this) and it was in a Domain =
situation that=20
      maybe couldhave had some effect on this.  I know for sure =
when I=20
      stopped the indexingservice and disabled it, the problem =
immediately=20
      went away and neverreturned.  It was definitely related =
to hard=20
      disk activity, because I couldsee the hard disk indicator =
flickering=20
      busily as the problem was happeningwhile I was typing in =
word. =20
      When I stopped the indexing service, the harddisk activity =
went away=20
      and so did the interference with my =
keyboardresponsiveness. =20
      
  Older hardware doesn't
matter.  If =
there is any=20
    user activity it stops.  It won't restart until there is a =
period of=20
    inactivity and will stop as soon as there is=20
  any.RichEven
though the indexing service =
stops=20
  running when the user starts typing, its effect on the responsiveness =
of a=20
  memory-constrained system can linger. This can happen if the indexing =
service=20
  consumes enough memory while it is running that it causes the system =
to start=20
  paging. When the user returns to typing, there will be a pause while =
the=20
  system pages back in what is=20
needed.Gregg

------=_NextPart_000_034A_01C61C10.B31A2F50--

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