Knocked Out Hauppauge Capture Card--WinTV

[W. eWatson]

I have a feeling that I damaged a WinTV card (Subject) today when I
plugged in a video device and the card popped up out of its slot. It's
possible I'm missing something else, a connection, but how would I know
it's not a h/w problem from the OS? Using System->Devices reveals nothing.

 

[Paul]

I have a feeling that I damaged a WinTV card (Subject) today when I
plugged in a video device and the card popped up out of its slot. It's
possible I'm missing something else, a connection, but how would I know
it's not a h/w problem from the OS? Using System->Devices reveals nothing.

Download Everest Home Edition.

http://majorgeeks.com/download4181.html

Go to DevicesCI Devices.

If the card is not being enumerated properly, you'd see
an "unknown" card type shown. Check all the entries listed,
and by the process of elimination, you may be able to tell
whether the card is showing up or not.

If the card is not enumerated in any way, it could be cooked.

If all the PCI devices are missing, then it could be the
interface on the Southbridge is damaged. But that would likely
have led to some complaints from the BIOS during POST.

Paul

 

[W. eWatson]

Download Everest Home Edition.

http://majorgeeks.com/download4181.html

Go to DevicesCI Devices.

If the card is not being enumerated properly, you'd see
an "unknown" card type shown. Check all the entries listed,
and by the process of elimination, you may be able to tell
whether the card is showing up or not.

If the card is not enumerated in any way, it could be cooked.

If all the PCI devices are missing, then it could be the
interface on the Southbridge is damaged. But that would likely
have led to some complaints from the BIOS during POST.

Paul

Thanks. I have Everest on this PC, and will bring it up on the other PC.
I think it's toast, but will call Hauppauge in the morning. One of my
video program reports its disappearance.

 

[Cari \(MS-MVP\)]

Have you tried physically removing the card and then replacing it...
preferably with a reboot in between?

i.e. Turn off PC, remove card, startup PC, turn off PC, reinserting card,
turning on PC.

 

[W. eWatson]

Have you tried physically removing the card and then replacing it...
preferably with a reboot in between?

i.e. Turn off PC, remove card, startup PC, turn off PC, reinserting
card, turning on PC.

Several times. However, I have not removed the card completely. Just
pushed it back in place.

 

[W. eWatson]

Download Everest Home Edition.

http://majorgeeks.com/download4181.html

Go to DevicesCI Devices.

If the card is not being enumerated properly, you'd see
an "unknown" card type shown. Check all the entries listed,
and by the process of elimination, you may be able to tell
whether the card is showing up or not.

If the card is not enumerated in any way, it could be cooked.

If all the PCI devices are missing, then it could be the
interface on the Southbridge is damaged. But that would likely
have led to some complaints from the BIOS during POST.

Paul

Oddly, I found references to BrookTree WinTV. There were maybe 6-8
devices of sort other another shown. No messages that suggested anything
was wrong.

 

[Paul]

Oddly, I found references to BrookTree WinTV. There were maybe 6-8
devices of sort other another shown. No messages that suggested anything
was wrong.

The free version of Everest is a few years old now, so it won't be
able to identify everything. Using vendor and device hex codes,
you can figure out any unknown ones, using the pci.ids file.
(This file is not "official" in any sense, so plenty of parts are
missing.)

http://pciids.sourceforge.net/pci.ids

Your card could have a BT848 or BT878 on it. Or the chip might
be newer, and be branded with Conexant printed on it. So you'd have
to check in the pci.ids file, under Brooktree, Conexant, or Hauppauge
and see what you can find.

If the chip can still be enumerated, then it may be working. The question
then would be, what is broken with respect to drivers or whatever.

Paul

 

[W. eWatson]

The free version of Everest is a few years old now, so it won't be
able to identify everything. Using vendor and device hex codes,
you can figure out any unknown ones, using the pci.ids file.
(This file is not "official" in any sense, so plenty of parts are
missing.)

http://pciids.sourceforge.net/pci.ids

Your card could have a BT848 or BT878 on it. Or the chip might
be newer, and be branded with Conexant printed on it. So you'd have
to check in the pci.ids file, under Brooktree, Conexant, or Hauppauge
and see what you can find.

If the chip can still be enumerated, then it may be working. The question
then would be, what is broken with respect to drivers or whatever.

Paul

Thanks for the info. It turns out that when the card popped up, it froze
the machine. I had to power it off. Apparently, that tangled up the
Haupaugge s/w. I re-installed it and it still didn't work; however, I
finally found another culprit a detached A/C plug inside the tube that
holds the camera in place. Before I did that I discovered the s/w
re-install did fix it though. I tried it on yet another camera with
success.

 

[W. eWatson]

Thanks for the info. It turns out that when the card popped up, it froze
the machine. I had to power it off. Apparently, that tangled up the
Haupaugge s/w. I re-installed it and it still didn't work; however, I
finally found another culprit a detached A/C plug inside the tube that
holds the camera in place. Before I did that I discovered the s/w
re-install did fix it though. I tried it on yet another camera with
success.

Just to close this out. The capture card was WinTV Plus GO. Details are
under the Hauppague web site under analog capture devices.