If a program doesn't claim to use XMS or EMS memory, chances are it's
   a protected mode program. DOOM by id and Descent (TM) by InterPlay are
   two such programs.
   
   In this program's Memory tab, turn off EMS and XMS memory, and set
   DPMI to whatever the game requires, or leave it on Auto. Auto mode
   will make Win95 allocate more RAM to the game as needed, but it will
   cause extra disk swapping. Set this to the game's recommended value,
   no higher than your total memory actually installed in the computer.
   
   If the game does its own disk swapping (like Descent does), fix the
   DPMI memory value to the game's recommended value and don't use Auto.
   There's no point in having Win95 and the game do swapping at the same
   time.
   
   Some DPMI games do bizarre stuff and may crash Win95 the first time
   running. If so, turn on the "Protected" switch just below the
   conventional memory setting. This will virtualize most of the I/O
   space in that game's DOS session. Turning on "Prevent DOS programs
   from detecting Windows" might help too. If the game does hardware
   detection, try by-passing it and specifying your video and sound card
   properties in the game manually. Descent has troubles detecting sound
   cards in a DOS session, for example.

     * 12.5.1. How come Strike Commander (TM) doesn't work? (And other
       VCPI programs) 
       
   Breidavick Gistiheimili told me that Strike Commander wouldn't run in
   a DOS Session because it couldn't communicate with the "EMS Memory
   Manager". In reality, SC requires VCPI services. Win95 DOS sessions
   don't support VCPI unfortunately. EMM386 normally provides VCPI
   services in real mode.
   
   If you run a game in a DOS session and get a mysterious message to the
   effect that it wants EMM386, it's most likely that it wants VCPI
   memory. You will have to resort to the Single mode DOS techniques
   below to make the game run.