How come PMODE/W takes a little while to load under EMM386?
PMODE/W allocates all of its extended memory pool during initialization whereas DOS/4GW allocates memory every time you (or the C libraries) call the DPMI memory allocation functions. The delay is caused by EMM386’s slowness in allocating pages. PMODE/W may take a little longer than DOS/4GW at startup in this case, but it will be much faster during the execution of the program since it does not need to call EMM386 for memory again after that. If the delay is a problem, you can adjust the amount of extended memory to allocate in PMWSETUP. The less memory there is to allocate, the faster loading will be under EMM386. However, keep in mind your memory requirements when changing that setting. How come DOS/4GW, Pharlap, or other 32bit DOS applications don’t work using spawn() under PMODE/W? Some other DOS extenders require extended memory to initialize. Also, the program you are trying to run may require extended memory. To remedy this, you can change the maximum amount of extended memory f
