Thanks… that was it!
The problem was that the shortcut wasn’t created during the install… and, I assumed it was a standard plug-in… located where other plug-ins would normally be. Instead, it is it’s own directory with it’s own shortcut.
Thanks for the help…As for Adobe’s support… well, the problem is that I spoke to 6 different support personal over 3 days and NOT ONE even knew that Mocha was a part of AE (in fact, a few said it was a plug-in not included and tried to sluff the problem off to Imagineer). In every contact, I had to navigate the customer support person on the Adobe site to prove it was a part of AE.
This problem should not have been a difficult question to answer. However, I am feeling the language barrior and lack of knowledge regarding the very basics regarding Adobe software is definately not good for the products reputation and a waste of Adobe’s money.
I don’t want to make this post sound like a rant… but, I would strongly suggest that someone at Adobe call and audit there own support lines and verify the quality of the people working the phone lines. The past few days indicates that the support personal (on a large scale) does not fullfill the concept of “support” even on a basic knowledge level.
Thanks – again…you have been very helpful.
Joe Moya
Side Note: As for escalating this problem… that too was a problem. It was supposedly escalated, but I never recieved any reply. Plus, I could not log into the support system… a seperate problem in and of itself… of which, that problem was also beyond there ability to help me with. I decided I would work with one problem at a time and chose to simply solve the Mocha problem first and work on the log-in issue second.