We have had a similar experience and have found it equally
annoying.  In fact, the user who was running the scheduler thought
that her machine froze and so she rebooted.  I will have her
check out making another window active.  I agree, though, that
the Window in which the scheduler is running should not become
active.  My only question is whether that is possible given that
Windows really is still only a single tasking operating system.

------------------------------------------------------------------
Robert P. Klein                          KL2 AT CU.NIH DOT GOV
Robert P. Klein                          KL2 AT CU.NIH DOT GOV
Phone: 301-496-7400                      Fax: 301-496-6905
Mail:  DCRT/CFB/ETS, 12A/1033, 12 SOUTH DR MSC 5607,
       BETHESDA, MD 20892-5607
------------------------------------------------------------------
== Original Message ==
== Original Message ==

>
> Subject: Windows Scheduler wish
>
> Hello all,
>
> Am I the only one who finds the ADSM scheduler's behavior of becoming
> the "active" window whenever it needs to talk to the server annoying.
>
> For instance, I was just in the middle of using my word processor when
> the scheduler kicked in causing my keystrokes to be sent to it and
> not to the word processor.  Even more annoying is that after the
> scheduler is done, it does not return focus to my word processor.  Then
> I get the annoying little ADSM "snozzing" cursor until I make another
> window active.