Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Programming questions
Message-ID: <26372@sun.uucp>
Date: Mon, 24-Aug-87 14:02:07 EDT
Article-I.D.: sun.26372
Posted: Mon Aug 24 14:02:07 1987
Date-Received: Tue, 25-Aug-87 04:26:35 EDT
References: <4119@udenva.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 29

In article <4119@udenva.UUCP> pbrody@udenva.UUCP (Paul Brody ) writes:
>	I am asking this question for a programmer friend of mine who is 
> currently working on a new piece of software for the Amiga. He is having
			^^^
> some trouble with getting access to the KS1.2 protected ram.

> Question:
> Where, on the KS1.2 disk, is the code that writes to the memory, (F80000
> being the believed location in memory) that write protects the KS1.2 ram ?
> The purpose being to put some NOPS on the KS1.2 disk that will disable the
> code and consequently leave the KS1.2 ram unprotected.

First the answer to this question can be ascertained by studying KS and the
Commodore schematics but the 64K question is Why?!!? A) If it is new software
why target a machine that will be only half the installed base by christmas?
KS is in ROM on the 500, and 2000. Don't you want these folks to buy your 
programs too? Also unless you recompute the Kickstart checksum you will find
your machine dieing with a 'ROM Failure' I believe.

> Please send reples to:
> pbrody@udenva

Sorry Paul, but this is one of those things that it is pretty silly to put
into a released product. I can understand hacking at it to figure out the
machine, just keep it out of any products I might pay money for and find
out that it doesn't work on my machine.
--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.