386P & Windows: Better DPMI than nothing.

Windows has a built-in DPMI manager, so if you run 
a 386-Powered program in a dos-box under MS-Windows, 386P will "see"
just a DPMI manager.
At program startup you probably will see lots of
"Calling DPMI function 501h to allocate extended memory" messages
Don't worry, it's 386P trying to get all the lockable extended memory
available (Windows doesn't return the exact free memory available)

Expect to get slower execution speed, under DPMI some instructions
are emulated thru software traps (i.e. OUT,CLI,STI and other)
and this causes some speed problems
And some hardware portions are virtualized (the page flipping system
gets screwed up because the virtualized I/O doesn't mimics 
the VGA status port correctly).
Maybe things will be better under Windows 4.0 (hope so).
You'd better 
 RUN AT FULL SCREEN and in "exclusive" mode (no background tasks
 and other crap like that)
 and set the following option into SYSTEM.INI
  TrapTimerPorts=False
or the code will run VERY slow and "bursty".

When you try the example programs expect troubles from example1.asm
because Windows virtualizes the Programmable Interval Timer
that generates IRQ0 (on my system the IRQ overhead when playing at 8008hz
is so high that the system looks locked up)(but after a while
you see signs of computing :} ).