2007-01-17, 08:50 PM
I've had multiple Hauppauge cards and it always takes them a while to get stable drivers and software. This is the reason I went to GB-PVR.
The only things I've installed for the PVR-350 is the base driver, the middlewear update, and the IR software although I have WinXP. I don't install anything from the CD.
http://www.hauppauge.com/pages/support/s...0-350.html
The drivers I'm using are from the link above and I follow the directions for "WinTV-PVR-350 driver version 1.18 and middleware version 2.2." I do the HCWCLEAR util and reboot. Once the system reboots, point it to where you've extracted the base driver once windows finds the 350 as 'new hardware.' Then I run the middleware update.
Since I exclusively use GB-PVR, I just install the IR software and run the fix in the GB-PVR config app. But I have seen users run GB-PVR without the IR software.
The only time I get the 'failed to initialize remote' is when I remove the drivers or when I tried to force the system to use use other drivers. The other possibility is that something flaked-out on the card itself.
The only things I've installed for the PVR-350 is the base driver, the middlewear update, and the IR software although I have WinXP. I don't install anything from the CD.
http://www.hauppauge.com/pages/support/s...0-350.html
The drivers I'm using are from the link above and I follow the directions for "WinTV-PVR-350 driver version 1.18 and middleware version 2.2." I do the HCWCLEAR util and reboot. Once the system reboots, point it to where you've extracted the base driver once windows finds the 350 as 'new hardware.' Then I run the middleware update.
Since I exclusively use GB-PVR, I just install the IR software and run the fix in the GB-PVR config app. But I have seen users run GB-PVR without the IR software.
The only time I get the 'failed to initialize remote' is when I remove the drivers or when I tried to force the system to use use other drivers. The other possibility is that something flaked-out on the card itself.