Reply-To: erik.wachtmeester@bighole.iaf.nl
Jon Hunt wrote in a message to Erik Wachtmeester:
 EW> I'm using Clipper 5.2e and Exospace 1.0g,
 JH> Same here.
Promising... ;-)
 EW> program from within a Clipper program using Clipper's RUN command,
 EW> the calling program can keep up to 155Kb real memory occupied. Is
 EW> there a way to reduce this amount? 
 JH> I use two libraries Overlay for Blinker and the Exospace version
 JH> OverClx, you can use these to specify memory. 
I searched the internet immediately and found SofDesign, a firm in Texas that
sells an Overlay() library. Is that the one you mean? I guess so, because in 
the
demo version there is a file named overclx.lib, but when I used it on one of 
our
major programs, the program halted in a DOSbox under OS/2 (that's the
environment I develop our Clipper apps under). I then tried it on my NT 4 box
(my Delphi development machine), and it halted also.
Maybe it will run flawlessly on a DOS machine, and maybe even on a Win95
contraption, but access violation errors in both OS/2 and NT do not make me 
that
confident in the quality of this library...
Maybe it's the way I tested it (quick'n'dirty, as usual)? I just added 'LIB
overclx' to the linkfile and in the source I only changed the one 'RUN (
cProgram )' line to 'overlay( cProgram, 0, '', '' )'.
Did I overlook something? Or did SofDesign? The Overlay() UDF is written in
assembler they say. Could it be that they leaned too much on DOS's tolerance
towards memory allocations?
Regards,
Erik 
--- ifmail v.2.12-tx8.6
---------------