Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!psuvax1!vu-vlsi!cbmvax!andy
From: andy@cbmvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Memory Fragmentation Question
Message-ID: <2279@cbmvax.UUCP>
Date: Mon, 31-Aug-87 18:32:41 EDT
Article-I.D.: cbmvax.2279
Posted: Mon Aug 31 18:32:41 1987
Date-Received: Wed, 2-Sep-87 01:41:47 EDT
References: <556489503.138.te07.linesville.ibm032@andrew.cmu.edu> <2074@umn-cs.UUCP> <567@sugar.UUCP>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 33

In article <567@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>There is a problem: screen and window memory needs to be contiguous... and
>then of course there's that RAM: 30K ripcord. but program loading shouldn't
>be a problem.

The ripcord was removed for the release Workbench disk.  (33.47)
It does make sure it has enough for emergencies before starting.
That, combined with the large buffers that copy uses
(because no one wanted to special case ram:) sometimes causes
problems.

>> As long as we're giving wish lists -- does there exist an equivalent to 
>> UNIX's "kill" for the Amiga?  A light skimming of the RKM's doesn't yeild
>> an easy solution to this problem aching to be answered.
>
>Nope. No resource tracking. Ack, oop.

There are a couple of libraries floating around that give resource
tracking by giving replacing the AllocMem, FreeMem, etc. system
routines.  They all have impacts on performance.

>-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter


-- 
andy finkel		{ihnp4|seismo|allegra}!cbmvax!andy 
Commodore-Amiga, Inc.

"Interfere?  Of course we'll interfere.  Always do what you're best at,
 I always say."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.