Setting "EPG Source" to "Schedules Direct" causes an "Unhandled exception".

[johnsonx42]

you can use MC2XML or XMLTV to download your Schedules Direct data into an XMLTV file and just re-map your channels to that file; no need to downgrade. then you just need an updateepg.bat in the scripts directory which NRecord will run each night before reading the XMLTV file. For MC2XML it would simply be:

Code:

cd \path-to-mc2xml
mc2xml

(the .dat file created when you first run MC2XML will take care of the parameters and login info)

[Braklet]

So something is clearly wrong with XP on the media computer. I will start by updating .NET

Unfortunately, I now have to go out on location for a few weeks, so I won't be able to wrestle with the problem until after Thanksgiving. I will be reverting back to 3.2.9 in the meantime, before my wife kills me (She does not yet know that I failed to record "Dancing with the Stars" on Monday - Please don't tell her).

Man, I know about spousal acceptance factor. Why do you think I'm still on v3.1.1? It's easier to sit and spin rather than tackle an upgrade...

Anyway, I think I will give Martin's test shim a go on my XP based HTPC and see where I am, then decide how to proceed with the NPVR upgrade. I really want some of the great features sub added to this last version (thanks all!).

[Braklet]

Anyway, I think I will give Martin's test shim a go on my XP based HTPC and see where I am, then decide how to proceed with the NPVR upgrade.

Looks like my HTPC succeeds connecting to SD; I got the same results as MarkHotchkiss' laptop. TLS is fine on my box.

I'll try an upgrade early next week.

[SFX Group]

Hi

Thought i would add, ive had a problem with Schedules Direct for a while (Un-Handled Exception), i dont use the PVR much (it is the backend to XBMC however no card at the moment).

But i had the large box with a RED X in it, the updated DLL here has fixed that (Windows XP 64bit here, no money to upgrade a non-broken server).

[djpup]

I had what I think is the same problem you've been struggling with. I'm running Windows 7 Pro SP1. If I did:

Settings
Channels
Click on a channel using Schedules Direct to select it
Click on Details button

I got an error message and a red X in the Lineup box.

I finally got that to go away by a combination of suggestions from this thread.

I updated NShared.dll
MD5: 66e771addb7adf961d377fab22045bec

I updated NextPVR.exe
MD5: aac7acb32baa0fd30d0502eb6fe291e1

Those didn't get rid of the problem. Finally, I went back to an Aero theme.

Right-click on a blank spot on the Windows desktop
Personalize
Select one of the Aero themes

That got rid of the red X, so I can continue to work on resolving some other issues I'm having due to Time Warner Cable (Los Angeles) having changed over to a completely encrypted digital system that requires use of a DTA (I have the lowest level of TWC service), so all my channels now come out of the DTA as analog channel 3 signals. I'm working on getting a Hauppauge IR Blaster to change the DTA channels and to reconfigure my channel selections in NPVR to work with the new setup.

I really dislike the Aero themes, so I hope that once I get everything running OK I can go back to a non-Aero theme.

[jim08127]

I had some problems figuring out how to set the SchedulesDirect lineup, I assumed incorrectly that when a lineup was displayed in the drop down control that this was my lineup defined on my SD account. Then I would try to use it, I would get some kind of string exception. Then it was not obvious how to reset and try again, I see in this thread that this can be done in the config.xml.

So I never saw the red x problem. But I do get unhandled exceptions even after I got the lineup set correctly, continuing allowed it all to work though.