Hauppauge HVR1600

[sub]

I re-installed GBPVR and reconfigured the Capture Sources. Setup "HVR 1600 Analog", "ATI AIW Radeon with Software Recorder" plugin and "HVR 1600 ATSC", in that order.

Things were working great until this past weekend till GBPVR did an update of the EPG. When it updated the EPG, noticed the channel list under "AIW Radeon" and "HVR 1600 ATSC" sources keep adding duplicate entries while channel list under "HVR 1600 Analog" does not change. Subsequently, when I try to run GBPVR and open TV Guide, it says TV Guide not setup (or something to that effect).

Zip and attach the logs and I'll take a look.

Could this be due to the problem described here

No, that only happened if you using the 'DVB EPG' option on your capture source.

Also, noticed Hauppauge released a version of their software for the HVR 1600with QAM support. I have model 74021 of the card which Hauppauge says should be supported. Not sure if it would work with W2K SP4 tho', either with the next release of GB-PVR next version or Hauppauge's own software?

If Hauppauge's beta software won't work w/ W2K, can the existing W2K drivers be 'tweaked' to make QAM work with GB-PVR's next release on W2K. I've seen other drivers that list WinXP and not W2K, but these drivers do work with W2K (even if some of them require some 'tweaking' of ini files, etc) due to the similar architecture of these operating systems. Not sure if this applies to HVR-1600 drivers used by GB-PVR, tho'?

In short, would appreciate any thoughts on HVR-1600 w/ QAM on W2K and if it can or cannot work?

I intend to add HVR-1600 QAM support in the next release. I cant answer you question about drivers on W2K. Basically GB-PVR would need your machine to have installed the drivers that offer QAM support for it to be possible.

[topperdude]

Zip and attach the logs and I'll take a look.

Thanks, sub - will attach the logs later today.

I intend to add HVR-1600 QAM support in the next release. I cant answer you question about drivers on W2K. Basically GB-PVR would need your machine to have installed the drivers that offer QAM support for it to be possible.

I remember the unsupported W2K drivers were installed from a folder Driver18. I just downloaded the Beta CD w/QAM and noticed the hcw18bda.sys file under Drivers/Driver18 (as well as some other files in that folder) were updated on 05/10, presumably with the QAM changes. I'm hoping I can continue to install the drivers from the new \Driver18 folder and use it on W2K (may try it when I get a chance). Perhaps someone else (zaphod7501 or any other member with HVR1600 on W2K) can chime in on this if they have already tried the QAM drivers on W2K.

Thanks,
-Topper

[DillPickle]

Probably tired of hearing this but, "You ROCK!" For those in the U.S. The 1600 is back on sale @ Circuit City for $70 after MIR.

I intend to add HVR-1600 QAM support in the next release. I cant answer you question about drivers on W2K. Basically GB-PVR would need your machine to have installed the drivers that offer QAM support for it to be possible.

[zaphod7501]

Perhaps someone else (zaphod7501 or any other member with HVR1600 on W2K) can chime in on this if they have already tried the QAM drivers on W2K.

"shs" indicated that the Hauppauge software will not work for QAM under Win2000 because of drivers. I have not given up completely yet but testing will have to be with third party applications, like GB-PVR.

The hcw18bda.sys is usually the stumbling block with Win2k. If you install it, then Windows may bluescreen with a ROM error at startup and you will have to start in safe mode and copy the old version back into the system32 directory. I don't know the method of startup, but those .rom files sure look like firmware to me, with hcw18bda.sys loading them. (I could be wrong, very wrong ) I plan on a mixed driver mode to begin with. The old hcw18bda.sys and the rest of the files new. That's what I do right now, anyway.

[topperdude]

Zip and attach the logs and I'll take a look.

Have attached the logs and couple screenshots.

Thanks,
-Topper

[sub]

That 'database disk image is malformed' error looks pretty serious. To me it sounds like your database is corrupt. Try deleting the gbpvr.db3 and copying empty.db3 to gbpvr.db3 - effectively starting again from a clean database.

[topperdude]

That 'database disk image is malformed' error looks pretty serious. To me it sounds like your database is corrupt. Try deleting the gbpvr.db3 and copying empty.db3 to gbpvr.db3 - effectively starting again from a clean database.

That's surprizing. Not sure why the database keeps getting corrupt on my PC. I just did a
re-install less than a week ago. At that time also, it seemed like the database was corrupt.

The only change to the system was installing and configuring the HVR-1600 analog and digital capture sources about 10 days ago. Prior to that, with only the ATI AIW card w/ Software or Graph Recorder plugins, I didn't used to get such frequent database corruption issues. Perhaps I will try copying the empty.db3 and configuring only one capture source and see if that helps.

Any other thoughts to narrow down the issue and prevent it from happening again? Am I not configuring the EPG sources correctly? Each of the Capture sources has an EPG source defined, with the same zap2it account for both analog sources and a different zap2it with only OTA HD channels for the HVR-1600 digital source.

Thanks,
-Topper

[sub]

That's surprizing. Not sure why the database keeps getting corrupt on my PC. I just did a
re-install less than a week ago. At that time also, it seemed like the database was corrupt.

I've never seen this specific error myself, or any reports of it from other users, but it certainly reads like a corrupt database.

The only change to the system was installing and configuring the HVR-1600 analog and digital capture sources about 10 days ago. Prior to that, with only the ATI AIW card w/ Software or Graph Recorder plugins, I didn't used to get such frequent database corruption issues. Perhaps I will try copying the empty.db3 and configuring only one capture source and see if that helps.

Any other thoughts to narrow down the issue and prevent it from happening again?

I'd definitely try going without adding the recorder plugin for your ATI AIW for a while, in case its is what is causing this to happen.

Am I not configuring the EPG sources correctly? Each of the Capture sources has an EPG source defined, with the same zap2it account for both analog sources and a different zap2it with only OTA HD channels for the HVR-1600 digital source.

I dont think its anything like that, or we'd be having a lot more people reporting the same problem.

[topperdude]

I'd definitely try going without adding the recorder plugin for your ATI AIW for a while, in case its is what is causing this to happen.

I understand there are other people using the recorder plugin with natively supported cards, like the PVR-150, and find it strange that the recorder plugin would not work with the HVR 1600. I'm not sure, however, if there are any other members using the recorder plugin with HVR 1600 in particular, so I guess there's no other option than for me to try out few different things:
a) Try using only Recorder plugin for few days and see if the problem can be reproduced
b) Try configuring either one or both HVR 1600 capture sources and see if the problem can be reproduced.

Would it be possible for the combination of the capture cards with the OS that could be causing the corruption? I wonder if there might be a way to check if the OS might be responsible for this?

Another long shot, if it helps any, is my primary HDD is a 20GB HDD that now has only ~3GB free (after all the recordings). I just added a 200GB HDD that I plan to dedicate to the recording and free up some space on the primary HDD. Could the low (~3GB) disc space cause database corruption - I doubt it because I haven't seen the free space go down by much when the EPG Update is being performed, but just thought I'd throw it out.

Anyways, will try things out and report back.

Thanks,
-Topper

[sub]

a) Try using only Recorder plugin for few days and see if the problem can be reproduced
b) Try configuring either one or both HVR 1600 capture sources and see if the problem can be reproduced.

This plugin obvious a variable that is an unknown quantity to me, since I didnt develop it, and never used it. While we look into this, it'd be best to take this variable out of the equation. I would definitely recommend uninstalling this plugin for a few days (remove its DLL from the plugins directory), so that you're running only with supported cards.