You are not running the installer from a network drive are you?

That can confuse the installer and it shows the MP 1 installed message.

I've paid for the upgrade, unistalled MP1 and Acoustic Bridge, and am running MP2 from a primary where there is a computer to the left and to the right of it.  8)

First, this is an AWESOME upgrade!  Really takes this application to the next level in every way. Well worth the upgrade price for me.  

The only bugs I have found so far are follows:

My main computer used to be on a domain but isn't anymore.  MP2 had a problem resolving the primary IP address, reporting some out to lunch IP address registered in Maine or somesuch for each of the secondaries (same IP).  Unlike MP1, there was no way to manually enter/lock the IP addresses to fix this. Note that the main GUI reported the correct local subnet address in the display, but the little "always connect to" checkbox option reported the wrong IP address, if that info helps.   I was able to resolve this by changing the computer from the old domain to the local workgroup.

Unlike with MP1, if I use the "lock mouse to primary when fullscreen application is used" option with MP2, use of Deskscapes causes the mouse to always be locked to the primary.  8P 

When running Diablo 3 on the Primary, I can move the mouse to the left secondary no problemo, just like in MP1, and I have to alt tab the application to move the mouse to the right secondary, also like MP1, so no problems there at all (re: expected and desired behavior).  However, in moving to the left secondary, sometimes the mouse curso disappears completely on a return to the main game.  The only way to get it back is to force a full screen redraw by teleporting back to town, etc.  This did not happen with MP1 under the identical situation, so something must have changed somewhere for this little bug to have popped up.  I'm not exactly sure what mouse actions cause the loss of cursor, however, as I can't duplicate it reliably...yet.

Drag and Drop does not work from Computer A across to Computer B (primary) to Computer C.  The image and cursor drag as if it should work and wants to work (which is just amazing to see!), it's just that the copy command never occurs.  I have to drag from A to B, then B to C, or vice versa.

All of these are expected in a beta.  But to be honest, these are all minor quibbles and this is one amazing, polished, solid piece of code. 

Thank you!  I can't seem to reliably duplicate the Diablo 3 bug.  It is still happening, but irregularly.  It might be related to dragging an item across from inventory to something else...but...will advise when I can actually be of some use on this one.  8)

So far it's been a dud for me. Been a Multiplicity user for years and for the first time my link between computers has been broken. Will uninstall and get back to the previous version. I use Windows 7

Could you be a little more specific about the issues you are having please.

I wrestled with it for a couple of hours trying to get it to work. No luck. The primary sees the secondary fine, i can add it to the grid and that's about it.

No way it will connect. I went as far to disable the firewalls completely using gpedit.msc but all i see is when i open the primary, on the grid the secondary will light up for a few seconds as if trying to connect and then goes blank.

Win7 and Win 2008 r2 both x64

When you say the primary sees the secondary fine, do you mean when you clicked add computer it showed in the list, or you had to manually enter the machine name?

If you ping the secondary machine name (the one Multiplicity is showing on the primary for the secondary) from a command prompt on the primary does it return the correct IP address?  I would also check that Multisrv.exe is running on the secondary.

I clicked and added it. It showed up automatically.

But pinging doesn't work indeed strange because it's accesible via all computers attached. The IP adress is correct.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping mediaserver

Pinging mediaserver.lan [192.168.1.12] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

The firewall may be blocking pings.

The odd thing is the code to show the machines is the same as the code to check if a machine is live and so light it up in the UI.  I cannot explain why it does not show as live unless the name lookup is failing.

If you double click on the computer on the grid what does the label on the checkbox say?  It usually says "Always use the IP address (x.x.x.x)".

As a test delete the machine from the UI and manually enter the machine and instead of the name on the add computer dialog, put 192.168.1.12 as the name.

NOTE - Below is a copy of the email I sent to Stardock support yesterday.
Today, I found this forum thanks to a user in your IRC channel, so I'm
posting this support request here as well, because I doubt that the regular
support staff is properly equipped to receive beta test feedback.  I've
updated the email slightly from the one I sent to support yesterday to
reflect things I noticed since then.

-----------------------------------------------------------------------------------

I'm not certain where to submit bug reports for the current beta test of
Multiplicity 2.0, and I can't seem to find a beta forum that lists
currently known issues. As such I apologize if I am sending this bug
report to the wrong place, and I also apologize if I am reporting issues
that are already known. If I should be sending bug reports somewhere else,
please let me know?

I've got three systems arranged in a row, and a system below the center
system.  The system on the far right is the primary.

O O O <-Primary
   O

The top three systems are connected via Cat6 cable to a HP Procurve gigabit
switch. The bottom system (The OQO) is connected via Wireless N.

The 2.0 beta of Multiplicity seems to lose connection to the secondary
computers on occasion. It's generally only for a second or two and then
control returns. This is accompanied by a taskbar popup that indicates the
connection was lost and then restored. This did -not- happen in the
previous version of Multiplicity that I just upgraded from. For testing
purposes, I set up continuous pings from my primary PC to the secondary
systems, and during the periods of time that Multiplicity disconnected, the
ping tests didn't show any drops or even an increase in ping time. I
performed several tests, uninstalling the new Multiplicity, restarting each
computer, reinstalling the old one, and testing for a while. The drops
definitely do not happen with the old Multiplicity, and they start
happening again when I reinstall the new one. -- Update -- Today, the
drops haven't been happening at all.  I cannot say with confidence if
the drops are a Multiplicity issue, or not.

