Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!aunro!ersys!bns From: bns@ersys.edmonton.ab.ca (Chris Dollmont) Newsgroups: comp.lang.pascal Subject: Re: SHRINK BEFORE RUNNING A CHILD PROCESS Message-ID: Date: 16 Jun 91 18:37:39 GMT References: <00949F69.12225740@EA.USL.EDU> Organization: Edmonton Remote Systems, Edmonton, AB, Canada Lines: 35 callawaycj@EA.USL.EDU (C.JamesCallaway) writes: > In article <11940@j.cc.purdue.edu>, zhou@brazil.psych.purdue.edu (Albert Q.Zh > >In Turbo Pascal, the dynamic memory to be used in a program has to be > >specified during the compilation by $M. However, when you run a child > >program with exec, you can not use any part of the memory already > >allocated for the heap even if it is free. Is it a way to get around this? > > > > > Maybe This Will Help! > > _TURBO_PASCAL_INTERNALS_ By Tischer Pub. ABACUS > > Contains Source For A Unit That Will Free Up Almost All Memory Used By Your > Program. When The Child Process Is Executed Your Program Is Saved To Disk > (Or Memory If Using VDISK, RAMDISK). After Termination Of The Child A Small > Block Of Code Added To The Child Will Install The Saved Program And Execution > Picks Up Just Like Normal. Sounds Pretty Useful, I'll Never Have A Need For I > > Also In The Book Are Units For Mouse Support, Managing Windows, Writing TSR's > Understanding Interrupts, Multitasking In TP, Using EMS And Extended Memory. Additionally, there is a unit by Kim Kokkenen (TurboPower) that does the same thing in a slightly more elegant fashion. The unit is available on Compuserve (and most local BBS's) and is usually bundled with a variety of tools for memory management. If only I could remember what it was called! Chris | Chris Dollmont | USENET: bns@ersys.edmonton.ab.ca | Blue North Software | Mail: 16936D 85th Ave. | | Edmonton, AB T5R 4A3 | These opinions remain valid only as long as they are visible...