Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!rex!ukma!phoenix
From: phoenix@ms.uky.edu (R'ykandar Korra'ti)
Newsgroups: comp.sys.amiga.introduction
Subject: Re: MONTHLY POSTING: Frequently Asked Questions and Answers V1.2 (April 1991)
Message-ID: <1991Mar31.153534.4535@ms.uky.edu>
Date: 31 Mar 91 15:35:34 GMT
References: <8990@chorus.fr> <1682@tardis.Tymnet.COM>
Organization: El'n'tk National Spaceport, Mission Control
Lines: 22

In article <1682@tardis.Tymnet.COM> jms@tardis.Tymnet.COM (Joe Smith) writes:
>NoFastMem = A program that optimizes things on an Amiga with a combination
>of Chip RAM, AutoConfig RAM, and Slow-Fast RAM.  It rearranges a system list
>such that when a program tries to allocate memory (and does not specify that
>it needs Chip RAM or Fast RAM), the memory will be allocated from Expansion
>RAM in preference to Slow-Fast RAM.  It keeps things running faster longer.
     Ah, right definition, wrong programme. This definition is for
FastMemFirst. NoFastMem is a programme which removes Slow-Fast RAM
and Fast RAM from the system availability list, so that _all_ ram
allocations must come from Chip RAM. This is provided so that certain
old, "broken" programmes that do not properly allocate their Chip RAM
(i.e., which call for _any_ ram when they specifically need Chip RAM)
can continue to function on a machine with Fast RAM.
     Personally, I don't run programmes that do this. :-)
     I can tell this was a typo, but I thought I'd post anyway to get
the correction out ASAP. Very nice list otherwise, by the way...
                                                    - R'ykandar.

-- 
          R'ykandar Korra'ti | Editor, LOW ORBIT Science and Fiction
             "I hate you, you timepiece from Hades." - Plucky Duck
         phoenix@ms.uky.edu | editor@lorbit.UUCP | ukma!lorbit!editor