![]() |
|
|||||||
| Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||
|
||||
|
one of my 250's gone???
I have two pvr-250's in my system and they both show up in device manager as working properly, however, a couple of days ago Sage had a crash (first one in months) and after rebooting the pc only 1 of the pvr-250's show up in Sage, both still show up in device manager. I can't even add the other through the setup wizard. This is not a huge deal since I have 4 other tuners and I do not see any conflicts. But I was wondering if anybody else has run into a similar situation.
__________________
If this doesn't work right, Then: "I'm going to blow up the Earth!" |
|
#2
|
||||
|
||||
|
The first thing I would check if some hardware suddenly disappears from SageTV after some problem occurs, is to see if the tuner is listed on the mmc/ignore_encoders property line in the properties file. This has been reported to happen in the past, though I don't know why it does.
- Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
|
#3
|
||||
|
||||
|
Once again I bow to your feet....
It was indeed on the ignore encoder list in the properties file. All is well now Thanx Andy
__________________
If this doesn't work right, Then: "I'm going to blow up the Earth!" |
|
#4
|
||||
|
||||
|
I had this same problem last night. But I reinstalled some VIA IDE drivers to try to fix some performance problems and Sage started ignoring my 250 but not my 150. Both showed up in the device manager. The 250 was set to be ignored in sage.properties, however, even removing it from there did not fix the problem (shutting down sage and saving the properties file). I reinstalled the PVR drivers/cards a few times, then reinstalled Sage but to no avail.
I physically removed the 150, switched the slot of the 250 and it was still not recognized. Then I moved the 250 back to its original slot and Sage recognized it. Then, I physically reinstalled the 150 and both were recognized. This was very understandably very frustrating. I highly suspect that my problem stems from my cheap VIA based mother board (PM800). I will never get another VIA chipset again. Hopefully this helps someone else having problems. |
|
#5
|
|||
|
|||
|
I have had the same problem with sage not recognizing one of my 2 pvr-250 MCE cards although device manager says both are working correctly. The sage properties file is set to ignore one of my 250's, but I cannot delete the entry, it keeps reappearing no matter what I do.
|
|
#6
|
||||
|
||||
|
That's because you need to completely shut down sage (both sage the program and sage the service if you have that running) before making changes to the properties file. Otherwise sage ignores any changes you make.
|
|
#7
|
||||
|
||||
|
Ok...I had the same disapearing pvr problem again. However, I noticed that when I totally shut sage down, the wintv2000 program that came with the card gave me an htv=0 error. Since both cards showed up in the device manager, I thought this was strange. I did some searching and found this thread:
http://www.hauppauge.co.uk/board/showthread.php?p=1432 These people have had the same problem and they all seem to have Raid controllers with Silicon Image SiI 3112 SATARaid Controller chipset. I believe I have a raid 0 setup, since my SATA is treated like a raid drive, but I'm not sure if I have this exact chipset. Anyway, their solution was a registry edit that changed the PRV drivers to start at "boot" instead of automatically. Specifically, the registry change is: "In regedit, go to this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\hcwPVRP2 Change the value "Start" from "3" to "0". " I tried this, and after rebooting several times, Sage still seems to recognize both of my cards. |
|
#8
|
|||
|
|||
|
So what do ya know...I have Silicon Image SATARaid as well...
I will try the fix. THANK YOU!! |
|
#9
|
||||
|
||||
|
Just be careful (i.e. you might want to backup the registry)...it has the potential to crash your system. In which case you can always revert to the last known good configuration in XP by hitting F8 on boot (I think it's F8).
|
|
#10
|
||||
|
||||
|
Interesting...according to my motherboard manual, I have a Via VT8237 Southbridge chipset that controls my RAID drives, not the Silicon Image. I wonder if it's more than just the chipset, but maybe a RAID configuration setting in the bios that interferes.
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|