[finalizedsven]

Just as the title suggests, I have questions about startup.
I'd like to know how to script things to boot or not boot up with the system, but my real problem is that I have a program that always opens that I tried to uninstall but can not.
the thread is called TheaterCS and it's a part of an M-Audio driver suite for an external sound card of theirs designed for PowerPC macs.
I uninstalled it (or so I thought) but the stupid thing keeps showing up in my active thread list and what's worse is that it opens up Rosetta because I'm on an Intel Mac.

I've searched high and low for the location of TheaterCS so I may delete it, but I can't even find it anywhere, even with the aid of Finder-mods that let me see all the hidden files, I came up with nothing.

so how do I stop what seems to be....not there.....from not booting?

[calverson]

Go to System Preferences > Accounts > Login Items.

[finalizedsven]

Originally Posted by calverson 

Go to System Preferences > Accounts > Login Items.

Good sir, I wish it were that easy. My application isn't in that list because I'm not sure exactly what it is i'm trying to stop from starting up with my system. It might be a script. I honestly have no idea. Whatever it is, it starts up with my system in a very sneaky manner, so what I'm asking for I guess is a list of all of the scripts and lists and places that OS X looks for to figure out what it boots with. Thanks though.

[calverson]

Hmm... A work around could be to create a script that kills that process and then run that as a start-up script. This would not solve your problem, but is a temp work around.

What is the parent process? You find this by selecting it in the activity monitor and then clicking on it, and then inspect process, and that will open up a window and tell you.

[calverson]

Also, worth looking at is startup in verbose mode (press command-v when you see the apple logo on boot) and looking to see what OS X is doing anything or executing a script.

Also, does it start up in Single user mode? (command-s on boot)

[larkost]

The likely places to look:

/Library/StartupItems (most likely)
/Library/LaunchAgents
/Library/LaunchDeamons
/Library/InputManagers (very unlikely in this case)

the version of these folders in ~/Library
the version of these folders in /System/Library (don't fiddle here)

/etc/mach_init.d
/etc/mach_init_per_login_session.d
/etc/mach_init_per_user.d

/etc/rc.* (probably not, but these are interesting)

/System/Library/Extensions/ (another place to not touch)

[finalizedsven]

Perfect!

I think that nailed it, I'll boot into OS X momentarily to test things out, it was the "startupItems" the held a bunch of old M-Audio stuff the uninstaller didn't catch

Thanks a million.