Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: A3000 DATA Cache (Can we PLEASE Settle this?)
Message-ID: <22512@cbmvax.commodore.com>
Date: 17 Jun 91 20:39:26 GMT
References: <1991May26.091925.20814@news.iastate.edu> <21999@cbmvax.commodore.com> <274.2857ae21@intersil.uucp> <22458@cbmvax.commodore.com> <276.285b897c@intersil.uucp>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 29

In article <276.285b897c@intersil.uucp> hamilton@intersil.uucp writes:
>In article <22458@cbmvax.commodore.com>, daveh@cbmvax.commodore.com (Dave Haynie) writes:

>> I can think of three reasons this might be happening:

>> 3) You have the latest ROM image on disk, but an old version of SetPatch.

>I just re-wrote my startup-sequence so the very first three lines are:

>	CPU
>	SetPatch
>	CPU

>So it's not SetPatch, 

What leads you to believe it's not SetPatch?  I pointed out that, very 
recently, the software people seem to have decided that enabling the data 
cache in ROM is a compatibility problem, since some 1.3 things that autoboot
from floppy have cache compatibility problems.  The fix, as they explained
it, was to enable the data caching in SetPatch.  So, it would be reasonable
to conclude that you have an old SetPatch.

Any different explanation will have to come from the software people...


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"This is my mistake.  Let me make it good." -R.E.M.