Xref: utzoo comp.sys.mac.programmer:18652 comp.sys.mac.misc:5067
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!rochester!cornell!uw-beaver!rice!Taffy.rice.edu!jack
From: jack@Taffy.rice.edu (Jack W. Howarth)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac.misc
Subject: Re: ROM in RAM
Message-ID: <1990Nov1.020326.26338@rice.edu>
Date: 1 Nov 90 02:03:26 GMT
References: <1990Oct31.084937.28930@world.std.com> <1990Oct31.171449.26235@midway.uchicago.edu> <1990Oct31.234943.29428@world.std.com>
Sender: news@rice.edu (News)
Distribution: usa
Organization: Rice University
Lines: 7

Actually, putting the ROMs into RAM would not be that hard. The ROMs contain
routines accessed by A-trap calls which vector into ROM so all those would
require is for you to reset the A-trap table by whatever amount of memory
you have moved the ROMs by to map them into RAM. Those parts of ROM that
contain resources other than trap routines (dialog boxes, etc.) would have
to be handled a bit differently.
                   Jack