I don't have Windows 2000 or XP, but you can certainly do this on
Windows 98 and Windows NT 4, which I do have. I would be very surprised
if Windows 2000 and XP have less functionality
I just double checked under XP and the available options for a task are
Daily
Weekly
Monthly
Once
At system Startup
At Logon
When Idle
If you are referring to "When Idle" the lowest setting here is 1 minute. Depending on what Microsoft are basing "When Idle" on, and in my case the machine it is running on is reasonably busy I would assume that idle periods of 1 minute would be pretty few and far between.
In any case, the client can also be run in "daemon mode". It can be
started at system start up, and then will run itself at intervals.
I found when trying to run the client in "daemon mode" at startup on Windows 2000 Professional using:
c:\gdipc\wperl.exe c:\gdipc\gdipc.bat -d 30 -l c:\gdipc\gdipc_log.txt
That if the system relies on a dialup connection, and the connection is not active when the daemon first tries to run ( which is the the case with a dialup at startup) the daemon will fail on it's first attempt and then make no further attempts to update. In Short the daemon only appears to work if a connection is established before it is called ?.
Best Regards,
Lachlan MacColl
>
> To overcome this problem I have written a C++ application that can be
> loaded at startup which allows a batch file to be run every "X" seconds. It
> runs the batch file in a hidden window which closes after execution.
>
> If you are interested in looking at this application for the possible use
> of Windows users I would be happy to send you a copy and provide it for free.
>
> Best Regards,
>
> Lachlan MacColl
