keyclone bug or i'm forced to search at other points?

[empeha]

Usualy every longer gaming session i run into this bug:

The screen gets black for ~1sek, then for ~1sek back to 'normal'. This usually happens 2-4 times in a row and goes hand in hand with heavy lag.
After this, i could'nt quit keyclone on the affected pc. Sometimes keyclone at this point works as it should (without the couldn't quit part), sometimes it does nothing and i need to start a new keyclone application on the affected pc or reboot.

Setup is 3 PC's with Keyclone, only my main and one of the alt pc's are affected.

[Miquexia]

are you using vista?

if so, try to change the keyclone.exe file, rightclick on it >> properties >> compatibility >> Run this program as an administrator.

[empeha]

I'm using XP.

[keyclone]

definite weirdness.

what do you mean by "longer gaming session"? i've been in for 6+ hours without any issues (using xp and vista). are you talking all day? (not that it should make a difference, just trying to understand)

how much memory do you have on the affected machine? how many wows are you normally running on it at the time? (machine specs please)

are you running the latest? v1.7r?

[empeha]

All machines:
keyclone 1.7r
XP

Main: Intel Core 2 6300, 2gb, Radeon x1900xtx (running 1 wow, max details)
2nd: Athlon 64 X2 4000+, 1gb, Radeon XPress 200 (running 2 wow, min details)
3rd: Athlon 64 X2 4000+, 1gb, Radeon XPress 200 (running 2 wow, min details)

i noticed the problem only on the main and 2nd (2nd and 3rd are complety identical except for the wlan card - so this could be a thing, i need to look closer if the problem is not from keyclone).

Maybe Main and 2nd wlan cards disturbed by a microwave oven or something like that.

With longer gaming session i mean that i haven't had this problem in sessions with 2 hours or less.

Edit: i dont have this problem bevor the latest wow patch.

[keyclone]

with 1GB of memory running 2 wows, i'm thinking you are running out of resources (memory) and could be thrashing to disk.

do you hear your disk drive starting to go crazy around that time?

watch your task manager and see what memory is doing during these times.

[empeha]

1 GB works fine, i use aperture to shrink the render area to 680x512 and 600x512 only for ui, the most time i dont need more than 500-600mb for the entire system.
I know the out of memory issue from my 5 wow on 1 pc with 2gb time. Thats not the problem (no disk drive going crazy at this time )
It also occours on the 2gb system, and one of the 1gb systems dont have this problem.
But i'll try to get as much information as i could, when it happend again.
I dont know if the problem is from keyclone, but if the problem occours the actually keyclone application is affected.

Maybe its caused if buttons like shiftlock, numlock, etc. accidently not sync on all 3 systems and i hit a shortcut i dont know about. (i'll check this the next time it happens)

[empeha]

Since i switched of any cpu affinity, the problem didn't occur.

[keyclone]

how did you specify cpu affinity? via a keyclone command or command line? (iow, is there a problem with cpu affinity in keyclone?)

[empeha]

i did it on main and machine 2nd with keyclone, on the 3rd one i've forgotten it. I dont know, if the problem is from keyclone, its the first day of testing it since the wow patch without cpu affinity, so maybe its a wow problem.