Windows 10 ruining dosbox?

[Pandersmack]

I have been enjoying the commander keen complete pack for a few months now, but yesterday my comp auto-updated to windows 10 and now dosbox wont work at all. Is anyone else experiencing this problem?

[Engwathang]

No. I got Win10, and the complete pack works fine for me

[monkeymadness]

Originally posted by Pandersmack:

I have been enjoying the commander keen complete pack for a few months now, but yesterday my comp auto-updated to windows 10 and now dosbox wont work at all. Is anyone else experiencing this problem?

Does dosbox not work at all or is it commander keen that is having the problem? How are you lauching the game? And when was the last time that you played the game before the problem occurred (a day before the update, months ago?)? If you could provide some info on what is happening when you try to play this can help solve the issue. You can't just assume that the Windows 10 update is causing the problem.

[redskeletons]

Won't open for me, period, from Steam..Running Windows 10. DosBox crashes.

[monkeymadness]

This should work:

Solution:
Look for the [keen(#).conf] file in C:Program Files>Steam>SteamApps>common>Commander Keen>base(#)>

Open it up with notepad and change the output=overlay (If that one doesn't work opengl or openglnb should, but ddraw and surface do not work when playing straight from steam and the default probably is set to surface)

If your game is having issues with the screen resolution, you want want to edit some other values in the keen.conf file.
This would be changing fullscreen=true, fulldouble=true, and fullresolution=[your screen's resolution]
Eg. fullresolution=1366x768 (When I first got the game it was running super wide and some of the game was cut off)

Save the file and it is ready to go.

A full discussion can be found here.
http://steamcommunity.com/app/9180/discussions/0/458604254423716777/

[monkeymadness]

PS This will need to be done for each game. This is if you want to run the game from steam. Another option is to just click on the bat file.

Found in C:Program Files>Steam>SteamApps>common>Commander Keen> labelled [Keen #.bat]

[peter.mercer]

Same problem. Just had steam auto-update now I cannot run anything from the DOSBOX DOS emulator which simply crashes.

[DrStatic]

Originally posted by monkeymadness:

This should work:

Solution:
Look for the [keen(#).conf] file in C:Program Files>Steam>SteamApps>common>Commander Keen>base(#)>

Open it up with notepad and change the output=overlay (If that one doesn't work opengl or openglnb should, but ddraw and surface do not work when playing straight from steam and the default probably is set to surface)

This worked for me, thanks.

[monkeymadness]

Originally posted by peter.mercer:

Same problem. Just had steam auto-update now I cannot run anything from the DOSBOX DOS emulator which simply crashes.

Did you try the above?

[monkeymadness]

For anyone wondering, I tested the game on windows 10 and the game runs. The issue is not windows 10, if your game is not running it has something to do with the way dosbox is set up (the output). If one of the outputs does not work another should, sometimes the output does not work with certain card/driver combos. I'm also almost positive that steam is still installing the old version (Dosbox .63) for this game. So I would also recommend updating to Dosbox .74 instead of using the old one.

[Pandersmack]

Originally posted by monkeymadness:

For anyone wondering, I tested the game on windows 10 and the game runs. The issue is not windows 10, if your game is not running it has something to do with the way dosbox is set up (the output). If one of the outputs does not work another should, sometimes the output does not work with certain card/driver combos. I'm also almost positive that steam is still installing the old version (Dosbox .63) for this game. So I would also recommend updating to Dosbox .74 instead of using the old one.

Yeah, so the weirdest thing is on my way to trying your remedy i selected the game programs from the common folder and they ran perfectly fine. In fact they ran even better than before, i could never play them full screen but now i can and the only thing i did different was access them from a different place... weird. But thanks for the advice. Great games! :)

[redskeletons]

Originally posted by monkeymadness:

This should work:

Solution:
Look for the [keen(#).conf] file in C:Program Files>Steam>SteamApps>common>Commander Keen>base(#)>

Open it up with notepad and change the output=overlay (If that one doesn't work opengl or openglnb should, but ddraw and surface do not work when playing straight from steam and the default probably is set to surface)

If your game is having issues with the screen resolution, you want want to edit some other values in the keen.conf file.
This would be changing fullscreen=true, fulldouble=true, and fullresolution=[your screen's resolution]
Eg. fullresolution=1366x768 (When I first got the game it was running super wide and some of the game was cut off)

Save the file and it is ready to go.

A full discussion can be found here.
http://steamcommunity.com/app/9180/discussions/0/458604254423716777/

Which folder am I going into and what am I changing? Changing 800x600 to 1920x1080 in all four folders, did nothing.

How do I know if it's crashing due to some other issue, and how do I rectify that?

[monkeymadness]

The most important thing to change is the output if the game is crashing. The other stuff just improves the resolution. So just change output=overlay. 90% of the time it will work. If your computer is different then you might need to try output=opengl, but that should get the game running. Try it on one of them. Once you found what works, change the others and enjoy!

[Koji]

I was running this game fine earlier today, just updated Steam not too long ago and I get this same issue with all dosbox games.. This is true for my windows 10 machine as well as my windows 7, my question is, would I have to find this same file in all of my games to get them to run? I found that running the batch file of the games in their directory seemed to work alright, but steam's loading of dosbox does somethin to it now.. so yeah, do I need to do this for all my .conf files or is there a way to do this for dosbox itself?

[redskeletons]

Setting to output=opengl fixed it for me. Thanks!

[monkeymadness]

Originally posted by Koji:

I was running this game fine earlier today, just updated Steam not too long ago and I get this same issue with all dosbox games.. This is true for my windows 10 machine as well as my windows 7, my question is, would I have to find this same file in all of my games to get them to run? I found that running the batch file of the games in their directory seemed to work alright, but steam's loading of dosbox does somethin to it now.. so yeah, do I need to do this for all my .conf files or is there a way to do this for dosbox itself?

So here is the thing. Although I'm not 100% sure on what the steam play button does (what file it is referencing), it seems to be running each game from their seperate config files (which is honestly quite annoying in my opinion). This means that if you want to use the play button, then you would have to change each one. If you ran the game from dosbox itself, then you would be able to use the one config file to play all the games, but then you would have to locate the files.
For example:

C:> cd Keen
C:KEEN> cd base1
C:KEEN>BASE1> keen1

Most people do not understand how this works, but if you do then this would work fine. Or you could create the shortcut for the BAT files and this should also run the games. Anyways, lots of options, but the easiest probably is to change the output a few times and run the game on steam if you don't really know how DOS works.

Originally posted by faze:

Setting to output=opengl fixed it for me. Thanks!

Glad it works!