In the era of windows3x, although Windows is like a multithreaded process to complete operations, sharing CPU time among multiple applications, giving every application a chance to execute, all applications must be single-threaded. After windows9x/nt/2000/xp/2003, Windows supports multiple threads as fully as UNIX, and Windows itself provides synchronization and scheduling capabilities for threads. So why do Windows Optimizer masters also provide process-managed software? Because the essential difference between windows9x and windowsnt/2000/xp/2003 is that windows9x is a pilot-multitasking operating system, and Windowsnt/2000/ XP/2003 is a preemptive multitasking system (another example of preemptive multitasking system is OS/2). The main difference is that, in preemptive multitasking (windowsnt/2000/xp/2003), the operating system simply suspends the thread to provide the appropriate time slices for other applications, and in the pilot preemptive multitasking system (WINDOWS9X), The operating system relies on applications to periodically recall control of the operating system so that other applications have access to their time slices. Obviously windowsnt/2000/xp/2003 has the ability to provide smoother switching for multiple tasks and threads, because it does not require the care of each application (or the programming skills of individual programmers) in the process of abandoning CPU control. However, windows9x because it does not have this feature, we often find windows9x situations where certain processes cannot be closed (especially when some game errors occur). The user can then use the WOPTI Process Management master to force the shutdown of these error processes. At the same time, Trojan horse programs usually need to reside in the system some process, and some anti-virus software because it can not actively shut down these processes to clean, will require users to restart the computer after the antivirus (that is, can not carry poison antivirus), encountered this situation, users can also pass the Wopti The process management master manually closes these suspicious processes and clears them.
In windows2000/xp/2003, the system's own process management tools (and ordinary process management software) cannot differentiate between processes with the same process name, for example: Users are often puzzled by multiple svchost.exe in the process list. Now it's easy, wopti. The Master of Process Management provides you with a handy differentiator to select the processes that need to be understood, and the first "command line and Parameters" in the process description below the main interface will immediately tell you the command-line parameter information for the process, such as: C: Windowssystem32svchost.exe-k Netsvcs and C:windowssystem32svchost.exe-k RPCSS Although the process name is Svchost.exe, from its parameters, it is the different services that are started. Alternatively, the user can expand the selected process on the main interface to view the command line and parameters.
New task: Wopti process Management Master will open the appropriate program, folder, document, or Internet resource for you based on the name you entered.
End Process: The selected process will end.
End Process Tree: will end the selected process and any child processes that are initiated directly or indirectly by it.
Different processes may contain the same module, even more so that individual malicious programs or viruses inject their own modules into other processes, such as system processes. For example, a plugin that is stored in the Downloaded Program Files directory CnsMin.dll injects space into other processes such as IE. In the previous version of Windows process management, users could check if the process had been injected by clicking "Publisher" in the module list, but it was still inconvenient. Now simple, WOPTI process Management master provides users with a powerful lookup function, users can easily find the specified module in which processes, such as: Input CnsMin.dll, constantly click "Find Next" can easily find their system all injected into the module of the process.
Find:
(1), find the process. Enter the process name keyword you want to find, and select Find target to process. Click "Find Next", Wopti Process Management master will find the items in the process list that match the input, and the WOPTI process management master will automatically select the Find results entry in the process list to facilitate user management of the found process. If there is more than one item in the process list that matches the keyword you want to find, repeatedly click Find next to find the next qualifying item after the existing lookup results until all processes traverse the end. Note: After the end of this round of search, click OK in the closing dialog to start a new round of traversal lookup from the beginning.
Computer knowledge
(2), find the module. Enter a keyword for the module name you want to find, for example: Ntdll.dll, select Find target as module. By clicking "Find Next", the Wopti process Management master will analyze each process in the process list to see if it contains modules that match the input content, and the WOPTI process management master will automatically select the process that contains the module in the process list to facilitate user management of the processes and modules found. Also select the Find result item in the module list. Different processes may include the same module, and then clicking Find Next repeatedly finds the next qualifying item after the existing lookup results until all processes traverse the end. Note: After the end of this round of search, click OK in the closing dialog to start a new round of traversal lookup from the beginning.
Set priority: Sets the priority of the selected process, including: Live, high, above standard, Standard, below standard, low. Note: Under Safe mode, the WOPTI process management master does not allow the priority of a process to be adjusted to live and high. First of all, most operating systems themselves process priority is lower than real-time, if a process to get more CPU time than the operating system, easy to cause system crashes. In addition, do not easily set the priority of the process to high, because the high-priority process from the low priority of the seizure of CPU time until it is idle, and the preemptive operating system if not reasonable prioritization, it is easy to crash.
When you right-click on a process and choose Set priority, you can set the priority of the process.
Click "Save" to generate a text file to facilitate viewing of process information.
View a list of process snapshots with detailed information for the current process.