Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MoxieFan

macrumors newbie
Original poster
Nov 9, 2005
12
0
I'm shutting down apps. so I can load / burn some CDs. - I start with the Finder (mistake). I'm sittin' here like a B.F.Skinner rat-in-training beaten' on these keys trying to figure out why there's no response from that little pointy arrow below The Finder. I then figure out what's going on as I back off and try something else. - Will ALL open applications show up as icons in the dock? Which others are resistant to 'quit' attempts? If there's no quit option under it's title in the Menu, I guess it's obvious . . . :mad:
 
There's a tool you can get that allows you to add some functionality to your Mac.. I can't quite recall what it's called, but I shall go look for it for you.

Edit; And.. Found it. Tinkertool. It does much, much more than just let you quit the finder, too.
 
Can I recommend leaving Finder open as you burn CDs. It really doesn't use all that many resources and using apps like those mentioned above to quit system processes is kinda asking for trouble.

The great thing about OSX is that an app (or process) doesn't generally require all that many resources if it's not being used unlike Windows which still apportions high CPU and RAM percentages to unused apps. :)
 
I've never had a problem with burns failing because I was running too many processes. I guess you could say I have enough faith in OS X's scheduler than to go ahead and quit all open apps before starting a burn.

The MacOS X kernel supports real-time thread scheduling; these threads are virtually guaranteed to get a certain amount of time on the CPU regardless of what else is going on in the system. Now, I don't know for a fact that the various included burning applications use real-time threads, but it makes sense to me given the nature of burning optical.
 
ElectricSheep said:
I've never had a problem with burns failing because I was running too many processes. I guess you could say I have enough faith in OS X's scheduler than to go ahead and quit all open apps before starting a burn.

The MacOS X kernel supports real-time thread scheduling; these threads are virtually guaranteed to get a certain amount of time on the CPU regardless of what else is going on in the system. Now, I don't know for a fact that the various included burning applications use real-time threads, but it makes sense to me given the nature of burning optical.
Another vote for NEVER having a problem with burning CDs in OS X. I don't even bother to shut down the other programs. Most of the time I even let them burn in the background while I do something else.
 
Unless you have an alternative, you pretty much need the Finder. Without it you can't browse you HD or open files or anything. It's not really a traditional App as such.
I can't really see why you would want to quit it! :confused:
As has been said before however, there are free programs out there which allow you to quit it if you so wish.
For me, when using my Macs, I use the finder almost continuously (to open downloads, start apps etc etc.)
It's been there since OS 1, so it's pretty essential!
 
The point behind quitting the Finder isn't because you don't want it/don't need it, it's the thought that any applications you have running are using a percentage of the CPU. However, as has been said already in this thread, this is quite untrue. If you run system profiler, you can see that the only thing that uses any substantial percentage of the CPU is the app which is currently selected, meaning that the finder isn't actually taking an CPU if you are, for example, burning a CD.
 
My feelings on the matter is that the negligible amount of the system resources used by the Finder in the background does not justify the use of utilities such as TinkerTool. While I have heard generally good reviews of TinkerTool, I believe that the possible harms that come from messing with your system like that far outweighs the harms that come from leaving the Finder open in the background. Such utilities tend to be major causes for problems, as it's messing with something that wasn't meant to be messed with. Save yourself some headaches later and avoid those kinds of modifiers.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.