Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!ncar!csn!boulder!happy.colorado.edu!kskelm
From: kskelm@happy.colorado.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 2.0 Compatibility Problem
Message-ID: <1991May18.105312.1@happy.colorado.edu>
Date: 18 May 91 16:53:12 GMT
Sender: news@colorado.edu (The Daily Planet)
Organization: University of Colorado, Boulder
Lines: 26
Nntp-Posting-Host: happy


>>>	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? 

   Well, on my publishers' machines, it apparently resets the system and
reboots immediately.

   It also exhibits strange behavior-- suddenly the software's right hand
doesn't know what the left is doing-- even though I'm *SURE* that a graphic
buffer has been properly loaded, the software suddenly doesnt think it is (I'll
have to work that one out one my own).

   ...Oh, yah... and I find that my executable generator does consistently
"break" under 2.0 (on any machine)... seems you folks have changed the DOS code
loader a bit???  Made it stricter?