Double Keys

I'm using KavoomKM to share keyboard/mouse across 3 pcs

I've got the screens setup like :
PC2 | PC1 | PC3

http://www.fivedragons.org/forum/pho.../medium/5b.jpg

My keyboard and mouse are physically connect to PC1, when I use keyclone to broadcast to the other two machines it works as expected if I type in wow on PC1, however if I type in wow on PC2 or PC3, I get double keys, so if I press "1", I get "11" etc

I think this has something to do with the interaction conflict between KavoomKM and Keyclone. I've also tried Octopus and got the same behavior.

I was wondering if anyone else has experienced this and knows of any workarounds.

PS - keyclone is great software, not complaining, just seeing if anyone knows a workaround.

I'm no expert by any means (I'm just browsing the forums at random) but it seems likely that keyclone and KVM are probably both sending keystrokes to your drone computers.

Also, nice setup. Does the cat have a purpose beyond stepping on the keyboard and wiping you? :P (that's all mine ever does, though yesterday she saved me by stepping on my Earth Shock button just in time to nuke an alliance's heal)

I use keyclone and Kavoom and get the same thing.... I use override (mute) when i need to type and this works fine. Make sure that you have your cursor parked on the "main" monitor before you push override, or else mute doesn't work. This sounds like a bigger pain than it actually is.

Hooks work like this. The last application to install the hook, the first in the chain it goes. The first app in the hook may prevent latter ones from getting events. So if you run keyclone after kavoom, and kavoom is on a client PC, the chances are, keyclone would send keys to the client as well. This is the reason Octopus has the "detect keyclone" option and attempts to jump in front of it. So I'm suprised that doesn't work, (it defaults on If i remember correctly). Theres a variety options to programmers of course, but otherwise you could run kavoom after keyclone and hope Kavoom is coded to cut off the hook chain on clients. That also assumes keyclone is not reinstalling its hooks during runtime, or doing anything to trigger hooks on kavoom clients (if applicable), and so forth. See all the scope of possibility... :wacko: