Keyboard not working over RDP

[nogginthenog]

Hi,

If I connect to a machine using Remote Desktop WinUAE works great but the emulated keyboard does not work. F12 works.

Any ideas?

[Toni Wilen]

Did you try without any config files? Customized input configs (especially if it was created with older version) may not be always fully transferrable.

Include winuaebootlog.txt if it does not help.

[jayminer]

I have the same problem today, it has always worked in the past but suddenly the keyboard won't work. Didn't really think about it until I saw your post, perhaps it's an update to RDP in Windows that has changed something since my computer installed updates yesterday. I haven't changed anything in WinUAE.

[nogginthenog]

I thought I'd check older versions.

WinUAE in 'portable' mode on a fresh PC via RDP. KS/WB 1.3.

Keyboard is working 3.2.0 & 3.2.2 [1] but not 3.3 & 3.4.
I tried -nodirectinput & -norawinput without luck.

F12 works in all versions but Alt+F4 does not work in 3.3/3.4.
64bit seems to make no difference.

Attached are logs from 3.2 & 3.3.

[1] 3.2.2 is hanging but it works on my main PC. Maybe because I don't have DirectX etc installed.

[jayminer]

Today I could use my keyboard over RDP, but I had WinUAE running from when I started it at home. Yesterday when I had issues I started it when I was already connected with RDP. Gonna try and close it completely and start it again at the end of the day to see if I get any trouble.

[Phantasm]

i've installed winuae running on a windows server running in azure cloud and I have this same problem. The keyboard input is not recognised at all.

Unfortunately since its a cloud based server i have no way of connecting to the server other than via RDP.


I've attached a log file for reference.

[Toni Wilen]

Does F12 still work?

Run winuae with -log -inputlog 1 parameters ("winuae -log -inputlog 1"), does pressing keys write log messages like "HANDLE=10041 CODE=1e Flags=0 VK=41 MSG=100 EXTRA=0 SC=1e"?

[Phantasm]

yes F12 works fine but no keys are functioning within the emulated environment.

Ran with -log -inputlog 1 and no log messages are produced when keys are pressed (log attached)

[Toni Wilen]

Does changing RDP Local Resources page Keyboard setting to "On the remote computer" help?

[Phantasm]

no unfortunately that setting did not make any difference. i've downloaded 3.2.2 now and tried with that and the keyboard is working fine on that version as previously reported.

[Toni Wilen]

Is that last working version? Could you attach logs (both winuaebootlog.txt and winuaelog.txt) using that version when using RDP? (I think I know the reason but I need confirmation)

[jPV]

I also have the same problem when trying to use WinUAE from my MorphOS machine via RDesktop. Would be really nice to get it working... have to find time to test it more, but at least I'll subscripe this thread now and good to know I'm not alone with my problem Somehow didn't hit here with Google earlier.

[Phantasm]

Originally Posted by Toni Wilen

Is that last working version? Could you attach logs (both winuaebootlog.txt and winuaelog.txt) using that version when using RDP? (I think I know the reason but I need confirmation)

i've just tried 3.3.0 and that doesn't work. i'll sort out the logs for you later on - and thanks for your assistance.

[Phantasm]

here are the logs from winuae 3.2.2 64bit running via rdp

[Toni Wilen]

RawInput enumeration..
RAWINPUT: found 6 devices
HID device check:
000000000016030B RIDI_DEVICENAME 1 failed
00000000005B0249 RIDI_DEVICENAME 1 failed
0000000000010035 RIDI_DEVICENAME 1 failed
DirectInput enumeration.. Keyboards..
I={6F1D2B61-D5A0-11CF-BFC7-444553540000} P={6F1D2B61-D5A0-11CF-BFC7-444553540000}
'Keyboard' 'Keyboard' 00000413 [Keyboard]

I thought so..

I dropped keyboard and mouse directinput mode in 3.3.0.

Perhaps normal Windows key events are good enough in this mode. Special keys like Windows keys probably won't reach applications anyway in RDP mode.

[Toni Wilen]

I can't make it work automatically because rawinput registeration still work under RDP but it does not send any events. It is not possible to detect this situation.

-norawinput fixed it previously but since 3.3 it only disables rawinput hid mode (joysticks).

http://www.winuae.net/files/b/winuae.7z should work with RDP if you add -norawinput_all or -norawinput_keyboard command line parameters.

[Phantasm]

i tried the version above and i was able to get some keyboard input using rdp, however when attempting to use it some more i noticed that not all the basic keys worked. I started working through the letters on the keyboard and got

qwertyuiopasd and then the rest of the letter keys did not work correctly.

very strange.

[Toni Wilen]

That is nearly zero-information report.. Does it happen every time? Does log still show keyboard messages and so on...

EDIT: Should be fixed now.

[Phantasm]

Originally Posted by Toni Wilen

That is nearly zero-information report.. Does it happen every time? Does log still show keyboard messages and so on...

EDIT: Should be fixed now.

sorry that you feel it was a poor bug report and thanks for fixing it so quickly. It is now working 100% including windows key.

[Toni Wilen]

Perfect. I could autodetect RDP mode but I don't want to force it if it gets fixed in the future.

Sorry for my standard reply, I usually try to do it only when some eab regular does it again and again