The selected ASIO audio device could not be initialized...

[sneakyimp]

I recently had my digi002 firewire card melt on me so I just had it repaired (and it works at the repair shop) but now I'm having a problem with protools. Protools is apparently looking for an audio device i used to have installed which did not work properly with PT9 (a usb 1800). For some reason, when protools couldn't find my melted digi002, it reverted to the usb 1800 (which is long gone). When I try to start PT9, I get the dialog that says The selected ASIO device could not be initialized. Please choose another audio device.. If I click OK then it shows me a dialog for the long-gone USB 1800 and there is no way for me to select my happy, newly fixed digi002 which is waiting patiently on standby.

My goals here:
Get PT to talk to my digi 002
Get PT to FORGET THE USB 1800 ever existed.

Any help would be much appreciated.

[filosofem]

Hold Shift N when launching Pro Tools.

[sneakyimp]

This did nothing. Note that I'm on Windows 7.

[filosofem]

Try grabbing a new driver here and follow the instructions below.

Control Panel>Device Manager>double-click on IEEE 1394 Bus host controllers>Double-click on the controller (or port) that your FireWire interface is connected to.
Click on the Driver tab.
Click on Update Driver.
Choose 'Browse my computer for driver software'.
Choose 'Let me pick from a list of device drivers on my computer'.
Choose '1394 OHCI Compliant Host Controller (Legacy)'.
OK.
Restart the computer.

[sneakyimp]

Thanks for your help. I'm currently in the process of uninstalling/re-installing everything. Where in that process might these steps lie?

[sneakyimp]

Also, is there any way to validate that the digi002 hardware is functioning before installing protools? Between the iLok, the hardware, and Protools, there are a lot of installs/reboots involved. The digi002 does not appear in the device manager so I don't know if it's functioning properly. It also doesn't appear as an option under the system sounds control panel.

My digi002 in bootup says:
Validating...
Loading...
Digi 002 / Standby

I'm concerned that the device might still be broken or that my computer's firewire port may have been damaged.

[filosofem]

Last and install what you need to validate.

[sneakyimp]

I have uninstalled/reinstalled protools twice now with some difficulties:
* upon reboot, protools tries to run something and then complains about out-of-date iLok drivers
* I must install PT 9.0.2 before I can update to 9.0.6. 9.0.2 won't even launch -- just dies.
* Once everything installed, PT9.0.6 still does not recognize hardware and says "hardware not found" which is different than my original message.

From what I can tell, my system is not able to communicate with the digi002 and this is what I'm trying to verify at the moment so I can decide whether or not to make the trek back to the repair shop (an authorized repair shop, btw) and have them take another look at it. Either that or try a different installation tactic.

In order to do that, I'd like to get an idea of whether I'm screwing up the protools install (or the iLok install) or whether the hardware is indeed incommunicado. Would a digi002 expose itself to Windows for use with the system sounds? If so, it's not even doing that.

[sneakyimp]

Alrighty I think my computer's FireWire card was damaged in the meltdown. I have connected my Digi002 to another Win 7 machine and that machine detects it immediately once it is powered on. Furthermore, once I installed the Digi002 drivers, the Digi002 became visible in the System Sounds control panel.

[filosofem]

Qualified SIIG FireWire adapters PCI and PCIe.