Robertmo and Drakah,

Thanks a million. the solution of disabling the Microsoft non-existant devices was great.

Yea thanks for this solution, even i had the same problem 😀

jimmy11 wrote:

Robertmo and Drakah,

Thanks a million. the solution of disabling the Microsoft non-existant devices was great.

Yea thanks for this solution, even i had the same problem 😀

Thanks a lot, disabling the Microsoft non-existent devices worked for me too.

lucy123 wrote:

Yea thanks for this solution, even i had the same problem 😀

Thanks a lot, disabling the Microsoft non-existent devices worked for me too.[/quote]

Problem was in keyboard hardware not in device driver. Or not supporting drivers ))
i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41
i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41
i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41
i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41
i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41
i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41i41
i41i41i41i41i41i41i41i41i41i41i41i41i41
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо

I have the same problem with the 0.74 version on Windows 7 64-bit if I use the binaries from the official website.

However, I've just downloaded and recompiled myself both SDL and DosBox using MinGW32 gcc/g++ 4.6.2 and the problem is gone in the freshly compiled version. If I use DosBox from the official website and the newly compiled SDL (simply overwrite the DLL), I don't have this problem anymore.

Looks like an SDL problem.

I've had this problem in DosBox 0.74 where the following keys all do not work:
\`='[
and where the ] key becomes [ and # becomes ]
This is fixed when I remove the USB infrared receiver for my Windows Media Center remote control from my computer.

It would be good if this could be fixed in DosBox itself - if DosBox only 'bound' to 'real keyboards' perhaps? Not sure what this looks like in Windows terms - but never had this problem in anything else... I think my 'unplug' solution is effectively the same as the 'Disable Microsoft eHome Infrared Transceiver' solutions mentioned above...

P.S. Should have said - the above is with a UK keyboard

Dosbox uses SDL as the input API, and SDL in turn uses Win32 API or DirectInput. It would be best to fix the problem in SDL. SDL allows switching input APIs with SDL_VIDEODRIVER but it also affects video output like the name hints.