| How to use
No matter
what kind of designing tool you select (Visual c++, Visual basic, Delphi, etc.)
You can use the Paq keylog engine.
Keylog
engine is an executable program named log.exe.
After you
run log.exe, the engine is started and begin to log. The log files are stored in
the "log" directory of the same directory which log.exe is putted.
log.exe [stop=false|true] [autostart=true|false] [logfile=filepath]
[exit]
Details
using information:
log.exe
stop=true autostart=true
means
Keylog engine is stopped and will be automatically started when computer is
restarted.
log.exe
stop=false autostart=false
means
Keylog engine is started and will not be automatically started when computer is
restarted.
log.exe registercode=********* registercompany=****** registername=******
means Keylog engine is registered with the specified register code.
If the register code is correct, the keylog engine will be
successfully turned into a registered version. You must use the
correct registername and registercompany which you provide when you
purchase, otherwise there maybe unpredictable error.
log.exe logfile=c:\aa.txt
means Keylog engine will write the log text into the file c:\aa.txt
log.exe exit
mean keylog engine will exit completely.
NOTE:
stop=true, autostart=true, stop=false, autostart=false is case sensitive and
there should be no inner spaces.
log.exe use a memory buffer to keep log text in the memory
temporary. We can run log.exe without any parameters to write all
the buffer text into log file. Each time when we "run log.exe exit",
all the text in the buffer will be written into log file then the
engine will exit.
NOTE:You can rename
the log.exe to any name. E.g. my.exe
Visual C++
example:
eg. the
path of the log.exe is c:\yourprogram\log.exe.
...
ShellExecute(NULL,"Open","c:\\yourprogram\\log.exe",_T("stop=false
autostart=true"),NULL,SW_SHOW);
...
NOTE:You
can use notpad to view the log results. Some times you have to wait a short time
to view the newly logged results because there is a buffer to store logged
results in the memory. If your program need to open the log files, close the
file handler as soon as possible to avoid file share conflict.
For other
designing languages, please see the reference book for the instruction of a
shell execution.
|
