Windows 7 + keyclone -> WoW windows crashing, and keyclone stops responding.

[Vecter]

Running Windows 7 64bit myself with 6gb of ram. Using Keyclone with 3 clients and maximizer. If I do not swap I have no problems. If I swap with 1 of the other clients I tend to not have any problems (pretty rare.) However once I start swapping with that 3rd client things tend to go downhill and I will lose mouse active window and Keyclone broadcasting. At first it was pretty inconvenient as I would shutdown all clients and keyclone and restart. However I soon realized I could just restart keyclone, manually add the 3 clients and set each maximizers position and be running full speed in about 30 seconds. Not bad (unless I lose that connection in a tough spot )

[D3K17]

Having the same problem here, I do not swap at all. I found windows 7 to be much more faster than any other OS when multiboxing with wow. I can get a good 12 or 20 minutes work of playtime with keyclone working, then boom the window disappears and the only way to remedy it is to quit all the wow clients, search for keyclone in the processes and quit it.

What is interesting though is, I 4 boxed on my macbook pro using it (4GB ram, 2.4 C2D, Windows 7 build 7000) and I never ran into any issues of this sort, so obviously I am doing something a bit different on my desktop.

Specs: Mac Pro Nahelem, 12 GB memory, 2x 2.93 Octad, Radeon HD 4870 X2 + Radeon HD 4870 Mac Edition running windows 7 build 7000 beta.

I am going to fiddle with some options to see if I can get it working stable again.

[Starbuck_Jones]

Windows 7 is just about to get the boot from my box. Its perdy, but there are so many little things that just keep going wrong. The Keyclone thing is one of them. I played last night just fine. Logged off, but left the wow login windows up, came down the next day and I couldnt get keyclone to do more than one keystroke push and it would quit working. Restarted it, rebooted, nothing. Ran it as administrator and it worked fine, Why it quit working when I just walked away from it last night is beyond me. Why I had to run it as an admin when I didnt before is beyond me.

Synergy isnt working right either for me. It was fine, then for no reason that I can find it started to do the super spinny thing on the host box. Normaly it only does that on client boxes if you dont lock the mouse. I have no fix for this problem yet or why just out of the blue it started to do it. But this is unacceptable with my setup and is a real deal breaker.

I cant get the screen saver to reliably work. most of the time it flat out wont kick on and when it does, any kind of hickup aborts it like the windows system messages that tell you dont have defender turned on even though ive told it a half dozen times not to notify me. I have a special case setup where I cant turn off the main monitor so I rely on he screen saver to not burn the windows desktop into it.

Twice now after reboots its uninsalled and reverted the Nvidia driver from the beta to the windows native driver.

So when I get back from my long weekend on thursday, im going to give it a few more trys, but I already downloaded vista 64 off of msdn. I would prefer to use xp64, but msdn doesnt have a 64bit version with service packs slipstreamed in and I need at least sp2 for the raid driver to work as its not available for download after it was intergrated into the OS. kinda like USB 2.0 drivers were.

[keyclone]

on vista, always run keyclone (and vent) as administrator.

[confusedtx5]

So when I get back from my long weekend on thursday, im going to give it a few more trys, but I already downloaded vista 64 off of msdn. I would prefer to use xp64, but msdn doesnt have a 64bit version with service packs slipstreamed in and I need at least sp2 for the raid driver to work as its not available for download after it was intergrated into the OS. kinda like USB 2.0 drivers were.

You can get a free program called nLite which you can use to slipstream the service packs onto an install disc yourself (or the individual raid driver). And do cool things like add in the cd key and if you do it correctly, you can setup the install so you can start it and walk away, come back in an hour and its done. I had the same problems myself, but my raid drivers could only be manually added with nLite. fyi, the Vista version is called vLite.

[Simulacra]

on vista, always run keyclone (and vent) as administrator.

have I told you lately that I love you ?

Just inatlled windows 7 build 7100 from using xp and of course had no idea what the hell this OS is all about - I wondered WTF is going on - thx KC

[Otlecs]

for an operating system to demand 6GB of memory, when an older one do just fine with 3GB running the same software, well...thats shit in my book

You need a new book. Really.

Adding more features to an OS doesn't usually make it demand less memory.

With memory being as cheap as it is these days, coding for minimal memory usage tends to take a distant second place to coding for high performance which can include things such as avoiding alignment faults by deliberately "wasting" memory.

On-topic though, this discussion - and the comments from both solidly encamped sides of the discussion - reminds me of a similar discussion here a long, long time ago when I was looking for Vista support, although I didn't even manage to secure a "on the list" before I dived in and had a go with it in any case

It's good to know that there are actually problems with KC and Windows 7 though - I'll be sure to keep that off my multibox machines until they're resolved.

Thanks for the heads-up.