Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!gradient.cis.upenn.edu!ferris
From: ferris@gradient.cis.upenn.edu (Richard T. Ferris)
Newsgroups: comp.os.msdos.misc
Subject: Re: Qemm troubles
Summary: Similar problems
Keywords: qemm
Message-ID: <44738@netnews.upenn.edu>
Date: 17 Jun 91 12:20:18 GMT
References: <sunshine.677124931@convex.convex.com>
Sender: news@netnews.upenn.edu
Reply-To: ferris@gradient.cis.upenn.edu (Richard T. Ferris)
Distribution: usa
Organization: University of Pennsylvania
Lines: 17
Nntp-Posting-Host: gradient.cis.upenn.edu

In article <sunshine.677124931@convex.convex.com> (Roger Sunshine) writes:
>Every so often, when running qemm and any program which makes extensive
>use of the extended/expanded memory it provides, my pc will get an interrupt
>13 (general exception), usually in the middle of running a command.  Most
>recently, it likes to occur when running Borland c++'s integrated environment
>and attempting to compile something.  I have seen the problem in qemm 4.2 -
>the current 5.1x ...

I have just installed both QEMM and Borland C++ on my Gateway 486/33
and I have found a similar problem.  When I use the /X option in the
buffers line in config.sys, I cannot run C++ from Windows 3.  I get a
system integrity error.  Taking the /X option out makes everything
fine.  Strange? Any ideas?

--RF
Richard Ferris
ferris@grad1.cis.upenn.edu