Path: utzoo!attcan!uunet!wuarchive!sdd.hp.com!ucsd!ucbvax!pasteur!cory.Berkeley.EDU!navas
From: navas@cory.Berkeley.EDU (David C. Navas)
Newsgroups: comp.sys.amiga
Subject: Re: Benchmark:A3000 w/ AMAXII
Message-ID: <28755@pasteur.Berkeley.EDU>
Date: 14 Oct 90 00:07:56 GMT
References: ...5070@cbmvax.commodore.com> <15090@cbmvax.commodore.com>
Sender: news@pasteur.Berkeley.EDU
Reply-To: navas@cory.Berkeley.EDU
Lines: 28


In article jesup@cbmvax.commodore.com (Randell Jesup) writes:
>In article martin@cbmvax.commodore.com (Martin Hunt) writes:
>>>>In article tombs@ee.rochester.edu writes:
>>>>>	A3000/25/50		MacIIci		MacIIcx			MAC+
>>>>>Dhrys/sec 2871(2717)			3736(3816)	(768.8)
>>> 
>>Fast RAM is used BEFORE Chip RAM, so the problem is most likely that
>>something is using up all the Fast RAM.  In the case of a stock 2M
>	Also, Amax may not be able to use memory above the 16M boundary,
>..for amax under the current MMU rom-images.  With real roms there will be
>another 512K of fast ram available (at least under 2.0).

Well, 512K if you don't run your startup-sequence :)
First off, Martin is certainly correct in saying that the Amiga OS allocates
FAST then CHIP (assuming you ask AllocMem to alloc some general purpose mem),
but the Mac works somewhat differently.  Not willing to stick foot into mouth,
I'll just say that I always thought the Mac assumed contiguous memory, which
makes it seem likely to me that they allocate memory from low t'high addresses.

I would hope that AMax fixed the 16M boundry, at least by doing some MMU
magic....

I've got AMax, and haven't used it except to impress some Mac weenie at school.
[Lord knows there are enough of 'em.]

David Navas                                   navas@sim.berkeley.edu
"Excuse my ignorance, but I've been run over by my train of thought."  -me