Set up keystroke logging in EXCEED 10.0

[jmckinzie]

I am trying to setup keystroke logging in exceed....to track my commands typed...

I looked at the help in exceed and it says:

If you encounter problems related to PC-to-host interactions, you can use either the Trace utility or a command-line trace to find a solution.

Creating and Enabling a Trace

A trace is a diagnostic tool that logs PC-to-host interactions to the hetrace.txt file located in the user's My Documents directory. The trace utility captures all keystrokes, commands, and selections on menus and in dialog boxes. It also records all communication activity. After you have reproduced the steps that caused the problem, you can view and analyze the logged data.

To enable a trace, press Ctrl+Shift+T. This key combination starts recording events to the hetrace.txt
file.

Note: If you modified default keyboard mappings, this procedure may not work. To reset the default settings, open the Keyboard Mapping dialog box, select the letter T on the keyboard and press Default.

I follow the directions exactly, and it spits out this in the file...

[09:35:02.573] [0] Socket Recv., Rc: 2, WSA Rc 0, Input Size 20000
[09:35:02.573] [0] Recv completed. Data follows:
0D 0A
[09:35:02.573] [0] Blocking Receive events...
[09:35:02.573] [0] VT Parser: ctrl (0D), CurPos 107382, Args[0..2] 0 0 0
[09:35:02.573] [0] VT Parser: ctrl (0A), CurPos 107380, Args[0..2] 0 0 0
[09:35:02.573] [0] Unblocking Receive events...
[09:35:50.043] [0] Socket Recv., Rc: 29, WSA Rc 0, Input Size 20000
[09:35:50.043] [0] Recv completed. Data follows:
1B 5B 37 6D 72 6F 6F 74 40 63 66 63 61 70 30 31 64 3A 2F 6F 70 74 0D 0A 23 1B 5B 6D 20
[09:35:50.043] [0] Blocking Receive events...
[09:35:50.058] [0] VT Parser: DO_SGR (2AF), CurPos 107510, Args[0..2] 16 0 0
[09:35:50.058] [0] VT Parser: r (72), CurPos 107510, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: o (6F), CurPos 107511, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: o (6F), CurPos 107512, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: t (74), CurPos 107513, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: @ (40), CurPos 107514, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: c (63), CurPos 107515, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: f (66), CurPos 107516, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: c (63), CurPos 107517, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: a (61), CurPos 107518, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: p (70), CurPos 107519, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: 0 (30), CurPos 107520, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: 1 (31), CurPos 107521, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: d (64), CurPos 107522, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: : (3A), CurPos 107523, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: / (2F), CurPos 107524, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: o (6F), CurPos 107525, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: p (70), CurPos 107526, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: t (74), CurPos 107527, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: ctrl (0D), CurPos 107528, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: ctrl (0A), CurPos 107510, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: # (23), CurPos 107640, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: DO_SGR (2AF), CurPos 107641, Args[0..2] 0 0 0
[09:35:50.058] [0] VT Parser: (20), CurPos 107641, Args[0..2] 0 0 0
[09:35:50.058] [0] Unblocking Receive events...

I have attached the entire file for you're viewing...

How do I set this up to display the commands typed and their order?

-TIA

[OldSchool · Accepted solution]

the keystroke loggin in exceed isn't going to help you if what you are interested in is the commands typed at the shell prompt. for that, you need to examine the History file. Implementation depends upon shell used. refer to the man pages of the shell in use, or post which one for more info. please.

[jmckinzie]

Thread is closed as I have found no viable solution.