Pro Version not working

Connection ok, switching not, looses M / K

from Stardock Forums
Hello,

Multiplicity Pro does not work, Trial did.

I tested Multiplicity and bought the Pro version. But now the program doesn't work correctly.

I did on both PCs:
Uninstall Multiplicity
Reboot
Install MUltiplicity Pro
Reboot
Activated Multiplicity Pro
Set one machine to master and the other to client
Set the client to "the right of the master"
The machine correctly connect to each other through multiplicity !! (trayicons get color, also when activating the "darken screen" option the client goes dark !!)

The error:
Now when I move the mouse to the right screen edge of the master it never appears on the client.
Also both (master AND client) stay "darkened" if the "darken screen" option is turned on.
From that point on i cannot access ANY pc !
The mouse and keyboard inputs go to neither the master nor the client !
Hitting Ctrl-Alt-Del shows the taskmanager BUT does not put the focus back to the master. Both systems stay "darkened" !

From that point on the only thing I can do is reset the master pc.

I tried de- & re-installing multiplicity pro a coupple of times. This did not help.

Also the Multiplicity Trayicon seems to constantly "blink". As if connection is lost for 1 second or so.

Note: NOTHING changed in terms of hard- and software except uninstalling the trial an installing the pro version !
multiplicity
8,566 views 23 replies
Reply #1 from Stardock Forums Top
I just tested a bit more and using hotkeys I am able to correctly switch back to the primary screen.
Accessing the client does not work though.
Reply #2 from Stardock Forums Top
I tested the LAN connection between the 2 PCs with
ping [ip of client] -n 1000

Not one ping was lost !

LAN connection is stable.
WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from WinCustomize Forums Top
Are you using teh computer name or IP to connect?  Try using the IP.
Reply #4 from Stardock Forums Top
I am pretty sure this is a BUG.

A bug caused by the "up to 6 screens" feature.

As neither the master nor the slave get the focus and inputs I guess that a THIRD actually not configured "ghost PC" gets the inputs. Probably an error in the networking code of M Pro...

Man I should have bought the cheap version after all ...
Reply #5 from Stardock Forums Top
Yes I am 100% sure.

Because using the "darken screen" feature I see the slave pc "darken" its screen as soon as I start Multiplicity on the master.
Reply #6 from Stardock Forums Top
Ups forgot to answer:
I use connection by ip.

For testing purposes I use
10.10.10.10/24
and
10.10.10.11/24
Reply #7 from Stardock Forums Top
i have the same exact problem. it can connect, but when i mouse to secondary, it disappears from primary but fails to control secondary. ctrl-alt-end seems to put the mouse back to primary ok

yee haw, reminds me of when i tried to use 1.0 last year.

vista64 primary, xp64 secondary
wireless on primary, wire on secondary

update-
i noticed the tray icon seems to flash to black monitors about every 10 seonds, for 1 second. so it shows the colors...then flashes to black and back to colors...about every 10 seconds. i have a ping-t going with no drops. i'll get periodic bumps from 1ms to 50+ms, but not related to this 10 second timing (and in fact very infrequently)

Reply #8 from Stardock Forums Top
Oh right. I forgot to mention that both my machines run Windows XP x64

This seems to be a 64bit or at least XP64 related issue.
Reply #9 from Stardock Forums Top
It is pretty frustrating that the licensed version does not work. My company tested multiple programs like Multiplicity and the trial was working top notch. Now we bought five licenses and can't use them at all.
Reply #10 from WinCustomize Forums Top

m4ko: Have you contacted support?

jbranc: It sounds like your secondary needs MP reinstalling.  A disconnect every 10 seconds would point to a much older version of MP being on the secondary and the loss of keyboard & mouse instantly would point to missing dlls.

Reply #11 from Stardock Forums Top
Hm.

I had multiplicity trial running on both working great.
Then I installed pro version (from the same exe-file of the same usb-stick) and it didn't work.
Then I re-installed the pro-version about 5 times now to no effect.

