XMS - I had no problem with using HIMEM.SYS. I used NETHACK, so I think that XMS was ok (or does DPMI uses memory directly?). Anyway: this was originally developed as one possibility to run Windows 3.x, so XMS had to be ok (it is impossible to start Windows without XMS driver).
Booting with just HIMEM.SYS in CONFIG.SYS was ok without any error messages.

EMS - EMM386.EXE complained about something, so there was probably no EMS. I did not expriment.

SoundBlaster: it is normally usable, just BLASTER variable is not defined.

MOUSE: you must load mouse driver. I used the one which I had to my Logitech mouse and it worked ok (although I tested it only in one program - Volkov Commander).

CD ROM: probably not possible

Directories mounted by MOUNT command: not possible

Mirek

Do you claim the sound blaster would just work natively without drivers?!

And did you talk about a USB mouse?

YES. Remember: you are still in DOSBOX - so you have SoundBlaster and PS/2 mouse. It has nothing to do with you actuall hardware !
Mouse and sound work perfectly. I tried a few games.

EMS works as well, you just must set another frame for EMS. I added FRAME=e000 to EMM386.EXE and it worked (EMM386.exe complained that there is ROM or RAM there, but I ignored it). Maybe a better frame address could be found.
I used succesfully Ultima Underworld 1 and 2 which definitely require working EMS.
Another usefull thing: loading things to high memory works as in normal DOS (when you need to free memory)

Mirek

So what's your exact line in config.sys for emm386?

I'm curious as to why you'd be trying to use EMM386/HIMEM when capability for EMS/XMS is built-in with no loss on the conventional mem side.

@guest:
device=c:\dos\emm386.exe FRAME=e000

It complains, but it works... I did not try to look for better value.

@snover:
We are talking here about booting another DOS version in DOSBOX:
1. Is the standard XMS/EMS support in DOSBOX usable when booting another DOS version?
I think that I tried one game without using HIMEM.SYS etc. and it complained ... But I will try it again.
2. I wonder: would loading of drivers to upper memory worked without EMM386.EXE?

Mirek

That line worked, thanks!

Anyway, you don't need to run a game to test your memory.
That's what mem.exe is for...

So without config.sys, you can see that:
1) XMS is 0.
2) EMS is just not listed anywhere.

After having the following config.sys:

1device=himem.sys
2device=emm386.exe FRAME=e000

Then:
1) XMS is no longer 0, but a positive number in Megas.
2) EMS is mentioned (and with a positive number in Megas).

mirekluza wrote:

2. I wonder: would loading of drivers to upper memory worked without EMM386.EXE?

no, you must have at least
device=c:\dos\emm386.exe noems

by the way it is always usefull to use "verbose" to be able to see additional information
device=c:\dos\emm386.exe noems verbose