Xref: utzoo comp.os.msdos.programmer:1026 comp.lang.c:31974
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!quasi-eli!cs.yale.edu!spolsky-joel
From: spolsky-joel@cs.yale.edu (Joel Spolsky)
Newsgroups: comp.os.msdos.programmer,comp.lang.c
Subject: Re: Child processes in Mess-DOS, and/or reducing code size
Message-ID: <26263@cs.yale.edu>
Date: 20 Sep 90 04:04:47 GMT
References: <1990Sep19.224551.27226@gpu.utcs.utoronto.ca>
Sender: news@cs.yale.edu
Followup-To: comp.os.msdos.programmer
Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
Lines: 20
Nntp-Posting-Host: zoo-gw.cs.yale.edu
Originator: spolsky@suned.CS.Yale.Edu

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.

Joel Spolsky
spolsky@cs.yale.edu                                     Silence = Death