Close dosbox and restart it, takes a fraction of a second.

If you want to test much games after each other, closing-restarting is really annoying. that's why this feature request 😀

That's the wrong way to test DOS games too....or hell even Windows games.

If your testing your games that way then your doing it wrong.

then please tell me how to test games the right way because you only have 2 choices: exit the game itself or close dosbox.

what other way do you have in mind ?

Restart DosBox after testing each game.

ermm I just said my feature request would make it possible not to do this for each game because it's annoying if you test much games.
so what's your point??

Use a dosbox frontend (see that sticky topic), and close the games by closing dosbox.

Mounting directories manual in dosbox takes about the same time as making a game profile, but once you got a game profile, you can start the game again in just 2 or 3 mouse clicks.

TheDude wrote:

ermm I just said my feature request would make it possible not to do this for each game because it's annoying if you test much games.
so what's your point??

Even closing games using the quit capability in the game itself you cannot be sure that the game cleaned everything up on quitting which is why alot of times you had to reboot in DOS on a real machine when you wanted to play another game. Now you want to add a function to quit the game that isn't supported by the game itself and then run another game.....and you want to do this for compatibility testing of games.....

See the problem here?

Execute DosBox and launch the game, if you don't want to quit the game normally then hit CTRL+F9 and then launch DosBox again.

Compatibility testing isn't about just loading games and testing away, there is alot more to it than that.

Either way it won't be added any soon.

DosFreak wrote:

Now you want to add a function to quit the game that isn't supported by the game itself and then run another game.....and you want to do this for compatibility testing of games.....

See the problem here?

no, there is no problem because the developers of dosbox can make sure that 'kill game' command initializes dosbox the same way as if you first booted it (initialization of all variables, objects, ... in the source code just like they are initialized/created when dosbox first starts).

maybe when we have savestates that you restore the starting state.
but until then there is no intention of adding it