Q: Why don't the services from my MAB [Multiple Architecture Binary] applications show up on my Release 3.0 machine?
A: When the service description file is located in an app wrapper of a MAB application and placed in ~/Apps, the services do not get properly registered on a Release 3.0 machine. However, the services are correctly registered on a post-Release 3.0 machine. This is a MAB bug in Release 3.0.
The workaround is to place a file or directory with a ".service" extension in either ~/Library/Services or /LocalLibrary/Services. A file with a ".service" extension must be a valid service description file. A ".service" directory must contain a valid service description file named "services" (e.g., the service description file would be named something like ~/Library/Services/myOwn.service or /LocalLibrary/Services/ALocalOne.service/services). Note that the extension ".service" does not end in an "s", but the file named services does. Also, the Workspace Manager only registers the services in these directories when the user logs in, it doesn't automatically update the service cache during a working session.
For more information on installing services, refer to ../AppKit/installing_new_services.