Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!sun-barr!rutgers!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga.hardware Subject: Re: Adding 16-bit memory to a 2500 Message-ID: <20764@cbmvax.commodore.com> Date: 19 Apr 91 11:38:40 GMT References: Reply-To: daveh@cbmvax.commodore.com (Dave Haynie) Organization: Commodore, West Chester, PA Lines: 23 In article kenny@mazurka.UUCP (Kenneth Fletcher Yarnall, Ab.D.) writes: >I asked this before, but I have my suspicions as to whether it got out... >I am thinking of adding memory to the 2091 in my 2500/30. I recall Dave >commenting a long time ago that it was possible to regulate the order in >which memory was used by the system, and thus ensure that this 16 bit memory >would be used only after all the 32 bit stuff had been soaked up. It's done automatically. The memory lists are ordered by expansion.library in the same order the configuration is done. The A26x0 magically makes the 32 bit memory the first configuration unit, regardless of what else might be in the system. So 32 bit memory always shows up first. Poof! Excepting, of course, that silly $00C0xxxx memory. You can always run FastMemFirst to reorder that list, or better yet, convert over to 1MB of Chip RAM and eliminate the problem alltogether. > Ken Yarnall /// kenny%mazurka@opusc.csd.scarolina.EDU -- Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy "That's me in the corner, that's me in the spotlight" -R.E.M.