Keyboard problems in Windows 7
 

Hi,

Not really a problem but more a solver for all ppl having problems with Windows 7 and some keys:

Right Shift
equal sign
etc..

Toni has added a -rawkeyboard option which is cool, but you can get rid of this problem definitely in Windows (works for other games/apps like Visual Pinball, emulators...) and so you can run WinUAE without an infamous .bat file :)

Check your computer "device manager" window in "keyboards" section

You have MCIR 109 keyboard installed for sure (maybe more than once). The keyword is "MCIR". Show properties, update driver and select HID compliant device (select from a driver list on my computer) and voilà.
Sorry if this is slightly inaccurate: my windows version is french and I'm trying to guess the keywords.

Original answer here: http://forums.techguy.org/hardware/6...isappears.html

I have PS/2 keyboard on my Win7, hence no probs :p
Well, the "dernier cri" of technology is not always the best thought ^^

MCIR = MC Infra-Red!
That's why your problem report should only apply to users requiring to install the MCIR 109 infrared controlling device driver for making use of either:

- an infrared-controlled keyboard
or
- an infrared-controlled gamepad
or
- an infrared-controlled USB numpad device

you're right, but I have no infrared keyboard, and those drivers prevent me from using keyboard properly in most games & emulators (does not work even on my builtin laptop keyboard)

This is not a problem anymore, since 2.2 rawkeyboard is the default :)
(as long as there is at least one rawkeyboard detected, fallback is old directinput mode)

Thanks Toni that's great news.

I'm usuing WinUAE 2.2 and just discovered my keyboard isn't working.

I've gone through WUAE's config screen a dozen times and can't see anything to help.

I'm using a wireless keyboard, would that cause an issue?

Standard debugging: attach winuaebootlog.txt and winuaelog.txt (enable logging in misc panel before starting emulation)

Here we go....

I should have thought about logging, just didn't see the darn switch, d'oh.

How do you know there are keyboard problems when you are booting using non-working configuration? (no KS ROM)

Test keyboard using A500 or A1200 quickstart configuration and some WB disk. Use of some random game for keyboard testing is bad idea.

EDIT: Do you mean nothing happens if you select "Test" (button in Input or gameports panel) and press keys? Not even F12?

It worked fine with WB 1.3. I shall have another poke and see what I can do.

Thanks again :)

It's working fine now. Sorry for being such a twerp :(

I shall now go and wander in the wilderness to seek forgiveness. I say 'wilderness', I mean Chiswick.

I'm sure Toni has got one brown paper bag spare for you. The mighty Amiga Gods shall accept this as thy atonement; hail thee lone wanderer :D