Win32 Client Trace Option |
Virtual Machine |
 |
With the PROIV Windows GUI Client (PROIV.EXE or PROIV.OCX) it is possible to record a log file of all the user interaction with the client and all data sent to and received from the PROIV Virtual Machine. Given a suitable log file, it is possible to know exactly what actions the user performed, and what the PROIV Virtual Machine actually sent to the client.
The log file options are enabled in the [Settings] section of the Client INI file, pro4v[n].ini. For example:
traceflags=*bkmx
logfile=c:\tmp\pro4.log
The traceflags setting controls what is logged. The following table summarizes the trace flag filters:
|
Trace Flags |
Description |
|
* |
General information |
|
b |
Buffers sent to or received from kernel |
|
k |
User Keystrokes |
|
m |
User mouse operations |
|
x |
DDE operations |
|
W |
Winsock calls |
|
Q |
Queued hint processing |
|
z |
Hint buffer / argument parsing |
|
T |
Telnet |
|
|
|
|
= |
[debug Client only] dump data |
|
> |
[debug Client only] function entry |
|
< |
[debug Client only] function exit |
|
h |
[debug Client only] hint processing |
|
.… |
[debug Client only] many other settings for internal use |
The most useful traceflag settings are:
-
‘*’ for general information
-
‘b’ for buffers sent to or received from the kernel
-
‘k’ for user keystrokes
-
‘m’ for user mouse operations
-
‘x’ for DDE operations
The logfile setting is simply the name of the file into which the log will be written.
 |
The log file can get very large, so it is advisable to only enable the logfile when attempting to reproduce a problem |
Since the log file is overwritten each time the Client is run, once a problem has been reproduced you should copy the log to another file. The following is an example of enabling many options for a debug client:
[Logging]
File=c:\tmp\proiv.log
Filter=>bchkxwHRWQ
Topic ID: 750068