New
#20
lol. yea im just concerned its rudementary/basic similar to the first synergy, and barriers or other non dynamic kvm that function off a designated server and client pc's. That would be fine if i simply needed 1 pc to control the rest - but as indicated i move around quite a bit, and i'd have to move quite a bit more if not for the ability to have another pc's peripherals take over as server dynamically so to speak.
MWB was updated to new version. News was out some time ago, but for a couple of weeks links pointed to old version.
Also Note on the first page, that you have to use the same version on both (all) computers is not true, at least not with version I use (latest 2.2.1.xxx and 2.1.5.xx)
I have successfully updated other computers (with older version) to the new one with the help of new MWB
![]()
@AndreTen,
I have noticed that my MouseWithoutBorders computers can control each other when they are merely connected to the internet [for which, as a public network, each computer is set to be non-discoverable].
The [default] WD Firewall setting for MouseWithoutBorders is to allow it on both Private & Public networks.
Is this behaviour the same with your computers?
My concern is that MwoB must be exploiting some method for discovering my computers on a public network and that others might be able to use the same mechanism.
Denis
Andre,
OK. Thanks for replying anyway.
And I meant to say well done some time ago for your second medal.
Well done,
Denis
Does anyone else experience speed issues when connected to slave devices? When I switch to other monitor the speed is so fast. Even with the relative option it doesn't work for me apparently, it's still way too fast. Yes I tried lowering the speed of the pointer but it's still not slow enough for normal usage. I have to move the mouse very carefully so I can use it at all.
Strange! I have been using MWB for three years with a mix of Win 7 and Win 10 PCs with only one problem. At times the setup for my mouse that I use with my left hand switched buttons depending on whether MWB was in use or not. I discovered that some specialist mouse software from Logitech needed tweaking. I never cured it, but by choosing MWB to always start whether or not I would be using it patched up the conflict.
I suggest you check if you have different mouse software in use.