tech e blog

Well said Primo! I just tried this out myself and it definitely sped up my computer

Most definitely it works

I thought Windows XP managed that by itself?

PPL that don't want to watch the video Right click desktop > new >Shortcut Now type this or past it in the box With out quotes "%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks" the put a name for it w/e you want click finish and put the shortcut on your desktop were ever you want. Your Welcome

I found the video a little blurry, so just to confirm for those who found the same, the shortcut created points to (without the quotes): "%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks"

This one is awesome, it really speeded up my computer. How did you find out this thing? Anyway, thanks alot.!!

it works very well! cause i had a little prob to read this here is the line "%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks" without quotes greetz

Just tried this. I noticed that windows programs like MSN minimized and maximized faster, thats about it :/ How do I know when that this shortcut worked?

it def works. yeee, this will be perfect right before running a game. like supreme commander.

I tried it, i had like 8 widgets showing system stats open when i tried it, here's what i saw: I opened the file, the CPU spiked to about 50-60% for a few seconds, no noticeable difference in ram or anything. However, i did notice that the computer for some strange reason DID behave faster after i ran this, im gonna try some more extensive testing but for now it looks like it works, even if it doesn't do anything noticeable to the RAM or cache.

if this earases "memory" is this just temporary files its erasing? does it shutdown unused processes ?

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 API s 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: Rundll32.exe advapi32.dll,ProcessIdleTasks 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: DWORD ProcessIdleTasks() The API itself is synchronous, so it won t return until the idle tasks have completed.