Type in "ver" for programs run in DosBox.

I think it's also in the video bios if you want to use an HD image.

get vesa mode information
it contains some words about dosbox

Though scanning the vga rom area for a dosbox string might be best,
as vesa might not be present (cga/vgaonly etc.)

DosFreak wrote:

Type in "ver" for programs run in DosBox.

What about someone running another COMMAND.COM inside DOSBox? It would return it's version on "ver", not the DOSBox version.

Qbix wrote:

get vesa mode information
it contains some words about dosbox

Indeed this helps, thanks. Using Interrupt 10.4F00, one can get DOSBox strings (even the version) as VBE2 vendor/model string.

wd wrote:

Though scanning the vga rom area for a dosbox string might be best,
as vesa might not be present (cga/vgaonly etc.)

Looking into the C000h segment I didn't find a string I could search. Do you know one?

OTOH I played with the dosbox.conf (setting different "machine=" values) file and the VESA method always worked. So the problem only occurs with DOSBox versions compiled without VESA? Then it wouldn't be too bad, as it seems to me they're non-standard.

Hm indeed no usable strings there. If you still want to use some rom scanning
use the values at 0xf000:0x2000 which are quite unique due to the callbacks.

Which data is that? More important: Is it constant for most DOSBox versions? (Yeah, I could grab a few and test it myself, but if someone else already knows it...) And how many byte is this structure?

Just look at it, if possible with the debugger (data AND code). It's a list
of int xx (where x is from 0 to 0xff) followed by the return callbacks.
This data is very unlikely to change and should always be accessible.

Now I got it, thanks. Anyway, my debugger always shows data and code 😀

Usually the data view!=code view though.