rebooting secondary while it has focus

from Stardock Forums

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 keyboard/mouse has no effect.


sometimes it will have NO keyboard or mouse control whatsoever. in this case i need to use the hard reset.


it seems like rebooting or shutting down the secondary while it has focus is pretty much a standard use case (afterall, i need the mouse or keybaord to do it).  am i the only one experiencing such awful behavior?

multiplicity
7,463 views 8 replies
Reply #2 from Stardock Forums Top
no. i'm not using any other stardock or similar software at all on either machine at this time. everything else is plain vanilla XP SP2
Star Control: Origins
Reply #3 from Stardock Forums Top
I have the same issue and have not yet found a resolution for it aside from being sure to move the focus back to the server system before the shutdown or restart happens. This solution although effective is not practical because there are times when I forget to change the focus in time and then have to restart the server system as well.

If any moderators are monitoring this thread please respond with possible solutions or advise us if there are any fixes or updates planned for this issue. I believe that a feature that causes the focus to change back to the server machine when it loses contact with the secondary (currently focused system)would be a good feature to implement.

Robert
Reply #4 from WinCustomize Forums Top

Multiplicity does move focus back to the primary machine when the secondary is disconnected.

It seems on some machines it leaves the cursor invisible after switching back.  CursorXP is known to cause this, but it seems something else is also making it happen.

Reply #5 from WinCustomize Forums Top
is there going to be any attempt made to debug and potentially fix this issue? or will some of us have to deal with the fact that if you don't switch back to the primary, multiplicity renders your computer 'inputless', which causes unsaved data to be lost, and forces into a hard reset?

will the "Quick detection of disconnected secodary" setting affect this in any way?
Reply #6 from WinCustomize Forums Top
MP 1.1 is in development and I have made a note to debug this further.
Reply #7 from WinCustomize Forums Top
thats great news!

do you have more information on the "Quick detection of disconnected secodary" setting?
Reply #8 from WinCustomize Forums Top
Quick detection of disconnected secondary just makes MP check the secondary is connected more often.  I believe MP is correctly detecting the secondary is disconnected, but leaving the mouse cursor invisible on your PC.