Hi there,
I thought I would share this with the rest of you because I almost threw out my TV Card believing it was DEAD.
Basically, after trying some different types of TV software, I found that my TV card (TwinHan V3021) was no longer recognised by any Driver (DBD or WDM) - although the device manager showed two devices for the tuner and capture devices with yellow excalamation marks after them.
As the Card was no longer usable, I put it in the bin and went out and purchased a brand new TwinHan Mini Ter Card (V3020C) which I put in my HTPC and went on my merry way.
By chance, while looking for drivers to improve my TV capture performance, I stumbed accross this posts:
http://forums.dvbowners.com/index.php?showtopic=1482&hl=
(make sure you check out the 2nd page!)
Basically, it's believed that one of the TV Software Programs actually believes the TwinHan card is something it's not and corrupts it's eeprom (probably Chris TV?).
This renders the card useless....
LUCKILY, it was not yet Garbage day and I retrieved what I thought was a faulty card out of the bin.
I followed the posts instructions, it worked !!!!
And I ended up with a working card again! So now I have two - and I'm a little cheezed off for having to buy a 2nd card, but now I guess I can try out MP with 2 cards.
Anway, incase this gets lost in the bowels of the other forum, here's a duplicate of the information...
*** NOTE this was done on a TwinHanDTV Ter VP-3021 and I am unaware if it works with other cards ***
Download e2prom.exe from http://users.panafonet.gr/scratched/e2prom.zip
run e2prom.exe, and confirm that you eeprom is corrupt by checking it against the following:
� 00:� 05 00 00 00 00 00 FB FF-FF FF FF FF FF FF FF FF
� 10:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 20:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 30:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 40:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 50:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 60:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 70:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 80:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 90:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� A0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� B0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� C0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� D0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� E0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� F0:� FF FF FF FF FF FF FF FF-FF FF FF FF 00 01 18 22
If it's different, then it's likely it's corrupt.
Use the 'e2prom.exe -?' to get the instructions on how to change each setting to match the above eeprom dump.
E.g., if I wanted to change the very first piece of data and the very last piece of data to the correct values the instructions would be:
e2prom.exe 00=05 FF=22
Once you've corrected the eeprom, reboot and the card hopefully will work as normal.
Anyway, hope this helps some poor soles out there...
BTW... general disclaimers apply blah blah blah.
ALSO!! Thanks to the original posters of the issue who worked out the fix!!!
Cheers
Matt.
I thought I would share this with the rest of you because I almost threw out my TV Card believing it was DEAD.
Basically, after trying some different types of TV software, I found that my TV card (TwinHan V3021) was no longer recognised by any Driver (DBD or WDM) - although the device manager showed two devices for the tuner and capture devices with yellow excalamation marks after them.
As the Card was no longer usable, I put it in the bin and went out and purchased a brand new TwinHan Mini Ter Card (V3020C) which I put in my HTPC and went on my merry way.
By chance, while looking for drivers to improve my TV capture performance, I stumbed accross this posts:
http://forums.dvbowners.com/index.php?showtopic=1482&hl=
(make sure you check out the 2nd page!)
Basically, it's believed that one of the TV Software Programs actually believes the TwinHan card is something it's not and corrupts it's eeprom (probably Chris TV?).
This renders the card useless....
LUCKILY, it was not yet Garbage day and I retrieved what I thought was a faulty card out of the bin.
I followed the posts instructions, it worked !!!!
And I ended up with a working card again! So now I have two - and I'm a little cheezed off for having to buy a 2nd card, but now I guess I can try out MP with 2 cards.
Anway, incase this gets lost in the bowels of the other forum, here's a duplicate of the information...
*** NOTE this was done on a TwinHanDTV Ter VP-3021 and I am unaware if it works with other cards ***
Download e2prom.exe from http://users.panafonet.gr/scratched/e2prom.zip
run e2prom.exe, and confirm that you eeprom is corrupt by checking it against the following:
� 00:� 05 00 00 00 00 00 FB FF-FF FF FF FF FF FF FF FF
� 10:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 20:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 30:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 40:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 50:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 60:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 70:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 80:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� 90:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� A0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� B0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� C0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� D0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� E0:� FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF FF
� F0:� FF FF FF FF FF FF FF FF-FF FF FF FF 00 01 18 22
If it's different, then it's likely it's corrupt.
Use the 'e2prom.exe -?' to get the instructions on how to change each setting to match the above eeprom dump.
E.g., if I wanted to change the very first piece of data and the very last piece of data to the correct values the instructions would be:
e2prom.exe 00=05 FF=22
Once you've corrected the eeprom, reboot and the card hopefully will work as normal.
Anyway, hope this helps some poor soles out there...
BTW... general disclaimers apply blah blah blah.
ALSO!! Thanks to the original posters of the issue who worked out the fix!!!
Cheers
Matt.