So I bought a Mac a month ago...

Yes, the Startup starts on Login. But the PC doesn’t have the security restrictions that Macs do so it’s not an issue, at least not for my problem. I can run it on login on Windows and it works fine; unfortunately I can’t run it on login for the Mac. Now you may proceed to tell me how much more secure the Mac is and how this is for my own good and if Windows restricted all this stuff we wouldn’t need anti-virus programs. Bleah bleah bleah. I’ll still use my PC more than the Mac.

And no, not all apps are services, but in general, anything designed to run on startup tends to be written as a service (it’s very easy to code something as a service versus a standard app, I do it all the time.)

No, there’s a one line thing (something like RegService32.exe, I can’t remember it exactly) that will register a service and do all the registry stuff. It’s pretty easy.

But dude, this was just one little criticism I had for the Mac - I’m not gonna spend all day defending it. All I’m sayin’ is my little keyboard/mouse sharing thing took about 5 minutes to set up on two PCs, including configuring one to be the server, and I dinked around trying to get it set up on the Mac for about 45 minutes before I just decided to click the damn icon when I wanted to use it.

Oh yeah, I agree with this completely. From my research, I couldn’t find a way to really truly start something on startup on the Mac without writing a shell script; I’d really like to be proven wrong on this, so if anyone knows a better way I’m all ears.

Did putting it in /Library/StartupItems not work for you?

Heh. Re-read the thread, previous posts go into details about why this doesn’t work for this particular app.

Not your StartupItems. root’s StartupItems. Anything placed in /Library/StartupItems gets run on boot. That’s boot not login.

Sure - once you know how to do it. A Unix guy will tell you “it’s not hard to have something startup automatically on Unix - you just add one line here or put a one-line script there.” I remember having to setup startup items on HP-UX and messing with init files - it was easy once I know how to do it.

You may not need it, but any application that can hijack an application used by that script (thus gaining admin privileges via daisy chain) may make you wish you had security. Trust me, this is something Unix people learned long ago before they took security seriously.

No, I’m saying it is easier to get under the hood and tinker with OS X to make it do exactly what you want, rather than kludging together things in Windows to make it sort-of work.

Definitely true, and there are several reasons a user might prefer or need a Windows OS. But generally speaking, OS X is better documented and easier to interface with on nearly every functional level, excepting the need for support of proprietary applications.

Stranger