Jump to content

M-Audio Firewire 1814 and Windows XP


Recommended Posts

Guest Kierano
Posted

Hi, I'm wondering if anyone out there knows of any acknowledged problems

between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814 (external

soundcard). The bottom line is the card was working beautifully for 3 months

then suddenly I'm getting disconnects - so much so that I now have a $500

piece of kit that I can't use. I can install the driver, click on the M-Audio

Control panel to adjust my settings, then I play an MP3 via WMP. It could be

OK for 5 minutes or sometimes even up to a couple of hours, then it will

disconnect. Here's what I've tried so far:

 

Disabling my onboard soundcard

Disabling the 1394 net adapter

Trying all the M-Audio drivers available

Checked that Windows Audio is started, which it has

Updated all relevant audio drivers i.e. Realtek AC '97

 

I have spent around 50 hours of effort on this, (and have received very

little assistance from M-Audio) so much so that I'm now seriously considering

investing in a Mac, just so that I can get back to making some music. I have

tested the device on a friend's Macbook and it works, so I know the problem

is with Windows. Here is my system spec:

 

Mainboard : Gigabyte GA-7VAX

Chipset : VIA KT400 (VT8377)

Processor : AMD Athlon XP @ 2000 MHz

Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

Video Card : NVIDIA GeForce FX 5500

Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

Ethernet Adapter

Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3

DirectX : Version 9.0c (July 2008)

Firewire card: ADS Pyro 1394 DV

 

 

When I look in the device manager, the firewire card appears under IEEE 1394

Bus host controllers and under Network adapters. It doesm't appear at all

under Sound, video and game controllers

 

 

Any advice gratefully appreciated. Also, if anyone knows of an external

firewire card (other than M-Audio) that actually works with Windows XP,

again, I'd like to know.

 

Thanks,

Kierano

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>Hi, I'm wondering if anyone out there knows of any acknowledged problems

>between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814 (external

>soundcard). The bottom line is the card was working beautifully for 3 months

>then suddenly I'm getting disconnects - so much so that I now have a $500

>piece of kit that I can't use. I can install the driver, click on the M-Audio

>Control panel to adjust my settings, then I play an MP3 via WMP. It could be

>OK for 5 minutes or sometimes even up to a couple of hours, then it will

>disconnect. Here's what I've tried so far:

>

>Disabling my onboard soundcard

>Disabling the 1394 net adapter

>Trying all the M-Audio drivers available

>Checked that Windows Audio is started, which it has

>Updated all relevant audio drivers i.e. Realtek AC '97

>

>I have spent around 50 hours of effort on this, (and have received very

>little assistance from M-Audio) so much so that I'm now seriously considering

>investing in a Mac, just so that I can get back to making some music. I have

>tested the device on a friend's Macbook and it works, so I know the problem

>is with Windows. Here is my system spec:

>

>Mainboard : Gigabyte GA-7VAX

>Chipset : VIA KT400 (VT8377)

>Processor : AMD Athlon XP @ 2000 MHz

>Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

>Video Card : NVIDIA GeForce FX 5500

>Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

>Ethernet Adapter

>Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3

>DirectX : Version 9.0c (July 2008)

>Firewire card: ADS Pyro 1394 DV

>

>

>When I look in the device manager, the firewire card appears under IEEE 1394

>Bus host controllers and under Network adapters. It doesm't appear at all

>under Sound, video and game controllers

>

>

>Any advice gratefully appreciated. Also, if anyone knows of an external

>firewire card (other than M-Audio) that actually works with Windows XP,

>again, I'd like to know.

 

You should try the hotfix from this KB article:

http://support.microsoft.com/kb/952825

 

- Thee Chicago Wolf

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>Hi, I'm wondering if anyone out there knows of any acknowledged problems

>between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814 (external

>soundcard). The bottom line is the card was working beautifully for 3 months

>then suddenly I'm getting disconnects - so much so that I now have a $500

>piece of kit that I can't use. I can install the driver, click on the M-Audio

>Control panel to adjust my settings, then I play an MP3 via WMP. It could be

>OK for 5 minutes or sometimes even up to a couple of hours, then it will

>disconnect. Here's what I've tried so far:

>

>Disabling my onboard soundcard

>Disabling the 1394 net adapter

>Trying all the M-Audio drivers available

>Checked that Windows Audio is started, which it has

>Updated all relevant audio drivers i.e. Realtek AC '97

>

>I have spent around 50 hours of effort on this, (and have received very

>little assistance from M-Audio) so much so that I'm now seriously considering

>investing in a Mac, just so that I can get back to making some music. I have

>tested the device on a friend's Macbook and it works, so I know the problem

>is with Windows. Here is my system spec:

>

>Mainboard : Gigabyte GA-7VAX

>Chipset : VIA KT400 (VT8377)

>Processor : AMD Athlon XP @ 2000 MHz

>Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

>Video Card : NVIDIA GeForce FX 5500

>Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

>Ethernet Adapter

>Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3

>DirectX : Version 9.0c (July 2008)

>Firewire card: ADS Pyro 1394 DV

>

>When I look in the device manager, the firewire card appears under IEEE 1394

>Bus host controllers and under Network adapters. It doesm't appear at all

>under Sound, video and game controllers

>

>

>Any advice gratefully appreciated. Also, if anyone knows of an external

>firewire card (other than M-Audio) that actually works with Windows XP,

>again, I'd like to know.

>

>Thanks,

>Kierano

 

Additionally, since I noticed you have DirectX July (this can't be

right), perhaps try installing the DirectX August Redistributable

update. June was the last one so I don't know how you have one from

July.

 

Auguest version is here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

 

- Thee Chicago Wolf

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Thanks - I was looking at that this morning and dismissed it as I only have

one FW device. However, anything's worth a shot. I've requested it and will

run it ASAP.

 

"Thee Chicago Wolf" wrote:

> >Hi, I'm wondering if anyone out there knows of any acknowledged problems

> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814 (external

> >soundcard). The bottom line is the card was working beautifully for 3 months

> >then suddenly I'm getting disconnects - so much so that I now have a $500

> >piece of kit that I can't use. I can install the driver, click on the M-Audio

> >Control panel to adjust my settings, then I play an MP3 via WMP. It could be

> >OK for 5 minutes or sometimes even up to a couple of hours, then it will

> >disconnect. Here's what I've tried so far:

> >

> >Disabling my onboard soundcard

> >Disabling the 1394 net adapter

> >Trying all the M-Audio drivers available

> >Checked that Windows Audio is started, which it has

> >Updated all relevant audio drivers i.e. Realtek AC '97

> >

> >I have spent around 50 hours of effort on this, (and have received very

> >little assistance from M-Audio) so much so that I'm now seriously considering

> >investing in a Mac, just so that I can get back to making some music. I have

> >tested the device on a friend's Macbook and it works, so I know the problem

> >is with Windows. Here is my system spec:

> >

> >Mainboard : Gigabyte GA-7VAX

> >Chipset : VIA KT400 (VT8377)

> >Processor : AMD Athlon XP @ 2000 MHz

> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> >Video Card : NVIDIA GeForce FX 5500

> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

> >Ethernet Adapter

