Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Child processes in Mess-DOS, and/or reducing code size
Message-ID: <8153@tekgvs.LABS.TEK.COM>
Date: 20 Sep 90 15:48:22 GMT
References: <1990Sep19.224551.27226@gpu.utcs.utoronto.ca> <26263@cs.yale.edu>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 32

In article <26263@cs.yale.edu> spolsky-joel@cs.yale.edu (Joel Spolsky) writes:
>In article <1990Sep19.224551.27226@gpu.utcs.utoronto.ca> sarathy@gpu.utcs.utoronto.ca (Rajiv Sarathy) writes:
>>Problem: a program that's too large to fit in memory.
>>Environment: C language in MS-DOS 3.x

>The easiest way to solve this problem:

>(1) Rush out and buy Borland Turbo C, and use its linker.
>(2) Use VROOM. It will do all the housework you need for overlays
>    automatically. Just divide your code up into segments and it will
>    automatically make sure that any segments that are in use are
>    loaded. It can even swap stuff into extended memory...

>Simple and elegant.

>In fact, you don't even need to buy Turbo C, just the Turbo Assembler
>Debugger, which comes with TLINK, the linker, the latest version of
>which will compile Microsoft .OBJ's fine.

Before people run out and buy the wrong thing, VROOM comes in the latest
Turbo Tools package, and in Turbo C++ (not Turbo C v 2.0) which also has
a C compiler option. 

There is a compilation switch you must use to use VROOM. Therefore you cannot
use VROOM with Microsoft .OBJ's. You must use Turbo C++ (or its C option) and/
or TASM.

Also, only code segments can be swapped. Data segments must always be resident.

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply