I'm curious... How would you be able to tell which process is the one
that's preventing the screen saver from starting?
One way would be process of elimination. Start with nothing running but the
base system; if the screensaver pops start adding the other tasks until the
screensaver no longer comes up.
There is a defined API by which a process can suppress idle detection,
intended for situations where interruption would impact the user
experience - video and audio playback, for example. At one point (some time
back) I looked for but didn't find a way to turn off the suppression from an
external process, and at this instant I can't even recall the API name.
Joe