The mouse control works well, but I find that (A) the Scroll Lock toggle to
lock to a specific PC won't toggle consistently unless your mouse is on the
master PC screen. On the secondary systems, scroll lock doesn't seem to
always work. It's intermittent and somewhat infrequent, however, and might
be hard to duplicate. If I can come up with way to consistently duplicate
the symptoms I will let you know.

The keyboard control seems to give me the most trouble. Sometimes, even
though I have moved the mouse to one of the secondary screens, the keyboard
input continues to be directed to the primary computer. I haven't been
able to identify why this is happening, but it happens frequently enough
that I keep an extra keyboard and mouse around to connect one of the other
PCs just in case. When this is happening, occasionally one or two of the
letters will be send to the target PC. During the time that this is
happening, mouse control on the secondary machines continues to work fine.
Pressing Control three times causes the single-pc / all PCs function to
toggle (I hear the beeps) but it doesn't change anything - Input continues
to only go the primary PC regardless of which PC currently has focus.

The ability to just drag items between desktops is *fantastic*. It's a
little bit inconsistent, though, as sometimes the icon you are dragging
just kind of "stops" at the border between workstations and the mouse
pointer keeps going.  (I'm not holding down any keys when attempting
to drag and drop) Also, sometimes the copy and paste functionality
doesn't work. I haven't noticed a common thread with regard to what makes
those functions fail. They work most of the time.

Occasionally the "Lock on full screen application" mode will lock the mouse
to the current PC even if there isn't a full screen application running.

The sound transfer functionality (Which basically appears to be Acoustic
Bridge?) works flawlessly, I haven't encountered any problems there.

If I was to make a suggestion, I would say that giving the users more
choice with regard to setting up what hotkeys they would like to use would
be nice. For example, I'd to be able to choose something other that
pressing control three times to toggle multi PC input, and to be able to
pick what key I want to toggle screen locking instead of scroll lock. Your
best competition is a program called Input Director - It offers a robust
system where you can set up specific macros (for lack of a better term)
which will execute specific commands on specific workstations. (For
example, when I was using Input Director with a multiple desktop manager, I
had a single keystroke (the ~ key) which automatically sent that command to
all workstations, causing each one to switch from Desktop 1 to desktop 2.
I can do the same thing with Multiplicity, but I have to press control
three times, then press the tilde key, then press control three more times
to turn it off. That's a seven keystroke process that I was able to
accomplish with one keystroke using Input Director.

Anyhow, thanks for the Multiplicty update. The new features are great, I
think it just needs a bit more polish and it'll be the best mutliPC/single
keyboard product in the world.

Good job Kailef.

I've got the keyboard problem happening right at this very moment.  If I move the mouse to a secondary PC and click an input field and type, the letters appear only here, on the primary PC, and not on the secondary.  Let me do a more thorough test and tell you what I find.

Okay:  It appears that modifier keys are still being sent to the secondary when this error is occurring.  The Windows key makes the start menu pop up on the secondary, and the backspace key erases existing text on the secondary, and the mouse is fully functional on the secondary.  However, any "regular" keys (1-0, a-z, etc) get sent to the primary PC even though the focus is on the secondary PC.  I suspect the Shift key is also being sent, but I determine that only by noticing that when I have the focus on the secondary PC and I type and the letters appear on the primary PC as I described, if I hold shift down, the letters that are being sent to the Primary do not become capital letters.  (Hopefully I am making sense)  Based on this I would hazard a guess that other special keys are being sent as well.  Let me try Tab.  Yes - Tab is sent to the secondary PC successfully, I can shift the cursor between input boxes with it.

I just tested with another of my secondary PCs, and the problem appears to be happening on all of them, identical symptoms.

I tested by pressing control three times.  I got the double beep that indicates input should be sent to all connected PCs, but there's no actual change in the behavior.  The symptoms are identical, regardless of whether or not Multiplicity is supposed to be sending to all connected PCs or just the PC with focus at the time.

My tests have shown that if I reboot the Primary PC the problem will go away temporarily.  If I reboot one of the secondaries (or all of them) it doesn't appear to change anything.

Hopefully my testing will prove helpful to you!  If you have any questions please don't hesitate to ask, I'm happy to assist.

I just spent about thirty minutes with this keyboard input problem happening to me, and it wouldn't stop.  After I posted my last message, I closed my browser (Firefox 14.0.1) and lo and behold, the problem stopped happening immediately.

So I opened the browser again - The problem did not return.  I then went back to this specific web page, where I am typing this post, and the symptoms immediately started happening again.  So, I am now able to consistently duplicate the problem on my end.

I'll gather more details and let you know where and when it happens, and work on identifying what programs do it, which will hopefully help you to track down the source of the issue.

 -Edit-

After posting the message, I immediately moved the mouse to the secondary PC and began hammering keys - After the message posted, keys started going through, then the page reloaded and as soon as it finished reloading the symptoms returned.  I have no evidence to support this supposition, but I think it has something to do with the text input field used for the "Quick Reply" at the bottom of the page.

-Edit 2-

Doesn't happen using Google Chrome.

now i get this