The RexxAPIManager has a check to see if it is possible to create kernel objects in the Global namespace (Global) If it is possible, the objects used for communication between RexxAPIManager and RexxAPIService are created in that namespace, if not the objects are created in the user's namespace.
On Vista, the current check is not sufficient for a standard user. The check passes, when in fact the standard user does not have the ability to create file mapping objects in the Global namespace.
If RxAPI is installed as a service, this presents no problem. If RxAPI is not installed as a service and the user chooses to always run ooRexx with elevated permissions, it also is not a problem.
However, it is a problem if the user chooses to not install RxAPI as a service and does not want to run ooRexx with elevated permissions. In this situation, the API manager will not start.
On Vista, we should stress that the best thing to do is to install RxAPI as a service. However, this should be fixed for users who choose not to install RxAPI as a service.