Remote Control Dying?

[Trevor]

Have you tried putting new batteries in it? Seriously...I don't trust any batteries that come with any product that might have been sitting in a wharehouse for several months.

That was exactly my first thought, and the very first thing I tried. (Should have mentioned it, seems days ago now)

[Trevor]

Sorry Capone. I installed the drivers on the shspvr site (being careful to overwrite the existing files in C:\Windows\System32 and C:\Windows\System32\drivers\ where appropriate), and it seemed to work great for an hour or two and then suddenly, i'm back to freezing again.

Anyone else have any ideas?

[capone]

Actually, you need to do full uninstalls and cleans before reinstall.

I think this was the set I used, w/ instr:
http://www.shspvr.com/smf/index.php?topic=7843.0

But maybe it's not your issue anyway. Good luck.

[Trevor]

I got it I got it!

First of all, the problem is definately correlated with recording. You record with the PVR 150 and soon (immediately afterward?) the remote dies out.

Secondly, the drivers that come with the Hauppauge PVR 150 suck, and need to be replaced ASAP.

Third, I didn't realize that the file you linked to was actually to be installed during the reboot process "Install drivers from directory". I was dumb and tried to copy the flies to the right place. Didn't work.

Hauppauge has a cleaning app, that wipes out all existing drivers. Very useful.

There's actually a ***35 set of drivers instead of the ***25 drivers that everyone else has linked to.

You need exactly:

1) Hauppauge's cleaning program (avaliable on their site)
2) The zip file you linked to (or the ***35 version in the same ftp directory)
3) The Remote IR drivers from the Hauppauge site.

And then you do the following in this order:
1) Unzip the zip file to the desktop
2) Run the cleaning program and reboot
3) When the machine reboots and finds the card, use the drivers from the zip file you just extracted. DO NOT USE the drivers on the disk, or those offered on the official Hauppauge site!!!!
4) Install the IR software
5) Run GB-PVR Config again, select the Hauppauge 45 button remote fix and save.
6) Restart IR from the Hauppage tools menu.
7) Run GB-PVR

I did a clean clean install, no WinTV at all, just GB-PVR and the IR. And after a night of recording, the Remote is still working!

I'm going to make a nice clean post with links and everything for all those poor new PVR150 users who are struggling to keep their remote working. (Perhaps worth a sticky? But first I need the PVR computer... the kids are watching Kim Possible right now.

Quick question, is there a difference between the ***25 and ***35 version drivers?

[Trevor]

OK, more links:

Released drivers here: ftp://ftp.shspvr.com/download/wintv-pvr_150-500/inf/
Prerelease drivers here: ftp://ftp.shspvr.com/download/wintv-pvr_...rerelease/

It looks as if the most recent release driver is pvr_2.0.24.23035.zip (unlike 23025, which you've referred to before). I actually found the 23035 release on some other forum (perhaps the UK Hauppauge support forum, where there was a HUGE discussion on the remote breaking)

Hmm, release notes don't say too much for the 23035 version:

Driver Release 2.0.24.23035.PreRelease (02/03/05)
* Testing I2C (IRBlaster) fixes.

Driver Release 2.0.24.23034.PreRelease (02/03/05)
* Wolfson overrideable through registry.

It also looks like theres a newer pre-release driver than you mention. Not sure if it's worth upgrading. Looks like you'd get the following:

Driver Release 2.0.30.23123.PreRelease (05/03/05)
* Additional finetuning to balance Line-In / FM / TV Volumes.

Driver Release 2.0.30.23117.PreRelease (04/27/05)
* Initial Fix for somewhat rare but possible system hang on MCE Auto Tuner Setup.
* Line-In and FM are much closer to TV Volumes and ALC is NOT in use.
* Potential Bluescreen/Hang on driver unload fixed.

Driver Release 2.0.30.23097.PreRelease (04/07/05)
* Internal Production-Level Support/Control for PCIConfig Space.

[capone]

The 2.0.30.23083 drivers I use are non-pre (read down the post, and someone explains it's just in the file name), and most importantly worked. I didn't have the other problems mentioned in the other drivers, so I opted to be happy w/ things working right, then being current for the sake of it.

When they add new drivers that add to overall quality, I'll bump up again. In the meantime, I learned long ago w/ upgrades and new drivers, don't get greedy.