Oh, to add. I've not had any of these problems stated by the OP. The only issue i encounter is the password (i have special characters and capitals in mine)
Oh, to add. I've not had any of these problems stated by the OP. The only issue i encounter is the password (i have special characters and capitals in mine)
So it's seems that i'm not the only one with this problem.Originally Posted by Stephan
http://www.dual-boxing.com/showthread.php?t=24249
For me it take one of my two cpu (dual core), so 50% of my ressources.
I suppose you are using quad core.
Last edited by Baltyre : 09-01-2009 at 02:07 PM
Software you can't figure out how to configure does not make it buggy software, thread title updated to something more reasonable.
0/10 troll factor.
His first complain is a serious problem who make Keyclone an unusable software.
Seems like only few have this bug, but it's serious enought to propose an unsuported version of keyclone 1.8 until the problem is fix.
2 different people have completely answered the issues he was having. Clean install and see if that fixes the problem. There is no reason to go back to 1.8. There is a problem, sticking your head in the sand in an older version isn't the answer. Debugging it is.
Not Fixed with a clean install of KC.
Then post some more details. This says NOTHING other than "I tried what you said and it didn't work, and I'm too lazy to give any other info I think may be helpful"
Ok.
I try to play with admin and compatibility options to fix this problem.
Don't know why but when i revert back to the initial settings, keyclone now half work.
It detect when a wow windows is close or a process killed with task manager.
(Previously it did not)
But if a wow windows crash. Like, for exemple, big lag in Dalaran, one of the wow freeze and i have to kill it with the process manager or sometimes with wow crash, the title of the wow windows stays on keyclone. (he think the wow windows is still there)
In few seconds, keyclone take 50% of my ressources (one cpu, i'm using a dual core), freeze and i have to kill it with process manager.
I will try to make a video to explain later this night.
I see that a lot of people don't have this problem, but his complain ("If you close one of the wow windows, keyclone.exe fires up to 25% cpu use an hold this. Keyklone.exe dont end until you kill it with the taskmanager.") prove that i'm not the only one with this issue.
Last edited by Baltyre : 09-01-2009 at 03:03 PM
Usualy, when i close all wow windows at once, it's common that one of them crash.
So i purposly make a crash to illustrate my problem with keyclone :
http://anonym.to/?http://virtunys.fr...sh-exemple.avi
I'm not an expert at making video, so sorry if it's not very clear.
That's not a keyclone problem.
If you close multiple copies of Wow at the same time they'll to write the same spot causing the error 303/302 or something. This has been happening since patch3.2 and not before (in my experience).
There are a lot of people with the problem and they're posting on the wow forums. It's incredibly easy to work around, just close the wow clients consecutively and not simultaneously.
Anyhoo, back to keyclone, unless you post specific details I'd have to agree with the other forums posters. We can't help you unless we know exactly what you tried and the error codes/messages/results, if any.
Posting Rules
Reply With Quote
Connect With Us