>>Well, the process eating the CPU cycles according to Task Manager is rc5des.exe. I don't know off hand what this exe is but I need to find out. It does not show up as an application, only a process. Interestingly enough, it priority is set to "Low". Wonder what it would do if it was set to "Real Time"? :-)
>
>I don't think this is an MS executable. There are no references to it in the current MSDN Library. Try a search on the registry, you might be able to figure out something from there.

Hey George,

I found out what it is. It's some sort of client the guy who set up the machine put on from distributed.net. I havent't had to time to look at it much but i understand tt takes th place of the "null execution process"(?). I.e. if nothing is using CPU cycles, it uses them ... all of them. And it's suppopsed to immediately stop using them if something else wants them. I shut it down. Not only do I not want something like this eating CPU cycles indiscriminately so I can't see what the CPU is doing, but me being the distrustful soul I am, I don't trust it to not cause problems on a machine I'm using as a server. What do you all think?