Screens blank after switch

When I switch from my Primary machine (Vista Ultimate x64) to either of my secondary machines (Vista Ultimate x64 and Vista Ultimate 32 bit) the screens on either inactive machine go black. Not simply the darken feature (which I have disabled) but the machines act like they are no longer getting video signal. If I wiggle the mouse on the individual machines, they come right back to life. If I switch back over to one of the other machines, it also wakes right up. (it does take a few seconds for the display to "warm" back up) This is not normal. When I was usiing the trial, I did not experience these problems. Not that I have purchased the Pro version I find this extremely annoying.
5,004 views 12 replies
Reply #1 Top
I am also having this problem, it makes moving to the secondary machine stutter making the change less then seamless. The main screen also darkens for a moment while i switch to the new screen. I am using the latest version on Vista Ultimate 64 for primary and Windows XP SP2 for secondary.
Reply #2 Top
Can you post your version of MP?
Reply #4 Top
Hmmm . . time to email support@stardock and reference this thread I think.  I can't replicate this.
Reply #6 Top
Hi
I had this problem using Vista32 on primary and XP on Secondary, it was quite annoying as the screen blacked out for about 3 seconds each time it switched. As a temporary work around I disabled UAC on the Vista machine, rebooted, and now everything works as it should.
Give it a go and see if you have any luck
'Rep
Reply #7 Top
I see this post is 2.5 months old. Has anyone come up with a way to fix this?

I am also having this problem, except that I am running two machines both with XP. It only started only 2 days ago, and I have been using Multiplicity for probably 4-6 months. I updated to the lastest version of multiplicity and it is still broken. I am very annoyed and frustrated, and any help to fix this would be appreciated.
Reply #8 Top
Have you updated anything else?  Video drivers?  Anything?
Reply #9 Top
I updated the video drivers and it's still broken.

I started having the problem right after my Time Warner cable internet went out for about an hour. When it came back up the router was not working properly. Rebooting the whole system worked to get the router going again, but I am just lost with this.

Of course I cannot be absolutely certain, but I think that the cable outage somehow messed it up.
Reply #10 Top
I recently bought the standard version of Multiplicity 1.21. I have Vista Home Premium x64 as the primary machine and XP Home on the secondary. I have had the "screen goes black" issue right from the start. I do not have the "Darken the screen when connected" setting enabled on either machine. Here is what I have observed:
- When moving from the primary to the secondary machine, the primary screen goes black while the cursor remains fully bright on the side of the primary screen. It takes around 2 seconds for the screen to fully fade to black and only then does control transfer to the secondary machine. Around 5 seconds after control moves to the secondary, the primary screen returns to normal.
- The fade to black looks like a deliberate fade rather than a video driver bug. The screen progressively fades down to black.
- When the primary screen returns to normal, it does not fade up but rather jumps instantly back to normal.
- When moving from the secondary to primary, the secondary screen instantly turns black and there is no delay in transfer of control to the primary machine.
- Unless I use an input device on the secondary machine directly, the screen does not return to normal until I transfer control to that machine again.
- If I kill the system tray application on the secondary machine, but leave the Multiplicity service running (MultiSrv32.exe) then the secondary machine behaves correctly.
- On the Vista x64 primary machine, killing the system tray application stops all Multiplicity functions. There is no service running that I can see.

Edit: I have sent this information to support, so here's hoping they come up with a fix.