Process Lasso consists of
a core engine and a user interface. The two are separated so that users can
completely close the user interface while keeping Process Lasso active, managing
processes. The core engine is run as ProcessGovernor.exe, while the user
interface is ProcessLasso.exe. Running only the core engine results in memory
usage of a mere 1-3MB (typically) and almost no CPU use.
When the user interface, ProcessLasso.exe, is
launched it automatically launches an instance of the ProcessGovernor.exe core
engine if one isn't already running for the current user. When you close the
user interface, you are asked whether you want to keep the core engine running
Each user session is meant to
have their own instance of ProcessLasso.exe and ProcessGovernor.exe. This is so
that they can have individual configurations and process rule sets, and so that
each instance is limited to its own processes.
|Process Lasso Graphical User Interface
This the graphical user interface that serves the purposes of configuring the
product, manually managing processes, and displaying current activity by Process
Lasso in real time. It also provides a graph to view current CPU usage and
system responsiveness. This component is optional and does not need to be
installed or running for proper operation of Process Lasso's core engine
(Process Governor). For usage documentation, click
|Process Governor Core Engine
||This is the core engine that applies process
management rules. This can run by itself for minimal resource consumption.
|Installer for Process Governor
||This utility allows you to configure how the Process
Governor starts at system boot or user login.
||This configuration file holds the process rules and options for
Process Lasso. It can actually be named anything, and be placed anywhere,
including remote shares. You can change its location using the Process Lasso
Management Console, supply command line parameters, or manually editing the
||This log file keeps a record of recent actions. You can disable it
to save a little more system resources. Its size is automatically trimmed
periodically in accordance with the logging configuration in the INI file. The
log can be stored anywhere, including remote shares. You can change its location
using the Process Lasso Management Console, supply command line parameters, or
manually editing the registry (HKCU).