Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!chrisg
From: chrisg@cbmvax.commodore.com (Chris Green)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 2.0 Compatibility problem
Message-ID: <21692@cbmvax.commodore.com>
Date: 17 May 91 17:33:19 GMT
References: <1991May16.200647.1@happy.colorado.edu>
Reply-To: chrisg@cbmvax.commodore.com (Chris Green)
Organization: Commodore, West Chester, PA
Lines: 28

In article <1991May16.200647.1@happy.colorado.edu> kskelm@happy.colorado.edu writes:
>
>>>   The problem is this: my software package runs on EVERY machine under 1.3,
>>>and I worked to get it 2.0 compatible, which it IS, on every machine BUT the
>>>A3000.  That is, it works FINE on a 3000 under 1.3, but not 2.0; An A3000/2.0
>>>is the ONLY platform it refuses to run on.
>>
>>	Does it work on an A2000 with a 68030 card, under 2.0 with the data and
>>code caches enabled? If not, than you've got either a self-modifying code
>>problem with the code cache, or a 68020/030 instruction set compatibility
>>problem (on the 020/030/010, MOVE SR,xxx is a privileged instruction).
>>	The other thing you might have problems with is that the A3000 has memory
>>above the 16M addressing limit of the 68000.
>
>    The software works fine on *EVERY* platform but A3000 under 2.0; it works
>on a 500, a 1000, a 2000, a 2500 (all in both 1.3 and 2.0), and it works
>on a 3000 in 1.3, but *NOT* in 2.0.
>

	What are the symptoms of the crash? lockup? guru( what number)?
strange behaviour? 
-- 
*-------------------------------------------*---------------------------*
|Chris Green - Graphics Software Engineer   - chrisg@commodore.COM      f
|                  Commodore-Amiga          - uunet!cbmvax!chrisg       n
|My opinions are my own, and do not         - killyouridolssonicdeath   o
|necessarily represent those of my employer.- itstheendoftheworld       r
*-------------------------------------------*---------------------------d