I have an old PC where to run old software and old projects:
This PC have CPU Intel Quad Q9550 @ 2,83 GHz, 4 GB RAM (seen 3,50 GB with PAE), system disk is a Samsung SSD 860 EVO 500 GB and secondary Hard Disk 2 TB, video board Nvidia GeForce GT520, with PCI card firewire chipset Texas Instruments; PSU ColorsIt 550. O.S. is Windows XP Home updated to Service Pack 3.
I have optimized the system with some tweaks on Bios and on OS, i disabled many services.
Now my problem: i can't install sound board Tascam FW-1804, install with his last installer v.1.80, install but don't goes to second step, that is when i connect and turn on soundboard, this and the pc do not recognize each other, firewire led on soundboard don't turn on. Just once installer it is gone to second step installing hardware drivers but firewire led remain turn off and when i restart PC this don't recognize Tascam soundboard, if i open control panel of this board remains grey. No sound, obviously.
Note:
Firewire card on PC is working fine because the pc have another soundboard (M-Audio FW-Solo) and this works fine.
Also the Tascam is working fine on my old notebook Toshiba Satellite A60-712 and his led turn on regularly.
Before trying to install Tascam on PC i uninstalled M-Audio.
Please help.

 

Last edited: Nov 7, 2020

is the firewire port integrated or a controller? I came across a similar problem with a different audio interface some time ago... the Firewire PCI controller wasn't getting enough power to run properly... i solved it buyin' a new power supply...

 

don't you think that the reason is in these actions? I'm 99.9% sure of this.

 

I agree with @_mahsofabish . Though it seems the case; can you confirm you have a PCI to Firewire adapter and what model?
Also, I don't know about Firewire versions, but it could be your Firewire adapter implements an old version enough for one card but not for the other.

 

I disabled integrated firewire (was a bad Agere LSI-FW3227) and now works with Firewire Texas Instruments on own PCI bus; PSU is another bad ColorsIt 550W. But question is M-Audio FW Solo works on this system.ColorsIt is a brand with a not very good reputation, but I think 550W is enough for the whole system, Tascam including, also because the soundboard run on laptop with much smaller specifications.

 

Last edited: Nov 7, 2020

Yes i think, but what? The other M-Audio soundboard firewire powered is working fine on this PC, but now i need Adat from my Tascam FW-1804. I disabled services related net (this pc is full offline), indexing, secondary acces, remote system and similar ...

 

Last edited: Nov 7, 2020

I looked for information about the card ...
long ago discontinued and not supported by the manufacturer.
the latest drivers from 2010, despite the declared support for windows 7, many do not work on this OS.
not even recognized by the system as an unknown device.
but at the same time, if it works, then more often with texas instruments chipsets (for example f-330).

 

if the BIOS has pci / firewire settings, then start with them, and also check the power settings.

 

PCI by Kalea Informatique with FireWire IEEE1394b FireWire 800 & 400, chipset Texas Instruments xi02213b (obviously i connect to FW 400).

 

Last edited: Nov 7, 2020

On this PC i works with Win XP SP3, old pc for old os for old apps for an old man

 

I understand.
in this case are you sure this card is fully working?

 

so I assume that you are powering it via the molex connector, right?
The interface per se should not be a problem (considering the fact that it works on your other setup), it's rock solid. I know people that still prefers it over more recent/decent alternatives and runs it on some top of the line audio setups.

 

Last edited by a moderator: Nov 8, 2020

Could have something to do with PNP and driver loading.

If you say the PCI FW works with the M-Audio interface on the same connector then the card itself is probably working fine. You could always check to make sure with something like PCI-Z.

If you installed the M-Audio card before you disabled services it would have gotten registered by windows PNP service already.

FW was a great bus for audio, much better clocking than USB2, I hope you find the solution.

PS.

If you are comfortable in linux you can also lspci off a bootable usb key, and hot plug your device in and out to see if you are getting a good connection. You could probably even boot a full fresh Win XP off a removable disk and see if the culprit is the hardware or a snag in settings.

I have a feeling that it is the Windows Universal Plug and Play Service (uPNP) some drivers from hotswap device drivers don't actually install until uPNP detects them. Look in Windows Device Manager when the card is plugged in, if you see an unrecognized device with matching name and description you might be able to force register the drivers from there.

1. Open the Run dialog box: press & hold the Windows key, then press the R key.
   
2. Type devmgmt. msc
   
3. Click OK

 

Last edited: Nov 8, 2020

Yes, via Molex!

 

in Windows Device Manager i don't see any unrecognized device, also because driver install don't goes, my Tascam it's as if it wasn't there ...

 

If you don't see it on a pci bus scan with lspci as an attached device @ the pci root where the card is, then you know you have a hardware issue between the card and the interface and your search for an answer is over.

I think pci-z does the same thing as lspci on windows but I've never personally used it, either way if you don't see your interface on a report from a bus scan then your pci card isn't seeing your interface.

If your driver doesn't install and register, programs will not see the device even if the operating system hardware discovery subsystem does. They are not the same thing. You can run a program to place your driver on the disk, but with hotswap devices that is not the same thing as 'installing the driver' you are just making it available for uPNP to install when it discovers a device.

 

Last edited: Nov 8, 2020

Have you tried these things?:
1. Find other versions of the software installer and try those.
2. Uninstall the software and plug in the Tascam without their proprietary software installed. I have a presonus F/W box
and it windows would see and use it just fine natively, but I didn't have as much control as with installing the presonus software/drivers.
3. A maybe idea. But, have you tried putting the firewire card in a different PCI lane on the motherboard?

The issue is definitely happening between the PCi F/W card and your audiobox. Try searching queries from that specific angle with your specific model or at least make. Hardware issues are rarely a singularity, unless of course there's extreme pilot error.

Seriously though, the very first thing you mention is the software didn't install correctly, plus that it's the latest version. You don't need the latest drivers just one that works. You have yet to address that issue.

 

Tried everything, I give up. Either it is an incompatibility with the PCI firewire chipset (which is also TI) or the sound card is gone (it starts to give problems even on the laptop where it used to work).
I'll look for a good technician to get it checked but it's hard to find.
Thanks people