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
jbranc
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.
yes - that works sometimes. othertimes, it does not.
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......
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 t
to have a button to say "install on secondary" or "upgrade secondary" have it push the install over hte network to the secondary seems pretty natural to me. however, i get your point that they operate independently. if that is the case, there should be a much easier way to get the software to the secondary without having to install the stardock central software on each box. its overkill.
so i have MP 1.02 on Primary and Secondary. I wish to upgrade to 1.05 on my Primary, i open Stardock Center. there is 1.05! i click "install", it installs and everything is great (aside from required reboot..) now i have 1.05 Primary, and 1.02 Secondary. My first instinct, given the nature of the product, is that in the Primary config window, i would be able to "push" the upgrade to the secondaries. after all, this is all about connecting machines, right? but, it doesn't appear thats p
when i have the focus on the secondary machine, and either reboot it or shutdown, i can never regain control of my primary again if i leave focus on the secondary the whole time it shuts down. sometimes my primary will react to my keyboard, and get some near mouse behavior. i'll be able to click and move, but there is no mouse cursor so knowing where the mouse is is trial and error. i have to reboot to recover from this - disconnecting and reconnecting the USB keyboar