[SOLVED] DosBox keyboard wrong without running from KDE.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Iím currently running Slackware 14_64 Iíve recently change lilo from the 80x25 text to 800x600x32 graphics mode. As a result, I have developed a problem with DosBox 0.74. From KDE it runs great. (in terminal mode) however, if I use Dosbox prior to loading KDE, the keyboard is all wrong. Itís like everything thing has been shifted to the left and down a row. The letter N is the Enter Key, with the left hand Alt key as the N key. The top row of letters (qwert) are numbers. Also everything to the right of the J key doesnít do anything from what I can tell.
I have searched the web about key mapping. It seems to be mainly for people who want to remap a certain few keys. Also when most people complain about keys being wrong, they tend to be talking about 1-3 keys, not the whole board.
Here is what Iíve done to date. Iíve went into dosbox.conf and change keyboard to us103 from auto. Iíve also started dosbox in KDE using the Ėstartkeymapping command. It created the keymap file with the keys mapped correctly. However, neither actions changed the result of booting up and starting DosBox without running KDE.
Has anyone else had this issue? Do we know if itís DosBox rev level related or just DosBox as a whole. Lastly and more importantly, has anyone developed a cure lol.
No need to make. It was a wheeze, because terminals in X read ~/.bashrc or /etc/bashrc and consoles read ~/.bash_profile or /etc/profile or /etc/profile.d. The idea was to get your X locale settings in console.
OK, the long way: run
from both kde terminal and console, and compare relevant differences. See if there's a language or something different, and if you have an icon for dosbox, see if there's switches included.
Well I have ran both conditions of printenv. From what I can make, there are several differences between terminal and prompt. But from a Font stand point the only thing I could find was the fact that KDE (X) uses a ghostscript. I did some homework and found that a ghostscript of 386 is designed for DOS coding and Windows 3.X However, apparently the gs command is for when in KDE only. When I tried it on boot up I got an error about missing some X component.
I've got a feeling this issue is bigger than me and I can't seem to find anything on the net. Given that I run from KDE most of the time, It's not that big of an inconvenience. I only tried it so I compensate for a graphics issue I have in KDE. When I use eclipse to program a console program, the screen won't switch to the correct screen resolution. I don't have that problem when I run the program from the prompt before KDE loading. I won't bore you with the drawn out story, I've started a thread a week or so back with no results. The option of working before loading KDE was a potential solution I was going to try.
I was thinking particularly about locale settings, as I thought they would influence the codepage chosen. Can you put a config.sys or autoexec.bat in dos box? That might handle it. IIRC there were three commands needed. It's been ~15 years since I farted with any of this, so this is _very_ rough at the edges.
mode con codepage prepare (codepage)
mode con codepage load (codepage)
ansi.sys gave the special characters (128-255), and was usually left out.
BK, thanks . I'll play around with the config.sys and autoexec.bat files. Like you I haven't messed with DOS for some years, though I still has an IBM P70 luggable I fire up on e every other week lol. I'll keep you posted one the out come. Thanks again and Happy Thanksgiving or it's equivalent where your at
Lol true. Seem like space age technology at the time. I loved it so much I've kept it.
VGA gas plasma screen with abilily to hook up VGA monitor
60 meg HD
One 25 serial port
One parallel port
PS2 mouse port
Windows 3.1 IBM DOS 6.22
Oh and it was micro channel at that.
Yep others have come and gone in this household but it just keeps on keeping on lol
Yeah, but being able to take your Doom or MS Quick C on the go made it way too cool. I used to do some coding for a local computer shop, so being able to upgrade from a PS2 286 for free and still keep my new 8513 monitor made it too good to pass up. If you get curious, I found this site a while back
Well I figured it out. I opened the dosbox0.74.conf file and actually read it instead of "scan" it lol. I found something about "usescancodes: Avoid usage of symkeys, might not work on all operating systems." So I found a few lines down from that the usescancodes section and turned it from true to false and my problem went away. Now DOSBox works both in KDE as well as console prior to loading KDE up.
Hope this helps someone
Last edited by Ace Blackwell; 11-25-2012 at 10:41 AM.
I put one through my hands myself, it turns out. It died with hard disk errors, and I couldn't quite find the same enthusiasm you had for yours. Enjoy while it lasts, or sell it to a collector - somebody with your love of trailing edge technology and more money :-).