Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!haven!adm!cmcl2!lanl!opus!jthomas
From: jthomas@nmsu.edu (543)
Newsgroups: comp.arch
Subject: Re: Self-modifying code
Message-ID: <JTHOMAS.89Oct18152705@tecate.nmsu.edu>
Date: 18 Oct 89 21:27:05 GMT
References: <6481@pt.cs.cmu.edu> <9175@etana.tut.fi> <672@sce.carleton.ca>
	<1148@crdos1.crd.ge.COM>
Sender: news@nmsu.edu
Organization: NMSU Computer Science
Lines: 13

In article <1148@crdos1.crd.ge.COM> davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) writes:

bill>   You *may* be thinking of the CP/M system generation. Since the o/s was
bill> written in absolute assembler it was shipped to run in a small (maybe
bill> 16k) system. When you created a larger version there was the original
bill> o/s and a list of locations which needed to be changed. The builder
bill> took a copy of the o/s and added a constant to each of the locations in
bill> the list.

And CP/M got that (too) from RT-11 which did it at initialization and got
it from .... ::-{})

Jim Thomas