Suddently, Input Director no longer working
1,877 views
Skip to first unread message
Pete Brown
Sep 10, 2011, 11:25:17 PM9/10/11
to Input Director
I've been using Input Director for well over a year. Other than an
occassional problem where copy/paste stops working, it has worked
quite well. My personal home machine is set as the master. My work PC
(located in the same spot here) is set as the slave.
Suddenly, just a few days ago, it stopped working completely. If I
kill ID on the slave, and re-run it, the master sometimes says it
detects the slave, but when I try and move my mouse up to it, it says
it can't find it. I've disabled the firewall to ensure that wasn't the
problem.
I didn't change any config on either machine. I don't know if some
recent pushed Windows Update change hosed ID.
The slave is set to allow any computer to take control. The port
number on the slave matches the configuration on the master.
Windows 7 on both machines. They are physically next to each other, on
the same network. They've joined different domains, however.
Pete
occassional problem where copy/paste stops working, it has worked
quite well. My personal home machine is set as the master. My work PC
(located in the same spot here) is set as the slave.
Suddenly, just a few days ago, it stopped working completely. If I
kill ID on the slave, and re-run it, the master sometimes says it
detects the slave, but when I try and move my mouse up to it, it says
it can't find it. I've disabled the firewall to ensure that wasn't the
problem.
I didn't change any config on either machine. I don't know if some
recent pushed Windows Update change hosed ID.
The slave is set to allow any computer to take control. The port
number on the slave matches the configuration on the master.
Windows 7 on both machines. They are physically next to each other, on
the same network. They've joined different domains, however.
Pete
Pete Brown
Sep 11, 2011, 2:33:33 PM9/11/11
to Input Director
I reinstalled the last normal release on both machines and is still
didn't work. I even did an uninstall and reinstall. On a whim, I
installed the lates beta. Installing the latest beta on both machines
fixed it.
Known issue with known fix in the beta?
Pete
didn't work. I even did an uninstall and reinstall. On a whim, I
installed the lates beta. Installing the latest beta on both machines
fixed it.
Known issue with known fix in the beta?
Pete
Shane
Sep 11, 2011, 7:25:26 PM9/11/11
to Input Director
On Sep 12, 4:33 am, Pete Brown <pmbr...@irritatedvowel.com> wrote:
> I reinstalled the last normal release on both machines and is still
> didn't work. I even did an uninstall and reinstall. On a whim, I
> installed the lates beta. Installing the latest beta on both machines
> fixed it.
>
> Known issue with known fix in the beta?
Hi Pete,
> I reinstalled the last normal release on both machines and is still
> didn't work. I even did an uninstall and reinstall. On a whim, I
> installed the lates beta. Installing the latest beta on both machines
> fixed it.
>
> Known issue with known fix in the beta?
No, there wasn't an explicit fix in the latest beta version. But given
the number of changes under the hood between v1.2.2 and v1.3, I'm not
surprised it fixed the problem.
Regs,
Shane.
SkipStein
Sep 17, 2011, 12:20:43 PM9/17/11
to Input Director
Yea, i had the same or similar thing happen. I am just getting back
to troubleshooting this issue as I really miss InputDirector!
I had been a long time devote of InputDirector and depended on it for
a long time. Now, since I switched to Windows7, I just cannot get it
to work. I have tried every combination setting I can think of.
Varied network adaptors (usually two gig adapters in each
workstation). Varied the port specifics, you name it.
It would be a nice feature to allow for a specific IP address to
point
to a slave. Even with DHCP, the address usually stays pretty much the
same.
It is so frustration now having this tool. Managing three keyboards,
mice, and such. I have a S-M-S configuration on a gig network. It was
SO nice before. All workstations are on W7 and current release
levels.
I run BitDefender, Windows firewall is off. I also use
SUPERantispyware to clean crap.
Also, I have downloaded the latest beta to try that; no joy.
If you have any suggestions I would love to hear them!
Cheers,
Skip Stein
Free Agent
Management Systems Consulting, Inc.
On Sep 11, 2:33 pm, Pete Brown <pmbr...@irritatedvowel.com> wrote:
> I reinstalled the last normal release on both machines and is still
> didn't work. I even did an uninstall and reinstall. On a whim, I
> installed the lates beta. Installing the latest beta on both machines
> fixed it.
>
> Known issue with known fix in the beta?
>
> Pete
>
> On Sep 10, 11:25 pm, Pete Brown <pmbr...@irritatedvowel.com> wrote:
>
>
>
>
>
>
>
> > I've been using Input Director for well over a year. Other than an
> > occassional problem where copy/paste stopsworking, it has worked
to troubleshooting this issue as I really miss InputDirector!
I had been a long time devote of InputDirector and depended on it for
a long time. Now, since I switched to Windows7, I just cannot get it
to work. I have tried every combination setting I can think of.
Varied network adaptors (usually two gig adapters in each
workstation). Varied the port specifics, you name it.
It would be a nice feature to allow for a specific IP address to
point
to a slave. Even with DHCP, the address usually stays pretty much the
same.
It is so frustration now having this tool. Managing three keyboards,
mice, and such. I have a S-M-S configuration on a gig network. It was
SO nice before. All workstations are on W7 and current release
levels.
I run BitDefender, Windows firewall is off. I also use
SUPERantispyware to clean crap.
Also, I have downloaded the latest beta to try that; no joy.
If you have any suggestions I would love to hear them!
Cheers,
Skip Stein
Free Agent
Management Systems Consulting, Inc.
On Sep 11, 2:33 pm, Pete Brown <pmbr...@irritatedvowel.com> wrote:
> I reinstalled the last normal release on both machines and is still
> didn't work. I even did an uninstall and reinstall. On a whim, I
> installed the lates beta. Installing the latest beta on both machines
> fixed it.
>
> Known issue with known fix in the beta?
>
> Pete
>
> On Sep 10, 11:25 pm, Pete Brown <pmbr...@irritatedvowel.com> wrote:
>
>
>
>
>
>
>
> > I've been using Input Director for well over a year. Other than an
> > quite well. My personal home machine is set as the master. My work PC
> > (located in the same spot here) is set as the slave.
>
> > Suddenly, just a few days ago, itstoppedworkingcompletely. If I
> > (located in the same spot here) is set as the slave.
>
> > kill ID on the slave, and re-run it, the master sometimes says it
> > detects the slave, but when I try and move my mouse up to it, it says
> > it can't find it. I've disabled the firewall to ensure that wasn't the
> > problem.
>
> > I didn't change any config on either machine. I don't know if some
> > recent pushedWindowsUpdate change hosed ID.
> > detects the slave, but when I try and move my mouse up to it, it says
> > it can't find it. I've disabled the firewall to ensure that wasn't the
> > problem.
>
> > I didn't change any config on either machine. I don't know if some
>
> > The slave is set to allow any computer to take control. The port
> > number on the slave matches the configuration on the master.
>
> >Windows7on both machines. They are physically next to each other, on
> > The slave is set to allow any computer to take control. The port
> > number on the slave matches the configuration on the master.
>
Reply all
Reply to author
Forward
0 new messages