timlee@public.btr.com (06/16/91)
If himem.sys is in config.sys, Windows (3.0) can run in protected mode. Here is the problem: With himem.sys, running Windows, Intel Code Builder C (iCC 1.0), or other DPMI extended program (i.e. anything linked with iCC) causes subsequent executions of Pharlap 386|* (2.2d), MetaWare High C (2.3), or any VCPI extended program (i.e. things linked with Pharlap 386|link) to be unable to find enough memory. Removing himem.sys removes this problem, but removes the possibility of running Windows in protected mode. What would be nice to know is if there is a simple way to "fix" the memory after running a DPMI program so that VCPI programs can find the memory again. Please email replies.