Re: [Avid-L2] Uninstall Madness

Yeah, that wasn't it.

I got this little beauty after finally removing ALL of Avid's software.  Allowing system preferences to allow ALL SOFTWARE to be installed.  Even put the installer on the desktop.

Ain't she a beauty?

I think I have one last question.  What's Adobe Premeire cost a month?

This is garbage.

Stefan Rhys

Contact: 626.679.0813

Filmmaker/Consultant

Coffee Cart Productions

E-mail: srhys@coffeecartproductions.com

Biography: www.neweraartist.net

Website: www.coffeecartproductions.com

**The information contained in this electronic mail is privileged and confidential information intended only for the use of the individual or entity named in the above address. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.**

On Feb 28, 2014, at 3:07 PM, Pierre H <ph@cineaste.org> wrote:

The "uninstaller was damaged" is apparently due to Mavericks' security. Try to go to System Preferences, Security, then unlock the lock at the bottom left, then "allow from anywhere" (don't know the exact phrasing, my Mac speaks frog. :)

Glad you could find some help here with the uninstalling. Glad we have this community!
Pierre

Re: Uninstall Madness
Fri Feb 28, 2014 12:09 pm (PST) . Posted by:"David Dodson" davidadodson@sbcglobal.net

I tried that, but it said the Uninstaller was "damaged" and that I needed to eject the entire disc image. Ugh,

On Feb 28, 2014, at 12:07 PM, Agustin Goya <agustingoya@gmail.com> wrote:

> 
> Use the unninstaller of 7.0.3, that might help.
> 
> 
> 
> Agustin Goya
> WANCAMP | POST
> +54-11-6545-2427
> http://www.wancamp.com.ar/
> http://www.linkedin.com/in/agustingoya/
> 
> 
> On Fri, Feb 28, 2014 at 5:04 PM, Greg Huson <Greg@secrethq.com> wrote:
> I had a similar problem on 2 of our systems - they had been updated over and over again, probably starting somewhere around OSx 10.5.8, and one of the machines was a (partial) clone of the other - so I took it as an opportunity to rebuild them 'from scratch' and did a clean OS install, which solved the problem.
>