Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!cs.utexas.edu!uunet!philmtl!philabs!ppgbms!paul
From: paul@ppgbms (Paul Evan Matz)
Newsgroups: comp.lang.c++
Subject: Anyone broken the 640K limit w/ Glockenspiel?
Keywords: Glockenspiel DOS 640K
Message-ID: <21684@ppgbms.UUCP>
Date: 1 Dec 89 03:54:45 GMT
Organization: PPG Biomedical Sys., Pleasantville, NY.
Lines: 30

Was hoping someone out there might have some tips for dealing with the
640K memory constraints running a C++ application under DOS.  We've
got the version initially distributed by Oasys, which turned out to
be Glockenspiel's.  We are using release 1.2 E1, and the Microsoft C 
compiler.  The DOS system platform is DOS 3.3, with LIM 4.0.  Our
application is standalone (no network drivers or TSRs, except for
a touch screen sensor driver), so there arn't a bunch of drivers or
TSRs to relocate.  This is a Metawindows library, however.

The application is a user graphical interface that creates many
"display" objects which are kept around forever, and can not really
be organized into groups of mutually exclusive parts to make
overlaying too easy.

Some initial ideas:
a) switch to a more efficient compiler?
b) ways to overlay C++?
c) run some sophisticated memory manager?


Would *really* appreciate any advice.  Please direct any email to
the address below.

Thanks (wishful thinking)
_____________________________________________________________
|Regards,                           One Campus Drive        |
|Paul Matz                          PPG Biomedical Systems  |
|914-741-4685                       Pleasantville, NY. 10570|
-------------------------------------------------------------
path ppgbms!moe!paul@philabs.philips.com