The keys were working in dosbox he said, so there's no problem with missing keys in the mapper file.
but wasn't working before, as his first post already stated he replaced the driver, and he said that he was messing with mapper a lot (so i guess he was deleting it many times before too, as he already know how to do it and where to find it)
but wasn't working before
But it was working after he replaced the keyboard driver so the mapper content is irrelevant.
> I had already been messing around with the .conf file and the mapper config file, so possibly if I had gone right to just changing the 109 driver from the start, I would have been done.
Nevertheless I mainly wanted to report a bug in mapper combined with keyboard too (not only with joystick).
Nevertheless I mainly wanted to report a bug in mapper
Right i guessed that, but steps for reproducing that (deleting lines from
mapper.txt is not something i care about) would be helpful.
http://i.frazpc.pl/pliki/2002/board_graf/1137 … 43795049612.jpg
this is similar to my keyboard cheapest ps2 nothing special.
Windows XP installs for it Logitech PS2 keyboard driver.
I have changed driver to standard pc/xt ps2 keyboard. I expected less buttons but all of them were still working.
I have changed driver to standard japan 106/109 ps2 keyboard:
in windows everything works correctly, but in dosbox: `, =, ], ' (four keys in total) doesn't work. Keymappers says unknown key when i try to add it) Mapper is not broken when i save it, all keys are mapped properly. When i run dosbox with sdl_videodriver=windib all keys work correctly in dosbox, (well the "win" and "menu" keys still doesn't work - "unknown key" but i guess that is normal)
Of course when i remove keyboard driver, the default logitech is loaded and all keys work too (except win/menu keys)
btw - when i was changing drivers windows complained sth about ps2 mouse driver...
You can check it yourself.
synholiday right-shift key was called an unknown key for you in the mapper when you tried to add it?
Thanks for the info. I don't see an easy way to add support for this type
of keyboard change. But mapper reset was already mentioned elsewhere.
