Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user maak ! (Registered 2024-04-18) You are not logged in - nap
CSDb User Forums


Forums > CSDb Discussions > Winvice 3.1 34049M - ignoring vmk files?
2017-11-07 04:09
mstram
Account closed

Registered: Dec 2013
Posts: 112
Winvice 3.1 34049M - ignoring vmk files?

It seems that Winvice 3.1 34049M is ignoring the keyboard (vkm) files.

The "A", "D", and "W" keys are not mapped correctly on my Win 7 / Lenovo R500 laptop.

While trying to decipher the vkm files, I swapped the "A", and "B" definitions, and it had no effect.

So I completely removed all vkm files from the C64 directory, and the keyboard still gives the same results ("A" is blank, "D" is "2", "W" is "back arrow".

**
With WinVice 2.1 (the only other version of WinVice I have), if I remove the vkm files, all the keys return "nothing" (except for the ... keys which is strange), but more what I would I expect than what ver 3.1 (34049M) is doing).

I haven't tried downloading today's "nightly build" yet, but I checked the bug tracker and haven't seen anything reported about vkm files.

** btw why does the "monitor" (alt-m) keyboard work perfectly? I ASSume it does NOT use the "mapping" / vkm mechanism ?
2017-11-07 08:40
JackAsser

Registered: Jun 2002
Posts: 1987
Report bugs here: https://sourceforge.net/p/vice-emu/bugs/
2017-11-07 11:39
chatGPZ

Registered: Dec 2001
Posts: 11100
it should work, did you perhaps use an old vice.ini? try deleting it and start vice

and well, reporting bugs for the windows UI is pointless at this point, they wont get fixed anymore - you'll have to wait for the gtk3 ui
2017-11-07 14:39
mstram
Account closed

Registered: Dec 2013
Posts: 112
Quote: Report bugs here: https://sourceforge.net/p/vice-emu/bugs/

Create Ticket popup

"To create a new ticket you must be authorized by the project admin"
2017-11-07 15:07
Compyx

Registered: Jan 2005
Posts: 631
You need a SourceForge account to be able to report bugs.
2017-11-07 15:56
mstram
Account closed

Registered: Dec 2013
Posts: 112
Quote: it should work, did you perhaps use an old vice.ini? try deleting it and start vice

and well, reporting bugs for the windows UI is pointless at this point, they wont get fixed anymore - you'll have to wait for the gtk3 ui


It's working !

I deleted vice.in from C:\Users\user\AppData\Roaming\vice\3.1\vice.ini .. restarted.

Thanks for the tip !

I wonder if it was copying vice.ini from my vice 2.1 ?

**Symbolic - win_sym.vkm ** works.
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
HBH.ZTH/Abnormal
CA$H/TRiAD
radius75
Hok/Remember
Sentinel/Excess/TREX
Guests online: 90
Top Demos
1 Next Level  (9.8)
2 Mojo  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Comaland 100%  (9.6)
6 No Bounds  (9.6)
7 Uncensored  (9.6)
8 Wonderland XIV  (9.6)
9 The Ghost  (9.6)
10 Bromance  (9.6)
Top onefile Demos
1 It's More Fun to Com..  (9.8)
2 Party Elk 2  (9.7)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.5)
5 Rainbow Connection  (9.5)
6 Wafer Demo  (9.5)
7 TRSAC, Gabber & Pebe..  (9.5)
8 Onscreen 5k  (9.5)
9 Dawnfall V1.1  (9.5)
10 Quadrants  (9.5)
Top Groups
1 Oxyron  (9.3)
2 Nostalgia  (9.3)
3 Booze Design  (9.3)
4 Censor Design  (9.3)
5 Crest  (9.3)
Top Graphicians
1 Sulevi  (10)
2 Mirage  (9.8)
3 Lobo  (9.7)
4 Mikael  (9.7)
5 Archmage  (9.7)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.065 sec.