Was: getting a file list in sorted order/IS: Finder tricks
Was: getting a file list in sorted order/IS: Finder tricks
- Subject: Was: getting a file list in sorted order/IS: Finder tricks
- From: email@hidden
- Date: Tue, 20 Aug 2002 03:59:23 EDT
While it is true that any recursive call can initiate an
overflow, I devised a trick years ago that made all macs
run smoother, better, less likely to crash... It only
applies to pre-OS X versions of the operating system,
though.
Trick: Up the memory allocation for the "Finder"
Theory: The "Finder" is an app, like any other, but has
certain high-level tasks assigned to it and thus should not
be treated as any other app. And like all apps, sometimes
giving the program more ram will increase it's stability
and should never cause any problems (unless you are
especially tight on memory).
Method: Duplicate the "Finder", edit it's type and creator
codes to be a regular app, up the memory allocations (from
962 Kb to 2450 Kb or thereabouts), reassign the correct
type and creator codes. Final step: move the original to
safe place and then place the modified finder into the
system folder and immediately restart. Oh, it's not a cure
for all the ills that application programmers can think of
(usually by accident through bad programming), but it
certainly improves the system's stability in most cases by
padding the finder with additional ram space.
Best Wishes,
=-= Marc Glasgow
Has wrote:
>
The "fold up and die" thing is a characteristic of _any_
>
recursive routine that calls itself too many times: the
>
call stack has a finite capacity, and if your program
>
builds up too many unfinished calls then sooner or later
>
runs out of room (overflows). Nature of the beast.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.