Path: utzoo!mnetor!uunet!husc6!m2c!ulowell!page
From: page@swan.ulowell.edu (Bob Page)
Newsgroups: comp.sys.amiga
Subject: Re: Massive Fragmentation with PopCLI & SetFont
Message-ID: <5395@swan.ulowell.edu>
Date: 11 Mar 88 17:43:00 GMT
References: <2118@polya.STANFORD.EDU>
Reply-To: page@swan.ulowell.edu (Bob Page)
Organization: University of Lowell, Computer Science Dept.
Lines: 32

ali@polya.UUCP (Ali Ozer) wrote:
>popcli
>setfont pearl 9 -s -r
>my chip memory is massively fragmented. We're talking:

Interesting ... I've seen the same problem, but had not tracked it down.
I also use setfont (pearl2, w/o options) but not popcli, and my
fragmentation was appearing BEFORE setfont.

Turns out (as near as I can determine) that is was caused by gamma 1
of the FastFileSystem.  Once I went to a later version it went away.

My startup-sequence was something like:

Mount wb:	(wb: is a 2MB partition running ffs)
wb:s/DefDisk	(reassign logicals)
execute s:Startup-Sequence

And wb:s/startup-sequence was:

mount dh0:
[etc]

I couldn't mount dh0: because memory was too fragmented.  The largest
fragment I had was about 440 bytes (out of 1MB fast mem).

Maybe you can run SNOOP and find out who's allocating memory.

..Bob
-- 
Bob Page, U of Lowell CS Dept.  page@swan.ulowell.edu  ulowell!page
"I don't know such stuff.  I just do eyes."  -- from 'Blade Runner'