Buffer Overrun Detected - Visual C++ Runtime Library

Keyclone worked perfectly well this morning. I came back after lunch and tried to login and suddenly I have issues. I get

Code:

---

Microsoft Visual C++ Runtime Library.  A buffer overrun has been detected which has corrupeted the program's internal state . . ..

---

Keyclone will not launch the windows anymore. I am running Vista 64 service Pack 1.

I have 2 real wow installs and the other 3 are virtual links to one of the installs. Thus, I cannot even manually launch the non-real wow installs.

Can anyone tell me how to fix keyclone?

make sure you can run wow normally... if you see the licensing page (due to updates, it is tuesday afterall).. make sure to accept the license for all your wow installs (and update it) without running your wows from keyclone

worst case scenario, try deleting (or renaming) your keyclone.ini and restarting it. that will start it from defaults.

Going to necrotap this thread real quick because it applies to (okay, appears to have solved) the situation I just ran into.

I was using Keyclone with two displays connected to one video card. Maximizer was configured to use various panes on each screen. I updated my video drivers, installed a second video card, and gave the second display to it. Notably, the second display is now DISPLAY3 instead of DISPLAY2 thanks to the two-per-card thing. I reboot after finishing everything, try to start up...Keyclone is now giving a buffer overrun error. D'OH!!!

Okay, so, what happened appears to be the whole WoW license reset thing. WoW sees a completely different video layout, and is pretty stupid about things like secondary displays to start with, even on the same card. So it panics, resets itself to run-once mode, all that. Which makes Keyclone go ZOMGWTF!!@$&&! and die.


So what I'm wondering is - do you have any way to make this type of crash more informative so it doesn't freak out new users like me? Or does WoW not behave "gracefully" enough to handle it better?

Thanks! Loving your work on this little wonder KC!

i've never seen the crash, so i'm not sure what wow is doing on exit.

i'll toss it on the list to look into