> >Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3

> >DirectX : Version 9.0c (July 2008)

> >Firewire card: ADS Pyro 1394 DV

> >

> >

> >When I look in the device manager, the firewire card appears under IEEE 1394

> >Bus host controllers and under Network adapters. It doesm't appear at all

> >under Sound, video and game controllers

> >

> >

> >Any advice gratefully appreciated. Also, if anyone knows of an external

> >firewire card (other than M-Audio) that actually works with Windows XP,

> >again, I'd like to know.

>

> You should try the hotfix from this KB article:

> http://support.microsoft.com/kb/952825

>

> - Thee Chicago Wolf

>

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>Thanks - I was looking at that this morning and dismissed it as I only have

>one FW device. However, anything's worth a shot. I've requested it and will

>run it ASAP.

 

Yes, it is worth a shot. My other thought was as to whether you've got

the current Hyperion Driver set going? Are you current on that as

well? It's a hunch but I've seen these niggling little things resolved

by updating chipset drives sometimes. Let me know if the KB fix helps

any.

 

- Thee Chicago Wolf

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

I installed the hotfix - unfortunately that didn't fix the problem.

 

OK - just downloading the August update as we speak. Not sure how I got the

set from July - it's what comes up on PC Wizard.

 

Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest one).

 

 

"Thee Chicago Wolf" wrote:

> >Hi, I'm wondering if anyone out there knows of any acknowledged problems

> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814 (external

> >soundcard). The bottom line is the card was working beautifully for 3 months

> >then suddenly I'm getting disconnects - so much so that I now have a $500

> >piece of kit that I can't use. I can install the driver, click on the M-Audio

> >Control panel to adjust my settings, then I play an MP3 via WMP. It could be

> >OK for 5 minutes or sometimes even up to a couple of hours, then it will

> >disconnect. Here's what I've tried so far:

> >

> >Disabling my onboard soundcard

> >Disabling the 1394 net adapter

> >Trying all the M-Audio drivers available

> >Checked that Windows Audio is started, which it has

> >Updated all relevant audio drivers i.e. Realtek AC '97

> >

> >I have spent around 50 hours of effort on this, (and have received very

> >little assistance from M-Audio) so much so that I'm now seriously considering

> >investing in a Mac, just so that I can get back to making some music. I have

> >tested the device on a friend's Macbook and it works, so I know the problem

> >is with Windows. Here is my system spec:

> >

> >Mainboard : Gigabyte GA-7VAX

> >Chipset : VIA KT400 (VT8377)

> >Processor : AMD Athlon XP @ 2000 MHz

> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> >Video Card : NVIDIA GeForce FX 5500

> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

> >Ethernet Adapter

> >Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3

> >DirectX : Version 9.0c (July 2008)

> >Firewire card: ADS Pyro 1394 DV

> >

> >When I look in the device manager, the firewire card appears under IEEE 1394

> >Bus host controllers and under Network adapters. It doesm't appear at all

> >under Sound, video and game controllers

> >

> >

> >Any advice gratefully appreciated. Also, if anyone knows of an external

> >firewire card (other than M-Audio) that actually works with Windows XP,

> >again, I'd like to know.

> >

> >Thanks,

> >Kierano

>

> Additionally, since I noticed you have DirectX July (this can't be

> right), perhaps try installing the DirectX August Redistributable

> update. June was the last one so I don't know how you have one from

> July.

>

> Auguest version is here:

> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

>

> - Thee Chicago Wolf

>

Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Try disconnecting the PC from the network and or disable your motherboard's

network chip and see if the problem goes away.

 

JS

 

"Kierano" <Kierano@discussions.microsoft.com> wrote in message

news:FF94FE89-5D5B-48B9-905A-CFD62597C3E8@microsoft.com...

>I installed the hotfix - unfortunately that didn't fix the problem.

>

> OK - just downloading the August update as we speak. Not sure how I got

> the

> set from July - it's what comes up on PC Wizard.

>

> Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest one).

>

>

> "Thee Chicago Wolf" wrote:

>

>> >Hi, I'm wondering if anyone out there knows of any acknowledged problems

>> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814

>> >(external

>> >soundcard). The bottom line is the card was working beautifully for 3

>> >months

>> >then suddenly I'm getting disconnects - so much so that I now have a

>> >$500

>> >piece of kit that I can't use. I can install the driver, click on the

>> >M-Audio

>> >Control panel to adjust my settings, then I play an MP3 via WMP. It

>> >could be

>> >OK for 5 minutes or sometimes even up to a couple of hours, then it will

>> >disconnect. Here's what I've tried so far:

>> >

>> >Disabling my onboard soundcard

>> >Disabling the 1394 net adapter

>> >Trying all the M-Audio drivers available

>> >Checked that Windows Audio is started, which it has

>> >Updated all relevant audio drivers i.e. Realtek AC '97

>> >

>> >I have spent around 50 hours of effort on this, (and have received very

>> >little assistance from M-Audio) so much so that I'm now seriously

>> >considering

>> >investing in a Mac, just so that I can get back to making some music. I

>> >have

>> >tested the device on a friend's Macbook and it works, so I know the

>> >problem

>> >is with Windows. Here is my system spec:

>> >

>> >Mainboard : Gigabyte GA-7VAX

>> >Chipset : VIA KT400 (VT8377)

>> >Processor : AMD Athlon XP @ 2000 MHz

>> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

>> >Video Card : NVIDIA GeForce FX 5500

>> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

>> >Ethernet Adapter

>> >Operating System : Microsoft Windows XP Professional 5.01.2600 Service

>> >Pack 3

>> >DirectX : Version 9.0c (July 2008)

>> >Firewire card: ADS Pyro 1394 DV

>> >

>> >When I look in the device manager, the firewire card appears under IEEE

>> >1394

>> >Bus host controllers and under Network adapters. It doesm't appear at

>> >all

>> >under Sound, video and game controllers

>> >

>> >

>> >Any advice gratefully appreciated. Also, if anyone knows of an external

>> >firewire card (other than M-Audio) that actually works with Windows XP,

>> >again, I'd like to know.

>> >

>> >Thanks,

>> >Kierano

>>

>> Additionally, since I noticed you have DirectX July (this can't be

>> right), perhaps try installing the DirectX August Redistributable

>> update. June was the last one so I don't know how you have one from

>> July.

>>

>> Auguest version is here:

>> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

>>

>> - Thee Chicago Wolf

>>

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

That's an interesting suggestion, but why would I have to do this? I have

powered down my router in the past to see if that helped (it didn't).

 

I have a colleague who can use this device on a Macbook with no problems. He

surfs the internet at the same time.

 

"JS" wrote:

> Try disconnecting the PC from the network and or disable your motherboard's

> network chip and see if the problem goes away.

>

> JS

>

> "Kierano" <Kierano@discussions.microsoft.com> wrote in message

> news:FF94FE89-5D5B-48B9-905A-CFD62597C3E8@microsoft.com...

> >I installed the hotfix - unfortunately that didn't fix the problem.

> >

> > OK - just downloading the August update as we speak. Not sure how I got

> > the

> > set from July - it's what comes up on PC Wizard.

> >

> > Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest one).

