How to uninstall software installed with an installer?
If the title isn't confusing enough for you, I'll explain a little more.
I would like to know how to uninstall a piece of software that was installed in OS X with an "Installer"? Most of the software installs just consist of copying a folder into the Applications directory or wherever you want it and launch it from there. However, occasionally there is software that installs with an installer and I don't know how to uninstall it completely from the system.
I thought there might be an equivalent to "Windoze Add/Remove" feature in OS X, and there might be, I just don't know where it is.
Any help would be appreciated. Thanks in advance.
I would like to know how to uninstall a piece of software that was installed in OS X with an "Installer"? Most of the software installs just consist of copying a folder into the Applications directory or wherever you want it and launch it from there. However, occasionally there is software that installs with an installer and I don't know how to uninstall it completely from the system.
I thought there might be an equivalent to "Windoze Add/Remove" feature in OS X, and there might be, I just don't know where it is.
Any help would be appreciated. Thanks in advance.

Comments
(EDIT: On second thought, with OS X the System wont let you delete system components, so blast away at what you find. Most of the components are hidden anyway and wont be found with Sherlock. Just look through the list and delete things related to MSN Messenger if any. My list came up with an ungodly ammount of AOL Instant Messenger folders/files, and a few msn ones. Plus a few icons for AIM.)
[ 07-04-2002: Message edited by: Spart ]</p>
[ 07-04-2002: Message edited by: BuonRotto ]</p>
<strong>Mac installers should and usually do uninstall as well as install. The only exception I've seen to this so far is Maya, which installs an uninstaller (confused yet?) with the application. Ideally if everyone played by the rules, no installers would be needed. But <a href="http://www.microsoft.com/mac" target="_blank">certain companies </a> can't help but make things harder than they should be.
[ 07-04-2002: Message edited by: BuonRotto ]</strong><hr></blockquote>
HEHEHE, nice shot with that link there! I must admit, however, they did a good job with Office X. Drag and drop, no installer crap.
Anyway, normally when a program installs with an installer icon, it'll generate an install log. You can read through this to see if there's any loose files floating around. Apple has also recommended to developers that they keep their entire program in a bundle (folder) to make things less complicated.
To answer your question, I am relatively new to the Mac and definitely OS X. Thanks for your input.
<strong>HEHEHE, nice shot with that link there! I must admit, however, they did a good job with Office X. Drag and drop, no installer crap.</strong><hr></blockquote>
True, good for them. I was thinking of the inexplicable installer for IE 5.2 that requires you to quit all running applications (except the Finder even though it's another app) and give your admin password (I assume they're tossing stuff in the System folder, yes?).
I could easily think of some other <a href="http://www.adobe.com/" target="_blank">stagnant farts</a> who are just as guilty of making life more difficult and clinging to the bad old days of application installs. Every time I have to deal with a Microsoft, Adobe, Macromedia, etc. the more I gravitate towards <a href="http://www.stone.com" target="_blank">up-and-comers</a> and <a href="http://www.caffeinesoft.com" target="_blank">alternatives</a>.
[ 07-06-2002: Message edited by: BuonRotto ]</p>
I didn't write the program but I certainly wouldn't use Mac OS X without it.
<strong> <a href="http://www.microsoft.com/mac" target="_blank">certain companies </a> can't help but make things harder than they should be.</strong><hr></blockquote>
I develop installs for Windows 'OS'--you can not know my pain
What's even more amazing: I mentioned Mozilla's "just-drag-it-to-the-drive" installation and was told " we don't want that: the user MUST be presented with a unified look-and-feel and MUST go by our requirements rules. It's ironic: PC users always talk about the "customisability" of the platform, but all things Windows are about preventing the off-step/customised use . . . .