Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!munnari.oz.au!metro!usage.csd.unsw.oz.au!hydra.maths.unsw.OZ.AU!1013734
From: 1013734@hydra.maths.unsw.OZ.AU
Newsgroups: comp.sys.amiga.hardware
Subject: Re: 68020 MEMORY ERROR
Message-ID: <1632@usage.csd.unsw.oz.au>
Date: 28 May 91 07:15:17 GMT
References: <1991May27.132900.28266@comspec.uucp>
Sender: news@usage.csd.unsw.oz.au
Reply-To: 1013734@hydra.maths.unsw.OZ.AU.unsw.oz (Peter "Silicon Head" Urbanec)
Organization: University of New South Wales, Sydney, Australia
Lines: 44

In article <1991May27.132900.28266@comspec.uucp> jeffg@comspec.uucp (Jeff Goebel) writes:
>I have a friend who recently bought a 68020 board I had been using for a few
>years.  On my system it worked, but on HIS, he gets a "Memory Configuration
>Error" when he does a reboot holding the two mouse buttons.
>
Well, well, well, I have had almost exactly the same problem. I sold my 68020
board out of my A2500 to a friend of mine. When he holds the buttons down
he gets "Out of Autoconfig memory space" or something like that. I can't
remember exactly what it was.

The A2620 (With 2 Meg of Fast RAM) works perfectly on my system with A2090A
hard drive controler in slot 1 (closest to the CPU slot). His system has an
A2091 in slot 1. I thought that the problem might be due to the fact that the
2 Meg of Fast RAM tries to Autoconfig into the same memory area as the A2091,
but I could be wrong.

>Oh - Forgot to mention.  It's the COMMODORE 68020 board, so a reboot while
>holding the mouse buttons brings up the 68000 or 68020 menu.  When he gets
>the error here, it still seems to work, but not as well as it should.
>
>When he operates in 68000 mode, programs which USED to work no longer do
>100%.  A few games screw up etc.  He blames me.  I don't have an answer.
>

I didn't do any extensive checking of the system performance, but at a glance
everything seems to work OK. (BTW: Some stuff doesn't work with the A2620 or
A2630 in place, even if you switch back to 68000 mode. Titanics music trax #1
and the new Enigma demo seem to be a few examples.)

>Do you?

I have no answers. I think that Dave Haynie might be able to answer our
questions, since he is the guy who designed the A2620. (I think he did, looking
at the circuit diagrams for it.) Then again, it may be a software fault in the
ROMs and someone else could be responsible.

Any comments Dave?

				Peter Urbanec.

			 1013734@hydra.maths.unsw.oz.au
			s1013734@spectrum.cs.unsw.oz.au

		---- The only sin is stupidity. ----