> >

> >

> > "Thee Chicago Wolf" wrote:

> >

> >> >Hi, I'm wondering if anyone out there knows of any acknowledged problems

> >> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814

> >> >(external

> >> >soundcard). The bottom line is the card was working beautifully for 3

> >> >months

> >> >then suddenly I'm getting disconnects - so much so that I now have a

> >> >$500

> >> >piece of kit that I can't use. I can install the driver, click on the

> >> >M-Audio

> >> >Control panel to adjust my settings, then I play an MP3 via WMP. It

> >> >could be

> >> >OK for 5 minutes or sometimes even up to a couple of hours, then it will

> >> >disconnect. Here's what I've tried so far:

> >> >

> >> >Disabling my onboard soundcard

> >> >Disabling the 1394 net adapter

> >> >Trying all the M-Audio drivers available

> >> >Checked that Windows Audio is started, which it has

> >> >Updated all relevant audio drivers i.e. Realtek AC '97

> >> >

> >> >I have spent around 50 hours of effort on this, (and have received very

> >> >little assistance from M-Audio) so much so that I'm now seriously

> >> >considering

> >> >investing in a Mac, just so that I can get back to making some music. I

> >> >have

> >> >tested the device on a friend's Macbook and it works, so I know the

> >> >problem

> >> >is with Windows. Here is my system spec:

> >> >

> >> >Mainboard : Gigabyte GA-7VAX

> >> >Chipset : VIA KT400 (VT8377)

> >> >Processor : AMD Athlon XP @ 2000 MHz

> >> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> >> >Video Card : NVIDIA GeForce FX 5500

> >> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

> >> >Ethernet Adapter

> >> >Operating System : Microsoft Windows XP Professional 5.01.2600 Service

> >> >Pack 3

> >> >DirectX : Version 9.0c (July 2008)

> >> >Firewire card: ADS Pyro 1394 DV

> >> >

> >> >When I look in the device manager, the firewire card appears under IEEE

> >> >1394

> >> >Bus host controllers and under Network adapters. It doesm't appear at

> >> >all

> >> >under Sound, video and game controllers

> >> >

> >> >

> >> >Any advice gratefully appreciated. Also, if anyone knows of an external

> >> >firewire card (other than M-Audio) that actually works with Windows XP,

> >> >again, I'd like to know.

> >> >

> >> >Thanks,

> >> >Kierano

> >>

> >> Additionally, since I noticed you have DirectX July (this can't be

> >> right), perhaps try installing the DirectX August Redistributable

> >> update. June was the last one so I don't know how you have one from

> >> July.

> >>

> >> Auguest version is here:

> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

> >>

> >> - Thee Chicago Wolf

> >>

>

>

>

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

I installed the Direct X update. Currently can't get the M-Audio drivers to

play ball. Have tried 3 times and am losing the will to live...

 

 

 

"Thee Chicago Wolf" wrote:

> >Hi, I'm wondering if anyone out there knows of any acknowledged problems

> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814 (external

> >soundcard). The bottom line is the card was working beautifully for 3 months

> >then suddenly I'm getting disconnects - so much so that I now have a $500

> >piece of kit that I can't use. I can install the driver, click on the M-Audio

> >Control panel to adjust my settings, then I play an MP3 via WMP. It could be

> >OK for 5 minutes or sometimes even up to a couple of hours, then it will

> >disconnect. Here's what I've tried so far:

> >

> >Disabling my onboard soundcard

> >Disabling the 1394 net adapter

> >Trying all the M-Audio drivers available

> >Checked that Windows Audio is started, which it has

> >Updated all relevant audio drivers i.e. Realtek AC '97

> >

> >I have spent around 50 hours of effort on this, (and have received very

> >little assistance from M-Audio) so much so that I'm now seriously considering

> >investing in a Mac, just so that I can get back to making some music. I have

> >tested the device on a friend's Macbook and it works, so I know the problem

> >is with Windows. Here is my system spec:

> >

> >Mainboard : Gigabyte GA-7VAX

> >Chipset : VIA KT400 (VT8377)

> >Processor : AMD Athlon XP @ 2000 MHz

> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> >Video Card : NVIDIA GeForce FX 5500

> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

> >Ethernet Adapter

> >Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3

> >DirectX : Version 9.0c (July 2008)

> >Firewire card: ADS Pyro 1394 DV

> >

> >When I look in the device manager, the firewire card appears under IEEE 1394

> >Bus host controllers and under Network adapters. It doesm't appear at all

> >under Sound, video and game controllers

> >

> >

> >Any advice gratefully appreciated. Also, if anyone knows of an external

> >firewire card (other than M-Audio) that actually works with Windows XP,

> >again, I'd like to know.

> >

> >Thanks,

> >Kierano

>

> Additionally, since I noticed you have DirectX July (this can't be

> right), perhaps try installing the DirectX August Redistributable

> update. June was the last one so I don't know how you have one from

> July.

>

> Auguest version is here:

> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

>

> - Thee Chicago Wolf

>

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>I installed the hotfix - unfortunately that didn't fix the problem.

>

>OK - just downloading the August update as we speak. Not sure how I got the

>set from July - it's what comes up on PC Wizard.

>

>Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest one).

 

5.20a, right? Double check one thing for me. Open device manager,

scroll down to System Devices and expend the tree for it. You'll

likely see some (two?) VIA entries down at the bottom. Double click

and check the driver dates on them. On my KT-600 motherboard, which I

don't have in front of me unfortunately, I think the dates were late

2007 based on the INF chipset drivers from the Hyperion set.

 

There's a couple more things you could look at or try. Since this card

basically runs on the built-in 1394 driver of XP and doesn't seem to

have anything from the Pyro site, here's what I would try:

 

1. Shut down the computer, Remove the Pyro card from it's PCI slot.

2. Boot up, go to Control Panel > System icon > Advanced tab > click

Environment Variables

3. Under System Variables, click New.

4. Enter devmgr_show_nonpresent_devices for the variable name and 1

for the variable value.

5. Click OK, OK, and OK to close System Properties.

 

Open device manager and then click View, Show Hidden Devices. Check

around and see if you can find the 1394 entry for your Pyro card.

You'll notice that devices that are live and connected have a very

solid icon and also there might be sort of faded icons. A faded icon

indicates a device that's no longer connected or orphaned. If you see

your Pyro card there, click it and press delete to remove it. Maybe

even remove any other 1394 related entries but that's your call.

 

Now, power down and put the Pyro back in but try another PCI slot if

you have one free. Power back up and see what happens.

 

Are you running the F13 BIOS on this motherboard?

http://www.gigabyte.com.tw/Support/Motherboard/BIOS_Model.aspx?ProductID=1392

 

One thing I noticed with the 1394bus.sys driver when I updated to SP3

on my laptop here was that it was still using the driver from SP2. I

manually overwrote the 1394bus.sys driver in

C:\Windows\System32\Drivers to the SP3 version (build 5512) and it

fixed a few issues I had with my Firewire DVD-burner. Check and see

what version you have residing in that folder.

 

Let me know if anything helps.

 

