Printable View
I'm not sure if updates are still being done actively to this application but personally its what i use for multiboxing and love it. However I have run several times into an issue with closing the server unintentionally with the 8x Esc that is present in this version. I was wondering if it might be possible to get a copy of the source or if the current maintainer could add a checkbox to disable this feature if we so chose.
thanks for your time!
Hello there. I've been reading this forum for some time now and I finally decided to give multi-boxing a go, actually dual-boxing (in World of Warcraft) :)
I have 2 PCs (I'll give the specs in a momment) and I've been toying with 3 apps basically:
- Synergy: it worked superb when it comes to moving from a desktop to the other and stuff, I was really impressed. But the camera spin is driving me nuts, despite the fix posted already, so I decided to move on.
- Multiplicity: it worked just like Synergy for me (at least keeping in mind my current needs) just without the camera problems. I don't mind buying the product, but it's not able to do all I need it to do.
- Multibox: now this is the one giving me serious headhaches. It has all the goodies from the 2 above plus some more, making it the best option for what I'm looking for (imho). But I'm having some trouble setting it up (see details below)
My 2 boxes are something like this:
- Box #1: it will serve as server and client. It's a PIV 3,4Ghz with 2Gb RAM, a rather decent ASUS motherboard, etc etc. SO is Windows XP Pro with SP2. SP2 firewall is disabled. I've also turned down any firewalls in this box while testing.
- Box #2: it will serve as secondary client. It's a PIV 2,6Ghz with 1Gb RAM, a formerly decent ASUS motherboard, etc etc. SO is Windows XP Pro without SP2 (I'll have to wait at least a couple of weeks before I can install it). No firewall software running during my testing either.
Now my problem:
- I run the server app in box #1.
- I run the client app in box #1.
- Server detects client #1 - OK.
- I run the client app in box #2.
- Server detects client #2 - OK.
- As soon as client #2 connects my mouse slows down loads and I cannot interact with the server app UI.
- A few seconds later client app in box #2 disconnects and I get the well known "01:31:40: Connection lost: Next attempt in 30 seconds."
And that's it. I cannot get past that point.
So far both boxes can see each other (they can share folders and stuff), I've made both Synergy and Multiplicity work and I've run tests with both without any problems of that kind. Yet I fail at making Multibox connect properly.
Do you have any clues or solutions? If so, those would be most appreciated. Thank you in advance :)
EDIT: I've been doing some more testing today. I've tried running the server in my box #2 just to see what might happen. And... it worked. So basically if I use my box #2 as server and box #1 as secondary box everything goes ok. But if I do it the way I'd like to do it (box #1 as server, box #2 as secondary box) it won't work.
Meh. Any ideas? Thank you again :)
I run multiplicity and keyclone on my 5 box. I used to have synergy and multibox but a couple of my pc's kept having very bizarre crashes (although connecting was fine) which started to get infuriating.
Since I made the change it's been rock solid and the crashing has stopped. Keyclone is $10 per license but I think its worth it (plus it also has the functionality of Autohotkeys which is a bonus).
See link below:
http://solidice.com/keyclone/
I distrust any application t hat makes outbound unknown connections (IE it wants to check its license without asking you) I have a phobia of being keylogged and that app seemed a little fishy when i looked into it.
Hmmmm...thats a very valid point and wasn't one I had previously considered. I'm sure the software is perfectly fine (and does work well) but it does raise a doubt so I think may just bite the bullet and buy some wireless keyboards.
I think I would've ended up buying a hardware solution anyway and, at the very least, it'll be a bit more reliable! :-)
Try adding enties to your host file for all your local machines. I had a very similar problem, detailed elsewhere, a few months ago and tracked it down to a reverse DNS lookup on the connecting node name timing out for some inadequately explored reason.
Entries in the host file for all local machines fixed it.
Thanks a lot, Otlecs. I did as you suggested and it's working now :D Time to get used to the keyboard broadcasting part.
g'afternoon,
i created keyclone originally for Shadowbane. My guild was facing certain defeat against an enemy with 5x our population. My first thought was that we needed a force multiplier... and since the game had just gone free, keyclone was born.
the only reason i decided to make it for sale was to limit the whining from the other guilds. if i did not make it available, complaints about cheating would have errupted (which happened anyhow). players had been multi-boxing for years, but keyclone made it far too efficient... and so.. the dead spoke.
anyways, the reason i tied it to the cpu was to limit the number of enemies i would have to face using the it. a side bonus was that it helps with beer money. in order to properly tie it to the cpu, i had to verify the license.. which is done in open text (well, the response code is encrypted, but that's inbound)
if you can think of another solution, please let me know.
oh yea, and if you guys care... i usually use it with 4 machines, running 1-6 accounts per box each with a keyclone. i then type in the main keyclone ip:port and they all connect as one. its not tied to any one game, and works VERY well with WoW (I was surprised how well it worked compared to SB).
in one test, i had 3 members of my guild tie into my keyclone (forwarded a port off my firewall)... and i was running 24+ characters on noobie island in SB.
if you guys want something more added to keyclone, just let me know. and if you have any cool video using it, send me the youtube link and i'll reference it on the keyclone page.
have fun,
kc
I'm trying to use both Synergy and Multibox with my dual-box setup, but the second computers WoW client gets disconnected to the loginscreen too often for comfort, both in and outside of combat.
The hostsfile has been modified (network behind a switch), both computers have had their network settings set to default and to various combinations, but I've had no luck getting it to not disconnect the alt.
(Windows XP, both computers have nForce motherboards and nForce network adapters on-board - I heard that could mean trouble, nothing that I know of can explain this behaviour.. unless I simply have a bum cat5 cable with the second computer? Will try and return if it solves it)
(edit: Might very well be connected to http://www.dual-boxing.com/forums2/v...isconnect#2668 , only seems a lot more rampant when using Syn/Mbox - even when simply standing still and not following it disconnects.)
Can multibox broadcast input from x-keys ok? I've had a look through the forum but can't find a specific answer. Best I could find was xzin saying it should work. Anyone actually using x-keys/multibox?
Thanks and apologies if it has been posted and I couldn't find it :)