You sure picked the wrong guy to answer this and I think that with 12
years of development experience you know a heck of a lot more than I do
about these things! I have about 17 yrs or pc experience but programing
is not my thing. I follow this NG mostly to learn and I don't answer
anything but the easiest thing so that the pros can concentrate on the
tuff stuff.
This is what I think might be going on. cmd.exe is probably not the
culprit here. You may have a rogue application or startup script that
is using or running commands with cmd.exe. Take a look at your registry
run keys and startup folders and see if anything unusual is in there.
Look in your Services Manager to see if anything there might explain the
cmd.exe behaviour. These 2 little applications may be of great help in
finding out more about the processes which could be running or using
cmd.exe and be to blame:
Process Explorer by Systernal:
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml
and Code Stuff Starter 5.6:
http://codestuff.cjb.net/
You seem to be quite sure that you don't have a virus or trojan so I
would think that a service or process is the guilty party. Did you try
using the kill command instead of the Task Manager's TerminateProcess?
The kill command line utility is in the Resource Kit, or probably
available by itself for download somewhere on the net. Sorry that's all
I can think of. See here for more on kill utility:
Cannot End Service Processes with Task Manager
http://support.microsoft.com/defaul...port/kb/articles/q155/0/75.asp&NoWebContent=1
John