Where can I find the Hauppauge 1.7.21177 drivers for 250/350 ?

[carlgar]

Originally posted by Gendalia
We just got a 250 to add to our 350. In the machine where the 350 works fine, adding the 250 causes it to not ever successfully complete booting win2k. This machine is a VIA chipset motherboard, with a celeron 766.

Are you aware of the "VIA 4-in-1 driver update will often fix compatibility problems with the WinTV" paragraph at the very bottom of
Hauppauge Driver Update Page ?

We borrowed my desktop box to put the 250 & 350 in to see what happens, and we see the initialization problems carlgar reports, with the 250's bottom third or so being blocky and the whole picture being awful. The 350's picture is perfect, but tvout fails in sage, although it works fine with wintv2000. Following carlgar's instructions for initialization makes the picture better with the 250. With both boards enabled, tvout will never work with sage, but tvout works fine with wintv2000, which I would agree makes that part a sage problem rather than a hauppauge problem. Disabling the 250 in hardware properties makes the 350 work just as it normally would in the current sage box.

Actually, I did get everything working properly as I mentioned in this post. However, I had to reboot my system less than 24 hours later and have not been able to dupicate. I believe I can duplicate getting the 350 TV out working with the bad 250 recording. I seem to lose the 350 TV when I try my initialization method. One thing that I have noticed that Frey needs to look at is the "Enable TV Out for PVR 350" option in the detailed setup. My experience shows that using the Apply is not enough. You need to restart SageTV. This may just need to be documented, but someone from Frey should address this issue.

[Gendalia]

Originally posted by carlgar
[B]Are you aware of the "VIA 4-in-1 driver update will often fix compatibility problems with the WinTV" paragraph at the very bottom of
Hauppauge Driver Update Page ?

I was not, thanks.
Even after installing the 4-in-1 driver update, windows wouldn't complete a boot with both cards in the machine, or even after taking one of the cards back out. We had to boot safe mode and delete the 350 from the device manager (we never had a chance to install a driver for the 250). Then we reinstalled the drivers, but sage didn't see a source, and we couldn't get it to see a source. We reinstalled sage, that didn't help, so we moved the sage directory to sage.old, reinstalled, copied wiz.bin & the video directory into the new install, and we were back in business with one 350.

[sudipto]

Gendalia: When Sage was not seeing the sources, you did NOT need to uninstall and re-install it. If it happens in the future, simply open the sage.properties file in text editor and find a line called "mmc/ignore_encoders=<list of encoders>". Once you find this line, delete the list of encoders (i.e. everything AFTER the "=" sign and save the file.

Oh BTW, you need to FIRST shutdown Sage before editing the sage.properties file and THEN edit and save the file and restart Sage. now you should be able to add the capture source(s) again.

This usually happens if you move the card(s) from one PCI slot to another.

[Gendalia]

That's good to know. In our experimentation with the VIA machine, we tried the 250 in every empty PCI slot, just to see if it mattered.

[sudipto]

I usually leave the PCI slot right next to the AGP slot empty, since in most boards that I have worked with, this first PCI slot shares IRQ with the AGP. In a 6 PCI slot mobo, I usually use the 4th and 6th for WinTV PVR cards.

Either way, once you have the cards all installed, it is good to go in Device Manager->View->Resources by Type and expand the IRQ group to see if there are any significant IRQ sharing going on; if so, it is worth re-arranging the cards or turning ACPI support OFF in the BIOS.

[Gendalia]

I tend to put the tuner cards as far away from the video card as possible, since video cards are classic generators of noise, and the tuners are susceptible to it.