Keyboard doesn't work in ver 1.0 (2 Viewers)

Claus

Portal Member
July 16, 2006
22
1
Home Country
Denmark Denmark
After upgrading from 1.0 RC1 to final 1.0, my keyboard doesn't work anymore.
I tried to copy the keymap.xml from my backup, as recommended in other threads, but that didn't help. (My keymap.xml is attached)
When I hit the "down" key on keyboard i get the following line in the log fil:
WM_KEYDOWN: wParam 40
and when I hit the "up" key on keyboard i get the following line in the log fil:
WM_KEYDOWN: wParam 38

I guess something is happening in MP but I see no effect on the screen.

Pleae help me to fix this problem


TV-Server Version: 1.0.0
MediaPortal Version: 1.0.0
MediaPortal Skin: Blue3
Windows Version: XP SP3
CPU Type: AMD Athlon 3000
HDD: Samsung 500G
Memory: 1GB
Motherboard: Asus A8N-E
Video Card: NVIDIA GeForce 6600
Video Card Driver: 6.14.11.6921
Sound Card: Creative SB Audigy 2 ZS
Sound Card AC3:
Sound Card Driver: 5.12.1.442
1. TV Card: Hauppauge WinTV PVR PCI II
1. TV Card Type: Analog
1. TV Card Driver: 2.0.43.24103
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case: D.Vine 5
Cooling:
Power Supply:
Remote: B&O BEO4
TV: B&O 6000MX
TV - HTPC Connection: S-Video
 

Attachments

  • keymap.xml
    30.6 KB

Claus

Portal Member
July 16, 2006
22
1
Home Country
Denmark Denmark
Please anybody!!!
My mediaPortal isn't worth much without keyboard support!

Extra info: I Checked the log file and got it confirmed that the keymap.xml file I think I'm using is actually the one being loaded. I also tried replace it with a keymap.xml from another computer running MediaPortal with a working keyboard , but same result.

Is there anything in the settings somewhere (e.g. remote control setup) which can "block" the keyboard events? ANY Ideas are very welcome!

Thanks in advance!

----------------
UPDATED:

SOLVED!

Disabling the MAME Devices plug-in fixed the problem.
 

Users who are viewing this thread

Top Bottom