VOGONS

DOSBox doesn't work on my machine

Topic actions

First post, by stevesk

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hello people! I am having problems with three versions of DOSBox. Here is my computer config:

Motherboard: Intel D865GBF - http://www.intel.com/products/motherboard/d865gbf/ - Using a Pentium 4 HT 3.0Ghz Processor with 1MB cache, 512MB RAM, Video: ATI Radeon 9550 offboard (AGP). Sound: on-board (Intel AC97 Adapter).

Operating System: Slackware Linux - Current, Kernel 2.6.17.4.

How did I install DOSBox: From the source, no extra parameters on ./configure . My Gcc version: 3.4.6.

Well, first what happens in DOSBox 0.62/0.63:

It runs okay, until I try to install a program (i.e. game, windows 3.11, etc.). The installer always give errors about being unable to install the files, and when I exit it, dosbox closes with the following output:

Segmentation fault

There are no other messages, only two reporting errors about sound but sound even works ok when I tried to run games which didn't need to be installed. When running games, dosbox also quits with the same output message insted of giving me back to the command prompt.

When I try to run DOSBOX 0.65:

My keyboard goes messed up. I have a ABTN2 layout keyboard which is not much different from U.S. default one (the position of "?", ":", "/", etc. changes but not the position of "a", "b", "c", "d", it keeps the same). When I press the keys, always a wrong output is given. E.g. I press CAPS LOCK, it outputs "m" and keeps writing a bunch of "mmmmmmmmmmmmmmmmmmmmmmm" until I press it again, so it stops giving me the bounch of "mmmmmmmmmmmmmmmmmmm". Sometimes if I press another key DOSBox even freezes. Not only DOSBox, but all my linux box! 😖

Is there any way to resolve these problems? Thanks! 😀

Reply 1 of 5, by wd

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

Sounds really odd. What SDL version is it? Does changing the
output= in dosbox.conf work any better? Or setting the
usescancodes=false?

Maybe you could compile dosbox from the sources and see if
it behaves different.

Reply 2 of 5, by stevesk

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Thanks for your reply, wd. I am using SDL 1.2.10 . I tried to change the ouput in /.dosboxrc from surface to overlay, opengl and openglnb but didn't sole anything. I also had set usescancodes=false in the same file but it also didn't work...and I am already compiling from the source 😉

Is there anything else I can do? 🙁

Reply 3 of 5, by stevesk

Posted on 
User metadata
Rank Newbie
Rank
Newbie

*solve anything 😀

Reply 4 of 5, by wd

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

> and I am already compiling from the source

Ah sorry, didn't see that.

Do you (or some other Slackware user) know if this appeared with
earlier kernels/distributions as well?

You could try it with sound disabled in dosbox.conf (nosound=true)
or a different linux sound interface, and maybe testing an older
version of SDL (1.2.7/1.2.😎.

Reply 5 of 5, by stevesk

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hey wd and folks! Well, I don't know about older kernels and distributions of slackware. I asked the IRC channel but just one guy was using dosbox and for him the things were working ok (though he said me he doesn't use dosbox too much). So I downgraded my SDL, here are the results:

DOSBox 0.63: I tried 2 older versions of SDL, 1.2.7 and 1.2.9 . Amazing! It worked well on both!!! Now I don't receive segmentation faults messages anymore (at least for the moment 😉 ). I am risking myself saying that, but I think the problem is solved! 😀

DOSBox-0.65: The problem persists, even trying older versions of SDL. The same problem, without any modification... 🙁

So for the moment I can only use DOSBox-0.63... 🙁

But, at least, half of the problem is solved! Thanks a lot wd!

Go to top of page Go to top of page
Back to DOSBox General
Close window
Close window