Path: utzoo!mnetor!uunet!husc6!linus!alliant!rosenkra From: rosenkra@Alliant.COM (Bill Rosenkranz) Newsgroups: comp.sys.atari.st Subject: Re: mshrink & lattice C Message-ID: <1670@alliant.Alliant.COM> Date: 28 Apr 88 23:04:08 GMT References: <19880427223042.6.JRD@MOA.SCRC.Symbolics.COM> Reply-To: rosenkra@alliant.UUCP (Bill Rosenkranz) Organization: Alliant Computer Systems, Littleton, MA Lines: 25 --- In article <19880427223042.6.JRD@MOA.SCRC.Symbolics.COM> jrd@STONY-BROOK.SCRC.SYMBOLICS.COM (John R. Dunning) writes: -> -> Date: 21 Apr 88 23:18:14 GMT -> -> Bill writes:(Bill Rosenkranz) ->[...] -> On startup of a GEM program all available memory is allocated (and zeroed). -> ^^^^^^^^^^^^ ->[...] -> ->Is THAT why every time I add more memory to my 520 I have to wait longer ->after loading an image before it starts running???? Does anyone know of ->a way to disable this 'feechur'? first of all, i meant to have a "?" after "(and zeroed" because i just wasn't *quite* sure. when your program starts, all .data stuff is initialized to zero, though. i think some programs use this fact, eventhough it is not portable (but then again, why make any GEM program portable :^). short of patching Mshrink, i don't know how to disable this, as you put it, 'feechur'. actually, i like the fact that i'll always get space filled with zeros. -bill