Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!snorkelwacker!usc!cs.utexas.edu!jarvis.csri.toronto.edu!torsqnt!lethe!geac!maccs!cs4g6ag
From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: CLIPPER OVERLAY HELP
Message-ID: <25D61910.29614@maccs.dcss.mcmaster.ca>
Date: 12 Feb 90 02:01:52 GMT
References: <90021007304075@masnet.uucp> <7453@yunexus.UUCP>
Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Organization: McMaster University, Hamilton, Ontario
Lines: 17

In article <7453@yunexus.UUCP> rreiner@yunexus.UUCP (Richard Reiner) writes:
$MS Link has been able to do overlays for years.  It has the added
$advantage of keeping the overlay code in the .exe file, rather than
$littering your world with .ovl files.

   PLINK will also do internal overlays if you want them.  However, there
may be valid reasons for not wanting them.  For example, let's say your
program's .EXE is 450K and you want to distribute it on 360K disks but
don't want to have to archive it and provide an unarchiving program.
If you can split it up into a 350K executable and one or more overlays,
you can now distribute it.

-- 
Stephen M. Dunn                               cs4g6ag@maccs.dcss.mcmaster.ca
          <std_disclaimer.h> = "\nI'm only an undergraduate!!!\n";
****************************************************************************
               I Think I'm Going Bald - Caress of Steel, Rush