Quote Originally Posted by 'TheBigBB',index.php?page=Thread&postID=150346#pos t150346
I really don't know, or wouldn't know, but I can say with some confidence that the program sends keystrokes a lot better when you have the system devoting an equal amount of work to each window. Any thoughts? This may explain why someone thought that Clonedkeys was not sending keystrokes as well as I thought it was.
Being that OSX is a *nix based operating system, I looked into a "re-nicer" program. this would allow you to modify the core unix priority levels for a process. I set clonekey at max priority, but it didnt make a difference.
(Duh..... during spikes i barely hit 45% average core usage)

Talking with the author of keywire, i recall him saying that after sending a keystroke to a window, the system would return a "operation completed" message. On the keystrokes that got dropped it still received the "operation complete" message from the system. I could possibly be a limitation or glitch in the OS, and that he would have to devise some sort of work around.

I'm currently at a crossroad personally.

1) make the mac pro my main, and build 4 more "hack-in-toshes" to each run a slave on their own 20"-er, just run the 30's on the macpro, and go hardware

2) bootcamp it, with vista ultimate 64 (yah yah i know.....Eeeewwwwwwww) and keyclone it. pull out a 8800gt and replace it with a GTX280 for use in bootcamp.
i've asked a few boxers on my realm and they use it and dont have a spam-lag on the key

3) gear up my 2 oldest accounts, and retire 3..... move back to dualboxing a pocket healer.

4) suck it up and quit bitchin