Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!maytag!watstat!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.lang.pascal
Subject: Re: Large memory pascal programs & 386
Message-ID: <1331@maytag.waterloo.edu>
Date: 19 Jan 90 13:40:03 GMT
References: <1964@uwm.edu> <5050@hydra.gatech.EDU>
Sender: daemon@maytag.waterloo.edu
Reply-To: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Organization: U. of Waterloo, Ontario
Lines: 23

In article <5050@hydra.gatech.EDU> bb16@prism.gatech.EDU (Scott Bostater) writes:
>In article <1964@uwm.edu> duncan@csd4.csd.uwm.edu (Shan D Duncan) writes:
>>
>>We need to set up a system to run pascal programs that need large
>>amounts of memory (1+ Mb).  The programs we would like to run are
>>from the phylip set and are written in standard pascal but have
>>been ported to turbo pascal.
>>
>
>You didn't mention whether you had one huge array of data or lots of small
>arrays.  If you don't need to access arrays >64K then one solution is to 
>use EMS memory. TP 4/5/5.5 comes with an example program that shows how to
>access EMS memory from within TP.  It isn't exceptionally pretty, but it can
>work. (transfering data from one EMS array to another EMS array might be
>rather kludgy)

Turbopower's Turbo Professional library handles EMS and extended memory well,
and their soon-to-be-released (that's been the status since last August!) 
Object Professional does it even better - your program needn't know whether
it's using EMS, extended, or disk.  Slower than true 32 bit operation, but
well worth looking at.

Duncan Murdoch