CC Applications PS, etc no launch in new install of ML on Imac Platform Cfg error: 213:5

Standard Adobe answer for this kind of issue is "Contact Our Product Support".

. after performing all the recommendations on the Adobe Community and Product support information resources. I went to the live support and spent 3 hours on line with Product Support "techs" Finally after last 2 hour session with Indian gentleman who could barely speak intelligible English...after he went through same routines that I had performed. (After took control of my desktop), he Changed config files by entitling them with bogus titles, asking me to trash the files, then re-title his newly authored files to the title he had trashed....(old trick) then tells me to empty trash... He did this a couple of times and I lost track of the data changes made.  Then he reported that he could not fix the issue and he would cause the case to be elevated  to a more experienced support person...AND THAT ADOBE WOULD GET BACK TO ME WITHIN 24-48 HOURS. He exited his control of my system from the desktop and left the scene. A case WAS OPENED AND I RECEIVED NO NOTICE OF ANY KIND FROM ADOBE. 

This morning about 44 hours after he elevated the case...I checked on it by logging on and found a case file SURPRISE SUPRISE..no new information.  I elaborated a little more on the urgency of finding a solution to the problem and mentioned that the 48-hour clock was about to run out on the issue...I NOTE now that a new case number was assigned for SAME EXACT ISSUE AND it was re-assigned a new case number!  THE OLD CASE (unsolved and apparently unattended) WAS DISMISSED!

Does this mean that I have another 48 hour waiting period?  This configuration error has existed on all CC apps that I have tried except Lightroom.  Since upgrading to Apple's Mountain Lion OS for IMAC, I have not been able to run my onboard application CS5.1 PS.  The application installation disc is ejected within 3 or 4 minutes after insertion in the DVD drive.  So I am unable to operate my PS which I have used and contiguously updated since 1991. 

Please suggest other alternatives..or if similar experience an approach strategy to solving this issue.