Topic       : Documentation for Thing
Author      : Arno Welzel/Thomas Binder/TransAction
Version     : thing.hyp 1.27E (23/8/1998)
Subject     : Documentation/Shells
Nodes       : 269
Index Size  : 6336
HCP-Version : 4
Compiled on : Atari
@charset    : atarist
@lang       : 
@default    : %I
@help       : %Hilfe
@options    : +g -i -s +y +zz -t4 -d10
@width      : 75
@hostname   : THING   
View Ref-FileFAQ - Can I set MagiC memory limits for programs?                     Thing

Q: Can I set MagiC memory limits for programs? MagiC includes a utility 
   (LIMITMEM.TTP) which can set the maximum available memory for a program. 
   Can I use this with Thing as well?

A: Yes. The 'Show info...' option in the 'File' menu includes a 'Program' 
   page which includes a 'MagiC! memory limit:' field where the amount of 
   memory can be entered in Kb. To remove a memory limit either clear the 
   field or enter 0.


Q: Why do executable files grow in size by 8 bytes after setting a memory 
   limit and reduce again after removing a limit?

A: Contrary to popular belief the memory handling flags are not stored 
   in reserved sectors in the program headers but appended to the END 
   of a program file.

   The 8 bytes begin with the text 'MAGX' followed by a 32 bit integer 
   containing the desired upper limit in bytes. In order to delete a 
   memory limit simply remove the extra bytes -- or add them for setting 
   a memory limit when none was present before. If you don't know exactly 
   what you're doing, use the Thing 'Show info...' dialog or other utility 
   because it's very easy to destroy the integrity of executable files!


      From Thing 1.25 onwards one can also enter a memory limit in the 
      options for installed applications. This works with MultiTOS, N.AES, 
      MagiC from version 4 on and most likely also with Geneva; this has 
      the advantage, among others, that the program file need not be 
      altered.