Windows kills the kill process based on the process name

File Description: tool software used to force the end of a specified process

Compiling environment: win7 x64 vc2005 SP1 Compilation

: Http://files.cnblogs.com/vk83/kill.rar

 

ProgramNote:

Because some P2P software is used to watch video programs online and download software similar to thunder, the background process on which the program depends will not be completely completed after the program exits, these processes may also use a large amount of network bandwidth for a period of time, which causes the network to be affected after the software is exited, memory usage affects our normal use and violates our personal wishes. So I wrote this software myself, and its implementation method is to call the Windows system interface, that is, Win32 API implementation. It mainly uses functions such as enumprocesses (), OpenProcess (), enumprocessmodules (), and terminateprocess () to terminate a specified process. This program can be called by other programs, so I did not write a window-based GUI application. In the future, it can be called and extended by a GUI panel. Of course, there are many methods to terminate the process. Here I just use the C/C ++ that I am most familiar with to implement such a function.

 

Usage:

Enter kill <process name> at the command line prompt. The process name is case sensitive, for example:

C: \> kill baidup2pservice.exe and press enter to forcibly terminate the background transmission process of Baidu audio and video.

C: \> kill thunderplatform.exe press enter to forcibly terminate the background process of thunder download.

Because some software is not very conscious, such as popular and PPS software, it is often the end of the main program, there is still a process in use network.

if they are conscious, I am much more worried. I am trying to make it easier for my mother to use computers for elders who are not familiar with the taskbar manager, so she does not have to know which processes should not be there or which processes should be there, but when some unconscious programs occupy the network, they do not know, resulting in poor computer usage. In actual use, I call kill to kill the specified process through a monitoring job running in the background. When I make my mother feel that QQ voice and video calls are not smooth, or, after exiting some P2P Video software, you can simply kill all the unconscious processes. Instead of having to understand problems like process and process management.