This program does not handle memory elegantly; if you exceed available memory or exceed an array bound, the code crashes. Because there is no file in memory, no data should be lost when this happens. (Maybe in the future this will become a little less fatal). If you run out of memory (error 7) and you are using MultiFinder or System 7.x, then increase the size partition by opening the Info window of PaleoMag and increasing the size in the box in the lower right part of the window. If you exceed an array limit (error 9) then consider your dataset and increase the appropriate values as described above. In some cases a copy of PaleoMag might have been set with values too large for it to be started on some Macs (this is why I usually distribute it with low values); if this has happened, you will either have to start PaleoMag on a machine with enough memory, or you can directly edit the array limits using ResEdit. The array limits are stored as numbers in string ("STR ") resources with ids of 200 (maximum number of samples/locality), 201 (maximum number of demags in any sample), 202 (maximum number of least squares directions/locality), and 203 (maximum number of demag steps/locality).
Presently many of the arrays in the code are dimensioned dynamically; this means that you might be able to run the code with a large number of samples without exceeding memory as long as you keep the number of windows open at once to a minimum. The most memory intensive windows are the two "Locality" windows ("Locality Equal Area..." and "Locality Strat Plot...") closely followed by the two "Least Squares" windows. Again, if the program crashes under MultiFinder/System 7.x and you need the multiple windows, increase the size partition in the GetInfo window for PaleoMag.
Table of Contents
1379 visits from Tue, Apr 21 1998 17:07 to Apr/ 6/02 22:40
346 visits from Tue, Apr 21 1998 17:07 to May/26/00 18:53