Do you have a list of DLLs that are installed by multiplicity ?
Or is there an installation-log available somewhere ?

Probably something went wrong with the un-install of the trial leaving a DLL behind or something like that.
Reply #12 from Stardock Forums Top
Forgot to answer again ^^

Yes I have created a ticket with ID PXI-728994

I have postet 3 or 4 times there already but have not received any answers yet.
Reply #13 from Stardock Forums Top
neil - this was a clean install on a new box. i stopped using MP for a while due to the frequent orphaned cursor on the primary forcing me to hard-reset. thought i would try again and the very first connection to the secondary forced a hard reset on the primary......
Reply #14 from WinCustomize Forums Top
Pressing Ctrl-Alt-End will terminate the MULTIPL.EXE process on the primary machine. This will move the keyboard and mouse focus back to the primary.  That should be mreo useful than the hard reset.
Reply #15 from Stardock Forums Top
yes - that works sometimes. othertimes, it does not.
Reply #16 from Stardock Forums Top
neil - this was a clean install on a new box. i stopped using MP for a while due to the frequent orphaned cursor on the primary forcing me to hard-reset. thought i would try again and the very first connection to the secondary forced a hard reset on the primary......


also, the 10 second blip occurs on primary not secondary.
Reply #17 from WinCustomize Forums Top

The 10 second blip would happen on the primary.  It is automatically disconnecting due to a protocol mismatch.  Usually MP 1.0 on the secondary and MP 1.2 on the primary.

Future versions of MP will inform you why a disconnect happened (and it would say the secondary did not respond in time)

Reply #18 from Stardock Forums Top

The 10 second blip would happen on the primary.  It is automatically disconnecting due to a protocol mismatch.  Usually MP 1.0 on the secondary and MP 1.2 on the primary.


Future versions of MP will inform you why a disconnect happened (and it would say the secondary did not respond in time)



In this case, both on are on 1.2 - no mismatch
Reply #19 from Stardock Forums Top
Same here. Both have version 1.2 installed.

I have installed multiplicity, uninstalled it and installed multiplicity pro on a clean VMWare XP32bit. I logged all those processes. So now I see which files and registry settings are created / deleted in each procedure. I couldn't find any dll issues because all of the dll files are in the Multiplicity folder. And that folder I deleted after unsintall.
Files:
http://www.modus-hightech.de/_zeugs/mprofiles.html
Registry:
http://www.modus-hightech.de/_zeugs/mproreg.html

Sidenote:
Is there a lower version available for download ? Probably it is a v1.2 issue with x64 or 64bit in general.
Reply #20 from Stardock Forums Top
Is it possible to use the Pro-version key with multiplicity "normal" ? If yes: Where can I get an copy of it ?
Reply #21 from Stardock Forums Top
Wow great...

My ticket to this issue:
Created On: Aug 29 2007 06:38 AM
Status: Open


Woohoo.
*irony*I see it was a good choice to not use the available freeware over the retail product multiplicity for better support.*irony*

Come on guys. The trial works perfectly fine where the retail "pro" version does not. And then you can't even respond to support questions ? Hyperlame...
Reply #22 from WinCustomize Forums Top

As it happens there will be a new beta of Multiplicity this week - probably Tuesday. 

What does troubleshooting say on the secondary?

I am going to suggest you uninstall MP from the secondary and install SDC on the secondary (http://sdc.stardock.com/sdcentral_setup.exe) and enter your MP Pro serial in that (Under thinkdesk components).  I suspect there is a problem with the secondary installation on a 64 bit box when using the standalone exe installer.

Then install from that onto the secondary.

The above method will also allow you to install the upcoming beta (you would also need to install SDC on the primary to use the beta).  I would backup sig.bin in the MP directory first.

Your support ticket gets put to the end of the queue each time you respond to it, so it is in with the August 31st ones now.

Reply #23 from Stardock Forums Top
The beta version fixed it. Thanks.