ooops, forgot. I am using your latest version 0.61.

Probably OpenGL bug (search forum for more information). Basically DOSBOX 0.61 requires working OpenGL - even when its use is not specified in DOSBOX.CONF.
Try to install different (newer) drivers for your graphic card.

Mirek

After trying a little further I moved the Dosbox folder up a level (don't ask me why), so it sits right under my root C:

The program seemed to open a little longer. Still a split second before it closes. It is opening a DOS box with some error messege. I am trying to capture each word as it opens and closes rapidly. So far all I can read it is Loading settings from config..." that is all I can read. Do I have to create a config file first? I see no mention of this in the INSTALL or README files.

The second line of text says "fatal signal..." and that is all I can catch of the second line.

It then also for a split second opens a second window labeled SDL_app and that's it.

Hope that helps.

just take the advice from mirek.

After attaching the above information do you still think it's a vid card driver issue? Hate messing with something if it ain't broke.

Yes. You are not the first one with this problem. I saw it myself.

Theoretically it can be something different, but with 90% probability it is OpenGL. Just try version 0.60 - 0.60 was without OpenGL.

The next version will not have this bug

Mirek

Thanks for such a quick response. I am d/l the latest drivers but will try version 06.0 first.

😀

ok... really dumb here but the only .60 version I see ends with .rpm. Never seen that. How do I open it?

I am having the same problem ... I have a voodoo 5 5500 (yeah I know ... oldass card) ...

I suppose I have to wait for the next ver.? ... is 0.60 still around?

http://sourceforge.net/project/showfiles.php?group_id=52551

look here for 0.60 and 0.58

Had the same problem with win xp. (playing railroad tycoon)
Fixed it with version 0.60.
At 0.62 download page.
I found a link to this page.

http://sourceforge.net/project/showfiles.php?group_id=52551

uninstall 0.62 and reinstall 0.60.

Works fine now

RockWopster: ponyboy had this problem with dosbox 0.61.
I think dosbox 0.62 should not have this problem.