HD PVR version 1.0.5.301 whql

[trini0]

I've never had any problems with crashing, but I do have *lots* of recording anomolies. I'll try it and see, but I doubt it will improve my situation...

[Cooper]

About 3 weeks ago I covered my 2 HD PVR IR's with black tape and since doing so I have not had to restart the due to capture error's. Before doing this I had to restart both at least once a week.

I was reading about this on another fourm and figured to give it shot and worked for me.

[phelme]

Ugh. My HD-PVR seized up again last night while starting to record Stargate. It wouldn't be so bad except that it completely hoses the Sage service until the HD-PVR is power cycled. This happens about every 3-4 weeks for me (guess that makes me lucky). I'm assuming there's no addressing of this issue in the update. I'll have to get that digital timer after all.

[rerooks]

I wish that was my problem. Lately, I have to reboot my machines after the HD-PVRs quit working. Power cycling them doesn't work. Restarting Sage doesn't work. Sage can find them, so they haven't disappeard, but somehow they cannot record.

The biggest problems I have with Sage involve HD recording....but then, Sage doesn't have control over the HD-PVR. Even with this, there really is no other practical solution for HD recordings.

Originally Posted by phelme

Ugh. My HD-PVR seized up again last night while starting to record Stargate. It wouldn't be so bad except that it completely hoses the Sage service until the HD-PVR is power cycled. This happens about every 3-4 weeks for me (guess that makes me lucky). I'm assuming there's no addressing of this issue in the update. I'll have to get that digital timer after all.

[trini0]

Originally Posted by trini0

I've never had any problems with crashing, but I do have *lots* of recording anomolies. I'll try it and see, but I doubt it will improve my situation...

I'm still having my recording anomilies. As far as I'm concerned, I think Sage is the culprit in my case...

[OldPCGUY]

My HD-PVR will lock up after my Dish VIP611 does a program update. It turns off the output until the 'select' button on the Dish remote is pressed.

After some time of not receiving a signal the HD-PVR will lock up causing Sage to lock up.

The Solution I have employed to solve this involves the following.

A) HD-PVR and DISH VIP612 in back of room next to server. HD-200 in front of room next to HDTV.
B) USBIRT IR blaser is taped to front of VIP-612 (not using HD-PVR blaster)
C)Using ShadeBlue STkeepalive - Works with USBIRT and sends 'select' IR code to VIP-612 every 4 hours and at 3:30am after program update.

This is a very stable setup but if you are running Windows XP then you need to make your OS stable also. Dumping MacAfee was big plus in system stability. I went with Clam Antivirus, Windows Defender, and IOBit Care.

So everything was running for weeks at a time and occasionallly my PC will hang up. Impossible (for me) to track down when it only happens once a month and I don't have the expertise to interpret Window's cryptic messages.

I recently allowed Windows Updater to update my OS. After this happened I started getting RAID access failures on all three RAID arrays. I had to go back to a March 15 Image and this problem dissappeared.

[sic0048]

I don't think your PVR is locking up. It is just that the DTB goes to sleep after getting an update. So you see the Dish screen saver until you press "Select" on the remote. This wakes the STB back up and causes it to start broadcasting again.

Some STBs use to have an option to turn off the automatic updates, but Dish is removing this option from all their STBs. That being said, there should still be an option to turn the sleep (or timeout) function of the STB. You want to make sure this setting is set to "Never". I have a 211k, so I'm not familar with your exact box, but it probably has something similar.

You can continue to use the program you have set up to send out a signal every 4 hours or you can use a timer on the STB. One of the menu options is to set a timer on the box. You can set it to tune to a specfic channel automatically at a specific time. So if your update occurs at 3:30am, then set a timer to tune to channel 120 at 3:55am for example. This will cause the STB to wake up, and if you have turned off the sleep function, it will stay active until 3:30am the next day when it automatically updates itself.

So this is just another option to what you are doing, but it is self contained in the STB (ie the box is responsible for the timer function, not the Sage software).

[Installman]

Anyone know where to get a copy of this driver? I'm using the very latest and am having nothing but issues. Tried both links and of course the HP one has the latest and the other requires a user name and password.

Thanks in advance

[jerryt]

Originally Posted by Installman

Anyone know where to get a copy of this driver? I'm using the very latest and am having nothing but issues. Tried both links and of course the HP one has the latest and the other requires a user name and password.

Thanks in advance

http://www.shspvr.com/ftp/download/wintv-hdpvr/

[Installman]

Thank You!!

[sic0048]

I don't know why these drivers work so well and the newer drivers work so poorly. Since switching back to this verison of the driver my HD-PVR system has been very stable. It has been about 10 days since I switched back. I was locking up about once per day on the newer drivers, but haven't had any lockups since going back to the .301 version.

[gibsonpa]

I have been using the .301 driver for many months...and have only one time a lockup happened. They seem to be near perfect on my system.

Also, I have 2 1600 cards...and recently had windows update to the latest driver (windows update)...and those cards started having lots of issues. Went back to the older driver (from 2007 believe it or not)...and the 1600's are now perfect.

Seems like the latest drivers from hauppauge are not always the best...at least for my setup.

[jerryt]

I also have zero lockups with these 1.0.5.301 drivers whereas all the other drivers gave me lockups.

Won't this suggest that the lockups are driver related and that Hauppauge should investigate why this driver has been so lockup free?

[SHS]

Originally Posted by jerryt

I also have zero lockups with these 1.0.5.301 drivers whereas all the other drivers gave me lockups.

Won't this suggest that the lockups are driver related and that Hauppauge should investigate why this driver has been so lockup free?

If that where ture case then ever one would have lockup but not the case now is jerryt when min of us are running v1.5.6.1 whql

[eric3a]

Don't want to be all King Solomon on both of you, but I think you're both right. Lock-ups are likely driver related, but that's not an indication that either 1.0.5.301 or 1.5.6.1 is better than the other one.

I think a lot of the lock up issues are driver related, with some drivers working for some, and some drivers working for others depending on their PC and HD receiver configuration.

If you get the right driver (properly installed) for your configuration, you get no (or extremely rare) lock-ups.
Eric

[Taddeusz]

I'm currently using the 1.5.6.1 driver. From my experience HDPVR stability has more to do with the source than anything else. I've had more trouble with my STB causing a cascading failure or just causing weird recordings, mostly no audio. I should probably trade my STB in for a different one. But, as far as my HDPVR itself, it's been pretty stable and required no intervention in the last few weeks that I can recall. Only my STB has needed attention.