Path: utzoo!utgpu!watmath!clyde!ima!bbn!mit-eddie!gary
From: gary@eddie.MIT.EDU (Gary Samad)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Gurus
Message-ID: <10639@eddie.MIT.EDU>
Date: 11 Dec 88 21:44:16 GMT
References: <8748@cit-vax.Caltech.Edu> <6739@xanth.cs.odu.edu>
Reply-To: gary@eddie.MIT.EDU (Gary Samad)
Organization: MIT, EE/CS Computer Facilities, Cambridge, MA
Lines: 24

In article <6739@xanth.cs.odu.edu> manes@cs.odu.edu (Mark Manes) writes:
}In article <8748@cit-vax.Caltech.Edu> childs@cit-vax.UUCP (David W. Childs) writes:
}>Hi,
}>I have been getting loads of gurus since updating my software
}>to 1.3 and Supra 5.1b.  I am mostly getting 00000003's but I
}>occasionally get a 0000000B.  The address is usually in the
}>002##### range.
}
}Good golly this seems familiar, I spent a great deal of time trying
}to figure out what caused the guru.  Try removing FASTMEMFIRST from
}your startup-sequence.  The guru goes away then (at least it did for
}me), then after you do that, join the team that is flaming Supra for
}not going with a standard 1.3 mount and mountlist.

Your note implies that the problem is with Supra.  I have a stock 2000
with Micron/ASDG 2 megs, a 2090, and an ST506 40Meg drive and had exactly
the same problems.  Through pure trial and error I determined that
removing the FastMemFirst cured the problems.

Now, I haven't been up on the net for awhile and may have missed something.
Has anyone determined why the FastMemFirst is the problem?  even with
CBMs own hardware?

	Gary