VOGONS

Common searches


First post, by kruwi

User metadata
Rank Member
Rank
Member

Here's another linux related dosbox question:

How can I change cpu cycles? ctrl+ f11, f12 don't work for me! Could it be that the problem is related to my LAPTOP keyboard?
Another big problem is that I cannot use many keys (For example, I have not yet found out how to type a backslash or a ":") I did not have these problems under win xp.

Reply 2 of 7, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

try
winkey +f11
and winkey + ctrl+ f11
else look at your window manager to see why it steals those 2 keycombo's.

Water flows down the stream
How to ask questions the smart way!

Reply 3 of 7, by Spearhead

User metadata
Rank Newbie
Rank
Newbie

if you are using KDE in default settings ctrl+number is reserved for switching desktops.
Go into the Control Center, look for the keyboard shortcuts and disable the ones that you want to use in DOSBox

Reply 5 of 7, by kruwi

User metadata
Rank Member
Rank
Member

All riddles solved!

I finally managed to upgrade do dosbox 0.65!!!!!!!!!!! After reading a linux beginner's book and some computer-magazines. The only question remaining: Why did suse not include ver 0.65 from the very beginning?

I'm able to adjust cpu-cycles via ctrl+win+F11/F12.

The keyboard problems are obviously related to ver 0.63, as they are gone in 0.65.

Thanks for your help, though.

Reply 6 of 7, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Different Linux distributions use different package management methods to retrieve packages from the internet. These packages are usually only updated if someone "out there" is interested in compiling the latest DosBox and updating the package.

Also DosBox 0.65 has "only" been out since March so it's somewhat understandable.

How To Ask Questions The Smart Way
Make your games work offline

Reply 7 of 7, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

> The keyboard problems are obviously related to ver 0.63

No, they come from the fact that SDL does a symkey translation
under localized linux (german keyboard layout in your case)
so we cannot do a direct symkey-to-key translation. We tried
to get rid of this by using the scancodes directly (which,
funny enough, led to a huge translation-table itself).