process tamer now functional

[garnet]

I'm not sure exactly what the problem was or exactly what the cure was. I did reinstall my system from a mirror copy and now everything is fine. Thanks for your efforts to help. I would not know what to say to jvaudrey who seemed to be having the same problem as myself. I will provide a textfile attachment of my current services profile if this would of help.

[FHM1]

To give an answer to garnet, why reinstalling the system helped:
The longer you're working with Windows, the more residu of opened files clutter up your harddisk. Even cleaning up and defragmenting does not clean up your disk entirly. Process tamer will then not be able to get a fix on where exactly it should look for the process to tame, because it gets mystified by windows. Reinstalling solves this problem.
For me Process tamer does a nice job in taming CPU usage, but there is another problem in your system that it doesn't handle and wich can and will make your system  become slow and "not responding" and that is if you use many programms at the same time or after one another windows takes a lot of time of cleaning up the threads and in the worst case create a stack overflow in the GDI resources thus rendering your system to be nonresponding. Adding a Ramcontroller helps out for a while, but a reboot does a better job.

[f0dder]

The longer you're working with Windows, the more residu of opened files clutter up your harddisk. Even cleaning up and defragmenting does not clean up your disk entirly. Process tamer will then not be able to get a fix on where exactly it should look for the process to tame, because it gets mystified by windows. Reinstalling solves this problem.

-FHM1

This has nothing to do with it - process tamer doesn't even know nor care what file is used for a process it's taming.

The real answer is "windows works in mysterious ways, and computers aren't really deterministic though people claim they are"

windows takes a lot of time of cleaning up the threads and in the worst case create a stack overflow in the GDI resources thus rendering your system to be nonresponding. Adding a Ramcontroller helps out for a while, but a reboot does a better job.

-FHM1

Trying to sound smart? That was absolute gibberish. "Stack overflow in GDI resources"? Gibberish. "Adding a Ramcontroller"? Can't do that, part of either the chipset or (in case of AMD64), the CPU.