1.0.16 available

[JavaWiz]

Hey there,

This is my first time posting on this forum, normally I just google all my questions, but this one has me totally stumped. I tried to update from GBPVR version 99.12 straight to 1.0.16, but even after installing and uninstalling the old version, whenever I attempt to install 1.0.16 I keep getting a 1904 error saying that the PsiParser.ax failed to register and to contact the support personnel. I'd appreciate some help on this one as I have been pulling out my hair on it.
Thanks

PS. I hope this is the right thread to ask this question on

You might try running the Re-RegisterFilters.bat file.

[mvallevand]

Hey there,

This is my first time posting on this forum, normally I just google all my questions, but this one has me totally stumped. I tried to update from GBPVR version 99.12 straight to 1.0.16, but even after installing and uninstalling the old version, whenever I attempt to install 1.0.16 I keep getting a 1904 error saying that the PsiParser.ax failed to register and to contact the support personnel. I'd appreciate some help on this one as I have been pulling out my hair on it.
Thanks

PS. I hope this is the right thread to ask this question on

If your reread carefully the first message in this thread you will see that you need to install a second file for the vc runtime. Searching PsiParser.ax on this forum should get you lots of hits too.

Martin

[MacStranger]

Thanks guys for the suggestions, but I already tried both of those things. I installed the vcredist_x86 and I tried re-registering the filters, but it just tells me that the LoadLibrary("PsiParser") failed. Would appreciate if anyone knows what to do about this.

Thanks

[MacStranger]

This is embarrasing!

I made a noobie's error. Never download a windows update file from anywhere other than microsoft website. The vcredist copy I picked up online was a dud. Thanks for trying to assist though.

I am mortified =)

[tcool93]

Why is is that everything made with open source/linux isn't user friendly. This program I never could install and still can't. Just way too much manual configuring.

[Pilot]

Why is is that everything made with open source/linux isn't user friendly. This program I never could install and still can't. Just way too much manual configuring.

Well, I think the problem may be your video card of choice. I'm using Hauppauge cards (two of them with three total tuners), and installing GBPVR was and is still a breeze.

Any problems I did encounter along the way were quickly resolved by either posting to or searching this forum. Most of the solutions came directly from the developer, after personally reviewing my error logs -- where are you going to get that kind of service and support from a commercial application? Will you even know who the developer is?

Setting up your own PVR is not an easy, one-click task. However, that being said, using the GBPVR software and this forum as resource (including direct access to the developer), I can honestly and seriously say that anyone should be able to get it up and working.

I suggest attempting the install again, and posting your specific questions and/or problems to the support forum here. You will get answers, you will get solutions, and in the end you will most assuredly get GBPVR up and working or you will know the reason(s) why you cannot.

[Daniel Bragg]

Wondering...
...Is there a thread specifically for SchedulesDirect issues?

What I'm encountering is thus:
Your EPG source does not appear to be configured correctly. Please check the EPG Source Settings and try again.
System.Net.WebException: The remote name could not be resolved: 'webservices.prod.schedulesdirect.tmsdatadirect.com'...

This is after I have applied the latest GBPVR, signed up for a new account through SchedulesDirect, erased all channels (all the ones I can -- there seems to still be a few "stuck" in Channels tab that I just can't seem to get rid of), in frustration, uninstalled and reinstalled GBPVR. I have installed the vcredist_x86 that I downloaded from this site (confirmed the MD5 sigs from both files).

OK, I just don't know what to do next. What can I do to scrub this and start from scratch? I've been happily using GBPVR for a couple of years now, but this whole Zap2It -> SchedulesDirect thing has my settings completely fouled.

Once more, into the fray!

Daniel

[sub]

Wondering...
...Is there a thread specifically for SchedulesDirect issues?

What I'm encountering is thus:
Your EPG source does not appear to be configured correctly. Please check the EPG Source Settings and try again.
System.Net.WebException: The remote name could not be resolved: 'webservices.prod.schedulesdirect.tmsdatadirect.com'...

You'd get this error if you havnt applied the SchedulesDirect patch from the sticky 'v1.0.16 survival guide' thread: http://forums.gbpvr.com/showpost.php?p=2...ostcount=7

[chili2rock]

Sub,
I noticed that with the new version about half of the programs that I record do not display the proper record time in the OSD. The programs that I have recorded are an hour in length, but when I use PVRX2 to view the program the record time shows anywhere between 20 and 30 minutes. Even though the record time shows as too short, the file size is normal for an hour long program. This seems to play havoc with the FF/REW feature when as it skips way forward or back in the program, not the 60/30sec as normal. I don't recall having this issue in previous versions of GBPVR. Not sure if others are experiencing the same issue or not.

[sub]

Sub,
I noticed that with the new version about half of the programs that I record do not display the proper record time in the OSD. The programs that I have recorded are an hour in length, but when I use PVRX2 to view the program the record time shows anywhere between 20 and 30 minutes. Even though the record time shows as too short, the file size is normal for an hour long program. This seems to play havoc with the FF/REW feature when as it skips way forward or back in the program, not the 60/30sec as normal. I don't recall having this issue in previous versions of GBPVR. Not sure if others are experiencing the same issue or not.

I'm guessing you own a PVR150 capture card, and you're just started seeing the PVR150 timestamp problem, ie just bad luck that it appears to have started after the upgrade.

The fix can be found here: http://forums.nextpvr.com/showthread.php?t=14006