Greetings,

Another question I have is about running jobs at user "idle" time. I am testing a job which should run after (say) 15 minutes of idle time. In order to test this, I set my screensaver to set in after 1 minute. After this minute expires the screensaver sets in, but the job is not started. What could be the problem?

Many thanks,

Marcel de Haan.

Which Windows version do you use?

In the Windows NT/2000 only the foreground window is notified by the Operation System when screen saver is started. Therefore the "idle" job will start only if the 24x7 is running in the foreground. There are several workarounds available but the implementation depends on the version of Windows.

: Greetings,

: Another question I have is about running jobs at user "idle" time.
: I am testing a job which should run after (say) 15 minutes of idle time.
: In order to test this, I set my screensaver to set in after 1 minute.
: After this minute expires the screensaver sets in, but the job is not
: started. What could be the problem?

: Many thanks,

: Marcel de Haan.

: Which Windows version do you use?

Currently I use Windows 98.

: In the Windows NT/2000 only the foreground window is notified by the
: Operation System when screen saver is started. Therefore the
: "idle" job will start only if the 24x7 is running in the
: foreground. There are several workarounds available but the implementation
: depends on the version of Windows.

: Currently I use Windows 98.

On Windows 98 you can use the following technique:
Setup your job as a script to run all day every minute
In the script put something like the following

Dim bActive, boolean
// Win API constant: SPI_GETSCREENSAVERRUNNING = 60

Call "user32.dll", "SystemParametersInfo", "uuBu", FALSE, 60, 0, bActive, 0
ifThen bActive, DO_SOMETHING
.....

if bActive is TRUE then it indicates that the screen saver is running