Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!jarthur!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Amiga 1000/ AmigaOS 2.0 / Expanded Memory
Message-ID: <13231@cbmvax.commodore.com>
Date: 16 Jul 90 18:14:19 GMT
References: <7102@scolex.sco.COM>
Reply-To: daveh@cbmvax (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 23

In article <7102@scolex.sco.COM> brianm@sco.COM (Brian Moffet) writes:

>Could someone explain to me why the expansion memory to be used
>for Amiga OS 2.0 has to be the first item on the bus (on a 1000)?

Well, one setup built for developers without MMUs uses a special version of
KickStart assembled for a base address of $00200000.  A program is used to
load this special KickStart into autoconfig RAM at $00200000, reset the
system, re-configure just that one RAM board, and then start up the new OS.
If the first autoconfig device isn't RAM, this scheme won't work.

This is, of course, only of interest to developers using these special 2.0
beta releases.  This isn't something that will persist for the release, ROMed 
version of 2.0 that will eventually be created.


>Brian Moffet	ext 3567	


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"I have been given the freedom to do as I see fit" -REM