Mouse constantly gets stuck nonresponsive on slave
1,940 views
Skip to first unread message
Michael
Feb 27, 2011, 3:08:56 AM2/27/11
to Input Director
I have a master (windows 7 x64) and a slave (Win7 x64 also).
Today, every 20-30 seconds when my mouse has been on the slave PC, the
mouse gets stuck, stops responding. After about 5-10s the mouse
begins to respond again. The mousepad on the slave still works, but
the master mouse cursor is 'trapped' over on the slave screen. It
happens so constantly as to be unbearable.
Is there a debug version I can run to check it?
I don't believe it's a connectivity issue as I have seen absolutely no
internet connection loss.
Just yesterday I installed SP1 for Win7 on my master. Maybe there was
something in there?
Has anyone else seen Input Director suddenly start to misbehave?
Thanks,
Michael
Today, every 20-30 seconds when my mouse has been on the slave PC, the
mouse gets stuck, stops responding. After about 5-10s the mouse
begins to respond again. The mousepad on the slave still works, but
the master mouse cursor is 'trapped' over on the slave screen. It
happens so constantly as to be unbearable.
Is there a debug version I can run to check it?
I don't believe it's a connectivity issue as I have seen absolutely no
internet connection loss.
Just yesterday I installed SP1 for Win7 on my master. Maybe there was
something in there?
Has anyone else seen Input Director suddenly start to misbehave?
Thanks,
Michael
Shane
Feb 27, 2011, 5:29:12 PM2/27/11
to Input Director
On Feb 27, 7:08 pm, Michael <mcoh...@gmail.com> wrote:
> I have a master (windows 7 x64) and a slave (Win7 x64 also).
> Today, every 20-30 seconds when my mouse has been on the slave PC, the
> mouse gets stuck, stops responding. After about 5-10s the mouse
> begins to respond again. The mousepad on the slave still works, but
> the master mouse cursor is 'trapped' over on the slave screen. It
> happens so constantly as to be unbearable.
Hi Michael,
> I have a master (windows 7 x64) and a slave (Win7 x64 also).
> Today, every 20-30 seconds when my mouse has been on the slave PC, the
> mouse gets stuck, stops responding. After about 5-10s the mouse
> begins to respond again. The mousepad on the slave still works, but
> the master mouse cursor is 'trapped' over on the slave screen. It
> happens so constantly as to be unbearable.
Which version of Input Director are you running?
How are two systems networked - wired or wireless? Both into the same
router/modem?
How often is it happening?
If you use the master hotkey (ctrl-alt-break) to return the cursor to
the master and then transition across to the slave, what happens?
Are there any Input Director messages popping up (slave unresponsive
messages?)
Regs,
Shane.
Rod
Mar 8, 2011, 12:52:05 PM3/8/11
to Input Director
I have a similar issue. My mouse is unresponsive when transitioning to
the slave. It just darts from one spot to another.
Both systems are Win7 32 bit and the slave still has it's mouse and
keyboard.
the slave. It just darts from one spot to another.
Both systems are Win7 32 bit and the slave still has it's mouse and
keyboard.
Cyprus Spirit
Mar 9, 2011, 1:45:30 PM3/9/11
to Input Director
Guys this smells something like a firewall (software or hardware
firewall) kicking in every couple of seconds.
Try disable firewalls in your modems / routers and even check windows
firewall.
Check if your switch gives the necessary priorities to the PCs and
that it is not overloaded with movies etc....
In the worse senario, check if the problem persists if you hardwire
the computers with a crossover cable / or adapter.
Other than this I can not think of anything else other than drivers
and slim down Operative Systems (I use one... Hahaha)
Anyway
Hope I helped....
Cyprus Spirit
firewall) kicking in every couple of seconds.
Try disable firewalls in your modems / routers and even check windows
firewall.
Check if your switch gives the necessary priorities to the PCs and
that it is not overloaded with movies etc....
In the worse senario, check if the problem persists if you hardwire
the computers with a crossover cable / or adapter.
Other than this I can not think of anything else other than drivers
and slim down Operative Systems (I use one... Hahaha)
Anyway
Hope I helped....
Cyprus Spirit
DaCeige
Mar 11, 2011, 4:52:57 PM3/11/11
to Input Director
I've experienced this behavior a number of times. Both host and
client machines are windows 7 x64 sp1. Typically I find it is related
to the host machine's i/o on the bus/memory/drive. Ie... Using
process explorer on the host computer, when a local process that may
not use much CPU but loads of i/o (like a backup/virus scan/large file
copy), the mouse starts exhibiting the problem on all slaves.
Of course if your cpu gets pegged on the host, or client, you can
expect buggy mouse movement.
Just remember the hotkey to get back to your master computer.... I
believe the default is <CTRL>+<ALT>+<BREAK>. It can also be changed to
something a little easier to hit on the main tab of the ID
configuration window.
I'm still trying to narrow it down.
I wonder if you can set ID to run at a higher priority (like my alps
touchpad software does).
client machines are windows 7 x64 sp1. Typically I find it is related
to the host machine's i/o on the bus/memory/drive. Ie... Using
process explorer on the host computer, when a local process that may
not use much CPU but loads of i/o (like a backup/virus scan/large file
copy), the mouse starts exhibiting the problem on all slaves.
Of course if your cpu gets pegged on the host, or client, you can
expect buggy mouse movement.
Just remember the hotkey to get back to your master computer.... I
believe the default is <CTRL>+<ALT>+<BREAK>. It can also be changed to
something a little easier to hit on the main tab of the ID
configuration window.
I'm still trying to narrow it down.
I wonder if you can set ID to run at a higher priority (like my alps
touchpad software does).
Trey
Mar 11, 2011, 11:06:08 AM3/11/11
to Input Director
I was having the same problem between two Win7, 64 bit systems. I
manually added an Allow policy in both machines' Windows Firewall for
port UDP 31234 (assuming you're using the default port in Input
Director v1.3beta) and things now seem to be working as expected.
Trey
manually added an Allow policy in both machines' Windows Firewall for
port UDP 31234 (assuming you're using the default port in Input
Director v1.3beta) and things now seem to be working as expected.
Trey
Michael
Mar 12, 2011, 5:44:20 PM3/12/11
to Input Director
Tried this but it didn't seem to help
A few more details:
When the freeze happens, if you waggle your mouse around, after some
length of time, typically 1-5seconds, the mouse will start moving
again.
It also affects typing. Sometimes when I am typing across, it just
stops (i.e. the connection breaks).
The Ctrl-Alt-Break key works, and when I move the mouse back over,
sometimes it succeeds, sometimes my mouse disappears back into the
slave, with the slave mouse unresponsive, and sometimes it tells me
"slave failed to respond".
Neither machine is pegging the CPU.
I am using version 1.2.2.
Someone in the house is using skype, though, onto a wireless machine,
but that shouldn't push the priority down enough to cause this
problem. I have a "g" wireless network, and internet access on the
slave is still snappy.
Michael
A few more details:
When the freeze happens, if you waggle your mouse around, after some
length of time, typically 1-5seconds, the mouse will start moving
again.
It also affects typing. Sometimes when I am typing across, it just
stops (i.e. the connection breaks).
The Ctrl-Alt-Break key works, and when I move the mouse back over,
sometimes it succeeds, sometimes my mouse disappears back into the
slave, with the slave mouse unresponsive, and sometimes it tells me
"slave failed to respond".
Neither machine is pegging the CPU.
I am using version 1.2.2.
Someone in the house is using skype, though, onto a wireless machine,
but that shouldn't push the priority down enough to cause this
problem. I have a "g" wireless network, and internet access on the
slave is still snappy.
Michael
Michael
Mar 12, 2011, 6:02:48 PM3/12/11
to Input Director
Another interesting factoid.
I am running a winscp transfer to an offsite machine, and I also have
the task manager up (all this on the slave).
When I move the mouse around constantly during the transfer, via
InputDirector, when the freeze comes, the WinSCP transfer also freezes
(the Task Manager does not).
Sometimes, if the break is long enough, WinSCP tells me the connection
has broken and asks me to log in again.
When I move the mouse around via the slave's trackpad, none of this
happens.
Somehow, Input Director is actually breaking off connectivity in other
applications.
Michael
I am running a winscp transfer to an offsite machine, and I also have
the task manager up (all this on the slave).
When I move the mouse around constantly during the transfer, via
InputDirector, when the freeze comes, the WinSCP transfer also freezes
(the Task Manager does not).
Sometimes, if the break is long enough, WinSCP tells me the connection
has broken and asks me to log in again.
When I move the mouse around via the slave's trackpad, none of this
happens.
Somehow, Input Director is actually breaking off connectivity in other
applications.
Michael
Michael
Mar 13, 2011, 1:12:36 AM3/13/11
to Input Director
It looks like this is almost certainly a router problem...
When the router is under pressure, I get a lot of minor drops in
connection.
The WinSCP drops coincided with Input Director drops, and they occured
even without Input Director, so I tracked them to the source.
When the router is under pressure, I get a lot of minor drops in
connection.
The WinSCP drops coincided with Input Director drops, and they occured
even without Input Director, so I tracked them to the source.
Michael
Mar 13, 2011, 1:36:26 AM3/13/11
to Input Director
It looks like this is almost certainly a router problem...
When the router is under pressure, I get a lot of minor drops in
connection.
The WinSCP drops coincided with Input Director drops, and they occured
even without Input Director, so I tracked them to the source.
On Mar 12, 3:02 pm, Michael <mcoh...@gmail.com> wrote:
When the router is under pressure, I get a lot of minor drops in
connection.
The WinSCP drops coincided with Input Director drops, and they occured
even without Input Director, so I tracked them to the source.
On Mar 12, 3:02 pm, Michael <mcoh...@gmail.com> wrote:
Da Ceige
Mar 13, 2011, 3:35:05 PM3/13/11
to input-d...@googlegroups.com
Wonder if this might be related to bits. Is inputdirector being
incorrectly classified as a bulk application?
incorrectly classified as a bulk application?
> --
> You received this message because you are subscribed to the Google Groups "Input Director" group.
> To post to this group, send email to input-d...@googlegroups.com.
> To unsubscribe from this group, send email to input-directo...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/input-director?hl=en.
>
Dean James
Jun 5, 2014, 5:53:53 PM6/5/14
to input-d...@googlegroups.com
For Me switching to IPv4 ONLY resolved the issue.
Reply all
Reply to author
Forward
0 new messages