|
|
|
|
Winlogger Help |
Key Features
Getting Started
Menu
Viewing the Log
Viewing Old Logs
Preferences
Exporting Logs
Registration
Reasons to use WinLogger
Suggestions to make Winlogger Work Better
Key Features
1. Simple view of all user navigation
2. Invisible footprint
3. shows events for current day, chronologically
4. Provides audit trail for user activity
To start using Winlogger, select "winlogger" from the main menu
(start button, program files). Winlogger will automatically start on startup
of the machine (the shortcut is put in the startup folder). Once winlogger
is running, an icon will show in the system tray. Once you see the icon,
Winlogger will be logging all your mouse and key strokes. This log is stored
on your hard drive. This file is private to your machine. This file is in
no way communicated to the outside world. Winlogger does not use the internet
in any way (except to show the help page when the user requests). Winlogger's
sole intent is to quickly and easily show the history of user navigation.
By righclicking on the WinLogger icon in the system tray, a menu will
popup. The menu items are:
| 1. Open Viewer |
Will show the user the current day log. See Viewing
the Log for more details. Also activiated by double-clicking
on the icon. |
| 2. Task Player |
Will start up the TaskPlayer application. TaskPlayer
has many complimentary features with WinLogger. See TaskPlayer
Help. |
| 3. Options |
Sub Menu: Allows the user to choose from Exporting
a Log, Viewing an Old Log, or changing Preferences. See the header
items for more detail |
| 4. Start/Stop Logging |
Toggles between start logging and stop logging. |
| 5. Help |
Brings up a browser looking to this web page. |
| 6. About WinLogger |
Shows an About Dialog Window containing the verion
number. |
| 7.Shutdown |
Stops Logging, and exits WinLogger |
The user can view the log by either double clicking on the icon in the
system tray (bottom right of the screen), or by right clicking on the icon,
and selecting "open viewer" menu option). The viewer window will
then show up. The user events show up chronologically. Only the user events
for that day will show. To see user events from past days, the user must
use the companion product TaskPlayer. The user will see a list of user events
that has been performed by the user. 1 line will show for each mouse click,
and 1 line will show for a set of keystrokes. The number of the event, the
time of the event, and the window name are shown on the screen. If the user
moves to another window in the course of operation, then a new line will
show in the log. All the key strokes will show that the user types in. Special
characters are shown in '<key>' to designate special keys. For example,
the control key is shown as <CTRL>. Please see the example
log screen for more details.
The mouse clicks are also shown in the same manner. The time the user performed
the click, the window the user clicked on, and the number of the event is
shown. Also, the text label under the point being clicked is shown. This
label identifies where the user clicked the mouse. Other information is
also shown with mouse events. This other information can be windows closing,
start button pressed, vertical or horizontal scroll bars moved, title bar
clicked, and task bar clicked (bar on the bottom of the screen containing
all the current applications). If no recognizable label is underneath the
mouse when the user clicks, then the application will show "clicked
x,y". This is a rare occurence when the only information about a mouse
event is only "clicked x,y".
The user can also right click on a task to see the image that was captured
when the user performed the click. This is useful in determining what the
user was clicking on when no words or letters were recognized by WinLogger
capture engine.
The user can view old Logs by right clicking on the system tray, selecting
options, and selecting the on the "View Old Logs" item. This
option always the user to view prior day activity. All activity is stored
in case the user wants to view history of user. The logs are broken out
into days. Once the user selects the particular day, then the log view
window will appear.
The user can view and change the preferences by right clicking on the
system tray, selecting options, and selecting the on the "Preferences"
item. Following is an explanation of the preferences:
-
Empty Image Directory Nightly
-
this preference controls whether the images that
are associated with click events are removed nightly. The daily log
files are automatically archived each night. The images may also be
if this preference is false. If the preference is true, the images
are removed nightly. The big reason for this preference is to minimize
the amount of disk space WinLogger needs. The archived logs could
grow to Gigs if this preference is false (this large size would be
over months of user activity).
- Empty Log
- a system check to see if the hard drive is getting full. If this preference
is checked, then WinLogger checks to see if the Hard Drive free space
is below the specified threshold. If it is, the WinLogger will remove
the current day images. (typically in the c:\program files\blinc\log\objs).
This preference was designed to keep the system functioning if WinLogger
has created many image files (more than the system could handle)..
The user can export a log by right clicking on the system tray, selecting
options, and selecting the on the "Export" item. This feature
is to allow a user to export the contents of the log into a readable export.
The user first selects a single log (a user can export an older log as
well). Then the user can select the columns which is to appear in the
export. Other options allow the user to select the export file name, and
whether the log should be emptied. Exporting allow the user to print the
logs, using another application to format the log. Also, searching for
a particular item in a log can be accomplished in the same fashion (export,
then opening the file using another application).
Please go to the registration web page to
get the registration code. The free trila version will expire after 30
days.
Quality Assurance people will be able to tell the developer exactly how
the bug or error was created by showing him the current log.
Mission critical applications will have audit trails of exactly the input
the user performed.
Help Desk users will benefit if their users they are supporting have
Winlogger installed. The help desk could view the users log and tell exactly
what the user performed to cause the problem, error or bug.
Other users can benefit from WinLogger by helping them find a lost password,
or finding out the sequence of events that caused the problem. Also, if
an application crashes, and the user losses their work, the companion
product TaskPlayer can re-play the events!!
Saving time and effort re-keying the lost information.
1. installation of winlogger needs Admin Privs!
2. To show pop-up descriptions for folder and desktop items
3. Remove Personalized Menus
-
Open Start Button, Settings, Taskbar and Start Menu
-
Check-off 'Use Personalized Menus'
4. Do not use transition effects for menus
|
|
