V7 to V9 Upgrade Fail - Help Needed

[Fuzzy]

The UI files also need to be updated.

[Taddeusz]

Originally Posted by Fuzzy

The UI files also need to be updated.

Oh, yes, brain not quite working at 100% this morning. More specifically the SageTV7 folder in STVs should be replaced.

[NetworkGuy]

Originally Posted by Taddeusz

Bare minimum you just need to replace the jar file and add the environment variable for your SageTV key. Upgrading the exe's is not strictly necessary but the key will still be required if you don't. Shouldn't be a problem with an existing installation. The only other thing to pay attention to is to make sure the only Lucene jar file you have in JARs is lucene-core-3.6.0.jar.

Mine is version lucene-core-3.0.1.jar. How do you get the newer version?

[Taddeusz]

Originally Posted by NetworkGuy

Mine is version lucene-core-3.0.1.jar. How do you get the newer version?

Looks like you can download it here: https://github.com/google/sagetv/tre...d_party/Lucene

[jusjoken]

Just keep in mind there ARE other files that have changed under v9 other than the SageTV7 STV, sage.jar and the lucene jar. It may will work but no guarantee now that developers have made other changes.

k

[mwittl]

So just for grins, I used Dependency Walker on the V7 and V9 versions of SageTVDX93D.dll and then saved the exported functions out as text files. I then ran a file diff on the two versions. The files are too big to upload here, but there appears to be huge blocks of differences in the versions. Someone who knows what they are doing should have a look at this to see what is going on with the V9 builds vs V7.

[Monedeath]

Originally Posted by jusjoken

Just keep in mind there ARE other files that have changed under v9 other than the SageTV7 STV, sage.jar and the lucene jar. It may will work but no guarantee now that developers have made other changes.

I think most of those changes were largely around EnterNoEscape and SageDCT/network tuner tie-ins and/or efforts just to get the thing to compile paired with removal of unused code(which may have mis-identified?). So as long as you don't rely on SageDCT, you're probably safe enough.

Of course, I haven't tested that. So I'm not sure at this time. If I'm ambitious I might have some answers in about 2 weeks. Haven't updated my SageTV V9 server in about a year. As I don't use SageDCT at this time, and nothing that I'm aware of since then has really been a "must have" or really "want to have" item for me right now. So basically one of those "If it ain't broke..." situations for me.

[mwittl]

So, I never was able to get V9 to work either as an upgrade to my V7 or as a standalone install on my main HTPC. It would try to start up but crap out with the messages I posted earlier in this thread. Due to problems I started to experience last week with the V7 Schedules Direct plugin, I decided to come back to this and upgraded my V7 with V9. I was hopeful it might work since this machine was recently updated with the Windows 10 Creator's update. Long story short...same problem. I replaced the V9 SageTVDX93D.dll with the V7 version of this file and BAM...it works.

My question is, what problems have I opened myself up to by doing this?

[Narflex]

Originally Posted by mwittl

So, I never was able to get V9 to work either as an upgrade to my V7 or as a standalone install on my main HTPC. It would try to start up but crap out with the messages I posted earlier in this thread. Due to problems I started to experience last week with the V7 Schedules Direct plugin, I decided to come back to this and upgraded my V7 with V9. I was hopeful it might work since this machine was recently updated with the Windows 10 Creator's update. Long story short...same problem. I replaced the V9 SageTVDX93D.dll with the V7 version of this file and BAM...it works.

My question is, what problems have I opened myself up to by doing this?

I can't think of any problems that would create since the code is identical between V7 and V9 for that library, it's just built differently.