Look here IEEE 1394 problems can happen because of PCI
latency problems in VIA chipset motherboards.
http://www.georgebreese.com/net/software/
>-----Original Message-----
>I can't help but I do have the exact same problem.
Generic
>card w. VIA chipset, Gigabyte motherboard with Athlon
>1800. The hub is present in the device Mgr but absolutely
>no response. It used to work perfectly before the WinXP
>registry corrupted. I've sinced reinstalled XP & this is
>the only outstanding issue.
>
>Carl
>
>
>>-----Original Message-----
>>I am looking for understanding and solutions for my
>>problem in XP. I have recently upgraded to XP, and have
>>devoted a great amount of time trying to recognize and
>>configure my hardware and support issues with XP. One
of
>>my challenging issues is this:
>>
>>XP recognizes my firewire card as a NIC card, and sets
up
>>a network connection for it. the card hence is useless
>>and wont work. I have done the basics (another driver
by
>>diff manufac., take out and reinstall, remove, configure
>>in network, device manager, etc.) The card is a generic
>>card that came with the sytem that HP uses. The
>>motherboard is a AM37 by Mainboard with integrated ac97
>>sound, nic, and video. The proc is AMD athlon 2400+ 2g,
>>p4 platform. The firewire or ieee 1394 card is made by
>>Smart Modular Technologies, and subbed at times to
>>selectron company in CA. finding the actual driver for
>>that card is hell. The card is a 2+1 port. XP thinks
it
>>has a signiature driver that, although the root is
>>defined as a OHCI IEEE 1394, it sets up the device under
>>network cards.
>>
>>If anyone can help with this i would love it. XP wont
>>let me keep it uninstalled to change it anyway, it
>>reinstalls it automatically, i never put a driver in for
>>it.
>>
>>Thanks
>>Rob
>>.
>>
>.
>