Some Keyclone Bugs I am Experiencing on Vista 64 SP1

Hello,



I am running 5 WoW instances on one machine. The specs are: QX9770, 8GB DDR3, 2xGTX280SLI, ASUS STRIKER II EXTREME etc etc.

When I exit keyclone after playing the program does not shut down, even when I right click on the little icon in the tray and then exit it looks like it has shut down but it really has not. I have to go into task manager and manually kill the keyclone process. Does anyone else have this problem?

Also I have a problem (this only happens sometimes) when I shut down keylcone my keyboard no longer works at all. To remedy this I have to unplug it and plug it back in.



I have never encountered either of these problems until using Keyclone. Any tips would be appreciated. TIA.

"When I exit keyclone after playing the program does not shut down, even when I right click on the little icon in the tray and then exit it looks like it has shut down but it really has not. I have to go into task manager and manually kill the keyclone process. Does anyone else have this problem?"

I have this problem as well -- and my fix for it is the same. If I try to launch keyclone again without killing the process it reports that I already have an instance of keyclone running. It's been this way since the May or June revisions.

I run Vista 64 as well.

it's been noted before...

the hang on exit bug happens when you close using the X in the upper right. so don't. right-click the tool tray and select 'exit' instead.

as for your keyboard 'locking up'... that's new. there is an expected 2-4 second delay as keyclone unhooks from windows.

did you install keyclone as administrator? by that i mean (and i really get tired of typing this.. over and over)... right-click the install binary/run-as-admin.. since microsoft doesn't think being logged in as administrator should imply administrator rights. (go figure).

next, you must run keyclone 'as administrator' (same as above)

off topic: the guy @ microsoft that came up with that distinction should be duct taped to the developer's wall o' shame

on topic:
of course.. another solution would be to not use vista in the first place