- Thee Chicago Wolf

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>I installed the Direct X update. Currently can't get the M-Audio drivers to

>play ball. Have tried 3 times and am losing the will to live...

 

This is the 5054v2 driver you're using right?

 

- Thee Chicago Wolf

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Right. It's a pretty tetchy driver. Not windows-compliant, which doesn't

help. What should happen is:

 

1) Install - it checks for previous installations then cleans the registry,

except it doesn't do a great job at that

 

2) Install again - this time it copies some files across

 

3) Reboot and wait for bootloader to get detected, except sometimes it does

but more often it doesn't. If you try and add it via 'Add hardware', you end

up with Code 10

 

4) Wait for the FW1814 itself to get detected

 

 

 

 

"Thee Chicago Wolf" wrote:

> >I installed the Direct X update. Currently can't get the M-Audio drivers to

> >play ball. Have tried 3 times and am losing the will to live...

>

> This is the 5054v2 driver you're using right?

>

> - Thee Chicago Wolf

>

Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Some motherboard network chips use firewire and could be causing the

disconnects.

 

JS

 

"Kierano" <Kierano@discussions.microsoft.com> wrote in message

news:BB599AA5-F56D-4923-8CB3-F0EF6D7A00BA@microsoft.com...

> That's an interesting suggestion, but why would I have to do this? I have

> powered down my router in the past to see if that helped (it didn't).

>

> I have a colleague who can use this device on a Macbook with no problems.

> He

> surfs the internet at the same time.

>

> "JS" wrote:

>

>> Try disconnecting the PC from the network and or disable your

>> motherboard's

>> network chip and see if the problem goes away.

>>

>> JS

>>

>> "Kierano" <Kierano@discussions.microsoft.com> wrote in message

>> news:FF94FE89-5D5B-48B9-905A-CFD62597C3E8@microsoft.com...

>> >I installed the hotfix - unfortunately that didn't fix the problem.

>> >

>> > OK - just downloading the August update as we speak. Not sure how I got

>> > the

>> > set from July - it's what comes up on PC Wizard.

>> >

>> > Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest one).

>> >

>> >

>> > "Thee Chicago Wolf" wrote:

>> >

>> >> >Hi, I'm wondering if anyone out there knows of any acknowledged

>> >> >problems

>> >> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814

>> >> >(external

>> >> >soundcard). The bottom line is the card was working beautifully for 3

>> >> >months

>> >> >then suddenly I'm getting disconnects - so much so that I now have a

>> >> >$500

>> >> >piece of kit that I can't use. I can install the driver, click on the

>> >> >M-Audio

>> >> >Control panel to adjust my settings, then I play an MP3 via WMP. It

>> >> >could be

>> >> >OK for 5 minutes or sometimes even up to a couple of hours, then it

>> >> >will

>> >> >disconnect. Here's what I've tried so far:

>> >> >

>> >> >Disabling my onboard soundcard

>> >> >Disabling the 1394 net adapter

>> >> >Trying all the M-Audio drivers available

>> >> >Checked that Windows Audio is started, which it has

>> >> >Updated all relevant audio drivers i.e. Realtek AC '97

>> >> >

>> >> >I have spent around 50 hours of effort on this, (and have received

>> >> >very

>> >> >little assistance from M-Audio) so much so that I'm now seriously

>> >> >considering

>> >> >investing in a Mac, just so that I can get back to making some music.

>> >> >I

>> >> >have

>> >> >tested the device on a friend's Macbook and it works, so I know the

>> >> >problem

>> >> >is with Windows. Here is my system spec:

>> >> >

>> >> >Mainboard : Gigabyte GA-7VAX

>> >> >Chipset : VIA KT400 (VT8377)

>> >> >Processor : AMD Athlon XP @ 2000 MHz

>> >> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

>> >> >Video Card : NVIDIA GeForce FX 5500

>> >> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

>> >> >Ethernet Adapter

>> >> >Operating System : Microsoft Windows XP Professional 5.01.2600

>> >> >Service

>> >> >Pack 3

>> >> >DirectX : Version 9.0c (July 2008)

>> >> >Firewire card: ADS Pyro 1394 DV

>> >> >

>> >> >When I look in the device manager, the firewire card appears under

>> >> >IEEE

>> >> >1394

>> >> >Bus host controllers and under Network adapters. It doesm't appear at

>> >> >all

>> >> >under Sound, video and game controllers

>> >> >

>> >> >

>> >> >Any advice gratefully appreciated. Also, if anyone knows of an

>> >> >external

>> >> >firewire card (other than M-Audio) that actually works with Windows

>> >> >XP,

>> >> >again, I'd like to know.

>> >> >

>> >> >Thanks,

>> >> >Kierano

>> >>

>> >> Additionally, since I noticed you have DirectX July (this can't be

>> >> right), perhaps try installing the DirectX August Redistributable

>> >> update. June was the last one so I don't know how you have one from

>> >> July.

>> >>

>> >> Auguest version is here:

>> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

>> >>

>> >> - Thee Chicago Wolf

>> >>

>>

>>

>>

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

OK - I understand your logic so tried it. Unfortunately, it didn't work,

although I was at least able to re-install the M-Audio drivers. Worked for a

couple of tracks then disconnected.

 

 

"JS" wrote:

> Some motherboard network chips use firewire and could be causing the

> disconnects.

>

> JS

>

> "Kierano" <Kierano@discussions.microsoft.com> wrote in message

> news:BB599AA5-F56D-4923-8CB3-F0EF6D7A00BA@microsoft.com...

> > That's an interesting suggestion, but why would I have to do this? I have

> > powered down my router in the past to see if that helped (it didn't).

> >

> > I have a colleague who can use this device on a Macbook with no problems.

> > He

> > surfs the internet at the same time.

> >

> > "JS" wrote:

> >

> >> Try disconnecting the PC from the network and or disable your

> >> motherboard's

> >> network chip and see if the problem goes away.

> >>

> >> JS

> >>

> >> "Kierano" <Kierano@discussions.microsoft.com> wrote in message

> >> news:FF94FE89-5D5B-48B9-905A-CFD62597C3E8@microsoft.com...

> >> >I installed the hotfix - unfortunately that didn't fix the problem.

> >> >

> >> > OK - just downloading the August update as we speak. Not sure how I got

> >> > the

> >> > set from July - it's what comes up on PC Wizard.

> >> >

> >> > Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest one).

> >> >

> >> >

> >> > "Thee Chicago Wolf" wrote:

> >> >

> >> >> >Hi, I'm wondering if anyone out there knows of any acknowledged

> >> >> >problems

> >> >> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire 1814

> >> >> >(external

> >> >> >soundcard). The bottom line is the card was working beautifully for 3

> >> >> >months

> >> >> >then suddenly I'm getting disconnects - so much so that I now have a

> >> >> >$500

> >> >> >piece of kit that I can't use. I can install the driver, click on the

> >> >> >M-Audio

> >> >> >Control panel to adjust my settings, then I play an MP3 via WMP. It

> >> >> >could be

> >> >> >OK for 5 minutes or sometimes even up to a couple of hours, then it

> >> >> >will

> >> >> >disconnect. Here's what I've tried so far:

> >> >> >

