This is such a vague question, but whenever I connect to any of my remote machines through RD Tabs 2.0.12, all keyboard input gets sent immediately except for the space key. I have to wait about a second after each space press for the space key to show up in the remote system. I have verified that connecting to a Vista, XP Pro, and 2003 Server box all see this same behavior.

Ideas?

That is a weird problem. I'm not experiencing it. I just tested on several remote systems and also have never noticed it before. Did this problem occur in previous versions of RD Tabs? Is there possibly network congestion interfering with the transmission? What version of Windows is RD Tabs running on? What version(s) of the .Net Framework do you have installed?

The only thing that messes with the input stream is the keyboard hook installed to listen for pre-remote desktop input for the SysKey function. I can make a build that disables this, if you want to test that out.

Hey Timothy,

Thanks for the quick response. RD Tabs is running on my Vista Business machine . . . it has .NET 2.0 and 3.0 installed, AFAIK. I'll give your application a shot on XP Professional before I ask for the special build. I love the app (just wish its footprint were a little smaller)!

Keep me updated on this. It's the first I've heard of it, but if it's the keyboard hook, it may at least call for an option to completely disable the keyboard hook for the rare workaround.