However I do have a large issue with typing being doubled in many
apps.
If I hit Win+R for the run box, I get two run boxes.
If I open the command prompt each letter I type is doubled so asdf
comes out as aassddff.
Same goes for the log in box for a remote desktop connection.
I can type fine in Notepad/IE/etc.
Both XP machines are laptops and this occurs on the master using
either an external USB keyboard or the internal keyboard.
They are connected via cables through a switch.
I use Input Director on Windows XP Professional standalone computer as
master and Acer Notebook with Windows XP Home as slave. They are
connected via wi-fi switch.
Some times (not always!) keyboard and mouse start to "double" on slave
computer while master behave itself perfectly. Key press can give two-
three-more same characters, it seems that it depends on press
duration. Mouse clicks are doubles, even mouse moves doubles ---
cursor moves approximately double of expected distance.
Such behavior appears and vanishes in arbitrary manner. Approximately
70% / 30% :-)
I try to use another computer as master with Windows XP Vista and also
wi-fi. It works normally. So I decided that failure is in my master
standalone computer.
I try to remove all programs that an my opinion can interfere with
keyboard/mouse. None helps.
So as I can see there are two possible reasons remains.
1. I use KVM Aten 732b to switch keyboard and mouse. But I can't guess
why the bug appears and vanishes when I do nothing but moves the mouse
around desktop.
2. I suspect master computer has buggy(?) wi-fi network controller. It
works without errors but has very small and floating data speed. May
it be the reason to Input Director to fail in such a manner?
Being a programmer myself, I can gladly give to author any additional
info and/or test/run special debug versions of program if it can help
him.
Can you try temporarily switching the problematic slave system from
wireless to wired, to see if that isolates the problem to the wireless
card?
Regs,
Shane.
Does the double-keying occur on the master and the slave, or just the
master?
Regs,
Shane.
Then I made slave system wired leaving master wireless and ops!...
disfunction is here again.
So I can conclude that the reason of the failure is in "semiworking"
network wireless adapter. Zyxel G-320H EE, if is matter.
I have to say once more that thhis device is fully functional in
"user" sense. That is it doesn't throw any errors during work neither
to user nor in event log and similar places. It just seems having very
slow connection speed and sometimes disconnecting without any obvious
reason.
Perfect device to develop error-resistant code, isn't it? :-)
I understand that it is unreasonable to develope code for nonworking
devices. But this case respresent the case of unreliable network
connection so I think the program will be better if it will work in
such conditions.
No answer for about a week... :-(
I've been sick these last few days.
> On Mar 16, 8:10 pm, Andrey Beletsky <abelet...@gmail.com> wrote:
>
> > I have to say once more that thhis device is fully functional in
> > "user" sense. That is it doesn't throw any errors during work neither
> > to user nor in event log and similar places. It just seems having very
> > slow connection speed and sometimes disconnecting without any obvious
> > reason.
>
> > Perfect device to develop error-resistant code, isn't it? :-)
>
> > I understand that it is unreasonable to develope code for nonworking
> > devices. But this case respresent the case of unreliable network
> > connection so I think the program will be better if it will work in
> > such conditions.
Input Director uses UDP instead of TCP. UDP is an unreliable protocol,
which on a local LAN network, will act reliably. There is some error
correction built into Input Director. I will look at what I can do in
future versions to improve this for mouse/keyboard data stream.
If you're willing to try an experiment, I'd be interested in having
you run a diagnostic version of Input Director, so I can analyse the
log. It sounds like data packets are being resent, sometimes twice. I
would have expected to see a loss of characters not a doubling up.
Regs,
Shane.
Hi Brad,
Just so I'm clear - this is happening on the master but not the slave?
If it is only the master - when the double clicking occurs, if you the
disable Input Director - does it immediately revert to behaving
correctly?
Regs,
Shane.
thanks for your answer, glad to hear you again!
Yes, I want to try an experiment. I myself somehow get involved with
network technologies. And it's very intresting to me too why UDP
packets double but not simply lost :-).
So you can mail me URL or test version itself. I'll try to run it as
soon as possible.
And about your dialog with Brad... He have double keystokes on SLAVE
as I have, read carefully above. :-) Master works well.
I would love to test out that diagnostic version but unfortunately I
ended up assigning the laptop to one of our new users. I guess that
is part of the fun of not having enough equipment to go around... :)
Hopefully I won't have the issue when I reappropriate another
machine. :)
Thanks!
Brad
Give me a couple of days, I'll email you when I've got it ready.
Regs,
Shane.