Why does the cursor return to the master with slave unresponsive messages?
When controlling a slave, the master monitors the slave to ensure that it is correctly processing the keyboard/mouse information sent to it over the network. The likely causes to why Input Director is returning the cursor to the master are: • Running Input Director over an unreliable network that is dropping data (for example a wireless network with poor connectivity) • If the slave system is unresponsive for several seconds (usually due to a rogue application) or freezes. By default Input Director will give a slave to 2 seconds to respond. If the cursor is being returned to the master frequently, you can increase the time Input Director will wait: • Open Input Director on your master • Switch to the ‘Master Preferences’ tab • Scroll down to the bottom of the panel • Change the time to wait for a slave to respond, e.g.
Related Questions
- I am currently studying for an undergraduate course in the UK and have got admission into a master’s course. Do I have to return to India to extend my student visa?
- Can the I2C-Trace kit be also used to send messages on the I2C bus (I2C Master capability)?
- How can I show multiple scenarios / return events in the Master Network Summary?
