VOGONS


DOSBox 0.70 crashes on me

Topic actions

First post, by tymime

User metadata
Rank Newbie
Rank
Newbie

I've been very happy with 0.65, so when I heard of the new version, I got it immediately.
But every time I try to start it up, it makes an attempt at loading the configurations, and then crashes. I've tried modifying dosbox.conf, updating DirectX, and even reading a few online tutorials, but nothing works. What's going on?

(P.S. Computer stats- Windows XP Home Edition, SP1, HP Pavilion a400y, Pentium 4 CPU, 260GHz, 504MB RAM)

Reply 2 of 49, by tymime

User metadata
Rank Newbie
Rank
Newbie

It came with a new one for some reason.

Reply 3 of 49, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Maybe your download was corrupted? Uninstaill, dowload again, and re-install.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 4 of 49, by red_avatar

User metadata
Rank Oldbie
Rank
Oldbie

How about deleting the dosbox.conf - or rename it - and see if it works like that.

Reply 5 of 49, by tymime

User metadata
Rank Newbie
Rank
Newbie

No good. 🙁

Reply 6 of 49, by eL_PuSHeR

User metadata
Rank l33t++
Rank
l33t++

Try different output=xxxx modes.

Try a different SDL.DLL

Intel i7 5960X
Gigabye GA-X99-Gaming 5
8 GB DDR4 (2100)
8 GB GeForce GTX 1070 G1 Gaming (Gigabyte)

Reply 7 of 49, by tymime

User metadata
Rank Newbie
Rank
Newbie

Nothing...

Reply 8 of 49, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Try setting the environment variable SDL_VIDEODRIVER=windib
and update your graphics card drivers.

Reply 10 of 49, by ErikGG

User metadata
Rank Member
Rank
Member

wd : didn't DOSBox from 0.65 on do that automatically?

I did have DOSBox 0.70 crash on me once by setting the windib value though. But that also happend to me with 0.65 though. Not on my desktop.

D.O.G. currently removes that value if a DOSBox 0.65, 0.66 or 0.70 version is run.

Erik.

Read the new FAQ.doc

Reply 11 of 49, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

No, actually it depends on the SDL version. <1.2.10 defaults to directx,
1.2.10 and above default to windib. As the windib driver is slower and
has bad keyboard input dosbox forces directx for >1.2.10 as well,
so it matches the old behaviour.
Still it's something to try with weird crashes.

Reply 12 of 49, by tymime

User metadata
Rank Newbie
Rank
Newbie

I just found the problem- the DirectDraw Acceleration was turned off for some reason. Thanks for the help, guys. 😀

Reply 14 of 49, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Funny, that causes crashes? Good to know.....

Reply 15 of 49, by gulikoza

User metadata
Rank Oldbie
Rank
Oldbie

One maybe related issue...
Trying to force windib with SDL_VIDEODRIVER and having output=ddraw will only show blank screen. It's funny cause output=surface works with windib. Log:

SDL_Init: Starting up with SDL windib video driver.
Try to update your video card and directx drivers!
CONFIG:Loading primary settings from config file dosbox.conf
MIDI:Opened device:win32
Failed to create ddraw surface, back to normal surface.

I have no idea why it would then fail to create the surface 😕

http://www.si-gamer.net/gulikoza

Reply 16 of 49, by ArtillaryGoat

User metadata
Rank Newbie
Rank
Newbie

I have the same problem, however I have a 500Mhz G3 iBook 192 MB RAM OS X 10.3.9

I am not particularly experienced with editing config files (though I understand the basics), and was also hoping someone might know the mac-specific settings I need to fix.

Reply 18 of 49, by ArtillaryGoat

User metadata
Rank Newbie
Rank
Newbie

Railraod Tycoon Deluxe, Colonisation, MOO, Scorch... They all work fine with a frameskip of 2 or 3 😁

Reply 19 of 49, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
gulikoza wrote:
One maybe related issue... Trying to force windib with SDL_VIDEODRIVER and having output=ddraw will only show blank screen. It's […]
Show full quote

One maybe related issue...
Trying to force windib with SDL_VIDEODRIVER and having output=ddraw will only show blank screen. It's funny cause output=surface works with windib. Log:

SDL_Init: Starting up with SDL windib video driver.
Try to update your video card and directx drivers!
CONFIG:Loading primary settings from config file dosbox.conf
MIDI:Opened device:win32
Failed to create ddraw surface, back to normal surface.

I have no idea why it would then fail to create the surface 😕

I have been busy trying to get my own MSYS/MinGW build of DOSBox-0.70 to work. Initially I got my self-compiled dosbox-0.70 to work with a pre-compiled SDL-1.2.11 from http://www.libsdl.org/release/SDL-devel-1.2.1 … -mingw32.tar.gz. Then I decided to have a go using a locally compiled version from http://www.libsdl.org/release/SDL-1.2.11.tar.gz. Didn't work 🙁 🙁

The DOSBox status window showed up with its "CONFIG: Using default settings. Create a ........" message, and immediately after Windows put up a dialog: dosbox.exe has encounted a problem and must be terminated. And I was offered to send an error-report to Microsoft.

I tracked down all the SDL-files that my from-the-sources-version installed, removed them, and installed the pre-compiled version. Worked. Removed the working version, recompiled my own version, installed, and got the same problem.

I then discovered the test-programs that comes with SDL. None of them crashed.

I tried starting DOSBox with different variations of DOSBOX_SDL_OUTPUT=xxxxx, but I still got the same crash.

Only when I started it with SDL_VIDEODRIVER=windib wouild my DOSBox start up with my from-the-sources version of SDL-1.2.11.

So now I ask you gentlemen: What can I have done wrong? Any compile flags that I need to set when compiling SDL? Any debugging flags I should try to set when compiling DOSBox?

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32