Quote Originally Posted by cmeche View Post
No, on a normal pc. I finally figured out the basics of hkn and got that working fine. At least now, if a rift window closes unexpectedly, I get a rift error message. It only completely disappears with no explanation with keyclone.
Quote Originally Posted by Klesh View Post
Wow... It IS a Keyclone problem, probably the same problems ISBoxer had back in the days (don't know what Lax had to change)...
I read that as it's failing with keyclone and HKN, the only difference is that due to the differences in UI hooking between the two, the crash either displays an error or does not. The root cause of the problem is not keyclone or HKN. I'd bet money on it.