SageTVDX93D.dll: Can't find dependent libraries

[jusjoken]

I am setting up a test VM for SageTV 9 and have sage running now (followed the windows install process outlined in the FAQ).

SageTV server runs and displays a window that only contains a BLACK/BLANK display.

The repeating error in the sagetv log is as follows.....

java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\SageTV\SageTV\SageTVDX93D.dll: Can't find dependent libraries

Can anyone suggest what I may be missing in my setup to get past this error ?

Notes: my VM is a Server 2012 R2 OS. It is not the same VM that I built the Windows EXE's or the Sage.jar.

Thanks
k

[jusjoken]

I copied the v7 "SageTVDX93D.dll" file to my sagetv folder and now it works. Obviously the issue is in my build of that file under VS2015 so I will have to check there as to what is missing.

k

[JustFred]

Yeah, it seems there's something funky about some of the native-code files built from open source. They build OK, but don't run correctly on **some** of my systems. SageTVDX93D.dll is a good example:
v7's file size was 688 KB; v9's size is only 332 KB. It was 132 KB when built by vs2005 (before the migration to vs2015). Seems like something is missing.

Running dumpbin on each of the 3 vintages of .dll's is interesting. Same number of exported functions, but the imported functions differ. Dramatically different sizes for the .data, .rdata and .text segments.

Not sure where to go from here.

[JustFred]

Apparently Microsoft has changed the DirectX runtime libraries since the Sage7 days. Try downloading & installing the DirectX End-User Runtimes (June 2010) at: http://www.microsoft.com/en-us/downl...n.aspx?id=8109
You should then be able to use the v9 SageTVDX93D.dll. Doing so resolved that issue in my failure case.

Pls report back with your results.

Unfortunately, it doesn't solve my other crash during channel-scan with non-network tuner on clear QAM.

[jusjoken]

This resolved it for me as well. I downloaded that file, ran it, extracted to c:\temp and then ran DXSETUP.EXE from c:\temp. I then put my locally built dll back and sage ran fine without issue.

Thanks
k

[JustFred]

Thanks for the feedback. I'll update the VS2015 Build Env thread with this info.