Dominic Thomas

Based on the ProcessExplorer screenshots, which showed that MPVISTA.EXE was also active on the faulting secondary, Neil suggested that I delete or rename this file in the Multiplicty folder. This program is only supoposed to operate in a Vista environment, so it's not clear why it was running under Server 2003, but after a reboot the system now passes its Troubleshooting function and all seems to be working well. My thanks to Neil, and to Carl for his advice as well.

Thanks, Neil - on their way to you now.

The date of MULTIWIN32.DLL on all systems is 28/08/2006. Running ProcessExplorer on the three systems shows very different results. If you can provide an email address, I can send the screenshots?

Not in my case - the service appears to start correctly, and the only sign (apart from the symptom itself) that there is a problem is that the Troubleshooting function on the tray icon reports "WINLOGON.DLL has failed testing". This seems to be a common problem, from what I'm now reading here, but one without any clear solution from SD as yet...

Thanks for the hotkey tip, Carl - that certainly saves some fuss! My Svr 2003 installation has been working OK for six months or more, though, so not quite like your problem. It's not clear what changed to break Multiplicity, though. Any more thoughts from Stardock on this problem, by any chance? After a wonderfully prompt first response, things have gone very quiet...

Sorry, my clarification needs clarifying - those are reaallyconfusing file names! The Multiplicity folder contains MULTISRV32.EXE and MULTIWIN32.DLL, but no MULTISRV32.DLL as mentioned in your post.

Just to clarify - the Multiplicity folder contains MULTISRV32.EXE and MULTIWIN32.DLL, but no MULTISRV32.EXE as mentioned in your post.

I have a primary running Server 2003 controlling a pair of secondaries, one running Win XP and the other Server 2003. The XP system is fine, but after a reboot of the Svr 2003 secondary this morning, when I try to move the mouse onto that secondary the pointer disappears completely and the keyboard on the primary becomes unresponsive. The only way to wake up either mouse or keyboard is to CTRL-ALT-DEL, at which point they work - until I click Cancel to return to the desktop, when both mouse and

Using Multiplicity Pro V1.02 on a group of two Server 2003 systems (one is the Primary) and one WinXP, and having some problems. All three systems are on the same switch, with 100Mbit/FD connections between them. Firstly, the behaviour of CAPS LOCK is rather unexpected. It only works correctly on the primary - if I turn it on on one of the secondaries, it is ignored completely, if I turn it on on the other secondary the keyboard's NUM LOCK l