Evyatar G.,1) From Microsoft's Windows Hardware Development Central (WHDC) - http://www.microsoft.com/whdc/archive/benchmark.mspx#E3E
"Idle Task Scheduling: The ProcessIdleTask API
The file placement optimization, which is done no more often than once every three days, is an example of a task that is carried out when the system is deemed to be idle. System Restore and other features of Windows XP also attempt to defer some work until the system is deemed to be idle. There are also some done-once-after-setup work items that also operate under the Idle Task Scheduling mechanisms.
All of these "idle tasks" are controllable by a system API in advapi32.dll, ProcessIdleTasks. The APIs sole purpose is to allow benchmarks a simple way to force any pending idle tasks to be executed immediately, without having to wait a lengthy period of time.
The API ProcessIdleTasks can be called in one of two ways, from the command line or synchronously from a program. To call ProcessIdleTasks from the command line, use this syntax:
When called from the command line, the ProcessIdleTasks work is done in the background asynchronously. It can take 10 to 15 minutes for idle tasks to complete. Task Manager will report processes running, and the disk will likely be active during this time.
The ProcessIdleTasks API takes no arguments and returns a standard Win32 error code. The definition is:
The API itself is synchronous, so it wont return until the idle tasks have completed"
2) There may be a replacement command, but I cannot seem to find one.
Wednesday, September 09, 2009 12:37 PM
- Proposed as answer by dreamsburnred Friday, September 11, 2009 9:08 AM