So, my nPVR on WinXP Pro x64 stopped getting lineups after I upgraded to nPVR 3.8.3 but it took a while for me to realize this failure. I only noticed when my pending recordings only showed two for last night and none beyond.
The nPVR Settings>Channels would fail now setting up the EPG. I would go to a channel, select SchedulesDirect as the source, then going to the lineup button I'd quickly get a box saying I couldn't connect to SchedulesDirect and to try again later. I've been told this has to do with SchedulesDirect moving to load balancing their servers and WinXP not having suitable encryption. I was disturbed that the nPVR wouldn't get me the drop down box showing login username and password.
I went into \App Data\nPVR and renamed the directory \nPVR.old.2016.11.09 and did the same in Program Files (x86) (hoping that if I could get it working I could find the file containing the 130+ recurring programs list and move it over). Then I installed nPVR 3.2.9, scanned devices and got my HDHR3 tuners channels. Now with the Settings>Channels populated, I tried mapping and this time when I input SchedulesDirect as source I got a login user name and password box with a Download button. Hooray I thought. I mashed the Download button, a 2 or 3 second hourglass icon appeared, but no response from SchedulesDirect. Lineup and Mapping dropdown boxes stayed blank with no choices.
But I have no difficulty logging into http://www.schedulesdirect.org on WinXP. I have an entry for the legacy SD-DD (XML) service, which historically has been providing the information to nPVR, and when I go to the report lineups problem I see that there are two listings, the SD-DD (XML) lineup specification described as CableDigital and also a lineup described as SD-JSON.
It seems to me nPVR is going to the SD-JSON login and download rather than the SD-DD (XML) it used in the past. I had no idea what JSON is and just did a Google search and got this:
JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999.
Now I know my WinXP Pro x64 started failing java upgrades more than a year, perhaps a few years ago. So, I'm guessing now that SchedulesDirect upgraded its java and it now causes nPVR to fail login to get lineups.
It was suggested I use xmltv.exe to get lineups from schedulesdirect but I don't see how that will work. If nPVR on XP can't login then how can xmltv.exe on XP login? Or is xmltv getting its listings elsewhere?
Is there some java workaround exploit that I can use to get nPVR on WinXP to login? I know there are different flavors of java. Suggestions? Thanks.
soyrunner
Okay, I see here (https://blogs.oracle.com/henrik/entry/th...of_java_on) the java installer has been fixed to allow installation on XP. Trying it now.... No joy although I now have Java8 on XP. Will try later versions of nPVR.... Nope, nPVR 3.6.6 fails to bring down the login dialog for schedulesdirect when I mash the lineup button.
The advantage nPVR with HDHomeRun3 gives me over my Tivo Premier XL4 is that if I record programs from 10pm to 11pm, my HDHR3 being on a second NIC of the XP machine (Hero Maximus VI motheboard) has those late recordings right there to start processing with MCEBuddy at say 11:05PM. MCEBuddy runs all night and usually finishes before I get up. If I can't use my HDHR3, because nPVR can't get lineups, any recording made between 10pm and 11pm must be transferred to the XP machine and that typically takes 20 minutes or so per hour program and for best MCEBuddy commercial removal the transfers must be completed before MCEBuddy start. Plus with both the 4 Tivo tuners and the 3 HDHR3 tuners I can get up to 7 programs. I have Win7 on an older machine but nPVR on that can't access the HDHR3 tuners on the unique subnet from that other machine and so without access to tuners there's no device population and no scanned channel listings to download lineups. The unique subnet for HDHR3 on the XP machines is for best recordings.
The nPVR Settings>Channels would fail now setting up the EPG. I would go to a channel, select SchedulesDirect as the source, then going to the lineup button I'd quickly get a box saying I couldn't connect to SchedulesDirect and to try again later. I've been told this has to do with SchedulesDirect moving to load balancing their servers and WinXP not having suitable encryption. I was disturbed that the nPVR wouldn't get me the drop down box showing login username and password.
I went into \App Data\nPVR and renamed the directory \nPVR.old.2016.11.09 and did the same in Program Files (x86) (hoping that if I could get it working I could find the file containing the 130+ recurring programs list and move it over). Then I installed nPVR 3.2.9, scanned devices and got my HDHR3 tuners channels. Now with the Settings>Channels populated, I tried mapping and this time when I input SchedulesDirect as source I got a login user name and password box with a Download button. Hooray I thought. I mashed the Download button, a 2 or 3 second hourglass icon appeared, but no response from SchedulesDirect. Lineup and Mapping dropdown boxes stayed blank with no choices.
But I have no difficulty logging into http://www.schedulesdirect.org on WinXP. I have an entry for the legacy SD-DD (XML) service, which historically has been providing the information to nPVR, and when I go to the report lineups problem I see that there are two listings, the SD-DD (XML) lineup specification described as CableDigital and also a lineup described as SD-JSON.
It seems to me nPVR is going to the SD-JSON login and download rather than the SD-DD (XML) it used in the past. I had no idea what JSON is and just did a Google search and got this:
JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999.
Now I know my WinXP Pro x64 started failing java upgrades more than a year, perhaps a few years ago. So, I'm guessing now that SchedulesDirect upgraded its java and it now causes nPVR to fail login to get lineups.
It was suggested I use xmltv.exe to get lineups from schedulesdirect but I don't see how that will work. If nPVR on XP can't login then how can xmltv.exe on XP login? Or is xmltv getting its listings elsewhere?
Is there some java workaround exploit that I can use to get nPVR on WinXP to login? I know there are different flavors of java. Suggestions? Thanks.
soyrunner
Okay, I see here (https://blogs.oracle.com/henrik/entry/th...of_java_on) the java installer has been fixed to allow installation on XP. Trying it now.... No joy although I now have Java8 on XP. Will try later versions of nPVR.... Nope, nPVR 3.6.6 fails to bring down the login dialog for schedulesdirect when I mash the lineup button.
The advantage nPVR with HDHomeRun3 gives me over my Tivo Premier XL4 is that if I record programs from 10pm to 11pm, my HDHR3 being on a second NIC of the XP machine (Hero Maximus VI motheboard) has those late recordings right there to start processing with MCEBuddy at say 11:05PM. MCEBuddy runs all night and usually finishes before I get up. If I can't use my HDHR3, because nPVR can't get lineups, any recording made between 10pm and 11pm must be transferred to the XP machine and that typically takes 20 minutes or so per hour program and for best MCEBuddy commercial removal the transfers must be completed before MCEBuddy start. Plus with both the 4 Tivo tuners and the 3 HDHR3 tuners I can get up to 7 programs. I have Win7 on an older machine but nPVR on that can't access the HDHR3 tuners on the unique subnet from that other machine and so without access to tuners there's no device population and no scanned channel listings to download lineups. The unique subnet for HDHR3 on the XP machines is for best recordings.