Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Problem when booting A2620 card
Message-ID: <16317@cbmvax.commodore.com>
Date: 5 Dec 90 18:14:31 GMT
References: <1719@syteke.be> <1990Dec4.201722.3506@agate.berkeley.edu>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 41

In article <1990Dec4.201722.3506@agate.berkeley.edu> felixh@tsunami.Berkeley.EDU (Felix Hack) writes:
>In article <1719@syteke.be> jim@syteke.be (Jim Sanchez) writes:
>>I hope someone has seen this before but when I boot my 2000 w/A2620
>>card in the "both mouse buttons pushed" mode I get an error message to
>>the effect "Out of config memory" or something similiar.  If I then
>>try to enter the 68000 mode, the system hangs up.  

>  I too get this message when trying to boot into the 68000 on
>my 2000, equipped with A2620 (2 Meg 32-bit RAM), Trumpcard
>SCSI interface, and Meta-4 Memory board (2 Meg 16-bit RAM).
>  However, the system doesn't hang, it works just fine
>in 68000 mode (where the 2 MB of 16 bit Fast RAM are really
>nice).

There are two problems at work here.  The double-mouse-button-reset trick will
kick in the autoconfig routines found in the A26x0 ROM.  Some early versions
of this ROM get confused about certain autoconfig devices, especially 128K
autoconfig units.  The best solution, if you don't like the "out of config
memory" message, is to order the latest ROMs from Commodore service.  Though
you really shouldn't need them for normal AmigaOS operation.

The ROM problem shouldn't cause a crash with the 68000 on, but you can easily
crash when changing from '020 or '030 to 68000.  This is basically an AmigaOS
anomoly, caused by the fact that AmigaOS was never built expect the CPU type
to change between warm boots.  Basically, when you power up, Exec is built up
from scratch, including placement of all the CPU type specific goodies.  When
you reboot, Exec looks around, sees that it's still living, and doesn't try
to rebuild everything, including the CPU type stuff.  So going straight from
68020/30 to 68000 operation causes the '020/'030 code to be in place for the
68000, which give you a great crash.  You can safely get to the 68000 either
by directly cold booting into it, or (if you have SetCPU V1.6), typing
"SetCPU ROMBOOT" to reset your system and erase ExecBase, of course grabbing
the mouse buttons after you give the command.

>  Felix


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
		      Wheeeeeeeeeeeeeeee...........