Xref: utzoo comp.os.msdos.programmer:5656 comp.os.msdos.misc:2474
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!public!btr.com!timlee
From: timlee@public.btr.com
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.misc
Subject: "Fixing" high memory after Windows
Keywords: DPMI himem.sys VCPI
Message-ID: <3077@public.BTR.COM>
Date: 16 Jun 91 01:10:24 GMT
Sender: timlee@public.BTR.COM
Reply-To: timlee@btr.com (Timothy J. Lee)
Followup-To: comp.os.msdos.programmer
Lines: 17

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.