PT M-Powered won't recognize FW 1814 - Device cannot start?

[adamfrandsen]

1. When I hook up my firewire 1814, I get two or three (cannot remember) unknown devices/controllers in my Device Manager.

2. After installing the driver manually, I see two M-Audio 1814 under Sound Devices but with a yellow question mark at one of them saying the device cannot start. The other one seems to be fine. At the same time there is still an unknown controller/device on my computer - which only appears, when I have the M-Audio Firewire 1814 plugged in.

3. The Tray icon is there and the mixer settings start up fine, but when I boost up Pro Tools 7 M-Powered, it cannot find the device...

How do I solve this or undo what I have done wrong?

(Driver installed is a 64bit Beta for Windows XP, only one other people got their M-Audio Firewire cards to work...)

 

[NosferatuX]

Try running windows update and see if it install the correct drivers for your system.

A bit of a good news for you, I just recently heard that the M-Adio 1814 drivers are out for Vista so you can check it out here which you can use on your Windows 7 installation

You can also use the Windows 7 Driver solution for this to work properly.

Let us know how it turns out

 

[adamfrandsen]

Thank you, but the 64bit Vista installer does not work in W7, it gives you an error, and then you have to browse to the temp folder and retrieve the ini-file, and the install manually/update driver... The XP 64bit driver turned out to do the job when installed manually as well, but the problem is with Pro Tools and not with the firewire driver, I think. I can use my 1814 in SoundBooth CS4, but when Pro Tools starts up, it prompts you that it cannot find the hardware, and then closes... Pro Tools supposedly does not support 64 bit systems, but I read on other forums that some people have made it run without problems on 64bit W7, and since it installed alright and loads fine until it starts looking for the hardware, I am looking to find a way to work around this problem... Any and all ideas are appreciated! Thanks,
/A

 

[adamfrandsen]

I also found out about the other devices, turned out that I in fact did not have all my drivers installed ok, but all is fixed now...

 

[NosferatuX]

Glad you got it all sorted out