This posting is older than 6 months and can contain outdated information.
Hello Jenny,
thanks for your feedback!
I can't really tell, what is going on on your computer. I can only
make an educated guess:
1) The "API” for adding login items is AppleScript only - and
partially broken in Tiger. Remote Buddy knows about that and tries to
work around this where needed.
2) The login items are stored as so called aliases - which çan keep
track of moving files, mount required network volumes, etc. - but
also use interna of the HFS filesystem to refer to the files. That
usually all works fine, but there may be situations where an alias
can not be resolved - i.e. if you replaced the file it points to.
3) Since login items are not really well documented, it is likely,
that on next startup, the alias can't be resolved, the entry for
Remote Buddy is automagically removed by the system - and of course -
Remote Buddy is not being started.
Remote Buddy stores the preference setting "auto-launch on
startup" (=> be sure to activate this in its preferences, if it isn't
already), looks through the login items on each startup and adds or
removes itself as appropriate according to the state of the auto-
launch setting. That's why a manual start of Remote Buddy should
actually fix the problem.
So, next time, please try this procedure when updating:
1) Put the old version to trash.
2) Copy the new version over to /Applications.
3) Start it manually from there once.
You shouldn't start Remote Buddy from the disk image, as that may
update the login item alias to point to the image file version
instead of your copy in /Applications.
Sorry for all the tech talk ;-)
Best regards,
Felix