> >> >> >Disabling my onboard soundcard

> >> >> >Disabling the 1394 net adapter

> >> >> >Trying all the M-Audio drivers available

> >> >> >Checked that Windows Audio is started, which it has

> >> >> >Updated all relevant audio drivers i.e. Realtek AC '97

> >> >> >

> >> >> >I have spent around 50 hours of effort on this, (and have received

> >> >> >very

> >> >> >little assistance from M-Audio) so much so that I'm now seriously

> >> >> >considering

> >> >> >investing in a Mac, just so that I can get back to making some music.

> >> >> >I

> >> >> >have

> >> >> >tested the device on a friend's Macbook and it works, so I know the

> >> >> >problem

> >> >> >is with Windows. Here is my system spec:

> >> >> >

> >> >> >Mainboard : Gigabyte GA-7VAX

> >> >> >Chipset : VIA KT400 (VT8377)

> >> >> >Processor : AMD Athlon XP @ 2000 MHz

> >> >> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> >> >> >Video Card : NVIDIA GeForce FX 5500

> >> >> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+) Fast

> >> >> >Ethernet Adapter

> >> >> >Operating System : Microsoft Windows XP Professional 5.01.2600

> >> >> >Service

> >> >> >Pack 3

> >> >> >DirectX : Version 9.0c (July 2008)

> >> >> >Firewire card: ADS Pyro 1394 DV

> >> >> >

> >> >> >When I look in the device manager, the firewire card appears under

> >> >> >IEEE

> >> >> >1394

> >> >> >Bus host controllers and under Network adapters. It doesm't appear at

> >> >> >all

> >> >> >under Sound, video and game controllers

> >> >> >

> >> >> >

> >> >> >Any advice gratefully appreciated. Also, if anyone knows of an

> >> >> >external

> >> >> >firewire card (other than M-Audio) that actually works with Windows

> >> >> >XP,

> >> >> >again, I'd like to know.

> >> >> >

> >> >> >Thanks,

> >> >> >Kierano

> >> >>

> >> >> Additionally, since I noticed you have DirectX July (this can't be

> >> >> right), perhaps try installing the DirectX August Redistributable

> >> >> update. June was the last one so I don't know how you have one from

> >> >> July.

> >> >>

> >> >> Auguest version is here:

> >> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

> >> >>

> >> >> - Thee Chicago Wolf

> >> >>

> >>

> >>

> >>

>

>

>

Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Have you looked at the event logs to see if there is anything related to

your problem?

 

JS

 

"Kierano" <Kierano@discussions.microsoft.com> wrote in message

news:252D1162-06F6-43D7-BD77-90DC90ABCDEF@microsoft.com...

> OK - I understand your logic so tried it. Unfortunately, it didn't work,

> although I was at least able to re-install the M-Audio drivers. Worked for

> a

> couple of tracks then disconnected.

>

>

> "JS" wrote:

>

>> Some motherboard network chips use firewire and could be causing the

>> disconnects.

>>

>> JS

>>

>> "Kierano" <Kierano@discussions.microsoft.com> wrote in message

>> news:BB599AA5-F56D-4923-8CB3-F0EF6D7A00BA@microsoft.com...

>> > That's an interesting suggestion, but why would I have to do this? I

>> > have

>> > powered down my router in the past to see if that helped (it didn't).

>> >

>> > I have a colleague who can use this device on a Macbook with no

>> > problems.

>> > He

>> > surfs the internet at the same time.

>> >

>> > "JS" wrote:

>> >

>> >> Try disconnecting the PC from the network and or disable your

>> >> motherboard's

>> >> network chip and see if the problem goes away.

>> >>

>> >> JS

>> >>

>> >> "Kierano" <Kierano@discussions.microsoft.com> wrote in message

>> >> news:FF94FE89-5D5B-48B9-905A-CFD62597C3E8@microsoft.com...

>> >> >I installed the hotfix - unfortunately that didn't fix the problem.

>> >> >

>> >> > OK - just downloading the August update as we speak. Not sure how I

>> >> > got

>> >> > the

>> >> > set from July - it's what comes up on PC Wizard.

>> >> >

>> >> > Re: Hyperion, yep - I'm running on VIA HyperionPro 5.20 (latest

>> >> > one).

>> >> >

>> >> >

>> >> > "Thee Chicago Wolf" wrote:

>> >> >

>> >> >> >Hi, I'm wondering if anyone out there knows of any acknowledged

>> >> >> >problems

>> >> >> >between Windows XP SP2 and SP3 and M-Audio's flagship Firewire

>> >> >> >1814

>> >> >> >(external

>> >> >> >soundcard). The bottom line is the card was working beautifully

>> >> >> >for 3

>> >> >> >months

>> >> >> >then suddenly I'm getting disconnects - so much so that I now have

>> >> >> >a

>> >> >> >$500

>> >> >> >piece of kit that I can't use. I can install the driver, click on

>> >> >> >the

>> >> >> >M-Audio

>> >> >> >Control panel to adjust my settings, then I play an MP3 via WMP.

>> >> >> >It

>> >> >> >could be

>> >> >> >OK for 5 minutes or sometimes even up to a couple of hours, then

>> >> >> >it

>> >> >> >will

>> >> >> >disconnect. Here's what I've tried so far:

>> >> >> >

>> >> >> >Disabling my onboard soundcard

>> >> >> >Disabling the 1394 net adapter

>> >> >> >Trying all the M-Audio drivers available

>> >> >> >Checked that Windows Audio is started, which it has

>> >> >> >Updated all relevant audio drivers i.e. Realtek AC '97

>> >> >> >

>> >> >> >I have spent around 50 hours of effort on this, (and have received

>> >> >> >very

>> >> >> >little assistance from M-Audio) so much so that I'm now seriously

>> >> >> >considering

>> >> >> >investing in a Mac, just so that I can get back to making some

>> >> >> >music.

>> >> >> >I

>> >> >> >have

>> >> >> >tested the device on a friend's Macbook and it works, so I know

>> >> >> >the

>> >> >> >problem

>> >> >> >is with Windows. Here is my system spec:

>> >> >> >

>> >> >> >Mainboard : Gigabyte GA-7VAX

>> >> >> >Chipset : VIA KT400 (VT8377)

>> >> >> >Processor : AMD Athlon XP @ 2000 MHz

>> >> >> >Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

>> >> >> >Video Card : NVIDIA GeForce FX 5500

>> >> >> >Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+)

>> >> >> >Fast

>> >> >> >Ethernet Adapter

>> >> >> >Operating System : Microsoft Windows XP Professional 5.01.2600

>> >> >> >Service

>> >> >> >Pack 3

>> >> >> >DirectX : Version 9.0c (July 2008)

>> >> >> >Firewire card: ADS Pyro 1394 DV

>> >> >> >

>> >> >> >When I look in the device manager, the firewire card appears under

>> >> >> >IEEE

>> >> >> >1394

>> >> >> >Bus host controllers and under Network adapters. It doesm't appear

>> >> >> >at

>> >> >> >all

>> >> >> >under Sound, video and game controllers

>> >> >> >

>> >> >> >

