> You should never let the free space on an OS10 system disk go below > 10 gigs or you are asking for trouble in the worst way. That's strange, I'm running Tiger on my iBook with only 10 gigs of harddisk space in total, just about 400MB free, no problems at all. > OS10 uses > the system disk as a kind of Virtual memory and unfortunately there > is just no way to take control of this and turn it off even if you > have tons of RAM and no need of that kind of virtual memory. If you have tons of RAM and no need for extra memory, no swap space (which is what you are referring to as "virtual memory") will be used. The fact that you think it does, may have to do with this wrong terminology; people look at their process monitor or similar apps and think that the amount of "virtual memory" is the amount of harddisk space used for swapping. It isn't. Virtual memory is a virtual (ie not really existing) humongous addressing space that the applications see, blissfully unaware of tricks like shared code space, protection, memory defragmentation and, once your physical memory is full despite these tricks, swapping. > (This > is actually one of the things I really hate about OS10, OS9 was much > superior in this particular regard IMO). OSX memory management is way superiour (in the aspects mentioned above). The "off"-switch of OS9 doesn't really compensate for that. All that would add to this is applications dieing horribly with failed memory allocations when your physical memory is full, despite the fact that swapping would have saved you. Maurits.