Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!crdgw1!vdsvax!trub!perley
From: perley@trub.crd.ge.com (Donald P Perley)
Newsgroups: comp.sys.amiga
Subject: Re: The Inevitable 1.4 Rom Problem
Message-ID: <10579@vdsvax.crd.ge.com>
Date: 8 Jan 90 15:11:47 GMT
References: <9001062100.AA02144@jade.berkeley.edu> <3981@orion.cf.uci.edu>
Sender: news@vdsvax.crd.ge.com
Reply-To: perley@trub.crd.ge.com (Donald P Perley)
Organization: GE Corp. R & D, Schenectady, NY 12345
Lines: 26

In article <3981@orion.cf.uci.edu> easu021@orion.oac.uci.edu (Jason Goldberg) writes:
>I tend to agree with Dave that the software should run on 1.4 and we should
>not need to be able to run 1.3/1.2 on our A500/2000's.  But I did find it
>a little funny that Dave didn't mention that he wrote a great little 
>utility called SetCpu which as I understand it allows you to load KS
>into RAM among other things.  I use it to load KS from ROM into 32 bit
>RAM but as I understand the DOCS you could also load KS from DISK to 16
>bit RAM.

Doesn't SetCpu use the memory management unit on your accelerator to remap
the kickstart memory?  That won't work on a normal (500/2000) amiga.

Another scheme is to insure that the jump tables returned from the
library open point to your ram copy of kickstart (isn't this the idea
behind setpatch?) Considering that the programs for which you want
KS1.2 aren't following the normal rules anyway, this probably won't
work either. 

Using SetCpu on a 2500 is no guarantee of success either.  A game that breaks
the rules on Kickstart may have some "feature" that is incompatible with
your processor, like using busy loops for timing.


-don perley

perley@trub.crd.ge.com