DosFreak, very clever. Works well too And to finish off this thread, MiniMax's suggestion to use multiple -config's solved my cascading problem. However, an automatic implementation would be awesome too.

Alright. But as I said above, I was able to suppress it by putting my autoexec in a config file instead of a batch file.

Qbix, I can redirect the "Welcome to DOSBox v0.72", etc, in the blue box?

Actually... before running your test, I just noticed this in my terminal window on my Mac: DOSBox version 0.72 Copyright 2002-2007 DOSBox Team, published under GNU GPL. --- CONFIG:Loading primary settings from config file DOSBox Preferences CONFIG:Loading additional settings from config file ./X-COM …

wd, it was a response. Please try not to be a prick. MiniMax, "Welcome to DOSBox v0.72", etc, in the blue box.

Well, DOSBox does not display the startup text on both my Mac and Windows machines. But, like I said, only when -config is used. And I always use @echo off. And I don't know what it would do in a non-DOSBox environment.

Is "cycles=4000" a standard DOS thing for autoexecs, or just DOSBox? I didn't know this could be done outside of a config file. Also, I prefer doing things in a config file because it loads faster and does not display the DOSBox startup text. This is what I'm looking for with my game launcher which …

MiniMax, but I'd rather not have to define the default one. rcblanke, I don't want to use DGBL.

Fair enough.

In response to Dominus, that is poorly structured XML - opening and closing tags on separate lines. Plus if a newbie accidentally deletes an equal sign, they won't as easily know exactly what to fix. XML has DTD to validate and can pinpoint the error. Plus, all this stuff is freely available without …

But what if I have my own defaults in dosbox.conf? For example, I have "fullscreen=true" in dosbox.conf then I execute dosbox with -conf game.conf game.conf does not contain a fullscreen declaration. When my game loads, it is not in fullscreen as its semi-cascade is dosbox's internal defaults, not …

Well, that's your opinion. However XML is here to stay. 10 years ago you could've said it was a fad, but not now. Being defined and validated by software worldwide confirms it is a standard. And just because of MAME, I never said follow suit. I only said that it is a standard, and standards are …

It's a standard. People are moving towards standards. So, it matches reality. MAME did it. And MAME is almost as cool as DOSBox.

True, but what newbie would really be looking at the config file source? Most people, including the computer literates, use front-ends nowadays.

XML is pretty much the new standard for config files in programming languages. MAME has updated from their old config format, and I think it'd be beneficial for DOSBox to do so as well.

I think it'd be great if config files could be cascaded. For those reading in that may not know what that means, well... For example, let's say we have a game that must run with cpu cycles set to 4000 while every other game must run at max. You would simply create a new config file for that game …