Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!decwrl!cookie.dec.com!wecker
From: wecker@cookie.dec.com (DAVE  TANSTAAFL  WECKER)
Newsgroups: comp.sys.amiga
Subject: Strangeness when copying to RAM:
Message-ID: <6803@decwrl.DEC.COM>
Date: Sun, 7-Dec-86 22:51:25 EST
Article-I.D.: decwrl.6803
Posted: Sun Dec  7 22:51:25 1986
Date-Received: Mon, 8-Dec-86 02:13:29 EST
Sender: daemon@decwrl.DEC.COM
Organization: Digital Equipment Corporation
Lines: 29


I'm confused (so what else is new :-). When using Matt's shell to copy a file
to the RAM: device, the following happens:

	238k free	- at start of copy
	153k free	- near end of copy (file is 85k)
	 68k free	- at VERY end of copy (looks like during close)
	153k free	- after copy completes

It looks like before finishing the copy, AmigaDOS eats up TWICE the size of
the file (this is using the AZTEC-C runtime routines on V1.1 of the O/S).
So just for grins, I did the standard copy command in c: and got:

	238k free	- at start of copy
	150k free	- near end of copy (file is 85k)
	135k free	- at VERY end of copy (looks like during close)
	150k free	- after copy completes

Not as bad... but still 15k disappears (for an instant). What is going on?
Is this a known bug? Do I have any control over it? Is it fixed in 1.2?

The problem arises when I want to run EMACS, VT100 and a MAKE at
the same time. When I get to the point where I want to copy c.lib up to
ram: (and there should be enough room) I run out of space (since I need 170k
of ram (for an instant) to hold the c library instead of 85k).

Any input would be appreciated.
Thanks,
dave	{decwrl|decvax|decuac}!cookie.dec.com!wecker