Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!bloom-beacon!spdcc!ima!esegue!johnl
From: johnl@esegue.segue.boston.ma.us (John R. Levine)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Separate overlay files w/ MSC
Message-ID: <1989Oct4.150541.264@esegue.segue.boston.ma.us>
Date: 4 Oct 89 15:05:41 GMT
References: <8000057@m.cs.uiuc.edu> <5484@ucdavis.ucdavis.edu>
Reply-To: johnl@esegue.segue.boston.ma.us (John R. Levine)
Organization: Segue Software, Cambridge MA
Lines: 17

In article <5484@ucdavis.ucdavis.edu> foss@iris.ucdavis.edu (Jim Alves-Foss) writes:
>I have heard of other linkers (PLINK (?)) that let 
>[put overlays in separate files.]

PLINK-86 does indeed let you put overlays in separate files.  It also
gives you considerably more control over the overlay structure, and does
it in a more transparent way so that indirect calls to overlaid code works,
unlike Microsoft.  The bad news is that Codeview doesn't know about that kind
of overlay so you have to use PFIX-86, which is a competent debugger but
does not have source debugging features as good as Codeview.

PLINK and PFIX were written by Phoenix Technologies, the famous BIOS
people but were recently sold to Polytron in Hillsboro OR.
-- 
John R. Levine, Segue Software, POB 349, Cambridge MA 02238, +1 617 492 3869
johnl@esegue.segue.boston.ma.us, {ima|lotus}!esegue!johnl, Levine@YALE.edu
Massachusetts has 64 licensed drivers who are over 100 years old.  -The Globe