I'm not sure if this problem is particular to 3.5 or predates it, because I've just come back to using Multiplicity after a long absence. Everything was working nicely except I was having difficulty reconnecting after disconnecting from a KVM session, to either computer configured as a secondary. I'd get the screen but couldn't interact with it. I had turned on the "Always use I.P. address option". Troubleshooting, I turned this setting off and the connection began working again immedia
rcobourn
Assuming your monitor has an available HDMI input, and your laptop an HDMI output, you'd do well to connect them via HDMI. Even better, if your monitor supports picture-in-picture, you have an ideal setup. The only problem with this setup is you are not looking at the camera on the laptop, and it appears you are contantly looking off to the side. If your work laptop will accept an external webcam, you can solve this issue by mounting the webcam on your desktop's monitor. You can then continue
Do you have to practice being such an ass or does it come naturally?
I also experienced this problem. This was same day as initial install, after reboot. I traced the problem to a conflict with Ultramon. As a fellow programmer Adam, I wouldn't be surprised to find out that you also run Ultramon. Try unloading Ultramon, run Multiplicity, then run Ultramon. Works here. I'm sorry you got such crappy treatment from Bichur with regards to your issue. If you don't run Ultramon, look for anything else you are running that would likely hook into the video driver s