My Dosbox 0.70 kept crashing on launch; I now know why (bug) \ VOGONS

My Dosbox 0.70 kept crashing on launch; I now know why (bug)

Topic actions

First post, by QuantumBinary

Posted on 2007-03-22, 06:18

QuantumBinary Offline

Rank Newbie

Rank: Newbie
Posts: 2
Joined: 2007-03-22, 04:21

I've used Dosbox for quite a while now and only had a problem when I moved to dosbox 7.

- Fresh install, new folder, no files.
- Will *always* crash on opening.
- The *only* way I can actually open it is to OPEN a dos window (start/run/cmd) and then REMOVE the active status from it by clicking somewhere on the desktop and THEN launching Dosbox. Launching this way has a 100% success rate. Everything else crashes on launch.

By crashing, I mean the following: goes to a full black screen with a line of text on the top and crashes 1/4 second after with a windows error regarding sdl.dll

I have tried re-downloading, re-installing, deleting and re-installing and even changing the settings per readme and forum advice. All to no go.

Like I stated, I can only open it (Dosbox) by pre-opening a DOS window first and then removing the active status of the DOS window by clicking on the desktop. Only then can I launch Dosbox 0.70

Just thought I'd let you folks now. Hope this helps others...

I managed to slow the PC down (by launching 3 massive applications at the same time) and thus, was able to read what flashed on the screen before the flash: "Using the default settings: Create a config file to change them."

------------

After having played with it a while, It now gives me a sdl.dll not found. even on a fresh re-install.... It's late, I give up..

Reply 1 of 12, by Freddo

Posted on 2007-03-22, 06:31

Freddo Offline

Rank Oldbie

Rank: Oldbie
Posts: 583
Joined: 2003-10-29, 21:56
Location: Sweden

Tried different outputs?

Reply 2 of 12, by QuantumBinary

Posted on 2007-03-25, 15:45

QuantumBinary Offline

Rank Newbie

Rank: Newbie
Posts: 2
Joined: 2007-03-22, 04:21

As stated in my post, I followed all forum and readme troubleshooting advice.

I actually posted the comment thinking that the programmers could possibly use the info.

*Addendum: I have modified my DOS window properties in the past. I'm thinking that is has something to do with that. I will run further tests on another machine and see if the modification to the properties is responsible for the dosbox crashing.

After all, I love your software; It's the least I can do. <grin>

Reply 3 of 12, by wd

Posted on 2007-03-25, 15:54

wd Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 10813
Joined: 2003-12-03, 21:23

Yes think those "start command window in fullscreen" kicks it out,
try removing that property, or fiddle with the SDL_VIDEODRIVER
environment variable (set it to windib or directx).

Reply 4 of 12, by Hacker

Posted on 2007-03-31, 20:19

Hacker Offline

Rank Newbie

Rank: Newbie
Posts: 4
Joined: 2007-03-31, 16:04

Hi,
I am experiencing the same behavior with 0.70 - instant crash at startup. Unfortunately, not even opening another Command prompt window solves it.

wd,

Yes think those "start command window in fullscreen" kicks it out,
try removing that property, or fiddle with the SDL_VIDEODRIVER
environment variable (set it to windib or directx).

How would I go about that? You probably are not talking about dosbox.conf.

TIA
Roman

Reply 5 of 12, by wd

Posted on 2007-03-31, 20:29

wd Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 10813
Joined: 2003-12-03, 21:23

Open a command shell window, navigate to the dosbox0.70 directory
and type "SET SDL_VIDEODRIVER=windib", then type "dosbox".

Or in control panel/system/advanced/environment add that SDL variable
and start dosbox through the start menu.

Do you have updated graphics drivers/directx?

Reply 6 of 12, by Hacker

Posted on 2007-03-31, 20:48

Hacker Offline

Rank Newbie

Rank: Newbie
Posts: 4
Joined: 2007-03-31, 16:04

Ah, one has to set it, thanks. 😀
Works now with that variable, thanks again. 😀

Do you have updated graphics drivers/directx?

As updated as possible. 😀 Unfortunately, the newest drivers for the Matrox Marvel G400 are the internal Windows XP drivers.
DirectX 9.0c.

Reply 7 of 12, by wd

Posted on 2007-03-31, 20:52

wd Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 10813
Joined: 2003-12-03, 21:23

Maybe you still can find out why it needs windib, can for example happen
when the default command shell window has the "start maximized" set.

Reply 8 of 12, by Hacker

Posted on 2007-03-31, 21:00

Hacker Offline

Rank Newbie

Rank: Newbie
Posts: 4
Joined: 2007-03-31, 16:04

Well, if I type cmd it does not start maximized. Or do you mean something else?

Reply 9 of 12, by DosFreak

Posted on 2007-03-31, 21:26

DosFreak Offline

Rank l33t++

Rank: l33t++
Posts: 13655
Joined: 2002-06-30, 16:35
Location: Milliways

Can the drivers for the other G400 models be used with the Marvel?

I thought DosBox reverted to WinDib now?

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

Reply 10 of 12, by Hacker

Posted on 2007-03-31, 21:32

Hacker Offline

Rank Newbie

Rank: Newbie
Posts: 4
Joined: 2007-03-31, 16:04

Can the drivers for the other G400 models be used with the Marvel?

There would most probably be some compatibility issues, and I'd probably lose the bit of video capture functionality I have.

Reply 11 of 12, by wd

Posted on 2007-03-31, 22:39

wd Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 10813
Joined: 2003-12-03, 21:23

I thought DosBox reverted to WinDib now?

No, SDL switched to windib by default and dosbox forces directx
(so the old "good" behaviour is still default).
But there's a bug in the fallback code which causes crashes when
the directx video driver can't be initialized for some reason.

Reply 12 of 12, by DosFreak

Posted on 2007-03-31, 22:41

DosFreak Offline

Rank l33t++

Rank: l33t++
Posts: 13655
Joined: 2002-06-30, 16:35
Location: Milliways

Hmmm, guess I'll look around on the net for issues with SDL and G400's...

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

Go to top of page Go to top of page

Back to DOSBox General