Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!uunet!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.mpifr-bonn.mpg.de (Michael van Elst)
Newsgroups: comp.sys.amiga
Subject: Re: copying large files into Ram Disk
Keywords: 1 meg, A500, 686208k file
Message-ID: <1124@mpirbn.mpifr-bonn.mpg.de>
Date: 30 Jul 90 21:44:00 GMT
References: <1827@lpami.wimsey.bc.ca>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 21

In article <1827@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
>Your 1 meg A500 has memory consisting of 512K FAST and 512K CHIP ram. The RAM:
>device requires contiguous memory for a file, I believe.

No, no. RAM: uses smaller chunks (8k I think). The older ram-handler (pre1.2)
would allocate larger chunks (if it got some) and therefore eat most
contigous memory blocks.

The problem of the original writer (copy large file into ram) is caused by
COPY allocating a larger buffer. This makes much sense for disk copies
but won't allow RAM: to get all free memory. You can use the BUFFER option
of the COPY command to allocate a smaller (or larger) buffer. Unfortunately
it won't tell you if it does use your option. If the requested buffer is
too small or too large it will simply ignore your preference. The BUFFER
option isn't there in WB1.2.

-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."