Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!wagner
From: wagner@utcs.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Mac vs. Amiga (really Atari vs. Amiga)
Message-ID: <1987Jan23.124111.13153@utcs.uucp>
Date: Fri, 23-Jan-87 12:41:11 EST
Article-I.D.: utcs.1987Jan23.124111.13153
Posted: Fri Jan 23 12:41:11 1987
Date-Received: Fri, 23-Jan-87 21:50:56 EST
References: <8701220147.AA26540@cory.Berkeley.EDU> <11902@sun.uucp>
Reply-To: wagner@utcs.UUCP (Michael Wagner)
Organization: University of Toronto Computing Services, general purpose UNIX
Lines: 20
Checksum: 65062

In article <11902@sun.uucp> cmcmanis@sun.uucp (Chuck McManis) writes:
>But Matt they don't have the nifty SetFuncion() call nor the RomTagsInRam
>stuff that makes little fixes easy. With a "Rom conversion" to 1.2 and
>the Additional 256K ram you get out of it (your WCS becomes fast ram)
>You can put simple changes for the ROM into RAM. With the proper Tags 
>the ROM will pick them up as replacements for its internal routines.
>Really an elegant compromise. (You can even go back an load your 1.1
>Kickstart to run brain damaged EA programs, but I don't think it will
>be write protected then. 

A while ago I asked if anyone had any documentation other than the
teasing reference in the Enhancer manual for RomTagsInRam.  I don't
think I ever saw any answers.  Someone out there must know something
about this feature.

People from time to time have spoken about writing their own
device drivers.  I spoke of perhaps front-ending the trackdisk.device.
We would need this information to do the job properly.

Michael