Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!psuvm!dxb132
Organization: Penn State University
Date: Monday, 25 Mar 1991 02:17:55 EST
From: <DXB132@psuvm.psu.edu>
Message-ID: <91084.021755DXB132@psuvm.psu.edu>
Newsgroups: comp.sys.amiga.misc
Subject: Re: KS 2.0 for A1000 (real solution)
Distribution: usa
References: <1991Mar22.170907.26385@ida.liu.se>
 <1991Mar23.035000.11891@fy.chalmers.se>
 <1991Mar24.070304.16395@en.ecn.purdue.edu> <91083.184310LEEK@QUCDN.QueensU.CA>

>In article <1991Mar24.070304.16395@en.ecn.purdue.edu>,                        u
>doctorj@en.ecn.purdue.ed
>(Jeffrey W Davis) says:
>>
>>Now, the non-developers version (Shipped with A3000) can be copied into
>>the address space pointed to by the Frances translation circuitry.

Well, a f80,000 version can be copied into that address space. The A3000
version (taken literally) won't work, because it has A3000-specific
code.

But this is going to become very unimportant when someone makes a
relocatable version of 2.0, which is already easy to do. As a simple
example, you can make a RamKickable (disk resident) module version of
(say) trackdisk.device with a simple program that compares the developer
($200,000) and 3000-Kickstart (f80,000). By the way, the 2.0 trackdisk,
when used with the 2.0 disk.resource, works fine under 1.3. At some
point we'll have a version that loads as an executable file, whereever
you have free memory (although in practice not, because it would
fragment your memory).

Now if you steal my super-genius just-has-to-be-original ideas I'll
sue your mother!!! :-) [Remember       : ideas are worth NOTHING. If you
want to make money how about making a product]

-- Dan Babcock