You should first specify what you mean by “Dos program”: $Bill has killed Dos starting with Win NT, and if you try to run a real 16 bits Dos application in gui mode (including the command prompt), you shall receive the message “XXX is not a valid windows 32 application”.
I suppose we are therefore talking not of real Dos mode applications (note that the link of the OP has 2 links for the game, one under Windows and the other one for Dos), but of Windows dos emulation.
In order for these applications to run (and speaking of XP), they must be launched, depending of how they are written, either by ntvdm or wowexec.
Let’s make the test (i am running cis v3, proactive, firewall custom, defense+ paranoid with every parameter checked, xp pro sp3).
Launching the first dos executable i have found in my software collection partition: fdate is a time managing dos utility, running from the command line without whatever installation (other, of course, then specifying the path if not default). (http://www.ferg.org/fdate/index.html, http://brucine.perso.neuf.fr/logs/fdate.zip)
There’s therefore no sense in launching FDATE.EXE, as the correct handling is to use it in batch scripts, something looking like:
Fdate /Ff /Oddmmyy /VDDAY
POWERARC -a -s -c4 I:\%DDAY%.zip F:\*.*
If, nevetheless, i click FDATE.EXE, it is intercepted by a defense+ request allowing explorer to run ntvdm.
But, you are right, and altough this click only returns informative stuff, the specific dos executable is not recognized as such, but only as a ntvdm generic request.
Now, let’s download the said game (adom_winbeta4).
Launching the game (i am not a gamer, but it’s the dumbest thing i ever saw, no gui, no action, no nothing…) now asks for explorer to execute Adom_winbeta4.exe, it is a normal behavior.
If wanting to run the Dos version (ADOM.EXE in adom111, but why would one want to do that?) i receive the same request than in the FDATE.EXE test.
Isn’t the “issue”, if any, in your CIS version and/or settings?