>> >> >> >Any advice gratefully appreciated. Also, if anyone knows of an

>> >> >> >external

>> >> >> >firewire card (other than M-Audio) that actually works with

>> >> >> >Windows

>> >> >> >XP,

>> >> >> >again, I'd like to know.

>> >> >> >

>> >> >> >Thanks,

>> >> >> >Kierano

>> >> >>

>> >> >> Additionally, since I noticed you have DirectX July (this can't be

>> >> >> right), perhaps try installing the DirectX August Redistributable

>> >> >> update. June was the last one so I don't know how you have one from

>> >> >> July.

>> >> >>

>> >> >> Auguest version is here:

>> >> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=c1367bc3-4676-481a-bfaa-5c15d1d7199d&DisplayLang=en

>> >> >>

>> >> >> - Thee Chicago Wolf

>> >> >>

>> >>

>> >>

>> >>

>>

>>

>>

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>Right. It's a pretty tetchy driver. Not windows-compliant, which doesn't

>help. What should happen is:

>

>1) Install - it checks for previous installations then cleans the registry,

>except it doesn't do a great job at that

>

>2) Install again - this time it copies some files across

>

>3) Reboot and wait for bootloader to get detected, except sometimes it does

>but more often it doesn't. If you try and add it via 'Add hardware', you end

>up with Code 10

>

>4) Wait for the FW1814 itself to get detected

 

Any luck with the suggestions I made?

 

- Thee Chicago Wolf

Posted

Re: M-Audio Firewire 1814 and Windows XP

 

=?Utf-8?B?S2llcmFubw==?= <Kierano@discussions.microsoft.com> écrivait

news:75F17E63-DA29-4464-8D43-A2B648F5D3A7@microsoft.com:

> Hi, I'm wondering if anyone out there knows of any acknowledged

> problems between Windows XP SP2 and SP3 and M-Audio's flagship

> Firewire 1814 (external soundcard). The bottom line is the card was

> working beautifully for 3 months then suddenly I'm getting disconnects

> - so much so that I now have a $500 piece of kit that I can't use. I

> can install the driver, click on the M-Audio Control panel to adjust

> my settings, then I play an MP3 via WMP. It could be OK for 5 minutes

> or sometimes even up to a couple of hours, then it will disconnect.

> Here's what I've tried so far:

>

> Disabling my onboard soundcard

> Disabling the 1394 net adapter

> Trying all the M-Audio drivers available

> Checked that Windows Audio is started, which it has

> Updated all relevant audio drivers i.e. Realtek AC '97

>

> I have spent around 50 hours of effort on this, (and have received

> very little assistance from M-Audio) so much so that I'm now seriously

> considering investing in a Mac, just so that I can get back to making

> some music. I have tested the device on a friend's Macbook and it

> works, so I know the problem is with Windows. Here is my system spec:

>

> Mainboard : Gigabyte GA-7VAX

> Chipset : VIA KT400 (VT8377)

> Processor : AMD Athlon XP @ 2000 MHz

> Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> Video Card : NVIDIA GeForce FX 5500

> Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+)

> Fast Ethernet Adapter

> Operating System : Microsoft Windows XP Professional 5.01.2600

> Service Pack 3 DirectX : Version 9.0c (July 2008)

> Firewire card: ADS Pyro 1394 DV

>

>

> When I look in the device manager, the firewire card appears under

> IEEE 1394 Bus host controllers and under Network adapters. It doesm't

> appear at all under Sound, video and game controllers

>

>

> Any advice gratefully appreciated. Also, if anyone knows of an

> external firewire card (other than M-Audio) that actually works with

> Windows XP, again, I'd like to know.

>

> Thanks,

> Kierano

>

>

 

Hello

 

Some FireWire audio interface are happier with a Texas Instrument

FireWire chip controller, I know it's also the case with the MOTU 828

mkII.

 

http://www.m-audio.ca/index.php?do=support.faq&ID=

2b420cae8f6a01a4431eeacc05719af3

 

HTH

Doum

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Hi there,

 

I followed all the steps you mentioned apart from the bios, which is always

a bit of a risky thing to do. Also, I already had the 5512 build for the

1394bus.sys.

 

When viewing the hidden devices, there were several instances of the 1394

Bus Host Controller, which I duly deleted, along with the 1394 Net Adapter. I

left the 1394 ARP Client Protocol in there. In addition, I spotted a Seagate

FreeAgent Pro IEEE 1394 SBP2 Device. This was a bad drive I had around 4

weeks ago, although it was after my problems had started.

 

On re-booting, the 1394 Controller was detected, along with Texas

Instruments OHCI Compliant IEEE 1394 Host Controller.

 

My main problem right now is getting the M-Audio drivers to run properly.

Oh, and the fact that my system gets stuck on the Hardware Profile page on

boot up. Mind you, it did that yesterday and then I enabled the USB keyboard

and mouse and it worked. This morning, not so lucky...

 

Thanks for all your suggestions so far. A friend of mine with an iMac all in

one has offered to thoroughly test the M-Audio box from Thursday night over

the weekend. If it works properly on his iMac, I may just have to bite the

bullet so I can get back to my music instead of trying to get this to work.

 

I really appreciate all your suggestions so far.

 

 

 

"Thee Chicago Wolf" wrote:

> >Right. It's a pretty tetchy driver. Not windows-compliant, which doesn't

> >help. What should happen is:

> >

> >1) Install - it checks for previous installations then cleans the registry,

> >except it doesn't do a great job at that

> >

> >2) Install again - this time it copies some files across

> >

> >3) Reboot and wait for bootloader to get detected, except sometimes it does

> >but more often it doesn't. If you try and add it via 'Add hardware', you end

> >up with Code 10

> >

> >4) Wait for the FW1814 itself to get detected

>

> Any luck with the suggestions I made?

>

> - Thee Chicago Wolf

>

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

No problem there, as mine is TI chipset.

 

Thanks anyway.

 

"Doum" wrote:

> =?Utf-8?B?S2llcmFubw==?= <Kierano@discussions.microsoft.com> écrivait

> news:75F17E63-DA29-4464-8D43-A2B648F5D3A7@microsoft.com:

>

> > Hi, I'm wondering if anyone out there knows of any acknowledged

> > problems between Windows XP SP2 and SP3 and M-Audio's flagship

> > Firewire 1814 (external soundcard). The bottom line is the card was

> > working beautifully for 3 months then suddenly I'm getting disconnects

> > - so much so that I now have a $500 piece of kit that I can't use. I

> > can install the driver, click on the M-Audio Control panel to adjust

> > my settings, then I play an MP3 via WMP. It could be OK for 5 minutes

> > or sometimes even up to a couple of hours, then it will disconnect.

> > Here's what I've tried so far:

> >

> > Disabling my onboard soundcard

> > Disabling the 1394 net adapter

> > Trying all the M-Audio drivers available

> > Checked that Windows Audio is started, which it has

> > Updated all relevant audio drivers i.e. Realtek AC '97

> >

> > I have spent around 50 hours of effort on this, (and have received

> > very little assistance from M-Audio) so much so that I'm now seriously

> > considering investing in a Mac, just so that I can get back to making

