Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.misc
Subject: Re: Few questions/observations about the A3000
Keywords: KS 2.0
Message-ID: <21180@cbmvax.commodore.com>
Date: 2 May 91 23:38:15 GMT
References: <1991Apr23.143421.17738@javelin.sim.es.com> <1991Apr24.172714.462@daffy.cs.wisc.edu> <1991Apr24.214121.4631@javelin.sim.es.com> <1991Apr25.154002.4471@daffy.cs.wisc.edu>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 27

In article <1991Apr25.154002.4471@daffy.cs.wisc.edu> pochron@cat52.cs.wisc.edu (David Pochron) writes:

>Unfortunately, the 2000 doesn't have a socket for 32 bit ROMs, 

Not surprising, since it doesn't have a 32 bit anything as far as the hardware
is concerned...


>so when 2.0 comes out, I will be stuck with losing 512K of my memory...BUT....If there
>were a way to install the 3000's 32 bit ROMs onto the A2630 board, you had
>better believe I would do it in a moment's notice!  (Hint, hint, D.H...A great
>A2630 daughterboard project... :-)

Well, strangely enough, that could be done, though not quite the way you're
thinking.  A3000 ROMs looks for A3000-specific hardware that won't be on an
A2500.  So they'll go into one of their friendly error notification loops.
However, you can do it the way we brought up the A3000, with two A2000 ROMs
sitting side-by-side.  The A2630 daughterboard can intercept any bus address
its designed likes, so this wouldn't be all that difficult to manage.

>          David M. Pochron   | Transparent DWV pipe:  For the man who wants to


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
      "That's me in the corner, that's me in the spotlight" -R.E.M.