no ti firewire x64

I have an nforce based motherboard (ASUS A8N32SLI) and thought I'd give the latest WVx64 a shot as WVx32 didn't recognize my U3 USB drives, doesn't have support yet for SPDIF out for the Realtek 850, and doesn't support the SIL 3132 controller all of which I'm sure will be forthcoming. But it seems I've taken a step backwards as there is no longer recognition of my TI 1394 chip. I would at least think there might be a placeholder for an unknown device in device manager, but no. Rerunning the hardware probe comes up with nothing. I haven't looked at the registry for the appropriate vendor/device ID string but I suspect it won't be there if it isn't in device manager.
Has anybody else run across the same problem with this chipset or had the opposite experience? Dropping in my XP hard drive shows everything to still be working and happy. I can't attest to XPx64 as I do not have a copy, if anyone should ask, but it might be nice to know if all of these devices are supported there equally as well as I would return in the end to WVx32 if they weren't. -- Brad

I don't have an ASUS Mobo but my onboard TI 1394 chips were recognized and the appropriate drivers installed. I also have a Unibrain Fireboard 800 installed that was recognized and installed. This happened for both V32 and V64.
"Brad" wrote in message

I have an nforce based motherboard (ASUS A8N32SLI) and thought I'd give the latest WVx64 a shot as WVx32 didn't recognize my U3 USB drives, doesn't have support yet for SPDIF out for the Realtek 850, and doesn't support the SIL 3132 controller all of which I'm sure will be forthcoming. But it seems I've taken a step backwards as there is no longer recognition of my TI 1394 chip. I would at least think there might be a placeholder for an unknown device in device manager, but no. Rerunning the hardware probe comes up with nothing. I haven't looked at the registry for the appropriate vendor/device ID string but I suspect it won't be there if it isn't in device manager.
Has anybody else run across the same problem with this chipset or had the opposite experience? Dropping in my XP hard drive shows everything to still be working and happy. I can't attest to XPx64 as I do not have a copy, if anyone should ask, but it might be nice to know if all of these devices are supported there equally as well as I would return in the end to WVx32 if they weren't. -- Brad

Har har. Will wonders never cease? Disregard my post as to this particular device as the camera cable broke off inside the connector. WVx64 now recognizes it just fine.
b