> > some music. I have tested the device on a friend's Macbook and it

> > works, so I know the problem is with Windows. Here is my system spec:

> >

> > Mainboard : Gigabyte GA-7VAX

> > Chipset : VIA KT400 (VT8377)

> > Processor : AMD Athlon XP @ 2000 MHz

> > Physical Memory : 1024 MB (2 x 512 DDR-SDRAM )

> > Video Card : NVIDIA GeForce FX 5500

> > Network Card : Realtek Semiconductor RT8139 (A/B/C/810x/813x/C+)

> > Fast Ethernet Adapter

> > Operating System : Microsoft Windows XP Professional 5.01.2600

> > Service Pack 3 DirectX : Version 9.0c (July 2008)

> > Firewire card: ADS Pyro 1394 DV

> >

> >

> > When I look in the device manager, the firewire card appears under

> > IEEE 1394 Bus host controllers and under Network adapters. It doesm't

> > appear at all under Sound, video and game controllers

> >

> >

> > Any advice gratefully appreciated. Also, if anyone knows of an

> > external firewire card (other than M-Audio) that actually works with

> > Windows XP, again, I'd like to know.

> >

> > Thanks,

> > Kierano

> >

> >

>

> Hello

>

> Some FireWire audio interface are happier with a Texas Instrument

> FireWire chip controller, I know it's also the case with the MOTU 828

> mkII.

>

> http://www.m-audio.ca/index.php?do=support.faq&ID=

> 2b420cae8f6a01a4431eeacc05719af3

>

> HTH

> Doum

>

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>I followed all the steps you mentioned apart from the bios, which is always

>a bit of a risky thing to do. Also, I already had the 5512 build for the

>1394bus.sys.

 

No, not so much. It would certainly eliminate all possibilities and

point to the drivers from M-Audio.

 

One other poster suggested it, have you considered picking up a newer

Firewire card? I own an Audiophile 2496 for some years and I know

M-Audio drivers aren't all that terrible. In your case it sounds like

installing and re-installing the drivers has gummed something up

somewhere.

>When viewing the hidden devices, there were several instances of the 1394

>Bus Host Controller, which I duly deleted, along with the 1394 Net Adapter. I

>left the 1394 ARP Client Protocol in there. In addition, I spotted a Seagate

>FreeAgent Pro IEEE 1394 SBP2 Device. This was a bad drive I had around 4

>weeks ago, although it was after my problems had started.

>

>On re-booting, the 1394 Controller was detected, along with Texas

>Instruments OHCI Compliant IEEE 1394 Host Controller.

>

>My main problem right now is getting the M-Audio drivers to run properly.

>Oh, and the fact that my system gets stuck on the Hardware Profile page on

>boot up. Mind you, it did that yesterday and then I enabled the USB keyboard

>and mouse and it worked. This morning, not so lucky...

>

>Thanks for all your suggestions so far. A friend of mine with an iMac all in

>one has offered to thoroughly test the M-Audio box from Thursday night over

>the weekend. If it works properly on his iMac, I may just have to bite the

>bullet so I can get back to my music instead of trying to get this to work.

>

>I really appreciate all your suggestions so far.

 

No problem, let me know how it goes.

 

- Thee Chicago Wolf

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

OK, still can't get the drivers to play ball.

 

In the meantime, I did my usual trawl through the M-Audio forums and managed

to pick up some suggestions made to another user:

 

The good news is that my chipst (VIA KT400) is a recommended one. My problem

seems to be that I am using a virtual IRQ (>15). Mine's on 17. So the FW card

is sharing resources with some other device (although I'm not seeing that

when I view devices by type). M-Audio say that ideally the device needs to

have its own IRQ below 16, and that this can be achieved through the bios

with the OS installed in 'standard PC' mode. This all sounds a bit convoluted

to me. Isn't there a more straightforward way in XP that I can re-allocate

the IRQs and somehow get the FW card on an IRQ under 16?

 

Other tips were to make sure I have the most recent VIA 4-in-1 driver (4.45

or higher), but I'm thinking that's what the Hyperion drivers are. Then they

suggest a bios update but only when using older VIA chipsets. I'm sure this

problem is down to the IRQ and if I can only find a way to get the FW card on

an IRQ lower than 16... but how?

 

 

 

 

 

"Thee Chicago Wolf" wrote:

> >I followed all the steps you mentioned apart from the bios, which is always

> >a bit of a risky thing to do. Also, I already had the 5512 build for the

> >1394bus.sys.

>

> No, not so much. It would certainly eliminate all possibilities and

> point to the drivers from M-Audio.

>

> One other poster suggested it, have you considered picking up a newer

> Firewire card? I own an Audiophile 2496 for some years and I know

> M-Audio drivers aren't all that terrible. In your case it sounds like

> installing and re-installing the drivers has gummed something up

> somewhere.

>

> >When viewing the hidden devices, there were several instances of the 1394

> >Bus Host Controller, which I duly deleted, along with the 1394 Net Adapter. I

> >left the 1394 ARP Client Protocol in there. In addition, I spotted a Seagate

> >FreeAgent Pro IEEE 1394 SBP2 Device. This was a bad drive I had around 4

> >weeks ago, although it was after my problems had started.

> >

> >On re-booting, the 1394 Controller was detected, along with Texas

> >Instruments OHCI Compliant IEEE 1394 Host Controller.

> >

> >My main problem right now is getting the M-Audio drivers to run properly.

> >Oh, and the fact that my system gets stuck on the Hardware Profile page on

> >boot up. Mind you, it did that yesterday and then I enabled the USB keyboard

> >and mouse and it worked. This morning, not so lucky...

> >

> >Thanks for all your suggestions so far. A friend of mine with an iMac all in

> >one has offered to thoroughly test the M-Audio box from Thursday night over

> >the weekend. If it works properly on his iMac, I may just have to bite the

> >bullet so I can get back to my music instead of trying to get this to work.

> >

> >I really appreciate all your suggestions so far.

>

> No problem, let me know how it goes.

>

> - Thee Chicago Wolf

>

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>OK, still can't get the drivers to play ball.

>

>In the meantime, I did my usual trawl through the M-Audio forums and managed

>to pick up some suggestions made to another user:

>

>The good news is that my chipst (VIA KT400) is a recommended one. My problem

>seems to be that I am using a virtual IRQ (>15). Mine's on 17. So the FW card

>is sharing resources with some other device (although I'm not seeing that

>when I view devices by type). M-Audio say that ideally the device needs to

>have its own IRQ below 16, and that this can be achieved through the bios

>with the OS installed in 'standard PC' mode. This all sounds a bit convoluted

>to me. Isn't there a more straightforward way in XP that I can re-allocate

>the IRQs and somehow get the FW card on an IRQ under 16?

>

>Other tips were to make sure I have the most recent VIA 4-in-1 driver (4.45

>or higher), but I'm thinking that's what the Hyperion drivers are. Then they

>suggest a bios update but only when using older VIA chipsets. I'm sure this

>problem is down to the IRQ and if I can only find a way to get the FW card on

>an IRQ lower than 16... but how?

 

Wow, in this modern day someone is suggesting it's an IRQ conflict?

