Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer Uninstall-Reinstall MCA 2.0.2

  • Uninstall-Reinstall MCA 2.0.2

    Posted by Mark Crenshaw on September 5, 2008 at 4:13 pm

    MCA 2.0.2, XP Pro SP3, 3 gig Ram, NVIDIA 980XGL,

    I’m having fits with getting MCA 2.0.2 to install properly.

    After a major system crash, I started with a clean install of XP SP3, added QT, WinMedia, NVIDIA drivers, then added MCA using the system FW port. All went well. After using the system for a few days, I decided stability was OK so I installed the Pyro64 card to move the DNA to it. Since then, I cannot get the Avid to recognize the DNA. I moved it back to the system FW port, removed the Pyro64 and nothing.

    I have uninstalled several times, but the process seems to be missing something. I found and followed a clean install checklist but something is still amiss.

    I uninstalled all Avid apps using Add/Remove Programs, removed the Avid folder from C:\Program Files. Checked to make sure the Avid folder was gone in C:\Program Files\Common Files. Removed flamethrower.sys from C:\Windows\System32\Drivers. Deleted the Avid folder from the registry.

    Now when I reinstall, the DNA does not chime when connected and XP does not recognize it as New Hardware. I can see the splash screen on the client monitor but when I launch MCA it gets to “Initialzing Audio” and displays a dialog saying there is a problem with the DNA. I checked to see if the flamethrower.sys driver had reinstalled to C:\Windows\System32\Drivers but it’s not there. I copied it over from a backup folder. The DNA chimes now when connected but MCA does the same thing on startup.

    Is there a way to manually install the DNA driver without the New Hardware wizard auto launching? I have tried looking in all the usual places…Device Manager, Add Hardware… but the DNA is not listed anywhere to manually update the driver and Add Hardware does not detect it when it scans.

    I’m stumped.

    Any help much appreciated.

    Mark

    Mark Crenshaw replied 17 years, 8 months ago 2 Members · 4 Replies
  • 4 Replies
  • Jon Zanone

    September 6, 2008 at 12:52 pm

    According to the Avid web site, MCA 3.0 is qualified under XP SP 2, not SP3 (clicky).

    You might try rolling back to XP service pack 2.

    Jon

    “Jamming our heads full of figures and angles
    And telling us stuff that we already know”

    Willie The Wandering Gypsy & Me
    Billy Joe Shaver

  • Mark Crenshaw

    September 6, 2008 at 1:45 pm

    Thanks Jon. I tried this yesterday with no change. I am stumped as to why this is happening. I have never seen anything like it. I guess I may be starting over again with a complete reinstall of everything. If that doesn’t fix it, I guess my DNA took a dive :(((

    I know some electronics have a “hardware reset” feature like holding down the power button for 10 secs or pressing another button during startup…anything like this on the Adrenaline?

    Thanks again,
    Mark

  • Jon Zanone

    September 7, 2008 at 9:49 pm

    I don’t know much about adrenalin – a shop next door has one, but I’ve never gotten into the nuts and bolts of one. Turning off the power should help.

    Also make sure you have the correct version of Quicktime.

    Jon

    “Jamming our heads full of figures and angles
    And telling us stuff that we already know”

    Willie The Wandering Gypsy & Me
    Billy Joe Shaver

  • Mark Crenshaw

    September 9, 2008 at 11:49 am

    Thanks to all who responded. It seems I have a problem with the DNA. I have tried reinstalling several times and even used another CPU and got the same result. I did find out the light surounding the power button on the DNA is amber in color…this means it is not communicating with the computer. When normal, it should be green. This color was present when connected to both machines. I reseated the lower chassis in the DNA…the one that houses the FW socket. The FW busses on both computers are known good and I tried several cables with each machine. It has been rock-solid for almost 5 years, I guess that’s not bad. The DNA doesn’t show the light combinations of a failed audio or video board so maybe it just needs a tweak of the FW interface.

    Peace,
    Mark

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy