Winfast TV 2000 Deluxe: Closed Captioning and other things

[dexterous1]

I've got some problems with my Winfast TV2000 Deluxe.

1) When I decide to use closed captioning I get a weird colorful ring on a black back drop that takes the place of my TV Channel that I'm watching for about a second, and then the TV Channel comes back in a funky monochromatic green color w/ closed captioning. My problem is that I do not want that monochromatic green on my TV. When I turn off closed captioning, everything resumes to normal.

2) For the life of me I cannot get the FM thing to work. Everytime I try, it freezes up with "wffm causing an error in mfc42.dll". I've had problems with that dll before when using PrintShop v. 10, but it's a common problem that has an easy fix by deleting an *.ini file for that program. But, this seems to be a little more difficult than that.

Here's what I've done to try to rectify the problem.

a) 2 reinstalls of the whole software on the CD.
b) Straight installs from the updated drivers on Leadtek's site.
c) Re-inserting the card on the PCI slots.
d) Installing with the old software and then updating the old software with the new drivers from Leadtek's site.
e) Updating the drivers on the video card

Here's my setup.

OS: WinME
My video card is an Nvidia GeForce 2 MMX.
PIII 1GHz
128MB RAM

The Winfast TV 2000 Deluxe card is hooked up to a VCR that has a regular TV antennae hooked up.

All in all I think this is a GREAT card. Even with these little quirks that I have with it. My sound is great, my recording is superb.

Thanks for any help!

[no1_vern]

Welcome to Techimo!
The first thing that comes to mind is did you try a DIFFERENT PCI slot when you reseated the card?

Can you post exactly what the message says? I couldnt find anything going on the information you gave me.

[dexterous1]

Yes, I have tried a different PCI slot. The error message I get with the FM program is:

"Wffm has caused an error in MFC42.DLL
Wffm will now close.

If you continue to experience problems, try restarting your computer"

And I've restarted, again, and again, and again...

[dexterous1]

Oh yeah, I forgot. After switching PCI slots, I still have problems with closed captioning.

[rockpile]

The first thing you need to do is get rid of the drivers that came with it and goto (ftp://ftp1.leadtek.com/tv_tuner/TV2000XP/Driver/030130/)

Download these drivers and all will be well

[dexterous1]

Thanks for the help rockpile, but I tried the new drivers you recommended and I still get the same results with bad closed captioning and no FM.

When I installed the new drivers, I first removed the old ones, uninstalled all Winfast stuff, and removed the TV card.

I then reinstalled the card and let it soak up all of the new drivers. Then I tried the closed captioning, and then the FM. I got the same exact errors.

Keep the suggestions coming, though. I really appreciate the help.

I e-mailed tech support on Monday, and am still waiting for a response. I've tried googling for my problem and I have seen people give up on the FM, but it seems that no one has had the closed captioning problems. As for the FM, I haven't seen any body describe the error I have either.

Hopefully something will come up.

Again, thanks everyone for taking time out of your day/night to help me out.

[dexterous1]

Ok, this case is closed. I got Tech Support to get back to me, and well...here's the story.

The Closed Captioning problem is due to a bug in software, it'll be fixed in one of their updates. They told me to keep an eye out for their update that fixes this problem.

They assumed that the problem with my wffm problem was due to a corrupt *.dll, so they sent me a new one. I downloaded it, installed it, and deleted the old one. And guess what? I DID NOT WORK!!!!

So, while I was at work today, I heard that my 10 month old son got a hold of the remote control. The computer was tuned in to regular TV, while my son chomped on the Video button twice to get to the S-Video display.

Then he chomped on the TV/FM button to toggle to the FM program. BINGO! FM worked. So, to sum it up, go through the same button sequence as my son to rectify the problem if it's similar to mine. Biting the buttons is optional.

-dex