That's a pretty far stretch since motherboard today have all but

eliminated the IRQ conflicts of yesteryear due to BIOS advancements.

 

I still stand by a BIOS update to ensure that IF there is any IRQ

sharing conflict, it may be resolved in a code update. I know your

hesitation but don't rule it out until you've exhausted everything.

 

A couple things you can do to free up some system resources would be

to go into your BIOS settings and disable the LPT port and any COM

ports. Both would use IRQs and disabling them would free up 2 IRQs at

the very least. Am I correct to assume you do not use an LPT based

printer or a serial port mouse? I don't think I've seen either in use

in well over 6+ years.

 

Have you also tried to put the FW card in another PCI slot? Some

BIOSes have a setting to forget the hardware configuration and this is

a bit of old trickery from the legacy days when certain PCI card

didn't play well in Plug and Play. It would basically remap all the

devices again and sometimes re-assign an IRQ to a device differently

than when it was in another PCI slot.

 

Forgot the VIA drivers. This is a hardware issue for sure.

 

- Thee Chicago Wolf

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Tried flashing the BIOS but it failed. Thankfully I have a dual BIOS so no

problems with rebooting. I had used @BIOS - is there a more reliable tool

that you know about (preferably non-Windows).

 

Checked the PnP/PCI Configurations in the BIOS, which are:

 

PCI1 / PCI15 - IRQ Assignment [Auto]

PCI2 - IRQ Assignment [Auto]

PCI3 - IRQ Assignment [Auto]

PCI4 - IRQ Assignment [Auto]

 

I have the ability to change 'Auto' to anything from 1 thru 15.

 

I did try changing the first one (PCI1 / PCI15) to 3 but it made no

difference. When I checked, the IRQ was still set to 17. Just want to make

sure that I don't screw anything up by doing this.

 

 

 

 

 

"Thee Chicago Wolf" wrote:

> >OK, still can't get the drivers to play ball.

> >

> >In the meantime, I did my usual trawl through the M-Audio forums and managed

> >to pick up some suggestions made to another user:

> >

> >The good news is that my chipst (VIA KT400) is a recommended one. My problem

> >seems to be that I am using a virtual IRQ (>15). Mine's on 17. So the FW card

> >is sharing resources with some other device (although I'm not seeing that

> >when I view devices by type). M-Audio say that ideally the device needs to

> >have its own IRQ below 16, and that this can be achieved through the bios

> >with the OS installed in 'standard PC' mode. This all sounds a bit convoluted

> >to me. Isn't there a more straightforward way in XP that I can re-allocate

> >the IRQs and somehow get the FW card on an IRQ under 16?

> >

> >Other tips were to make sure I have the most recent VIA 4-in-1 driver (4.45

> >or higher), but I'm thinking that's what the Hyperion drivers are. Then they

> >suggest a bios update but only when using older VIA chipsets. I'm sure this

> >problem is down to the IRQ and if I can only find a way to get the FW card on

> >an IRQ lower than 16... but how?

>

> Wow, in this modern day someone is suggesting it's an IRQ conflict?

> That's a pretty far stretch since motherboard today have all but

> eliminated the IRQ conflicts of yesteryear due to BIOS advancements.

>

> I still stand by a BIOS update to ensure that IF there is any IRQ

> sharing conflict, it may be resolved in a code update. I know your

> hesitation but don't rule it out until you've exhausted everything.

>

> A couple things you can do to free up some system resources would be

> to go into your BIOS settings and disable the LPT port and any COM

> ports. Both would use IRQs and disabling them would free up 2 IRQs at

> the very least. Am I correct to assume you do not use an LPT based

> printer or a serial port mouse? I don't think I've seen either in use

> in well over 6+ years.

>

> Have you also tried to put the FW card in another PCI slot? Some

> BIOSes have a setting to forget the hardware configuration and this is

> a bit of old trickery from the legacy days when certain PCI card

> didn't play well in Plug and Play. It would basically remap all the

> devices again and sometimes re-assign an IRQ to a device differently

> than when it was in another PCI slot.

>

> Forgot the VIA drivers. This is a hardware issue for sure.

>

> - Thee Chicago Wolf

>

Guest Thee Chicago Wolf
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

>Tried flashing the BIOS but it failed. Thankfully I have a dual BIOS so no

>problems with rebooting. I had used @BIOS - is there a more reliable tool

>that you know about (preferably non-Windows).

>

>Checked the PnP/PCI Configurations in the BIOS, which are:

>

>PCI1 / PCI15 - IRQ Assignment [Auto]

>PCI2 - IRQ Assignment [Auto]

>PCI3 - IRQ Assignment [Auto]

>PCI4 - IRQ Assignment [Auto]

>

>I have the ability to change 'Auto' to anything from 1 thru 15.

>

>I did try changing the first one (PCI1 / PCI15) to 3 but it made no

>difference. When I checked, the IRQ was still set to 17. Just want to make

>sure that I don't screw anything up by doing this.

 

Yikes, BIOS flash in-Windows? I've never done one of those in my life.

I'm used to the DOS method of doing things. Hold the boat though.

 

Check this KB article that just popped up yesterday. It has an even

newer OHCI1494 driver and fix. Might be worth trying:

http://support.microsoft.com/kb/951410

 

Fingers crossed!

 

- Thee Chicago Wolf

Guest Kierano
Posted

Re: M-Audio Firewire 1814 and Windows XP

 

Thanks for all your help. In the end, this is a bit like a bad investment -

throwing good money after bad; except it's effort. I have spent so long on

this that I finally decided to cut out the stress. This morning I have

ordered an iMac which I know is built for audio and video. I now look forward

to getting back to my music rather than worrying about how to get my device

in the top 15 IRQs. In fact, some time in the not too distant future, I hope

to be able to look back on this time and laugh.

 

You have been a lifeline in helping me leave no stone unturned - so thanks

again!

 

 

 

 

"Thee Chicago Wolf" wrote:

> >Tried flashing the BIOS but it failed. Thankfully I have a dual BIOS so no

> >problems with rebooting. I had used @BIOS - is there a more reliable tool

> >that you know about (preferably non-Windows).

> >

> >Checked the PnP/PCI Configurations in the BIOS, which are:

> >

> >PCI1 / PCI15 - IRQ Assignment [Auto]

> >PCI2 - IRQ Assignment [Auto]

> >PCI3 - IRQ Assignment [Auto]

> >PCI4 - IRQ Assignment [Auto]

> >

> >I have the ability to change 'Auto' to anything from 1 thru 15.

> >

> >I did try changing the first one (PCI1 / PCI15) to 3 but it made no

> >difference. When I checked, the IRQ was still set to 17. Just want to make

> >sure that I don't screw anything up by doing this.

>

> Yikes, BIOS flash in-Windows? I've never done one of those in my life.

> I'm used to the DOS method of doing things. Hold the boat though.

>

> Check this KB article that just popped up yesterday. It has an even

> newer OHCI1494 driver and fix. Might be worth trying:

> http://support.microsoft.com/kb/951410

>

> Fingers crossed!

>

> - Thee Chicago Wolf

>

×
×
  • Create New...