-
I just got home from work, and I thought I'd killed the Keyclone task, but found that it's still running, so I'll make a few screenshots that may or may not be useful. I'm no programmer so I can't say, I just work in OS/App support :D
A few images from Process Explorer and Task Manager:
Performace tab -
http://img166.imageshack.us/img166/3...perfjs0.th.jpg
Performance Graph tab -
http://img166.imageshack.us/img166/4...erfgeq9.th.jpg
Threads Tab -
http://img89.imageshack.us/img89/331...threvn7.th.jpg
Task Manager -
http://img89.imageshack.us/img89/7493/taskmgrhv5.th.jpg
I do unfortunately not have any Task Manager details from the time before Keyclone hung up.
Generally I cannot see any changes over a short time other than WS Shared and I/O Other. I/O Other is where the spikes on the I/O Bytes performance graph comes from.
I/O Other is increasing by 1 every 4 seconds or so. This may be normal.
System Information:
OS: Windows XP Professional with SP2.
HW: Gigabyte GA-K8N Pro SLI with AMD 3700+ and 3GB Memory. BFG 8800GT and Creative X-Fi Fatal1ty
*Edit:*
I did a quick check after I'd killed the process, and started a new process. I simply started all wow instances (all on the same computer), and logged in (I never entered the game), then closed them all, and closed the keyclone window. For a few seconds the system were not usable, as the mouse disappeared. The Keyclone window disappeared, but the icon in the tray remains, along with a process in the process list. Neither can I access the keyclone menu from the applet in the tray, it does nothing if I right-click it.
There are no I/O spikes in the performance graph, even if I/O Other is still increasing by 1 every 4 seconds.
I've attached my keyclone.ini file (replaced login name with 'username'). Also had to change the extension from ini to txt.