Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Weird 2000 vs 3000 problem
Message-ID: <21948@cbmvax.commodore.com>
Date: 28 May 91 04:41:30 GMT
References: <1991May27.060647.3462@nntp-server.caltech.edu>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 20

In article <1991May27.060647.3462@nntp-server.caltech.edu> tll@nntp-server.caltech.edu (Tal Lewis Lancaster) writes:
>I a program that runs fine on a 2000.  But when I try it on a 3000 it
>crashes.  

>The 3000 is running under 2.0 (Kickstart 37.130, Workbench 37.46).  
>Enforcer makes a bunch of complaints and the the machine locks up.  The
>best guess as to the location where Enforcer complains is during a 
>particular UNLINK statement.

	A common cause of something like this is running 1 byte past the end
of a string.  This puts a null byte in the high byte of the next longword.
Of course, if all your memory is below 0x00ffffff and the next longword is
a ptr, this has no effect.  On an A3000, there's memory above that, so the
address can be trashed.  This is what was wrong with Less on the fish-disks.

-- 
Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
"No matter where you go, there you are."  - Buckaroo Banzai